Hi there, >>> actually, snippets are classified by Tom >>> by languages, by product (writer, calc ...) >>> >>> i think we should keep this classification >> yes we should, i will extend the hierarchical structure to take care >> of that. But of course i will first choose the language and than the >> area. As i already have mentioned in the guidelines it should be >> possible to extend the hierarchy on demand and seems that this is a >> valid request and i simply forgot it. > i have extended the structure to reflect the same sub categories as > before on the snippet page. See for example > http://wiki.services.openoffice.org/wiki/API/Samples/StarBasic Tom's classification allows one to not only choose the module and langauge, but also see in which other languages snippets exist. For those who are able to use more than one language it would be very helpful to be able to easily navigate to another language for the same module.
Also, Tom added the ability to incorporate links to the offiicial IDL documentaiton which is *very* handy! I would like to see that as well: this e.g. allows to get the overall idea/approach to get a specific feature realized in any of the available languages to start out, but be able to get to the OOo documentation. It is many times a real problem to quickly navigate to the interesting IDL definitions. Snippets that have links incorporated allow for a nice starting point to navigate directly to all IDL definitions which are relevant for a certain snippet. Ad syntax-highlighting: Tom uses the powerful "vim" syntax highlighting feature, to automatically highlight the code. Is there a possibility in this Wiki to supply HTML or xhtml? "vim" allows for exporting syntax-highlighted files in HTML and xhtml, and also allows for determining whether a CSS should be produced and used for it or not (if not, each element will be colorized with font elements). --- It will be interesting to see whether supplying a Wiki for snippets will indeed cause more snippets to be made available (it did not look complicated to me to use Paolo's Snippet creator, which imposed a minimal structure on snippets like the language, the area and send the resulting XML file to Tom). If I could have a wish in this area then it would be to allow for an infrastructure which would have at least the same functionality as the current Snippet infrastructure (syntax highlighting, embedded links, systematic description of the snippet including its version number, good overview and navigation among the snippets at all times). ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
