The Problem is, what I think, to find or create such files by my self. I searched for months to find a C# grammar file for JavaCC. There isn’t so I used the Java and changed some stuff. Very error related because I don’t know much about grammar stuff.
Now I will rewrite my Plugin to ANTLR, because I found a proper C#.g4 file and will have a look whether it is better or not, but I think it is. So if you want to implement Haskell or F# to NB you need those files too and I think, to use a similar functionality what other IDEs/Editors alredas have would be better, because such user defined files are already there, look into the list for NotePad++: http://docs.notepad-plus-plus.org/index.php/User_Defined_Language_Files sor UltraEdit: https://www.ultraedit.com/downloads/extras/wordfiles.html Not to missunderstand here. We really need such simpler method to bring a new language to NetBeans but we should use similar technics like other IDEs/Editors already do. So we can use the great list of user defined files from other IDEs/Editors. Von: Peter Blemel Gesendet: Montag, 19. Juni 2017 17:13 An: [email protected] Betreff: Re: Provide basic editor features for more file types out of thebox[WAS: Re: AW: Introductory Email] I do. I wrote both of my editors in Schliemann, and then re-wrote them when it was abandoned. There was some discussion at the time about why it was unsupportable, or perhaps just obsolete but I don't remember the details. However, that experience is part of why I am proposing an "editor generator" instead of another scripting language. When developing a JavaCC or ANTLR grammar most tools require you to write the grammar first, in text, and then provide tools for visual representation. As a software developer I have found this process to be tedious and error prone, and a lot of important meta data is lost. I propose to reverse the process, using a data model that can be manipulated by visual editing tools to model the language (and editor features), from which code can be generated and maintained. Additional plugins could be written that do other things with the model. Peter ________________________________ From: Sven Reimers <[email protected]> Sent: Monday, June 19, 2017 9:00 AM To: [email protected] Subject: Re: Provide basic editor features for more file types out of the box[WAS: Re: AW: Introductory Email] Who can remember Schliemann Project in NetBeans? Sven Am 19.06.2017 1:08 nachm. schrieb "Emilian Bold" <[email protected]>: > In theory adding LSP support should be just as easy since the server does > all the heavy lifting. > > But if we want to have for example Erlang syntax highlighting, etc. in the > first case we just add another 10kb configuration file. In the second case > we have to find and ship an Erlang LSP server. > > --emi > > Pe 19 iun. 2017, la 12:13, ehsavoie <[email protected]> a scris: > > > LSP is an API so you would 'only' have to start a process and connect to > it > > (through input/output stream mostly). > > From my point of view a LSP editor is the generic editor you are talking > > about, and the LSP server is the file you are loading from. > > The advantage is that you have a quick more advanced support of a lot of > > languages without even having to support them while you would have to > > support every file you are providing. > > > > > > ---------- > > Emmanuel Hugonnet > > http://www.ehsavoie.com Java in the Alps - ehsavoie.com<http://www.ehsavoie.com/> www.ehsavoie.com On the 16th of October was hold the first NetBeans Day event in France thanks to Geertjan Wielenga , Nebrass Lamouchi (@NebrassLamouchi) and Paul Bernardi from ... > > http://twitter.com/ehsavoie ehsavoie (@ehsavoie) | Twitter<http://twitter.com/ehsavoie> twitter.com The latest Tweets from ehsavoie (@ehsavoie). WildFly dev, AlpesJUG leader, NetBeans Dream team member. Grenoble, France >
