Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Nebula » grid widget part of SWT
grid widget part of SWT [message #63010] Wed, 15 April 2009 15:33 Go to next message
Mircea Luchian is currently offline Mircea LuchianFriend
Messages: 89
Registered: July 2009
Member
Hello,

Is there a plan to put the grid widget part of SWT API? In addition,
when would this widget become modified from ALPHA to BETA and from BETA
to a full release?

Thanks,

Mircea
Re: grid widget part of SWT [message #63022 is a reply to message #63010] Wed, 15 April 2009 18:53 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
*[Disclaimer: This is my current personal view and has not been
discussed with all Nebula committers but this will follow immediately
after I posted the answer to this thread]*

Hi Mircea,

The initial indent of Nebula in the past has been to provide a
playground to explore new ways for widget who might migrate to SWT once
the API is stable.

In reality we had rethink this because none of our widget will ever get
part of the SWT release. Instead I think Nebula is going to provide a
place for reusable UI-Widgets who can't get part of SWT or JFace because
they only hold widgets used by the Eclipse-Platform.

With the latest contributions we added to Nebula we already made this
step reality (e.g. XViewer is a such a component, as well as the
RadioGroup widget) I see nebula more as a central place where
UI-Components get a place which are reusable outside the direct
project-scope they are developed in. So we are one answer to the ever
occurring "BLOAT" discussing when it comes to UI-Components.

This new focus implies to things:
a) instead of relying on the fact that once our widgets are mature we
need to split nebula into 2 projects:
- Nebula-mature
- Nebula-incubation
b) We make 1.0 releases of all widgets part of Nebula-mature

But it gives us new possibilities:
a) We have much more freedome when it comes to minor Java-Version we
need to support => We allow Java 5 API
b) We can define our own release train and time

But it also implies new working areas:
a) We need to work hard to get our widgets build => For most mature
widgets this is already reality (See our new download page)
b) We need to get out of people brains that our widgets are alpha/beta
whereas the reality is that they are extremly stable
c) We need better project management to coordinate the effort going into
the widgets

So what are the next things to happen is that:
- Widgets who get part of Nebula-mature get built
- Widgets who get part of Nebula-mature are IP clean
=> Nebula-mature will not have access to Parellel IP because it is not
an incubation project
- Widgets (Owners) part of Nebula-mature have to decide on releases
dates (You can think of Nebula-mature-Release to something
Galileo-Release for Eclipse but at our project level because all
widgets are still quite independent though they are technically not
Eclipse-Projects on their own)

I hope this answers your question without answering the real question
:-) so maybe I can summerize it:

Yes you will see a stable release of Nebula-Grid in future (though I
can't give you a final date) but it won't be part of SWT but part of the
new Nebula-Mature project.

Tom

M. Luchian schrieb:
> Hello,
>
> Is there a plan to put the grid widget part of SWT API? In addition,
> when would this widget become modified from ALPHA to BETA and from BETA
> to a full release?
>
> Thanks,
>
> Mircea
Re: grid widget part of SWT [message #63024 is a reply to message #63022] Wed, 15 April 2009 19:53 Go to previous messageGo to next message
Mircea Luchian is currently offline Mircea LuchianFriend
Messages: 89
Registered: July 2009
Member
Thank you Tom,

It's good to know that there is a custom widget library that gets mature
with time. Whether part of SWT or Nebula, it does not matter much for a
software engineer using the API. I have been looking in implementing a
grid similar to the one in nebula, however, seeing it exists in the
Alpha stage, I will certainly use it in my product once the API is stable.

Mircea

What matters more is the

Tom Schindl wrote:
> *[Disclaimer: This is my current personal view and has not been
> discussed with all Nebula committers but this will follow immediately
> after I posted the answer to this thread]*
>
> Hi Mircea,
>
> The initial indent of Nebula in the past has been to provide a
> playground to explore new ways for widget who might migrate to SWT once
> the API is stable.
>
> In reality we had rethink this because none of our widget will ever get
> part of the SWT release. Instead I think Nebula is going to provide a
> place for reusable UI-Widgets who can't get part of SWT or JFace because
> they only hold widgets used by the Eclipse-Platform.
>
> With the latest contributions we added to Nebula we already made this
> step reality (e.g. XViewer is a such a component, as well as the
> RadioGroup widget) I see nebula more as a central place where
> UI-Components get a place which are reusable outside the direct
> project-scope they are developed in. So we are one answer to the ever
> occurring "BLOAT" discussing when it comes to UI-Components.
>
> This new focus implies to things:
> a) instead of relying on the fact that once our widgets are mature we
> need to split nebula into 2 projects:
> - Nebula-mature
> - Nebula-incubation
> b) We make 1.0 releases of all widgets part of Nebula-mature
>
> But it gives us new possibilities:
> a) We have much more freedome when it comes to minor Java-Version we
> need to support => We allow Java 5 API
> b) We can define our own release train and time
>
> But it also implies new working areas:
> a) We need to work hard to get our widgets build => For most mature
> widgets this is already reality (See our new download page)
> b) We need to get out of people brains that our widgets are alpha/beta
> whereas the reality is that they are extremly stable
> c) We need better project management to coordinate the effort going into
> the widgets
>
> So what are the next things to happen is that:
> - Widgets who get part of Nebula-mature get built
> - Widgets who get part of Nebula-mature are IP clean
> => Nebula-mature will not have access to Parellel IP because it is not
> an incubation project
> - Widgets (Owners) part of Nebula-mature have to decide on releases
> dates (You can think of Nebula-mature-Release to something
> Galileo-Release for Eclipse but at our project level because all
> widgets are still quite independent though they are technically not
> Eclipse-Projects on their own)
>
> I hope this answers your question without answering the real question
> :-) so maybe I can summerize it:
>
> Yes you will see a stable release of Nebula-Grid in future (though I
> can't give you a final date) but it won't be part of SWT but part of the
> new Nebula-Mature project.
>
> Tom
>
> M. Luchian schrieb:
>
>> Hello,
>>
>> Is there a plan to put the grid widget part of SWT API? In addition,
>> when would this widget become modified from ALPHA to BETA and from BETA
>> to a full release?
>>
>> Thanks,
>>
>> Mircea
>>
Re: grid widget part of SWT [message #63025 is a reply to message #63024] Wed, 15 April 2009 21:24 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
Hi,

I'd say the main API is stable and it hasn't changed since a long time.
We only added new API but didn't break any API contract since quite a
long time.

Tom

M. Luchian schrieb:
> Thank you Tom,
>
> It's good to know that there is a custom widget library that gets mature
> with time. Whether part of SWT or Nebula, it does not matter much for a
> software engineer using the API. I have been looking in implementing a
> grid similar to the one in nebula, however, seeing it exists in the
> Alpha stage, I will certainly use it in my product once the API is stable.
>
> Mircea
>
> What matters more is the
>
> Tom Schindl wrote:
>> *[Disclaimer: This is my current personal view and has not been
>> discussed with all Nebula committers but this will follow immediately
>> after I posted the answer to this thread]*
>>
>> Hi Mircea,
>>
>> The initial indent of Nebula in the past has been to provide a
>> playground to explore new ways for widget who might migrate to SWT once
>> the API is stable.
>>
>> In reality we had rethink this because none of our widget will ever get
>> part of the SWT release. Instead I think Nebula is going to provide a
>> place for reusable UI-Widgets who can't get part of SWT or JFace because
>> they only hold widgets used by the Eclipse-Platform.
>>
>> With the latest contributions we added to Nebula we already made this
>> step reality (e.g. XViewer is a such a component, as well as the
>> RadioGroup widget) I see nebula more as a central place where
>> UI-Components get a place which are reusable outside the direct
>> project-scope they are developed in. So we are one answer to the ever
>> occurring "BLOAT" discussing when it comes to UI-Components.
>>
>> This new focus implies to things:
>> a) instead of relying on the fact that once our widgets are mature we
>> need to split nebula into 2 projects:
>> - Nebula-mature
>> - Nebula-incubation
>> b) We make 1.0 releases of all widgets part of Nebula-mature
>>
>> But it gives us new possibilities:
>> a) We have much more freedome when it comes to minor Java-Version we
>> need to support => We allow Java 5 API
>> b) We can define our own release train and time
>>
>> But it also implies new working areas:
>> a) We need to work hard to get our widgets build => For most mature
>> widgets this is already reality (See our new download page)
>> b) We need to get out of people brains that our widgets are alpha/beta
>> whereas the reality is that they are extremly stable
>> c) We need better project management to coordinate the effort going into
>> the widgets
>>
>> So what are the next things to happen is that:
>> - Widgets who get part of Nebula-mature get built
>> - Widgets who get part of Nebula-mature are IP clean
>> => Nebula-mature will not have access to Parellel IP because it is not
>> an incubation project
>> - Widgets (Owners) part of Nebula-mature have to decide on releases
>> dates (You can think of Nebula-mature-Release to something
>> Galileo-Release for Eclipse but at our project level because all
>> widgets are still quite independent though they are technically not
>> Eclipse-Projects on their own)
>>
>> I hope this answers your question without answering the real question
>> :-) so maybe I can summerize it:
>>
>> Yes you will see a stable release of Nebula-Grid in future (though I
>> can't give you a final date) but it won't be part of SWT but part of the
>> new Nebula-Mature project.
>>
>> Tom
>>
>> M. Luchian schrieb:
>>
>>> Hello,
>>>
>>> Is there a plan to put the grid widget part of SWT API? In addition,
>>> when would this widget become modified from ALPHA to BETA and from BETA
>>> to a full release?
>>>
>>> Thanks,
>>>
>>> Mircea
>>>
Re: grid widget part of SWT [message #594427 is a reply to message #63010] Wed, 15 April 2009 18:53 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
*[Disclaimer: This is my current personal view and has not been
discussed with all Nebula committers but this will follow immediately
after I posted the answer to this thread]*

Hi Mircea,

The initial indent of Nebula in the past has been to provide a
playground to explore new ways for widget who might migrate to SWT once
the API is stable.

In reality we had rethink this because none of our widget will ever get
part of the SWT release. Instead I think Nebula is going to provide a
place for reusable UI-Widgets who can't get part of SWT or JFace because
they only hold widgets used by the Eclipse-Platform.

With the latest contributions we added to Nebula we already made this
step reality (e.g. XViewer is a such a component, as well as the
RadioGroup widget) I see nebula more as a central place where
UI-Components get a place which are reusable outside the direct
project-scope they are developed in. So we are one answer to the ever
occurring "BLOAT" discussing when it comes to UI-Components.

This new focus implies to things:
a) instead of relying on the fact that once our widgets are mature we
need to split nebula into 2 projects:
- Nebula-mature
- Nebula-incubation
b) We make 1.0 releases of all widgets part of Nebula-mature

But it gives us new possibilities:
a) We have much more freedome when it comes to minor Java-Version we
need to support => We allow Java 5 API
b) We can define our own release train and time

But it also implies new working areas:
a) We need to work hard to get our widgets build => For most mature
widgets this is already reality (See our new download page)
b) We need to get out of people brains that our widgets are alpha/beta
whereas the reality is that they are extremly stable
c) We need better project management to coordinate the effort going into
the widgets

So what are the next things to happen is that:
- Widgets who get part of Nebula-mature get built
- Widgets who get part of Nebula-mature are IP clean
=> Nebula-mature will not have access to Parellel IP because it is not
an incubation project
- Widgets (Owners) part of Nebula-mature have to decide on releases
dates (You can think of Nebula-mature-Release to something
Galileo-Release for Eclipse but at our project level because all
widgets are still quite independent though they are technically not
Eclipse-Projects on their own)

I hope this answers your question without answering the real question
:-) so maybe I can summerize it:

Yes you will see a stable release of Nebula-Grid in future (though I
can't give you a final date) but it won't be part of SWT but part of the
new Nebula-Mature project.

Tom

M. Luchian schrieb:
> Hello,
>
> Is there a plan to put the grid widget part of SWT API? In addition,
> when would this widget become modified from ALPHA to BETA and from BETA
> to a full release?
>
> Thanks,
>
> Mircea
Re: grid widget part of SWT [message #594446 is a reply to message #63022] Wed, 15 April 2009 19:53 Go to previous message
Mircea Luchian is currently offline Mircea LuchianFriend
Messages: 89
Registered: July 2009
Member
Thank you Tom,

It's good to know that there is a custom widget library that gets mature
with time. Whether part of SWT or Nebula, it does not matter much for a
software engineer using the API. I have been looking in implementing a
grid similar to the one in nebula, however, seeing it exists in the
Alpha stage, I will certainly use it in my product once the API is stable.

Mircea

What matters more is the

Tom Schindl wrote:
> *[Disclaimer: This is my current personal view and has not been
> discussed with all Nebula committers but this will follow immediately
> after I posted the answer to this thread]*
>
> Hi Mircea,
>
> The initial indent of Nebula in the past has been to provide a
> playground to explore new ways for widget who might migrate to SWT once
> the API is stable.
>
> In reality we had rethink this because none of our widget will ever get
> part of the SWT release. Instead I think Nebula is going to provide a
> place for reusable UI-Widgets who can't get part of SWT or JFace because
> they only hold widgets used by the Eclipse-Platform.
>
> With the latest contributions we added to Nebula we already made this
> step reality (e.g. XViewer is a such a component, as well as the
> RadioGroup widget) I see nebula more as a central place where
> UI-Components get a place which are reusable outside the direct
> project-scope they are developed in. So we are one answer to the ever
> occurring "BLOAT" discussing when it comes to UI-Components.
>
> This new focus implies to things:
> a) instead of relying on the fact that once our widgets are mature we
> need to split nebula into 2 projects:
> - Nebula-mature
> - Nebula-incubation
> b) We make 1.0 releases of all widgets part of Nebula-mature
>
> But it gives us new possibilities:
> a) We have much more freedome when it comes to minor Java-Version we
> need to support => We allow Java 5 API
> b) We can define our own release train and time
>
> But it also implies new working areas:
> a) We need to work hard to get our widgets build => For most mature
> widgets this is already reality (See our new download page)
> b) We need to get out of people brains that our widgets are alpha/beta
> whereas the reality is that they are extremly stable
> c) We need better project management to coordinate the effort going into
> the widgets
>
> So what are the next things to happen is that:
> - Widgets who get part of Nebula-mature get built
> - Widgets who get part of Nebula-mature are IP clean
> => Nebula-mature will not have access to Parellel IP because it is not
> an incubation project
> - Widgets (Owners) part of Nebula-mature have to decide on releases
> dates (You can think of Nebula-mature-Release to something
> Galileo-Release for Eclipse but at our project level because all
> widgets are still quite independent though they are technically not
> Eclipse-Projects on their own)
>
> I hope this answers your question without answering the real question
> :-) so maybe I can summerize it:
>
> Yes you will see a stable release of Nebula-Grid in future (though I
> can't give you a final date) but it won't be part of SWT but part of the
> new Nebula-Mature project.
>
> Tom
>
> M. Luchian schrieb:
>
>> Hello,
>>
>> Is there a plan to put the grid widget part of SWT API? In addition,
>> when would this widget become modified from ALPHA to BETA and from BETA
>> to a full release?
>>
>> Thanks,
>>
>> Mircea
>>
Re: grid widget part of SWT [message #594453 is a reply to message #63024] Wed, 15 April 2009 21:24 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
Hi,

I'd say the main API is stable and it hasn't changed since a long time.
We only added new API but didn't break any API contract since quite a
long time.

Tom

M. Luchian schrieb:
> Thank you Tom,
>
> It's good to know that there is a custom widget library that gets mature
> with time. Whether part of SWT or Nebula, it does not matter much for a
> software engineer using the API. I have been looking in implementing a
> grid similar to the one in nebula, however, seeing it exists in the
> Alpha stage, I will certainly use it in my product once the API is stable.
>
> Mircea
>
> What matters more is the
>
> Tom Schindl wrote:
>> *[Disclaimer: This is my current personal view and has not been
>> discussed with all Nebula committers but this will follow immediately
>> after I posted the answer to this thread]*
>>
>> Hi Mircea,
>>
>> The initial indent of Nebula in the past has been to provide a
>> playground to explore new ways for widget who might migrate to SWT once
>> the API is stable.
>>
>> In reality we had rethink this because none of our widget will ever get
>> part of the SWT release. Instead I think Nebula is going to provide a
>> place for reusable UI-Widgets who can't get part of SWT or JFace because
>> they only hold widgets used by the Eclipse-Platform.
>>
>> With the latest contributions we added to Nebula we already made this
>> step reality (e.g. XViewer is a such a component, as well as the
>> RadioGroup widget) I see nebula more as a central place where
>> UI-Components get a place which are reusable outside the direct
>> project-scope they are developed in. So we are one answer to the ever
>> occurring "BLOAT" discussing when it comes to UI-Components.
>>
>> This new focus implies to things:
>> a) instead of relying on the fact that once our widgets are mature we
>> need to split nebula into 2 projects:
>> - Nebula-mature
>> - Nebula-incubation
>> b) We make 1.0 releases of all widgets part of Nebula-mature
>>
>> But it gives us new possibilities:
>> a) We have much more freedome when it comes to minor Java-Version we
>> need to support => We allow Java 5 API
>> b) We can define our own release train and time
>>
>> But it also implies new working areas:
>> a) We need to work hard to get our widgets build => For most mature
>> widgets this is already reality (See our new download page)
>> b) We need to get out of people brains that our widgets are alpha/beta
>> whereas the reality is that they are extremly stable
>> c) We need better project management to coordinate the effort going into
>> the widgets
>>
>> So what are the next things to happen is that:
>> - Widgets who get part of Nebula-mature get built
>> - Widgets who get part of Nebula-mature are IP clean
>> => Nebula-mature will not have access to Parellel IP because it is not
>> an incubation project
>> - Widgets (Owners) part of Nebula-mature have to decide on releases
>> dates (You can think of Nebula-mature-Release to something
>> Galileo-Release for Eclipse but at our project level because all
>> widgets are still quite independent though they are technically not
>> Eclipse-Projects on their own)
>>
>> I hope this answers your question without answering the real question
>> :-) so maybe I can summerize it:
>>
>> Yes you will see a stable release of Nebula-Grid in future (though I
>> can't give you a final date) but it won't be part of SWT but part of the
>> new Nebula-Mature project.
>>
>> Tom
>>
>> M. Luchian schrieb:
>>
>>> Hello,
>>>
>>> Is there a plan to put the grid widget part of SWT API? In addition,
>>> when would this widget become modified from ALPHA to BETA and from BETA
>>> to a full release?
>>>
>>> Thanks,
>>>
>>> Mircea
>>>
Previous Topic:[Grid, GridViewer][PATCH] rowspan support
Next Topic:CDateTime used as cellEditor
Goto Forum:
  


Current Time: Tue Apr 16 20:00:47 GMT 2024

Powered by FUDForum. Page generated in 0.34908 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top