Fired up the trusty ol' Linux Laptop January 24, 2007
1) Get them talking.
---This involves having objects in JS that correspond to all my objects in Java. Also, a communication protocol, through XML, including updates, deletes, gets, and custom methods.
2) Automate it.
---This involves wrapping each thing in JS functions, like "update(myObj, callback);" which will generate all the XML and make the call, calling the callback function when it returns. Callback will have to have a few parameters, like error message, if it succeeded, etc.
3) Develop custom controls in JS / HTML (Dynamic HTML) for common types (labels, files, to be determined).
There are a few problems with this method that will hopefully be addressed...
1) Security: People who know my XML scheme and the place that accepts it could just write something that posts to the method with the right format of XML and do disastrous things. I have an idea for this, and it will be done before any site that uses this goes up.
2) Search engines won't see it: With everything being dynamic, there's no content on the page when a search engine browses to the site. There's some placeholder html where everything will go, but no content. Unless I have the atom feeds or some meta data in the html.
3) State saving: I will need a system for generating query string parameters based on the values on the page, and also, when someone goes to that page with those values in the query string, it'll load the page how they remember it. This might be tough, or it could be easy.
I think that's about it. Wish me luck, it should be done before Web 3.0 comes out :D