Re: Language infrastructure (reloaded)

OK reading through the  following pages:

http://wiki.netbeans.org/GsfToParsingAndIndexingApiMigration
http://wiki.netbeans.org/ParsingAPI
http://wiki.netbeans.org/How_to_create_support_for_a_new_language
and  "Rich Client Programming: Plugging into the NetBeans Platform
<http://www.amazon.com/Rich-Client-Programming-Plugging-NetBeans/dp/0132354802>"
book

Is it correct if I state that CSL is the way to go for new languages? Or is
it only limited to "scripting" languages. For example, in my IDE, I can
only find CSL plugins for HTLM, CSS, sql, yaml and some others. Ruby and
Java are not listed.

Does it mean, they don't use the CSL API, because:
1) it doesn't fit their more advanced needs or
2) they use an older API and the effort to migrate them is too big?

I just need a bit of info here, just to not write stupid things later. ;-)

Appreciate you help

JMB


On Mon, Nov 7, 2016 at 2:31 PM, Jean-Marc Borer <[email protected]> wrote:

> Thank you Gj, I was thinking my post ended up in /dev/null ;)
>
> On Mon, Nov 7, 2016 at 12:49 PM, geertjan wielenga <
> [email protected]> wrote:
>
>>
>> More: http://wiki.netbeans.org/GsfToParsingAndIndexingApiMigration
>>
>> Gj
>>
>>
>> On 7-11-2016 13:48, geertjan wielenga wrote:
>>
>>
>> History of language infrastructure: https://blogs.oracle.com/geert
>> jan/entry/lexer
>>
>> Gj
>>
>> On 7-11-2016 13:43, geertjan wielenga wrote:
>>
>>
>> Lots of people are interested in this. :-) Just a question of time etc.
>>
>> Gj
>>
>> On 7-11-2016 13:40, Jean-Marc Borer wrote:
>>
>> Ok, so no one seems interested in this topic then...
>>
>> On Mon, Oct 24, 2016 at 1:55 PM, Jean-Marc Borer <[email protected]>
>> wrote:
>>
>>> Hello members,
>>>
>>> I know, it was already partly discussed in the thread
>>> http://forums.netbeans.org/viewtopic.php?t=65697&high
>>> light=language+infrastructure
>>>
>>> I wanted to start porting my simple language stucture based on the book "Rich
>>> Client Programming: Plugging into the NetBeans Platform
>>> <http://www.amazon.com/Rich-Client-Programming-Plugging-NetBeans/dp/0132354802>"
>>> to a modern approach and try to document it as a or several tutorials.
>>>
>>> Reading through the thread again to refresh my memory, I will probably
>>> base my work on Quorum language (Thank yous Stefik) as well as what I can
>>> find at https://github.com/GeertjanWielenga/Python4NetBeans.
>>>
>>> I hope those projects use the "most" state of the art implementation for
>>> a new language support. @Stefik and Geertjan, do you agree with this
>>> statement?
>>>
>>> Now there are still some questions that I would like to be answered to
>>> be able to write a "clean" tutorial. Googling around and using information
>>> stored in my spongy memory ;), there is/were different language APIs in NB
>>> history.
>>>
>>> First there is the old "roots" way described in Rich Client Programming
>>> book that I used in the first place. Then there was Schliemann which seems
>>> to be discontinued. Then came GSF which is partly documented/used in the NB
>>> tutorials. But now it seems it is also becoming deprecated. Now there is
>>> CSL.
>>>
>>> Is CSL the new language infrastructure? It seems to have GSF parts in
>>> it, since the csl.api readme.txt fle still makes references to GSF.
>>>
>>> Now I am lost. Can someone here out explain me:
>>> 1) the history of the language infrastructures?
>>> 2) tell me what is infrastructure to use now (state of the art) and its
>>> name (I have a hint but would prefer that someone confirms my idea)?
>>>
>>> Help would be greatly appreciated.
>>>
>>> Cheers,
>>>
>>> Jean-Marc
>>>
>>
>>
>>
>>
>>
>