Notice that there is another proposal for a subversion client at
http://www.eclipse.org/proposals/subversive/.
By making the necessary changes to the core ArgoUML code we will risk to
be looking at an ArgoEVersive implementation based on the ArgoUML
project and not on the ArgoUML part of the ArgoEclipse project. ;-) I
think this would be good i.e. not the ArgoEVersive but the fact that new
things could be build on the code from the ArgoUML project and not from
the code in the ArgoEclipse project.
/Linus
> -----Original Message-----
> From: Bogdan Ciprian Pistol [mailto:[EMAIL PROTECTED]
> Sent: den 31 augusti 2006 20:34
> To: [email protected]
> Subject: Re: About the future of ArgoUML and ArgoEclipse
>
> I misspeled something, sorry about this:
>
> "About the headless absolute requirement, I agree it isn't an absolute
> requirement, but it would be nice to have it, so it is on our To Do."
>
> Also I've looked at Eclipse's plugins, at Subclipse and at
> ArgoEclipse. I consider Subclipse a great plugin, they made a proposal
> to Eclipse to be included in the future releases.
> (http://www.eclipse.org/proposals/svn/)
>
> Bogdan,
>
> On 8/31/06, Bogdan Ciprian Pistol <[EMAIL PROTECTED]> wrote:
> > Hello all,
> >
> > I would like to write a few lines to tell you my opinion about the
> > proposals from Linus.
> >
> > Linus suggested that the ArgoEclipse project be merged with ArgoUML,
> > the ArgoEclipse downloads be relocated to the argouml-downloads
site,
> > ArgoEclipse is an alternate distribution format of ArgoUML,
> > ArgoEclipse+ArgoUML should be called ArgoUML, it is ArgoUML from the
> > Eclipse point of view, in consequence the perspective name should be
> > ArgoUML not ArgoEclipse, the Show View group name should be ArgoUML
> > not ArgoEclipse, the name of the update site on the web page should
be
> > ArgoUML not ArgoEclipse, this will make ArgoUML be the market name
> > and ArgoEclipse is the project within ArgoUML that enables ArgoUML
> > from within Eclipse, a headless build is not an absolute
requirement.
> >
> > My opinion is this: The ArgoEclipse project shouldn't be merged with
> > ArgoUML. Take the example of Subclipse, Subclipse is not merged with
> > SVN, they are distinct. ArgoUML, in my opinion, should do exactly
the
> > reverse, try to be a core project with just functionality, without
> > GUI, it shouldn't rely upon Swing or SWT (as a plugin) or anything
> > else, it should provide just the business logic for other GUI parts.
> > This will allow the developers to focus on specifics, if we mess all
> > of them together then it will become even harder to try to adapt
> > ArgoUML for something else (other GUI maybe). If we want both
Eclipse
> > plugin and Swing application then we should have distinct projects.
> > ArgoUML shouldn't have anything to do (as a project because the
> > developers could interact or even contribute to all the projects)
with
> > the Eclipse plugin or Swing application, it should have a stable,
> > strong API, so that every GUI project can use easily the API. So if
I
> > think that ArgoEclipse should be a separate, should be one of the
GUIs
> > of ArgoUML. If this would happen then ArgoUML will become more
> > popular, because it will allow other interested developers to build
> > ArgoUML GUIs for their IDE or applications.
> >
> > The downloads: ArgoUML should have links to ArgoEclipse download
site,
> > because of the decentralization. It doesn't matter a lot where is
> > located the plugin, but to be more decentralized, and I think is
good
> > to make responsible a specific GUI project about it's downloads. If
> > you download Subclipse you don't go to http://subversion.tigris.org,
> > you go to http://subclipse.tigris.org.
> >
> > ArgoEclipse is an alternate distribution format of ArgoUML? I
> > thinkArgoEclipse is ArgoUML+a GUI part.
> >
> > ArgoEclipse+ArgoUML should be called ArgoUML? Depends on what
happens,
> > if we merge ArgoUML with this plugin then it should be called
ArgoUML.
> > This will mean that ArgoUML is everything: Swing GUI, Eclipse
plugin,
> > and ArgoUML core. If we will not merge the projects then obviously
we
> > need a different name, ArgoEclipse sounds good.
> >
> > It is ArgoUML from the Eclipse point of view, in consequence the
> > perspective name should be ArgoUML not ArgoEclipse, the Show View
> > group name should be ArgoUML not ArgoEclipse?
> > I agree with Linus, this plugin definitely is ArgoUML with a
different
> > GUI, the components from it should be renamed. When I first named
> > them, I chose very quickly some names that were in my head, also you
> > could observe the inconsistency (because I chose all the names
> > quickly): some components are called ArgoUML (in the New Wizard the
> > ArgoUML file in the ArgoUML group, in Export Wizard the ArgoUML
> > group). Also Subclipse is just the plugin's name, it uses SVN
> > everywhere.
> >
> > The name of the update site on the web page should be ArgoUML not
> > ArgoEclipse? When you go on the update site what are you uploading,
> > ArgoUML or ArgoUML (project) + Eclipse plugin stuff (project). Only
if
> > the ArgoUML will merge with ArgoEclipse I think it's not confusing
to
> > call the update site ArgoUML.
> >
> > This will make ArgoUML be the market name and ArgoEclipse is the
> > project within ArgoUML that enables ArgoUML from within Eclipse? My
> > opinion is that ArgoEclipse (as a name and plugin) extends the
ArgoUML
> > (name and project/application) outside it's boundaries enabling it
to
> > be used in Eclipse and popularizing it. ArgoEclipse isn't just
ArgoUML
> > renamed (only if we merge the two will be the case), it's ArgoUML
plus
> > something new, something that doesn't hide ArgoUML. Everyone knows
> > that Subclipse is a cloth for SVN, Subclipse doesn't undermine SVN,
> > they exist as two market names and are becoming more and more
popular.
> > Subclipse also by becoming more popular, makes SVN more popular.
> >
> > About the headless absolute requirement, I agree it's an absolute
> > requirement, but it would be nice to have it, so it is on our To Do
> > List.
> >
> > Please feel free to comment on this or disapprove me if you think
I'm
> wrong.
> >
> > Cheers,
> > Bogdan
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
