Thursday, August 13, 2009

Web tools

A proper web tool reads and writes one or more data formats. Data formats may be purpose built XML, or common interoperating formats, or a hybrid mixture as for example XML with multiple namespaces. The read and write operations are in HTTP.

Web tools are Web APIs. One example is the Atom Publishing Protocol. Another example is the variety of GData applications.

More complex web tools may employ XMPP or Wave Protocol. While not HTTP, they're friends of ours, too.

The syntelos server is a web content repository. Content includes data sets, records, an individual datum like the cell of a spreadsheet, as well as more traditional software code, descriptions, etc..

Of course the first example of using web data from a web repository is using HTML in a browser as a graphical user interface.

The client side and server side software in a tool or tool set present the user and the web at large with the data and user interfaces for automated and manual work on the data.

The syntelos web tools framework has many layers of software as data.

  • The server is programmed in plain java source code which is uploaded, compiled and installed via HTTP, "in the browser". The server side application programming will be able to employ jbxml / jela configuration modeling and programming.

  • Client side application programming will be able to employ the same kind of jbxml / jela modeling and programming via WTKX -- which loads its jbxml / jela applications into reloadable windows like a web browser.

  • And from each of these points, additional layers of modeling and programming are possible as additional jbxml / jela layers.


This is a complete domain for dynamic web development from plain java to model- augmented java. It is web extensible in every dimension. And of course it is secure.

In conventional plain java, a program works in the context of its embedding system and libraries. In model- augmented java, a program is an operation in the scope of an object model or graph configured in XML. The XML model is particularly good for reasoning about a subsystem, and may be represented in an independent graphical user interface.

These frameworks intend to maximize end user productivity by putting all web development into the browser, and then separating various related web user efforts.

For example in UI Design and Content Editing. In a typical wiki, Content Editing is still tied into UI Design as in creating tables, leading to a degradation of productivity. When the formatting of all elements including tables is determined by the application, the productivity of Content Editing is raised by not needing to be concerned with visual design issues.

No comments: