As someone from a team that will be using use nebula components in the
very near future, I agree with this thinking. We'd like to see "one-stop
shopping" in the form of a zip with everything.
Jack Davis
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David J. Orme
Sent: Thursday, December 21, 2006 10:51 AM
To: [email protected]
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
-----
Message: 1
Date: Thu, 21 Dec 2006 10:17:30 +0200
From: Roland Tepp <[EMAIL PROTECTED]>
Subject: Re: [nebula-dev] Support for Eclipse Data Binding
To: Nebula Dev <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"
I'm not a committer either, but here are my 2 cents:
First - the separation of plug-in per widget is good for Nebula
because
I find that I often want to include just one or the other widget
and
don't want to clutter my classpath with others unless I so
choose to.
Maybe You could have a build scipt that would generate 2
variants of
plug-in(s) - one "jumbo" plug-in that contains the whole soup
and one
that builds separate plug-ins per widget.
So that those who just want the "nebula widgets", would pick the
whole
thing, but those who want to pick and select, can do that as
well...
Tom Schindl kirjutas mulle midagi seesugust:
> Hi,
>
> I'm not a commiter but my feelings are:
>
> - nebbinding +1
> - one plugin / widget -/+0 although I'm more against
>
> What would be when you group widgets:
> - org.eclipse.nebula.table
> - org.eclipse.nebula.text
> - ...
>
> You need some top-level plugins which hold things shared by
different
> plugins. Create a seperate plugin / control would be the same
as if SWT
> would provide a seperate plugin for each of it's widgets.
>
> Tom
>
--
Roland Tepp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: roland.vcf
Type: text/x-vcard
Size: 223 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/nebula-dev/attachments/20061221
/0a23716e/roland.bin
------------------------------
Message: 2
Date: Thu, 21 Dec 2006 09:36:48 -0500
From: Christopher J Gross <[EMAIL PROTECTED]>
Subject: Re: [nebula-dev] Support for Eclipse Data Binding
To: Nebula Dev <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Re: shared things, thats actually something we are trying to
avoid. If
any of the widgets want to be included in SWT, they should try
to have as
little dependencies as possible. So we are trying to avoid
sharing
classes across widgets. So this will actually be a boon to that
effort.
Tom Schindl <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
12/20/2006 02:03 PM
Please respond to
Nebula Dev <[email protected]>
To
Nebula Dev <[email protected]>
cc
Subject
Re: [nebula-dev] Support for Eclipse Data Binding
Hi,
I'm not a commiter but my feelings are:
- nebbinding +1
- one plugin / widget -/+0 although I'm more against
What would be when you group widgets:
- org.eclipse.nebula.table
- org.eclipse.nebula.text
- ...
You need some top-level plugins which hold things shared by
different
plugins. Create a seperate plugin / control would be the same as
if SWT
would provide a seperate plugin for each of it's widgets.
Tom
Chris Gross schrieb:
> Sorry Dave, forgot to respond to this.
>
> Yes I think we should have a separate nebbinding (or maybe
just
> nebula.binding?). This also brings up another thought I've
had. We
> should really separate our widgets into separate plugin
projects. Right
> now, we are just creating separate jars but using the same
project. I
> did this originally so we could ensure that everyone was using
the same
> set of dependencies. But this makes it difficult for
developers to use
> our widget in Eclipse applications. It would make much more
sense have
> each widget constitute its own plugin. This would also mean
that any
> additional facilities for each widget (viewers, databinding
support,etc)
> would also have to be separate plugins. I think this makes
sense.
>
> What does everyone else think?
>
> -Chris
>
> David J. Orme wrote:
>> All,
>>
>> With Eclipse 3.3 comes official API support for Eclipse Data
Binding.
>> I'd like CompositeTable to support this API along with the
JFace
>> Viewer API. We have the NebFace project for JFace viewers,
should we
>> create a NebBinding project for Data Binding support?
>>
>>
>> Regards,
>>
>> Dave Orme
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> nebula-dev mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> nebula-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
https://dev.eclipse.org/mailman/listinfo/nebula-dev/attachments/20061221
/5cc804b0/attachment.html
------------------------------
Message: 3
Date: Thu, 21 Dec 2006 09:43:43 -0500
From: Christopher J Gross <[EMAIL PROTECTED]>
Subject: Re: [nebula-dev] Support for Eclipse Data Binding
To: Nebula Dev <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Skipped content of type multipart/alternative-------------- next
part --------------
A non-text attachment was scrubbed...
Name: roland.vcf
Type: application/octet-stream
Size: 224 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/nebula-dev/attachments/20061221
/53f21367/roland.obj
------------------------------
Message: 4
Date: Thu, 21 Dec 2006 09:52:37 -0500
From: Christopher J Gross <[EMAIL PROTECTED]>
Subject: Re: [nebula-dev] Zest and Nebula
To: Nebula Dev <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Skipped content of type multipart/alternative-------------- next
part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 50414 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/nebula-dev/attachments/20061221
/29f1c083/attachment.gif
------------------------------
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
End of nebula-dev Digest, Vol 9, Issue 17
*****************************************
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
