Jürgen Schmidt wrote: > Hi Tom, > > > Tom Schindl wrote: > >> Hi, >> >> keep me up to date about when ooRex-LanguageBinding is released >> offically. >> >> We should more generally discuss what languages should be avaible on the >> snippet-page. >> >> At the moment the following ones are available on the snippet-page: >> - OOBasic >> - C++ >> - Java >> - Python >> - XSL >> >> Others I'm aware of but not on the snippet-page: >> - JavaScript >> - ooRex >> >> 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. > 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. > 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. > > Juergen
>> -----------------------8<-----------------------
>> <snippet>
>> // .... As usual
>> <answer>
>>
>> <listing lang="Java">
>> </listing>
>>
>> <listing lang="Python">
>> </listing>
>>
>> </answer>
>>
>> </snippet>
>> -----------------------8<-----------------------
>>
Well what I thought was that the solution for a problem can be found for
all languages withing one page. Languages aren't any more navigational
entries.
In ASCII-Art a page would look like this:
----------------------------------------------
| GENERAL-INFO |
| QUESTION .... |
| ANSWER .... |
----------------------------------------------
| SNIPPET-SOURCE |
----------------------------------------------
| Java | C++ | Python |
----------------------------------------------
| public static void main(String args) { |
| |
| } |
| |
| |
----------------------------------------------
Languages are modeled as Tabs within the the current-page where as the
main navigation-structure holds:
- Components (Office, Writer, ...)
- Topics (Connect 2 OO-Process)
Maybe we could provide an alternative navi-structure which is base on
languages like we have it nowadays.
The point I'm trying to make is the following:
What I'm afraid of is that nowadays you have to create for-each language
you solve the same problem one more snippet e.g.:
- connect2oo_cpp.snip
- connect2oo_java.snip
- connect2oo_python.snip
The topic, ... remains the same only the way to solve it differs. I hope
you can get my idea?
I think its more natural to have one code-snippet which holds the topic
and all possibilities (in our case languages to solve it).
I see if i can create an example page easily.
Tom
signature.asc
Description: OpenPGP digital signature
