Hi Andy,
Well that's right, but in my opinion :
- e4 isn't ready yet
- Nebula widgets already have animation support right know (PShelf,
Gallery), and it's better to use the same API for all of them (allows
effect sharing between widgets). Otherwise, I would have used exactly
the same code as SAT directly in the Gallery widget.
- API and code is so simple that we'll be able to remap it to SWT api
when e4 will be released.
- The proposal is a sub-project for Nebula, we're not trying to
replace the upcoming animation support of SWT.
It seems that a draft of the new api is on the e4 demos. I didn't have
time to look at it yet....
Nicolas
Le 9 janv. 09 à 15:38, Andy Maleh a écrit :
I'm very interested in Nicolas' SAT project as I would like to
integrate it with Glimmer, but I thought it was just an experiment
that would be made irrelevant by the next version of SWT since I
heard it has animation support. Is that true?
Andy
On Thu, Jan 8, 2009 at 9:06 PM, Jeremy Dowdall
<[email protected]> wrote:
Hi Everyone,
A bit of background - Nicolas is in the process of getting his
animation toolkit work, SAT, through an IP review, and I'm working
on a proposed sub-project of Nebula called the Custom Widget Toolkit
(CWT) to provide a home for tools (like SAT) that help us build
better widgets.
There has also been some more discussion about the future direction
of the Nebula project itself and how to deal with its scattered
release schedule.
Tom has mentioned adding a subproject, called Incubation, that will
host new / experimental / whatever widgets that are not ready to
join a single unified release schedule. The base Nebula project
will then be comprised only of mature widgets ready to do an
official release with a review and all.
The proposed CWT would be a second subproject:
Nebula
Incubation
CWT
Whether CWT is released in-phase with Nebula or not is something for
thought and discussion.
Nicolas mentioned that he'd like his animation toolkit to be
accessible to more than just Gallery. After looking it over I asked
if he'd be interesting in having it be a part of CWT and he agreed
that it seemed to fit there rather well. Tom then mentioned we
should bring this discussion back to the newsgroup because there are
other people here who may like to contribute. I'm sure he's right
on that - the topic of reusable widget code has been bounced around
here before, and everyone one of the Nebula committers have written
something that we all could have used.
The CWT project proposal: http://www.aspencloud.com/cwt
The initial code came out of the CDateTime rewrite (whose CQ has
just been approved today so code should be hitting CVS this weekend)
but with the addition of things like SAT, that's just a start.
So, as widget developers, what do people think about a project like
this?
What features would you find most helpful?
What features have you been working on that would benefit other
Nebula components?
How do we coordinate it with SWT's development? For instance, Chris
G. mentioned an animation toolkit may be on the table for e4 - has
anyone talked with any SWT dev about this?
What about accessing SWT's internal classes? I've been using several
to get at things SWT probably won't open up - how do we deal with
issues like this?
All questions and comments welcome,
Jeremy
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev
--
//Obtiva - Agility Applied. Software Delivered.
www.obtiva.com
_______________________________________________
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
