On Wed, Nov 12, 2008 at 11:25 AM, ant elder <[EMAIL PROTECTED]> wrote:
> > > On Tue, Nov 11, 2008 at 11:30 PM, Dan Becker <[EMAIL PROTECTED]>wrote: > > <snip> > > > >> Personally I get frustrated when I read or make Tuscany demos or >> presentations and the simple composites must be created with PaintShop or >> some non-tech tool. >> > > This may not be quite what you had in mind but a while back someone created > an SCA diagram stencil for Visio [1], lots of people wont have Visio so > maybe we should create a similar template for OpenOffice Draw and make that > available on the Tuscany website so anyone can use it to create good looking > pictures. (Disclaimer, i know little about OpenOffice Draw but googling it > it does seem to have a stencil facility) > > ...ant > > [1] > http://soastation.blogspot.com/2007/10/sca-diagram-stencil-for-visio.html > > I'm interested in consumability and ease of use. I've tried to extract a few things from my mental list that I think have an impact... For the user Documentation Complete extension documentation Document common tasks +1 Ram's suggestion of document/sample alignment. Also share README content with website Distribution Separation of core from extensions Smaller total number of jars and remove all jar Have an obvious first steps thread in the distro Development Improve policy story Deployment * Clear hosting/deployment options with samples Clarify/Simplify domain story Management Debug Restructure validation itests and index from messages Improve tracing and document how to exploit Runtime model dump For the developer Development * Review SPI, clean and document * Modularity (there has been much discussion already) * Remove IOC nature of runtime construction * Builders structure * Contribution processing structure Build Speed it up * Structure. I'd like to separate core from extensions and disitributed content from content in development * Build/test with the distribution structure Release Need to simplify and make it easily repeatable * marks the things I think have to be at least considered (but not necessarily completed) at trunk bring up. Everything else builds on this. Simon
