www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.dwt - plan for swt 3.5

reply Frank Benoit <keinfarbton googlemail.com> writes:
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.
Aug 28 2008
next sibling parent Jesse Phillips <jessekphillips gmail.com> writes:
On Fri, 29 Aug 2008 04:37:34 +0200, 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.


hmm, lots of things for Mac, I would guess the browser stuff wouldn't get 
into DWT :)
Aug 28 2008
prev sibling parent reply bobef <bobef nosmap-abv.bg> writes:
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.

P.S. I love DWT and respect your hard work on it, but this way of doing GUI is
dying. This is just MHO, of course.
Sep 02 2008
next sibling parent "Chris R. Miller" <lordSaurontheGreat gmail.com> writes:
bobef wrote:

 Frank Benoit Wrote:
=20

 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.


=20
 Few quotes from this page as well as eclipse 4 plan page:
=20
 "Investigate performance improvements on all platforms. "
=20
 "Investigate SWT in a Browser "
=20
 "    *  Declarative UI=20
=20
     * CSS stying=20
=20
     * Animation and Effects API=20
 "
=20
 "'e4' is the incubator code name for the next major version of the Ecli=


pse platform, 4.0. Topics being investigated include declarative UIs (CSS=
, etc.), scripting (Javascript and others), flexible resource models, plu=
gins implemented in other languages, and DOM driven RESTful architectures=
=2E "

=20
 I don't why these plans reminds me of what I said once :)
=20
 http://www.digitalmars.com/webnews/newsgroups.php?art_group=3Ddigitalma=


rs.D.announce&article_id=3D11189

=20
 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.
Sep 02 2008
prev sibling parent reply Frank Benoit <keinfarbton googlemail.com> writes:
bobef schrieb:

 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.
 
 P.S. I love DWT and respect your hard work on it, but this way of
 doing GUI is dying. This is just MHO, of course.


Hm, i don't know if its dying. Perhaps D, as a system programming
language, is also loosing ground in the big game. Managed code seems to
get more and more important.

However, for me, i see D and DWT as important :)

Bobef, once you wanted to port the HtmlLayout/Sciter to DWT. Are there news?
Sep 02 2008
parent reply bobef <bobef nosmap-abv.bg> writes:
Frank Benoit Wrote:


 bobef schrieb:

 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.
 
 P.S. I love DWT and respect your hard work on it, but this way of
 doing GUI is dying. This is just MHO, of course.


 
 Hm, i don't know if its dying. Perhaps D, as a system programming
 language, is also loosing ground in the big game. Managed code seems to
 get more and more important.
 
 However, for me, i see D and DWT as important :)
 


Me too. D is important because other system languages suck (compared to D :)
and DWT is important for D, because it lacks good GUI otherwise.


 Bobef, once you wanted to port the HtmlLayout/Sciter to DWT. Are there news?


I don't know what you mean by porting it to DWT. I used it inside DWT with
mixed success. It is usable inside DWT but I did't make enough effort because I
was doing all my GUI work with HTMLayout and DWT is too heavy just to create a
parent window for HTMLayout. Now I am doing something else - something like XUL
using DWT and TiScript (the scripting engine of Sciter), but I don't have much
time so it is going slowly. Otherwise it is working very well with almost
automatic binding of DWT to TiScript. I don't know if I will be able to finish
it but I will share it anyway when it becomes mature (or I'm totally unable to
continue).

Regards
Sep 02 2008
parent BLS <nanali nospam-wanadoo.fr> writes:
bobef schrieb:

 Frank Benoit Wrote:
 

 bobef schrieb:

 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.

 P.S. I love DWT and respect your hard work on it, but this way of
 doing GUI is dying. This is just MHO, of course.


 Hm, i don't know if its dying. Perhaps D, as a system programming
 language, is also loosing ground in the big game. Managed code seems to
 get more and more important.

 However, for me, i see D and DWT as important :)


 
 Me too. D is important because other system languages suck (compared to D :)
and DWT is important for D, because it lacks good GUI otherwise.
 

 Bobef, once you wanted to port the HtmlLayout/Sciter to DWT. Are there news?


 
 I don't know what you mean by porting it to DWT. I used it inside DWT with
mixed success. It is usable inside DWT but I did't make enough effort because I
was doing all my GUI work with HTMLayout and DWT is too heavy just to create a
parent window for HTMLayout. Now I am doing something else - something like XUL
using DWT and TiScript (the scripting engine of Sciter), but I don't have much
time so it is going slowly. Otherwise it is working very well with almost
automatic binding of DWT to TiScript. I don't know if I will be able to finish
it but I will share it anyway when it becomes mature (or I'm totally unable to
continue).
 
 Regards


Porting HtmlLayout ...  What about Harmonia ? Is this project still alive ?
bjoern
Sep 03 2008