Geertjan's Blog

  • March 28, 2007

Breathing Life into a Dead Coyote (Part 2)

Geertjan Wielenga
Product Manager
In Breathing Life into a Dead Coyote (Part 1), I stated my intention to commit the Schliemann code I've been working on to an upgraded version of the Groovy support module on Coyote. Well, today I did just that. So as not to mess up other things on Coyote, I created a separate directory and put everything in there. By "everything", I mean that I started with the 5.0 version of Groovy, opened the suite in my development build of 6.0, built everything, threw away stuff that prevented compilation from succeeding, threw away the 'syntax' package (based on Lexer), which I replaced with my half-baked Schliemann code, threw away some more stuff (all neatly recorded in the README.txt in the new directory on Coyote) and then eventually ran the suite without a problem. This is the best case scenario of what is currently possible with Coyote for 6.0:

Somewhere along the line I broke something, because the 'Run Script' button is never enabled, now. So that needs to be investigated. But, the point is, I now have the old Groovy data object working together with my Groovy.nbs file. "How is that possible?" you ask in incredulity, tinged with awe. The answer is this example snippet that I received this morning from Hanz Jancura, who is the NetBeans engineer behind Schliemann:

<folder name="Editors">
<folder name="text">
<folder name="css2">
<file name="language.nbs" url="CSS.nbs"/><attr name="createDataObject" boolvalue="false"/>

Note the line in bold. This way, you can continue using your old data object, while reaping the benefits of Schliemann.

Update: I found that the above approach does not actually work. To make my data object work together with Schliemann, I had to add this line to my manifest file, below my loader's declaration, to ensure that the data objects are installed in the correct order:

Install-Before: org.netbeans.modules.languages.dataobject.LanguagesDataObject

If you now go to Coyote, you just need to check out the content of one directory, the one indicated by the hand icon below:

That contains everything I've committed. Some stuff may be broken, while other stuff is unstable. But this is a starting point for further integration, specifically integration of the Schliemann-related code, over the next days/weeks. Remember to use a very recent 6.0 daily build, like I'm doing; get the Generic Languages Framework Studio from the development Update Center, as described recently in this blog. Anyone is welcome to join the project and contribute.

Join the discussion

Comments ( 10 )
  • Peter Knego Thursday, March 29, 2007
    Hi Geertjan,
    I tried to compile the modules, but unfortunately failed. Here's what happened:

    1. Downloaded latest daily build of Netbeans (28 Mar) and installed it. Added the Generic Languages Framework Studio from Update Center. (Added a few other modules - hope that's OK?)

    2. Pulled nb60groovy from Coyote CVS, and successfully opened it in NetBeans. Four dependent projects opened: Coyote - Suite, Coyote - Groovy Support, Coyote - Groovy Projects, groovy-all.

    3. Tried to Build the Coyote - Suite and failed with the following error:

    /home/peter/Projects/download/netbean_28_Mar_2007/harness/suite.xml:51: The following error occurred while executing this line:
    /home/peter/Projects/download/netbean_28_Mar_2007/harness/build.xml:74: No dependent module org.netbeans.modules.languages

    Do you have any idea what could be wrong? Thanks for your help.
  • Geertjan Thursday, March 29, 2007
    Sorry, you also need to get 'Generic Languages Framework', not just 'Generic Languages Framework Studio'. That's what 'org.netbeans.modules.languages' refers to.
  • Geertjan Thursday, March 29, 2007
    And I suspect you need to install it 'Global', which is a checkbox somewhere in the Update Center wizard.
  • Peter Knego Thursday, March 29, 2007
    Installing modules with option 'Global' did the trick. Everything works now. Thanks.
  • Geertjan Thursday, March 29, 2007
    Brilliant! Read the readme.txt in the main directory, to see where things are at. (And remember... the whole thing is buggier than the underside of a rock in a desert...)
  • Geertjan Friday, March 30, 2007
    I committed a change today -- the 'Run Script' button is no longer in the Groovy editor toolbar, replaced by a menu item in the popup menu that appears when you right-click in the Groovy editor.
  • &#31036;&#20202;&#20844;&#21496; Monday, April 30, 2007
  • Jens Tuesday, May 8, 2007
    Hi Geertjan. Thanks for this work!! I'm trying it on NB6.0 milestone 9 and am having some difficulties. I can import the four projects and have installed the 'Generic Languages Framework' - no sign of the 'Studio' module however. Trying to compile I get a lot of errors for the class org.netbeans.api.languages.DatabaseManager missing. Any thoughts on this?
  • Geertjan Tuesday, May 8, 2007
    Hi Jens. Yeah, I couldn't find the Studio module either. I was told I would need to build it from the sources, somehow and for some reason it currently isn't in the update center. That might be the cause of your other problem. Remember that Schliemann isn't stable at all, so if you use it there's a big chance that what you build will break while Schliemann continues to grow. Thanks for liking my work.
  • vasant Monday, February 25, 2008

    I am new user of the D Programming language.

    What is editor used for this language and how to run the prog.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.