plan for swt 3.5

[Chris R. Miller]

bobef wrote:
> Frank Benoit Wrote:
> 
>> FYI, this link was posted on the dev mailing list:
>> http://wiki.eclipse.org/SWT/Plan3.5
>> 3.5 is the next SWT revision and will be released in sommer 2009.
> 
> Few quotes from this page as well as eclipse 4 plan page:
> 
> "Investigate performance improvements on all platforms. "
> 
> "Investigate SWT in a Browser "
> 
> "    *  Declarative UI 
> 
>     * CSS stying 
> 
>     * Animation and Effects API 
> "
> 
> "'e4' is the incubator code name for the next major version of the Eclipse platform, 4.0. Topics being investigated include declarative UIs (CSS, etc.), scripting (Javascript and others), flexible resource models, plugins implemented in other languages, and DOM driven RESTful architectures. "
> 
> I don't why these plans reminds me of what I said once :)
> 
> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D.announce&article_id=11189
> 
> All of the above quotes is already in HTMLayout/Sciter.
> Why am I bringing performance? Because HTMLayout is fast.

So how would that all work?  I'm imagining something akin to
Cocoa/Objective-C, only using a bunch of function tables (almost like
the argparser from Tango*) to simulate the weakly-typed functionality.

* http://dsource.org/projects/tango/wiki/ArgParserExample

I'm pretty much sure that you'd still be able to use the old and "dying"
 method of GUI construction even with the newer system, because the old
ways are more or less how you'd create a new custom widget to use.  I
might not have grasped the whole epiphany, so my little ideas might not
be fully formed compared to others who have committed more thought to
the problem.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-dwt/attachments/20080902/997606ed/attachment.pgp>