#847 LilyPondTool 2.14.8

closed-rejected
None
5
2014-11-06
2012-08-06
Bertalan Fodor
No

{{{ LilyPondTool 2.14.8
Source: Source code is in SVN with the tag 2.14.8 at https://lily4jedit.svn.sourceforge.net/svnroot/lily4jedit
Announcement: A new version of LilyPondTool is now available for releasing. It now depends on the new Julie plugin.
Requires Java 1.6
Requires jEdit 04.05.99.00
Required plugins:
Console 4.3.7 (console.ConsolePlugin)
ErrorList 1.7 (errorlist.ErrorListPlugin)
GnuRegexp 1.0.1 (GnuRegexpPlugin)
Jakarta Commons 0.6 (jakartacommons.JakartaCommonsPlugin)
Julie 1.0 (net.sf.julie.jedit.JuliePlugin)
Project Viewer 2.1.3.7 (projectviewer.ProjectPlugin)
SideKick 0.7.5 (sidekick.SideKickPlugin)
Templates 4.1.1 (templates.TemplatesPlugin)

Short Description: Editor environment for LilyPond.

Long Description: <html>
<p>LilyPondTool provides a plugin for jEdit with a lot of features that can help making LilyPond scores faster, easier and with less error. Features include:</p>
<div class="itemizedlist">
<ul class="itemizedlist" type="disc">
<li class="listitem"><p>Document Wizard to set up documents easier with lyrics support</p></li>
<li class="listitem"><p>Integrated dockable PDF viewer with point-and-click support</p></li>
<li class="listitem"><p>Structure browser with code folding</p></li>
<li class="listitem"><p>LilyPond parser for finding simple errors during typing</p></li>
<li class="listitem"><p>Convenient running of LilyPond and related tools</p></li>
<li class="listitem"><p>Automatic code completion for typing commands and tweaking properties</p></li>
<li class="listitem"><p>Automatic hyphenation of lyrics using OpenOffice dictionaries</p>
</html>
}}}

Discussion

  • Corrections needed:

    1. props: Julie 1.2, not 1.0

    2. props: other plugin dependencies should also be raised. ProjectViewer and Template throw exceptions. I suggest to give up-to-date versions of all the plugins. Up-to-date means taken from correctly running LilyPondInstance on jedit 4.5.

    3. compilation error:
    /m/temp/7/pf/sandbox/LilyPondTool-2.14.8/LilyPondTool/src/lilytool/parser/lilypond/library/classes/SmobSupport.java:18: type parameters of <T>T cannot be determined; no unique maximal instance exists for type variable T with upper bounds T,java.lang.Object
    return Smobs.unsmob(value);
    I managed to build after inserting conversion to T in that line.

     
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-06

    Dear Jarek, I committed the fixes, can you check now? Thank you.

     
  • Bertalan

    Many commands from Score menu fail with exception, for example Score Setup Wizard. I attach the exception text. Is everything ok with these commands? I'm testing on Windows at the moment.

    I'm going to test all the menu commands before release.

    By the way: probably Julie will be released as 1.3, so here in props it should also be 1.3. When we get a satisfying working trunk of LilyPondTool, a new submission will be needed anyway. So until that moment we can work on LilyPondTool trunk.

     
  •  
    Attachments
    • assigned_to: nobody --> jarekczek
     
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-10

    Thanks. Is lilyAssist.dat present in the root of the generate LilyPondTool.jar?

     
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-11

    ... actually this stack trace is familiar, though I cannot reproduce it. Are there no extra clues in the activity log to what can cause this exception.

     
  • You seem to be right Bertalan. There is something. After line 219 it looks like Julie is not initialized properly. See attached log. Are you using the same Julie as I do? From Julie trunk?

     
  • activity log from 2012-09-12 Julie init failure line 219

     
    Attachments
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-12

    This can happen if Julie.jar, the julie.shp inside it, and the lilyAssist.dat in gen of LilyPondTool are not consistent..
    I saw this error during the building process, but after a rebuild and making sure that lilyAssist.dat was generated with the latest Julie everything worked.
    Can you double check that the lilyAssist.dat file in LilyPondTool.jar is the 949 revision?

     
  • I'll verify this Bertalan. And you please verify that this works:
    1. do a fresh checkout (to a new directory) of Julie, and please give the url you use
    2. build Julie
    3. do a fresh checkout of LilyPond (give me the url also please)
    4. build LilyPond using just built Julie
    5. try Score Setup Wizard

    Note that in point 3 if you download trunk you get also tags and you have to remove them. Or maybe I did something wrong because I got this unwanted "tags" directory.

     
  • A theory about incompatibility between LilyPondTools and Julie seems to prove itself. I think there should be a better message than current non-informative one. Could you develop a message that:

    1. explain the user that there is an incompatibility between the 2 plugins
    2. give developers details about the incomatibility, for example the name of the class causing problem

    When we have this message I guess you'll be able to diagnose my failure to run the plugin. If I am to support more details, you know my email.

     
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-20

    Hi, I've committed a new version of the generated lilyAssist.dat, created with the trunk of both LilyPondTool and Julie. Can you check again?

     
  • I prefer to have a clear message before proceeding. Maybe Eric will have a different opinion, so you may choose to wait for him. BTW: a quick test shows the same effect as before.

     
  • Bertalan Fodor
    Bertalan Fodor
    2012-09-22

    I have no other idea - this might because of a difference in the platforms, the Java version, a bug in jEdit class initialization. Actually I don't want to put in an error message which might or might not be correct.
    For this time being, I consider giving up struggling with a proper "official" build, and instead distribute my plugin as a zip.

     
    • status: open --> pending-rejected
     
    • status: pending-rejected --> closed-rejected