As a web app developer, what I would love to see for the Moz & FF 2.0 series is an expanded set of capabilities as an application platform. The top few items on my list would include:
SVG
This will allow interactive graphic applications that are just not possible now with primarily text-oriented DHTML.
A better client-side VM.
Like real compiled Javascript 2.0 or perhaps a Python VM. You can do some amazing and surprising things with client-side JS, but as web apps tackle what are now primarily the domain of "fat" installed apps, we're going to need some real client side power. The ability to create and call libraries of routines will prove to be important.
Heavy duty form support, including the ability to create and use form "widgets"
These issues are being addressed in both Ian Hickson's WHAT-WG and W3C's Xforms. Implementations of these in compiled code would be great.
Client-side persistent store
From what I gather, Moz 2.0 will embed the small SQL engine SQLite to store it's configuration data, etc.. How about providing access to this engine for web apps? Think of it as maybe a cookie on some relational algebra radioactive steriods. Imagine being able to download chunks of data from your server-side store and work with them locally. You would effectively have web apps that continue to work when disconnected from the web.
Want to compete with MS's upcoming XAML platform? I believe this list will go a long way toward that.
Slashdot Mirror
putting the insulation inside the tank, or making a double-wall tank, like a thermos?
- SVG
- A better client-side VM.
- Heavy duty form support, including the ability to create and use form "widgets"
- Client-side persistent store
Want to compete with MS's upcoming XAML platform? I believe this list will go a long way toward that.This will allow interactive graphic applications that are just not possible now with primarily text-oriented DHTML.
Like real compiled Javascript 2.0 or perhaps a Python VM. You can do some amazing and surprising things with client-side JS, but as web apps tackle what are now primarily the domain of "fat" installed apps, we're going to need some real client side power. The ability to create and call libraries of routines will prove to be important.
These issues are being addressed in both Ian Hickson's WHAT-WG and W3C's Xforms. Implementations of these in compiled code would be great.
From what I gather, Moz 2.0 will embed the small SQL engine SQLite to store it's configuration data, etc.. How about providing access to this engine for web apps? Think of it as maybe a cookie on some relational algebra radioactive steriods. Imagine being able to download chunks of data from your server-side store and work with them locally. You would effectively have web apps that continue to work when disconnected from the web.