Hi Sebastian,

I fear maintaining different component sets would be too much work. Of course, anyone who wants to use bleeding edge features can do so by accessing the view.sprite property - which is, as you say:

in dhtml = div
in SWF8 = MovieClip
in SWF9 = sprite

I agree, Flash 10 is leading when it comes to innovation. That said, webkit continues to catch up in a lot of ways, with such recent additions as round rects, drop shadows and 3d transformations.

And, there are some features that DHTML has that we really should support, like pargins, padding and borders - I have a change out that will add this for swf9/10 and DHTML. We're trying hard to strike a balance between adding new features and filling in runtime gaps...

Raju has done an excellent job scouting ahead and prototyping features (like drop shadows) so we can easily fold them into the platform as formalized features. I'd like to see more of that from the community - just quick prototypes showing what they'd like to see added.

As always, thanks for your contributions!

Sebastian Wagner wrote:
hi,

I've added some ... maybe contra-revolutionary ^^ points to the wiki... so don't take that too personal but I think its worth thinking about!

http://wiki.openlaszlo.org/OpenLaszlo_5_community_wishlist


    General

    * Rethink pattern of *Write once, run everywhere*, it seems not to
      be feasible in the future or only with enormous effort. So its
      maybe better and cleaner to have different component sets for each
      Runtime, instead of trying to build ONE component set that then
      compiles into all runtimes (cause the code that produces those
      components has almost more exceptions then it has code that is
      equal among all platforms). So maybe you just make some basic
definitions like:
view in dhtml = div

view in SWF8 = MovieClip

view in SWF9 = sprite

But based on that you can than work in different folders and component sets. Of course that means duplicate code in some areas but on the long run you need a team with 20+ permanent core developers to keep track of all runtimes. And a change ... even minimalistic things, in one runtime does effect automatically all runtimes. And what happens when you add a new runtime now? SVG or Silverlight or ... actually the complexity of even very simple things will be that kind of horrible that its almost a Science to bring a simple Hello World-Text component into all Runtimes.

And I think for some of the CSS or Flash10 features you just find no equivalent into the other runtimes. So the things that those runtimes have in common is getting smaller and smaller ... and you fill your time in fixing those runtime-gaps instead of improving and extending the Platform with new features.


just my two cents ^^
Sebastian

--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
[email protected] <mailto:[email protected]>

--
Regards,
Max Carlson
OpenLaszlo.org

Reply via email to