Hi Jürgen,

... cut ...


Which languages should we support? Which languages should not be
supported? Should we maybe restructure our snippet-page not seperating
our pages into programming languages but rather task. Jürgen already
said that he'd like to have every snippet in every language.


I think we should concentrate on the most popular and offical languages supported in OO.org. But let us see how many snippets will be contributed for other currrently not supported languages. We can extend the page later as well.

What restrictions are there (time-wise, resource-wise, political-wise) which would have to/should be followed (who must/should concentrate on what) ?

And of course having the snippets available in all supported languages would be great and it should be easy for people to get started with any contribution to our snippet collection.

That would be most helpful.

How we select the snippets is not so important for me. If we should first select the language and second the functional topic or vice versa. But i think that selecting the language first would be more natural and keeps the follow up pages smaller.

Maybe a solution employing various (even client-sided) XSLT stylesheets would allow for freely choosing/picking the desired listings and renderings? If so, one could even ask for submitting the code-snippets in some XML-mark-up that you define upfront, and for which one can get at nutshell-examples so none-XML-savvy people can still create and submit correctly marked-up files (and maybe even allow entering the text in a form which then will get processed to create the XML-files the transformations can work on.

---rony


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to