|
: 9 : 9 : 0 |
If you start working with an existing Domino Web Database, smart people who have worked on it before you, tend to have used existing widgets. Those often consist of some client code, a css-file and some javaScript files. The newer they are, the more they tend to use javaScript libraries as prototype, script.aculo.us or/and jQuery.
I mean stuff like www.dynarch.com/projects/calendar/, eight.nl/files/leightbox/, fckeditor, tabbed-table solutions, navigation-trees- etc.
As the javaScript and css for those component can't be in one place, they are often spread all over the design elements of the database or even across different databases. Across different databases, if folks try to centralize their css, js-Libraries for different nsfs, which isn't a bad idea. Now it can be really time-consuming to find all those pieces. It would be great, if this would be documented. Now documentation is great, but has one bad problem: Anybody likes to read a concise documentation, but it can be really hard to write and update those in a consistent and concise fashion.
It would be cool to have kind of a Gui Client (not notes: can be Swing, Eclipse-plugIn, .NET or whatever), which assists the developer in creating such a documentation, for example by offering all the forms, subforms, scriptlibraries, fileresources, javaScript-Libraries, etc. of the databases as dropdown lists and fields to add some explanatory text. The tool might save the information in a xml-format. This xml can be saved in the notes database.
There is no market for such a tool. It could be developed openSource. Am thinking about it, myself.
|