On Wed, Apr 15, 2009 at 6:18 PM,
<nebula-dev-request@xxxxxxxxxxx> wrote:
Send nebula-dev mailing list submissions to
nebula-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev
or, via email, send a message with subject or body 'help' to
nebula-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
nebula-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of nebula-dev digest..."
Today's Topics:
1. Nebula Binaries (Moor Su)
2. On the state and future of Nebula - Part 1 (Tom Schindl)
3. Re: On the state and future of Nebula - Part 1 (Steve Northover)
4. Re: On the state and future of Nebula - Part 1 (Wayne Beaton)
5. Re: Nebula Binaries (Tom Schindl)
6. Re: On the state and future of Nebula - Part 1
(Christopher J Gross)
----------------------------------------------------------------------
Message: 1
Date: Wed, 15 Apr 2009 22:22:14 +0530
From: Moor Su <moorsu@xxxxxxxxx>
Subject: [nebula-dev] Nebula Binaries
To: nebula-dev@xxxxxxxxxxx
Message-ID:
<614b85580904150952x6d243ecevf0e9d07f34c450d3@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I have noticed that the nebula binary downloads are not available on the
eclipse's
nebula home page.
Can I build the jar files from the sources available from
http://www.eclipse.org/nebula/source.php and use it in commercial
applications?.
Or is there any tentative date available for the official release?
-Thank you very much!
MS.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/nebula-dev/attachments/20090415/eedfbee8/attachment.html
------------------------------
Message: 2
Date: Wed, 15 Apr 2009 21:19:00 +0200
From: Tom Schindl <listom@xxxxxxxxxxxxxxx>
Subject: [nebula-dev] On the state and future of Nebula - Part 1
To: nebula-dev@xxxxxxxxxxx
Message-ID: <49E63324.7050708@xxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15
Hi Nebula-Community,
This is a multi series on my view of the state and future of Nebula
which has the target get us out of the nebula.
Part 1: The mission statement and its consequences
--------------------------------------------------
I just replied to a newsgroup thread which asks whether the Nebula-Grid
will get part of SWT one day and hence out of Alpha/Beta state.
While answering the question I some things got to my mind. I would like
to rephrase them here and ask for your comments.
The first thing that I realized is that our main problem in the past was
and still is our mission statement.
"The Nebula project is a source for custom SWT widgets and other UI
components. Nebula is also an incubator for SWT. Some Nebula widgets
will graduate into SWT and therefore into the main Eclipse Platform."
Though this statement may not sound new to you I think many of our
problems stem from it.
a) It makes Nebula look like a playground for big boys and girls for the
outside user
b) It doesn't reflect reality because our controls will never get part
of SWT because the main purpose of SWT is to work with widget
provided by the Native Platforms
c) It makes us Nebula-Developers unconsciously work as we are not
working towards a stable widget (even if it means to hold of new
features until we have a release)
So the first thing we need to fix is our mission statement. What to you
guys think about the following mission statement:
"Nebula is a place where different Eclipse-Projects and Independent
developers collaborate on building Custom SWT widgets and reuseable
UI-Components useable in UI-Applications built using SWT."
Some of the latest additions we added to Nebula (e.g. XViewer) fall
directly into this category of reusable UI-Components. The above is a
first try to cover the new scope and mission of our Nebula-Project!
Naturally I'd like to get response on the statement and your idea of the
mission of Nebula so that we come up with a mission statement within the
next say 2 weeks.
Thanks
Tom
------------------------------
Message: 3
Date: Wed, 15 Apr 2009 17:56:13 -0400
From: Steve Northover <Steve_Northover@xxxxxxxxxx>
Subject: Re: [nebula-dev] On the state and future of Nebula - Part 1
To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
Message-ID:
<OF39EBDAD7.DB8A249B-ON85257599.0077AC38-85257599.00786D3B@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
I think this is a much better statement and fully support changing the
mandate.
When Nebula was started, the hope was to graduate widgets, but the reality
was that this didn't happen. Part of this was due to the native widget
mandate, part was due to lack of time and resources, part due to the goal
of keeping the toolkit small, etc. I think we started out with good
intentions, but the road to hell is paved with good intentions.
Tom Schindl <listom@xxxxxxxxxxxxxxx>
Sent by: nebula-dev-bounces@xxxxxxxxxxx
04/15/2009 03:19 PM
Please respond to
Nebula Dev <nebula-dev@xxxxxxxxxxx>
To
nebula-dev@xxxxxxxxxxx
cc
Subject
[nebula-dev] On the state and future of Nebula - Part 1
Hi Nebula-Community,
This is a multi series on my view of the state and future of Nebula
which has the target get us out of the nebula.
Part 1: The mission statement and its consequences
--------------------------------------------------
I just replied to a newsgroup thread which asks whether the Nebula-Grid
will get part of SWT one day and hence out of Alpha/Beta state.
While answering the question I some things got to my mind. I would like
to rephrase them here and ask for your comments.
The first thing that I realized is that our main problem in the past was
and still is our mission statement.
"The Nebula project is a source for custom SWT widgets and other UI
components. Nebula is also an incubator for SWT. Some Nebula widgets
will graduate into SWT and therefore into the main Eclipse Platform."
Though this statement may not sound new to you I think many of our
problems stem from it.
a) It makes Nebula look like a playground for big boys and girls for the
outside user
b) It doesn't reflect reality because our controls will never get part
of SWT because the main purpose of SWT is to work with widget
provided by the Native Platforms
c) It makes us Nebula-Developers unconsciously work as we are not
working towards a stable widget (even if it means to hold of new
features until we have a release)
So the first thing we need to fix is our mission statement. What to you
guys think about the following mission statement:
"Nebula is a place where different Eclipse-Projects and Independent
developers collaborate on building Custom SWT widgets and reuseable
UI-Components useable in UI-Applications built using SWT."
Some of the latest additions we added to Nebula (e.g. XViewer) fall
directly into this category of reusable UI-Components. The above is a
first try to cover the new scope and mission of our Nebula-Project!
Naturally I'd like to get response on the statement and your idea of the
mission of Nebula so that we come up with a mission statement within the
next say 2 weeks.
Thanks
Tom
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/nebula-dev/attachments/20090415/795f49f1/attachment.html
------------------------------
Message: 4
Date: Wed, 15 Apr 2009 18:56:52 -0400
From: Wayne Beaton <wayne@xxxxxxxxxxx>
Subject: Re: [nebula-dev] On the state and future of Nebula - Part 1
To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
Message-ID: <49E66634.4040607@xxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
+1
I think Nebula can stand on its own.
Wayne
> Tom Schindl <listom@xxxxxxxxxxxxxxx>
> Sent by: nebula-dev-bounces@xxxxxxxxxxx
> 04/15/2009 03:19 PM
> Please respond to
> Nebula Dev <nebula-dev@xxxxxxxxxxx>
>
>
> To
> nebula-dev@xxxxxxxxxxx
> cc
>
> Subject
> [nebula-dev] On the state and future of Nebula - Part 1
>
>
>
>
>
>
> Hi Nebula-Community,
>
> This is a multi series on my view of the state and future of Nebula
> which has the target get us out of the nebula.
>
> Part 1: The mission statement and its consequences
> --------------------------------------------------
> I just replied to a newsgroup thread which asks whether the Nebula-Grid
> will get part of SWT one day and hence out of Alpha/Beta state.
>
> While answering the question I some things got to my mind. I would like
> to rephrase them here and ask for your comments.
>
> The first thing that I realized is that our main problem in the past was
> and still is our mission statement.
>
> "The Nebula project is a source for custom SWT widgets and other UI
> components. Nebula is also an incubator for SWT. Some Nebula widgets
> will graduate into SWT and therefore into the main Eclipse Platform."
>
> Though this statement may not sound new to you I think many of our
> problems stem from it.
>
> a) It makes Nebula look like a playground for big boys and girls for the
> outside user
>
> b) It doesn't reflect reality because our controls will never get part
> of SWT because the main purpose of SWT is to work with widget
> provided by the Native Platforms
>
> c) It makes us Nebula-Developers unconsciously work as we are not
> working towards a stable widget (even if it means to hold of new
> features until we have a release)
>
> So the first thing we need to fix is our mission statement. What to you
> guys think about the following mission statement:
>
> "Nebula is a place where different Eclipse-Projects and Independent
> developers collaborate on building Custom SWT widgets and reuseable
> UI-Components useable in UI-Applications built using SWT."
>
> Some of the latest additions we added to Nebula (e.g. XViewer) fall
> directly into this category of reusable UI-Components. The above is a
> first try to cover the new scope and mission of our Nebula-Project!
>
> Naturally I'd like to get response on the statement and your idea of the
> mission of Nebula so that we come up with a mission statement within the
> next say 2 weeks.
>
> Thanks
>
> Tom
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
------------------------------
Message: 5
Date: Thu, 16 Apr 2009 01:07:06 +0200
From: Tom Schindl <listom@xxxxxxxxxxxxxxx>
Subject: Re: [nebula-dev] Nebula Binaries
To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
Message-ID: <49E6689A.5000209@xxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
The statement does not reflect the current state because we have a build
for some of our widgets since about 2 weeks.
http://www.eclipse.org/nebula/downloads.php
Naturally you can use our code in commercial applications (as long as
you follow the EPL rules) but because we are currently in parallel IP
and don't provide a release there's the *unlikely* possibility that code
parts violate IP.
There's no release date defined yet but it's part of the on going Nebula
restructuring.
Tom
Moor Su schrieb:
> Hi,
>
> I have noticed that the nebula binary downloads are not available on the
> eclipse's
> nebula home page.
>
> Can I build the jar files from the sources available from
> http://www.eclipse.org/nebula/source.php and use it in commercial
> applications?.
>
> Or is there any tentative date available for the official release?
>
> -Thank you very much!
> MS.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
------------------------------
Message: 6
Date: Wed, 15 Apr 2009 19:18:06 -0400
From: Christopher J Gross <chris.gross@xxxxxxxxxx>
Subject: Re: [nebula-dev] On the state and future of Nebula - Part 1
To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
Message-ID:
<OFED25D4CF.E9BF5D58-ON85257599.007F8E59-85257599.008003AE@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
+1 from me as well.
I had hoped at the beginning that Grid could eventually find its way into
SWT but I never got it to the point where I felt it was ready. There were
always things to do (like fix the tree api, really implement SWT.VIRTUAL).
And in the end its probably more appropriate that there's a core toolkit
and an a-la-carte extras project.
I think the new mission statement below is a good one. (Again) Kudos to
you Tom for taking the reigns of Nebula and moving it forward. My time to
focus on Nebula will continue to be minimal and I'm glad to see its in
good hands.
regards,
-Chris
From:
Steve Northover <Steve_Northover@xxxxxxxxxx>
To:
Nebula Dev <nebula-dev@xxxxxxxxxxx>
Date:
04/15/2009 05:55 PM
Subject:
Re: [nebula-dev] On the state and future of Nebula - Part 1
I think this is a much better statement and fully support changing the
mandate.
When Nebula was started, the hope was to graduate widgets, but the reality
was that this didn't happen. Part of this was due to the native widget
mandate, part was due to lack of time and resources, part due to the goal
of keeping the toolkit small, etc. I think we started out with good
intentions, but the road to hell is paved with good intentions.
Tom Schindl <listom@xxxxxxxxxxxxxxx>
Sent by: nebula-dev-bounces@xxxxxxxxxxx
04/15/2009 03:19 PM
Please respond to
Nebula Dev <nebula-dev@xxxxxxxxxxx>
To
nebula-dev@xxxxxxxxxxx
cc
Subject
[nebula-dev] On the state and future of Nebula - Part 1
Hi Nebula-Community,
This is a multi series on my view of the state and future of Nebula
which has the target get us out of the nebula.
Part 1: The mission statement and its consequences
--------------------------------------------------
I just replied to a newsgroup thread which asks whether the Nebula-Grid
will get part of SWT one day and hence out of Alpha/Beta state.
While answering the question I some things got to my mind. I would like
to rephrase them here and ask for your comments.
The first thing that I realized is that our main problem in the past was
and still is our mission statement.
"The Nebula project is a source for custom SWT widgets and other UI
components. Nebula is also an incubator for SWT. Some Nebula widgets
will graduate into SWT and therefore into the main Eclipse Platform."
Though this statement may not sound new to you I think many of our
problems stem from it.
a) It makes Nebula look like a playground for big boys and girls for the
outside user
b) It doesn't reflect reality because our controls will never get part
of SWT because the main purpose of SWT is to work with widget
provided by the Native Platforms
c) It makes us Nebula-Developers unconsciously work as we are not
working towards a stable widget (even if it means to hold of new
features until we have a release)
So the first thing we need to fix is our mission statement. What to you
guys think about the following mission statement:
"Nebula is a place where different Eclipse-Projects and Independent
developers collaborate on building Custom SWT widgets and reuseable
UI-Components useable in UI-Applications built using SWT."
Some of the latest additions we added to Nebula (e.g. XViewer) fall
directly into this category of reusable UI-Components. The above is a
first try to cover the new scope and mission of our Nebula-Project!
Naturally I'd like to get response on the statement and your idea of the
mission of Nebula so that we come up with a mission statement within the
next say 2 weeks.
Thanks
Tom
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/private/nebula-dev/attachments/20090415/916a1e7c/attachment.html
------------------------------
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
End of nebula-dev Digest, Vol 36, Issue 4
*****************************************
