3 ms·

Its ironic.

by samfisher83 11y ago

Its ironic.

coldtea 11y ago
No, he means a properly done sandbox but native and 2D accelerated platform without the DOM cruft. Not sure why it's so hard, probably because it's in nobody's interests but the users (as every major just wants to promote their own platform and have the web play second fiddle to it).
- zbyte64 11y ago
  So like a canvas element then?
  - coldtea 11y ago
    In the sense that Cocoa or Windows top level window hierarchy is also like a "canvas element". In other words, like a canvas element which has a full, comprehensive, standard UI library with tons of standard, pre-built widgets (not just the meagre web form controls), including a full featured text widget with all the trimmings, plus a free drawing component of its own (for totally custom UIs and controls).
- wtetzner 11y ago
  Doesn't sound so different from Java applets.
  - coldtea 11y ago
    The core concept, maybe. Then again, a top tier BMW doesn't sound so different than an Edsel either. They both have internal combustion engines, 4 wheels, a steering wheel, and they take you from place A to place B in similar speeds (in orders of magnitude). That's because you're focusing on the similarities which don't say anything -- what's important in all cases are the differences. Which in this case are mostly about the implementation. - the UI wouldn't be a part of a page, it would be THE page. - it shouldn't be an over-engineered mess of a GUI toolkit like Swing. - it should offer modern and capable widgets, instead of the bizarro, limited and uncanny value one's that Swing offers (if you don't get into intricate customization of your own). - it should be faster than the web app it replaces -- applets were often slow to load AND slow to run. - it shouldn't be controller by a single company. - it shouldn't be proprietary. - it should, if possible, cater to many programming languages. - it should play natively with the HTTP model, AJAX etc.

3 ms·

Its ironic.

by samfisher83 11y ago

Its ironic.

coldtea 11y ago
No, he means a properly done sandbox but native and 2D accelerated platform without the DOM cruft. Not sure why it's so hard, probably because it's in nobody's interests but the users (as every major just wants to promote their own platform and have the web play second fiddle to it).
- zbyte64 11y ago
  So like a canvas element then?
  - coldtea 11y ago
    In the sense that Cocoa or Windows top level window hierarchy is also like a "canvas element". In other words, like a canvas element which has a full, comprehensive, standard UI library with tons of standard, pre-built widgets (not just the meagre web form controls), including a full featured text widget with all the trimmings, plus a free drawing component of its own (for totally custom UIs and controls).
- wtetzner 11y ago
  Doesn't sound so different from Java applets.
  - coldtea 11y ago
    The core concept, maybe. Then again, a top tier BMW doesn't sound so different than an Edsel either. They both have internal combustion engines, 4 wheels, a steering wheel, and they take you from place A to place B in similar speeds (in orders of magnitude). That's because you're focusing on the similarities which don't say anything -- what's important in all cases are the differences. Which in this case are mostly about the implementation. - the UI wouldn't be a part of a page, it would be THE page. - it shouldn't be an over-engineered mess of a GUI toolkit like Swing. - it should offer modern and capable widgets, instead of the bizarro, limited and uncanny value one's that Swing offers (if you don't get into intricate customization of your own). - it should be faster than the web app it replaces -- applets were often slow to load AND slow to run. - it shouldn't be controller by a single company. - it shouldn't be proprietary. - it should, if possible, cater to many programming languages. - it should play natively with the HTTP model, AJAX etc.