Frank W. Zammetti wrote:I do think there is more
that can be done, and I still think the tags are the best way to present it.
Maybe tags that leverage dojo.js?
Today I did some refactoring of the whole thing, and the important point of it all is that a developer will be able to quite easily use Dojo if they wish. Basically, there will be a bunch of "standard" actions that can be performed, the idea being that they may be sufficient 80% of the time and so NO code has to be written by the developer, but you will have the ability to write your own (and also register them with the tags for easy reuse, more on that later!) if you want.
I don't want to say Dojo is the answer period, or that something else is the only answer, including whatever I might dream up, but I want to make sure I allow for flexibility to choose, which I think this does.
Hey, if you'd like to be involved with my efforts, I could certainly use the help in ...
Do you sf.net or wiki type resources?
I'll be doing sf.net... Once I have a complete codebase (not final, just more complete than what I posted previously) I'll see about getting it set up as a project on struts.sf.net. I think that's the right place for it.
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
