[Tapestry-developer] Exciting new Spindle functionality

[Geoff Longman]

got your attention? I have some ideas for really improving the useablity of the HTML editor in Spindle.   The trigger was that I got 50 or so templates dumped in my lap today. I spend so much time working on spindle that I don't *use* it often enough to build real stuff. Today I need to convert those 50 templates into pages.   to generate interest and input I'm cross posting this as spindle-list audience is small.   If this gets out of hand we can move it to the wiki...   Thinking of creating a view in eclipse that would be tied to the HTML Editor... Component Pallet.   It would contain a list of components something like this:     This is image borrowed from ASP.net's WebMatix product. Imagine it filled with tapestry components.   Each section (above they're HTMLElements, Web Controls, etc) would be as follows:   Section 1   Framework - the framework components   Section would contain the framwork components   Section 2   App name - the appname if the project is an Application Project or Lib name - the lib name if the project is a Library project   Section would contain the components defined in the App   Section 3 - Section n-1 the libraries declared as used libraries in the above section)   Section 4 - Quick Access - a scratch pad for easy access, you'd put frequently used components here (from the above) also, I think that any Components defined in the spec but not yet put into the template would be listed here.   To use, drag a component onto the template. On releasing the mouse button you'd get a popup that asks you insome elegant way..   No selection in Template       insert as "jwcid="name"" at the cursor (if its a tag at drop point)     insert as "<span jwcid="name"/> at the drop point (if its outside a tag)     insert as "<span jwcid = "name"></span> at drop point (if its outside a tag)   If there is a selection but the drop point is outside the selection it works as above,   however, if the drop point is inside the selection surround it         insert as <span jwcid="name"> SELECTED TEXT </span>   if the rules above (outside a tag, or inside a selection) are not met, then drop is disallowed.   The contained component would be automagically created in the spec.   pretty cool eh? I'm thinking this will be the focus for development of Spindle 1.2   Some neat things that would need to be accommodated by Tapestry...   associating an icon, and short name with a component associating an icon and short name with a Library.   There's a million other features that could be added to this view: Add a library to the application/library without going to another editor Rename a contained component  "        "                     " Make the property view work here so you could edit the parameters at the same time (This would be hard to do given the existing framework). there could be a plethora of these little features that would reduced the need to jump back and forth between editors.   Geoff   Geoffrey Longman Intelligent Works Inc.