[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [nebula-dev] Re: one plugin per control
|
Are we talking about packaging widgets, or the structure of CVS? Should
these be the same?
I guess I am not officially a committer yet, but I really like 1 zip per
control. I think we could then take a poll of who wants to be in a
release (we have sort of already done this), and these could all be
packaged up as a Nebula release (we can export a bunch of plugins as a
Zip). Then if someone wants to try out all the widgets they can do this.
I'm not sure if we have decided on how to go with JFace style widgets,
that is if a widget is available in two different forms. Is this two
different plugins (one that depends on another) or just 1 and you can
access it in either way? If we go with the second approach then we have:
org.eclipse.nebula.grid
org.eclipse.nebula.ctabletree
org.eclipse.nebula.compositetable
org.eclipse.nebula.pgroup
org.eclipse.nebula.pshelf
org.eclipse.nebula.graph (zest graph)
However this doesn't help if and when we move to SWT, since the JFace
and SWT parts must be separated then. Although I guess if we forced
package conventions within the plugins (SWT and JFace must be in
separate packages and the SWT package must not have eclipse.ui
dependencies this would work).
Cheers,
Ian
David J. Orme wrote:
OK, I think that's two +1s; one from Chris and one from me. Do we
have a third committer on board? What do the rest of you think?
Regards,
Dave Orme
-----
Message: 1
Date: Thu, 21 Dec 2006 11:09:45 -0500
From: Christopher J Gross <chris.gross@xxxxxxxxxx>
Subject: Re: [nebula-dev] Re: nebula-dev Digest, Vol 9, Issue 17
To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
Message-ID:
<OF1541DFC7.B4A15C7E-ON8525724B.00584C2E-8525724B.0058C909@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
I don't have a problem with this. I don't think we should worry about
including a src.zip but I'm board with snippets and javadoc. Most people
don't care about the source. Re javadoc, ideally I'd like to include a
help plugin that added the javadoc to the main Eclipse help.
"David J. Orme" <djo@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: nebula-dev-bounces@xxxxxxxxxxx
12/21/2006 11:51 AM
Please respond to
Nebula Dev <nebula-dev@xxxxxxxxxxx>
To
nebula-dev@xxxxxxxxxxx
cc
Subject
[nebula-dev] Re: nebula-dev Digest, Vol 9, Issue 17
I've been thinking about this and I'm still supportive, but don't want to
lose some of the benefits of how we do things now.
One advantage we have right now is that we provide closer to one-stop
shopping for people who download our controls.
What I mean is that inside the download zip, we all provide a JAR for the
widget itself and a separate JavaDoc directory, all at once. In
CompositeTable, I've extended this idea and made my build script also
include a src.zip and a snippets.zip so that when someone downloads
CompositeTable, they really have *everything* they need to get started
with it. We can get away with this because our controls are really small
downloads to begin with, so throwing all the documentation, source code,
and snippets into the distribution makes sense.
If we were to move to one plugin per control, I would still want the
download file to be a ZIP containing the plugin jar, plus all the
stuff it
currently has (snippets.zip, src.zip, JavaDoc, etc). There is no reason
to make our users download five tiny things in order to use a control.
One
download should be sufficient.
Regards,
Dave Orme
------------------------------------------------------------------------
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
