[rainbow-eiffel-developers] Plan for next RainbowEiffel release

[Brian Y. <bri...@ve...>]

Yes, I branched out wxEiffel from ELJ to RainbowEiffel; ELJ project is now
defunct.
Now wxEiffel becomes a part of RainbowEiffel and we need to maintain it.

Gobo folks are trying to port their libraries to SE 2.1 beta1 -- see
following email:
http://sourceforge.net/mailarchive/forum.php?thread_id=5983612&forum_id=1688
.  According to the email, there are a lot of bugs in SE 2.x and it's better
not to port RainbowEiffel to SE 2.x for now.  I agree with you and we'd
better stick with SE 1.1 until SE 2.x becomes stable and fate of Gobo port
to SE 2.x becomes clear.

Let's prioritize the tasks again.
(1) Port IDE to Linux (Marcos)
(2) Re-architect and redesign the IDE (Brian, Marcos)
(3) Implement configuration/project manager, build manager (Brian)
(4) Implement class/feature browser (Marcos)
(5) Integrate unit-test framework with IDE (Brian)
(6) Implement debugger (Brian)
Let's target to include these in next RainbowEiffel release probably at
beginning of January/2005 -- this may to too ambitious.

What do you think?
If you agree, I will create subprojects/tasks in SourceForge.
We will use SE 1.1 and Gobo 3.3.

-- Brian


> -----Original Message-----
> From: Marcos Macedo [mailto:mar...@gm...]
> Sent: Wednesday, November 17, 2004 7:03 PM
> To: Brian Yan
> Subject: Re: Contributing to RainbowEiffel
>
>
> I was looking at the EiffelZone and, as far as I can read, the
> wxEiffel is now part of the RainbowEiffel project. Is that right?
>
> If so then should I assume that we need to adapt wxEiffel, too?
>
> I really need to try some simple examples of wxEiffel.
>
> I'm looking for test Gobo and SmartEiffel 2.0 to see what is really wrong.
>
>
> On Wed, 17 Nov 2004 19:35:29 -0200, Marcos Macedo
> <mar...@gm...> wrote:
> > Thank you,
> >    I like your ideas and I want to reinforce my will.
> >
> > Let`s do some comments:
> >
> > (1) The case of the Base Library is Important. But Rewrite a Base
> > library just for this project is a huge task. Could we just do the
> > Gobo to SmartEiffel 2.0 evolution. Do you think that there will be
> > many conflitcs in this task? Pehaps we can even avoid a fork by
> > talking to the Godo team.
> >
> > (2) The Number 2 is heavly number 1 dependent. Do you think that this
> > is really our prority order? Pehaps we can do all our refactory work
> > with SmartEiffel 1 and then plan an wevoluttion early. Will we have
> > problems with wxEiffel too?
> >
> > (3) I`m very interested in the Linux Port, since I don`t use WIndows
> > at home and I can`t find any Linux SmartEiffel IDE other then emacs
> > eiffelmode. I could start working on this right now. I just need to
> > try some basic work and  look for it. This will only depend on (1) and
> > (2), but I can work on this without thinking in this problem first.
> >
> > (4) I can help in the re-architect of the project. I can start looking
> > for analise and document the actual architecture to look at where we
> > can improve it. I have special interest in the browser, as I think
> > that Eiffel can be really strong with a refactor browser and this is
> > what I think that is the future of Rainbow IDE. This can add real
> > value to it.
> >
> > I`m interested in both design and development works.
> >
> >
> > Marcos Macedo
> >
> >
> >
> > On Wed, 17 Nov 2004 02:06:02 -0600, Brian Yan
> <bri...@ve...> wrote:
> > > Hi Marcos,
> > >
> > > You're in the project member list now and have access to CVS.
> > >
> > > EiffelBase will not be supported anymore because of its
> licensing issue with
> > > non-standard Eiffel contructs which are used by SmartEiffel
> 2.0 and beyond.
> > > Gobo's support for SmartEiffel 2.x is uncertain and hence the
> Gobo libraries
> > > will not be used anymore.
> > > So there is a need to have a Base library of our own that
> will be used by
> > > other parts of  RainbowEiffel.
> > >
> > > The priorities are as follows:
> > > (1) Base library design and implementation
> > > (2) Port existing IDE code to SE 2.0 (Windows)
> > > (3) Port IDE to Linux
> > > (4) Design and implement new IDE features (configuration
> manager, build
> > > manager, debugger, class/feature browser, DLL support,
> plug-in modules,
> > > etc.).  We may also want to re-architect and redesign the
> IDE.  Currently
> > > the IDE has no clear and good architecture/design yet.
> > >
> > > I will try to come up with more detailed task list later on.
> I hope you can
> > > participate in both design and development works.
> > >
> > > -- Brian
> > >