The link to extension guide pointed to a set of modules and their description. There is yet another extension guide under documentation. This one is a guide for extension developer. It explains how to build an extension. The module mapping information seemed relevant for the extension developer and I moved it to this guide and called the whole thing extension developer guide.
Ant started scripting.impl. This could go to the user doc since this one is more user centric. It talks about how to develop different component implementations (looks like). Venkat, I don't understand your proposal. We already have news information on the front page. We could put the news about .90 there and link to the change/readme files from there. Including the content of the change file on the home page will make it very difficult to read and consume. On 5/26/07, Simon Laws <[EMAIL PROTECTED]> wrote:
Starting to look a lot better. Venkat +1 for info in release right on the front page. Instead of, or as well as, the Release Notes can you include the information from the Changes doc which tells people what is in the release? Also I note that the link to the Extension Guide has gone missing. There were two sets of information on this page 1/ Links to references to all the user configurable elements of the Tuscany Runtime as provided by extensions. How about we reinstate this information as User Reference. As distinct from the User Guide which is a more chatty document 2/ Links to short desctiptions of the intention of each of the other system modules that make up the Tuscany runtime which gives the budding developer a leg up in terms of identifying what the modules are for. Again this is disitinct from the chatty and abstract nature of the Architecture Guide and also Distinct form the process oriented Developer Guide. How about this being called the Developer Reference. Simon
