lily4jedit-devel — This list is for discussing development of lily4jedit.

[Lily4jedit-devel] Broken again

[Valentin V. <v.v...@gm...>]

Hi Bert, hi everyone,

I've just tried jEdit v.pre13, and it's broken again! The Templates
plugin doesn't work anymore, nor does LilyPondTool (none of the
versions I tried, at least).

Honestly, I'm so pissed off with these repeated breakages, that I'd be
ready to fork jEdit myself just to get free of such annoyances.

Cheers,
Valentin

Re: [Lily4jedit-devel] External PDF preview: missing double quotes.

[Bertalan F. <lil...@or...>]

no, you put it before the .Pdf extension

> ------- Original Message -------
> From: "Valentin Villenave" <v.v...@gm...>
> To: lil...@li..., "Bertalan Fodor" <lil...@or...>
> Sent: 08/03/06/, 0:36:59
> Subject: Re: [Lily4jedit-devel] External PDF preview: missing double quotes.
> 
> 2008/3/5, Valentin Villenave <v.v...@gm...>:
> 
> >  I took the liberty to correct it myself in the source code; can you
> >  please review it to make sure I didn't do anything wrong?
> 
> Hi Bert,
> 
> I've just seen you've "fixed my fix": sorry, I now realize I had
> probably put an extra quote :)
> 
> Cheers,
> Valentin
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
> 
> 

Re: [Lily4jedit-devel] External PDF preview: missing double quotes.

[Valentin V. <v.v...@gm...>]

2008/3/5, Valentin Villenave <v.v...@gm...>:

>  I took the liberty to correct it myself in the source code; can you
>  please review it to make sure I didn't do anything wrong?

Hi Bert,

I've just seen you've "fixed my fix": sorry, I now realize I had
probably put an extra quote :)

Cheers,
Valentin

Re: [Lily4jedit-devel] External PDF preview: missing double quotes.

[Bertalan F. <lil...@or...>]

It should be in ConsoleProcess, so perhaps in 2.10.5 it will be good. Or 
won't :-)

Valentin Villenave írta:
> 2008/3/5, Bertalan Fodor <lil...@or...>:
>   
>> iirc I already fixed on either trunk or 2_10 branch
>>  where is your fix?
>>     
>
> It's on trunk.
>
> I haven't seen it fixed -- where's yours? :)
>
> Valentin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>
>   

Re: [Lily4jedit-devel] Compatibility problems

[Valentin V. <v.v...@gm...>]

2008/3/5, Valentin Villenave <v.v...@gm...>:
> OK.
>
>  Everything seems to work fine here (WinXP, JRE6).

Further testing on linux (Mandriva 2008.1, sun-java6):

Same tests, same (positive) results.

Valentin

Re: [Lily4jedit-devel] Compatibility problems

[Valentin V. <v.v...@gm...>]

OK.

Everything seems to work fine here (WinXP, JRE6).

- completion popup: OK

- barchecks: OK

- JPedal + ruler + etc: OK

- MIDI: not OK (can't remember what I need to install to get it working)

- convert-ly: odd error in the console (but I guess it's not related to LPT)

- external PDF preview: not OK (the spaces-in-filenames-thing I
addressed earlier)

- Score Setup Wizard: OK (Gee, you haven't implemented my correction
in the French localization file -- maybe I'll commit it on the SVN if
it's ok)

- "insert staves", etc: all OK

- sidekick parsing: OK

I think you can definitely upload it to the plugin central...

Cheers,
Valentin

2008/3/5, Bertalan Fodor <lil...@or...>:
> Give it a try at http://www.organum.hu/LilyPondTool.jar
>
>
>  > ------- Original Message -------
>  > From: "Valentin Villenave" <v.v...@gm...>
>  > To: "Bertalan Fodor" <lil...@or...>
>  > Sent: 08/03/05/, 21:02:13
>  > Subject: Re: [Lily4jedit-devel] Compatibility problems
>  >
>  > 2008/3/5, Bertalan Fodor <lil...@or...>:
>  >
>  > > I've done it yesterday. I'll upload LPT tonight to the plugin rep. But it is not thoroughly tested and won't be until that.
>  >
>  > I wanna apply for beta-testing! :)
>  >
>  > Cheers,
>  > Valentin
>  >
>  >
>


-- 
Cheers,
Valentin

Re: [Lily4jedit-devel] External PDF preview: missing double quotes.

[Valentin V. <v.v...@gm...>]

2008/3/5, Bertalan Fodor <lil...@or...>:
> iirc I already fixed on either trunk or 2_10 branch
>  where is your fix?

It's on trunk.

I haven't seen it fixed -- where's yours? :)

Valentin

Re: [Lily4jedit-devel] External PDF preview: missing double quotes.

[Bertalan F. <lil...@or...>]

iirc I already fixed on either trunk or 2_10 branch 
where is your fix?

> ------- Original Message -------
> From: "Valentin Villenave" <v.v...@gm...>
> To: lil...@li...
> Sent: 08/03/05/, 21:10:41
> Subject: [Lily4jedit-devel] External PDF preview: missing double quotes.
> 
> Hi Bert, hi guys,
> 
> I've just installed lilytool on windows, and suddenly I realized the
> "Preview with an external viewer" doesn't work because of spaces in my
> PDF folder's name.
> 
> The PDF reader's name (as defined by the user in Plugin Options) is
> already enclosed in double quotes, but the PDF document's name isn't;
> therefore the command is recognized, but not it's argument.
> 
> I took the liberty to correct it myself in the source code; can you
> please review it to make sure I didn't do anything wrong?
> 
> P.S. About the JPedal window (yeah, it's kind of an obsession); making
> it dockable does not imply everyone should have to dock it. It's just
> about giving them the ability to do so :)
> You can refer to my initial post on
> http://sourceforge.net/mailarchive/forum.php?thread_name=eefe316d0709070836p451b4607pbc52fd2c5c4abce%40mail.gmail.com&forum_name=lily4jedit-devel
> -- 
> Cheers,
> Valentin
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
> 
> 

Re: [Lily4jedit-devel] Compatibility problems

[Bertalan F. <lil...@or...>]

Give it a try at http://www.organum.hu/LilyPondTool.jar

> ------- Original Message -------
> From: "Valentin Villenave" <v.v...@gm...>
> To: "Bertalan Fodor" <lil...@or...>
> Sent: 08/03/05/, 21:02:13
> Subject: Re: [Lily4jedit-devel] Compatibility problems
> 
> 2008/3/5, Bertalan Fodor <lil...@or...>:
> 
> > I've done it yesterday. I'll upload LPT tonight to the plugin rep. But it is not thoroughly tested and won't be until that.
> 
> I wanna apply for beta-testing! :)
> 
> Cheers,
> Valentin
> 
> 

[Lily4jedit-devel] External PDF preview: missing double quotes.

[Valentin V. <v.v...@gm...>]

Hi Bert, hi guys,

I've just installed lilytool on windows, and suddenly I realized the
"Preview with an external viewer" doesn't work because of spaces in my
PDF folder's name.

The PDF reader's name (as defined by the user in Plugin Options) is
already enclosed in double quotes, but the PDF document's name isn't;
therefore the command is recognized, but not it's argument.

I took the liberty to correct it myself in the source code; can you
please review it to make sure I didn't do anything wrong?

P.S. About the JPedal window (yeah, it's kind of an obsession); making
it dockable does not imply everyone should have to dock it. It's just
about giving them the ability to do so :)
You can refer to my initial post on
http://sourceforge.net/mailarchive/forum.php?thread_name=eefe316d0709070836p451b4607pbc52fd2c5c4abce%40mail.gmail.com&forum_name=lily4jedit-devel
-- 
Cheers,
Valentin

Re: [Lily4jedit-devel] Compatibility problems

[Valentin V. <v.v...@gm...>]

2008/3/5, Bertalan Fodor <lil...@or...>:

> I've done it yesterday. I'll upload LPT tonight to the plugin rep. But it is not thoroughly tested and won't be until that.

I wanna apply for beta-testing! :)

Cheers,
Valentin

Re: [Lily4jedit-devel] Compatibility problems

[Bertalan F. <lil...@or...>]

These jEdit guys are going insane. They brake plugins then they remove. 

> -Finally make LilyTool compatible with pre12, or convince the jEdit
> guys to stop breaking things for once :)

I've done it yesterday. I'll upload LPT tonight to the plugin rep. But it is not thoroughly tested and won't be until that.

> Plus, this does really emphasize the need for ready-to-use bundles
> such as my EasyLily initiative (only, made better by people who know
> how to code ;)

I like EasyLilyPond. I hope someone will maintain it ;-)

Bert

[Lily4jedit-devel] Compatibility problems

[Valentin V. <v.v...@gm...>]

Hi Bertalan, hi guys,

I don't know if anyone of you has recently tried to set up a
LilyPondTool environment but it's really a PITA.

First of all, one needs to install jEdit pre11. No link is given on
jedit.org, so you have to either go to the project page and browse the
archives, or (smarter way) copy the pre12 download URL and replace 12
with one.

(If you had the misfortune to install pre12, LilyPondTool will not
even appear in the plugin list. It's an annoyance, though I understand
why you have intentionally made it so.)

Next. jEdit is set up, great, hurray, etc. Now, you'll open the Plugin
Manager, select LilyPondTool, which will automatically select the
appropriate dependencies (the Template plugin, among others). *But*...
LilyPondTool officially requires Templates 4.00 or above... which is
officially incompatible with jEdit pre11! By default, selecting
LilyPondTool installs Templates 3.30; then jEdit complains about the
incompatibility and refuses to regard LilyPondTool as installed.


So you have to figure out where the plugins are installed, and go look
for a recent Templates jar. On the page
http://plugins.jedit.org/plugins/?Templates
Only 4.1.1 is mentioned, which is definitely not compatible with
pre11. So you have to browse the whole archives on sourceforge and
download a decent zipped Templates (either 4.00 or 4.1.0), then unzip
the jars in the jars folder.

Gee... Four possible solutions:
-Let LilyPondTool accept Templates 3.30 (I'm not sure it will get
along well, because of the older Velocity),
-Tell the Templates guys to mark their 4.00 or 4.10 plugin as
compatible with pre11 (I never had any issue with it)
-Finally make LilyTool compatible with pre12, or convince the jEdit
guys to stop breaking things for once :)
-Let things the way they currently are, *but* at least document the
whole process described above anywhere on lilypondtool's homepage.

Plus, this does really emphasize the need for ready-to-use bundles
such as my EasyLily initiative (only, made better by people who know
how to code ;)

-- 
Cheers,
Valentin

Re: [Lily4jedit-devel] New member of the crew...

[Joshua K. <jos...@gm...>]

Sorry I forgot to reply back to the list!

On Jan 16, 2008 10:25 AM, Joshua Koo <jos...@gm...> wrote:

> Welcome Valentin!
>
> I've seen your webpage on EasyLilypondTool. Great effort and nice job!
>
> However, it has been a long time since I've really use LilyPond not to
> mention when I last work on it. The closest thing to music I'm doing now is
> preparing for my grade 8 piano exams and joining my university's symphony
> orchestra.
>
> I hope you'll enjoy the stay in this project, and learn many things (like
> I did, Bert is like a mentor :) and improve the project and the fun we have!
>
>
> Cheers,
> Joshua Koo
> http://zz85.is-a-geek.com/
>
>
> On Jan 16, 2008 6:30 AM, Bertalan Fodor <fo...@fr...> wrote:
>
> > Welcome, Valentin!
> >
> > If you just get involved in a way that you give tips, templates that
> > will help as well.
> > Currently I'm working on the rewrite of the LilyPond and Scheme parser
> > that takes much time from me. If I am ready with that I will release
> > LilyPondTool 2.11-r1 or 2.12-r1 depending on whether LilyPond itself
> > gets to the 12 release or not.
> >
> >
> > > - I have put a few icons in trunk/EasyLilyPond/icons. Comments
> > appreciated :)
> > >
> > We definitely need new icons. I've already copied the lilypond starter
> > icon to the LilyPondTool folder.
> > > - I don't know if a jEdit plugin can modify the "perspective" (the way
> >
> > > windows are placed, docked, etc). In EasyLilyPond I have added many
> > > pre-defined "properties", it would be great if some of these could be
> > > added in LilyPondTool itself (e.g. dock the Console at the bottom, the
> >
> > > Sidekick on the left etc.).
> > >
> > Well, a plugin should not do it automatically, but they are just
> > properties, which can be changed. So we could create a menu item for
> > "set recommended perspective" or so.
> > > - I have posted a former mail to suggest making the JPedal window
> > > dockable. I think this could be a HUGE improvement (at least, I would
> > > be delighted), because this way we could include the graphical score
> > > in the perspective, etc.
> > >
> > I remember I tried it one time, I don't remember why I haven't finished
> > it. Perhaps I just didn't have enough time.
> > > - maybe consider reordering some items in the LilyPondTool Toolbar,
> > etc.
> > >
> > I would like to create some user interface to enable the modification of
> > it without hacking the LilyPondTool.props file.
> > > - maybe redefine some default keyboard shortcuts
> > >
> > > EDITING IMPROVEMENTS:
> > >
> > > - the sidekick completion popup can be annoying when the space
> > > characters is set to accept auto-completion. We should definitely
> > > remove this.
> > >
> > Yeah, but SideKick's default is that space will auto-complete. I will
> > check this, however.
> > > - It would be great if we could tell jEdit to save .ly files with
> > > UTF-8 encoding by default. Maybe this would prevent thousands of users
> >
> > > to ask questions on the LilyPond mailinglist. In EasyLilyPond, I have
> > > set it in the default properties (with ISO 8859-1 as fallback
> > > encoding).
> > >
> > Ly files are automatically saved in UTF-8. At least there is some code
> > for it, but I remember there were problems with the functionality after
> > some change in the jEdit core.
> > > - Similarly, I'd like to set the default indentation as "Soft indent
> > > (emulate spaces with tabs)", with a 2 spaces indentation. It makes
> > > LilyPond files look much nicer, especially when users copy/paste their
> > > code in a mail or in a LSR snippet.
> > >
> > I don't agree with this myself, and I use proportional font (Lucida
> > Sans). Users usually prefer different settings.
> > > - I dont know if we can set a regexp to automatically detect CamelCase
> > > words and colors them. Very often, one has to use custom contexts in
> > > LilyPond, such as TimeSig, or whatever, and unfortunately these
> > > contexts are left uncolored.
> > >
> > Hm. It is not completely impossible to do this, however there are
> > problems: jEdit's syntax coloring is not dynamically redefinable (as far
> > as I know, or at least it is hard), and I would not like to use naive
> > regexps for this, because that way many other words could be colored
> > wrongly.
> > > BUGS TO BE ADDRESSED:
> > >
> > > - the last versions of jEdit seem to be somehow broken. I don't know
> > > if there is anything that we can do (I doubt it). Lots of Beanshell
> > > errors, etc.
> > >
> > Yes, in jEdit 4.3pre12 they broke almost all the plugins for fixing one
> > bug :-|
> > > - jEdit under linux is full of bugs. the auto-completion popup window
> > > open in the background (hence it is placed *behind* the jEdit window,
> > > and therefore is not useable); the small hint-boxes that apperar when
> > > you enter a barcheck do not disappear (after a while, the screen gets
> > > full of these, and you have to close jEdit and open it again.
> > >
> > I never use linux, however all of these might be a problem with the
> > linux display driver and/or the java virtual machine.
> > > - lots of bugs with the swing interface (the windows are not correctly
> > > placed, the mouse is not placed at the same place than the actual
> > > cursor, etc). I have reproduced these bugs with jre 1.5, 1.6 and 1.7.
> > > Then again, I doubt we can do anything.
> > >
> > Yes, bug reports are very valuable.
> > > - the JPedal viewer is completely buggy on my computer, even with a
> > > fresh installation (XP and Linux). The staves are not correctly
> > > placed, etc.
> > >
> > That's strange. At me it is almost perfect, only dotted lines are bad.
> > > LONG-TERM POSSIBLE (OR NOT?) FEATURES:
> > >
> > > -i18n the whole thing. I know nobody has ever cared about localizing
> > > jEdit (as a matter of fact, I'm puzzled with their development
> > > policy), but maybe we could do something. I *am* willing to spend a
> > > few dozen hours on it, if someone can just tell me what to do. If the
> > > jEdit guys are not interested in this kind of contributions, *we*
> > > could really use it (for instance, we could simply fork the jEdit
> > > program to distribute a (partially) localized version with the
> > > LilyPondTool bundled with it. Just thinking out loud.
> > >
> > Well, there are jEdit localization on the jEdit community forum or
> > somewhere there. I remember I've seen a German localization there. It
> > consisted only a property file: it is very simple: all plugins have
> > their strings as properties in the PluginName.props file. So you only
> > have to put together all the property settings in one large file, like
> > frenchJedit.props and put it into the properties folder inside jEdit
> > folder. That way you can localize jEdit and many plugins.
> > LilyPondTool's localization is much elegant: you write
> > messages.properties files, like messages_fr.properties and LilyPondTool
> > will choose one automatically based on the user's current locale. The
> > framework for this is already there in LilyPondTool, but the hardcoded
> > Strings in the java source files are not yet changed: only one place.
> > > - multi-languages Documentation. And examples files. In EasyLilyPond,
> > > the launcher detects the system Locale, and opens a translated example
> >
> > > file on the first run. By translated it, I mean that not only are the
> > > comments localized, but even the notenames.
> > >
> > Now that's something I must think about. Because I package the doc along
> >
> > with LilyPondTool it would need to create either a 200MB archive which
> > is definitely a no-no, or create different versions of the plugin.
> > > - LSR integration in jEdit. As you may know, the LSR has become a
> > > vital resource in LilyPond documentation; for example, the "commonly
> > > tweaked properties" that you can see in the Notation Reference are
> > > directly generated by the LSR. Plus, we have now a tagged-based LSR
> > > browing that could be really awesome in jEdit.
> > >
> > Very good idea. I have also started to implement a context-sensitive
> > automatic help window that would enable us to list the LSR examples for
> > \lyricsto if the cursor is on the word \lyricsto.
> > > - LSR snippets editing and posting in jEdit. This was a proposal I
> > > made months ago, before the LSR became such a huge thing.
> > Sure, actually Java is very good at http things.
> > > - Forking JPedal. Currently, this viewer just sucks (this is a
> > > personal opinion, of course). By forking it, we would get rid of its
> > > partially non-free licence, and we would have the ability to add some
> > > nice features and interface tweaks (zooming feature, continuuous
> > > layout, etc). Of course it's a really long shot here.
> > >
> > We have already forked it :-) Some day ago I tried to integrate the new
> > version of it, but found that it would need to restart from zero, and
> > the latest version still not fixed the dashed line bug.
> > > - Use a free Java implementation. (OK, now it is pure science-fiction,
> >
> > > but maybe in a couple of years...?)
> > >
> > NO! That's a very bad idea, believe me. And: the Sun implementation is
> > open sourced now as well. And has a very liberal license.
> > > Looking forward to working with you :)
> > >
> > Me too.
> >
> > Bert
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Lily4jedit-devel mailing list
> > Lil...@li...
> > https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
> >
>
>

Re: [Lily4jedit-devel] New member of the crew...

[Bertalan F. <fo...@fr...>]

Welcome, Valentin!

If you just get involved in a way that you give tips, templates that 
will help as well.
Currently I'm working on the rewrite of the LilyPond and Scheme parser 
that takes much time from me. If I am ready with that I will release 
LilyPondTool 2.11-r1 or 2.12-r1 depending on whether LilyPond itself 
gets to the 12 release or not.


> - I have put a few icons in trunk/EasyLilyPond/icons. Comments appreciated :)
>   
We definitely need new icons. I've already copied the lilypond starter 
icon to the LilyPondTool folder.
> - I don't know if a jEdit plugin can modify the "perspective" (the way
> windows are placed, docked, etc). In EasyLilyPond I have added many
> pre-defined "properties", it would be great if some of these could be
> added in LilyPondTool itself (e.g. dock the Console at the bottom, the
> Sidekick on the left etc.).
>   
Well, a plugin should not do it automatically, but they are just 
properties, which can be changed. So we could create a menu item for 
"set recommended perspective" or so.
> - I have posted a former mail to suggest making the JPedal window
> dockable. I think this could be a HUGE improvement (at least, I would
> be delighted), because this way we could include the graphical score
> in the perspective, etc.
>   
I remember I tried it one time, I don't remember why I haven't finished 
it. Perhaps I just didn't have enough time.
> - maybe consider reordering some items in the LilyPondTool Toolbar, etc.
>   
I would like to create some user interface to enable the modification of 
it without hacking the LilyPondTool.props file.
> - maybe redefine some default keyboard shortcuts
>
> EDITING IMPROVEMENTS:
>
> - the sidekick completion popup can be annoying when the space
> characters is set to accept auto-completion. We should definitely
> remove this.
>   
Yeah, but SideKick's default is that space will auto-complete. I will 
check this, however.
> - It would be great if we could tell jEdit to save .ly files with
> UTF-8 encoding by default. Maybe this would prevent thousands of users
> to ask questions on the LilyPond mailinglist. In EasyLilyPond, I have
> set it in the default properties (with ISO 8859-1 as fallback
> encoding).
>   
Ly files are automatically saved in UTF-8. At least there is some code 
for it, but I remember there were problems with the functionality after 
some change in the jEdit core.
> - Similarly, I'd like to set the default indentation as "Soft indent
> (emulate spaces with tabs)", with a 2 spaces indentation. It makes
> LilyPond files look much nicer, especially when users copy/paste their
> code in a mail or in a LSR snippet.
>   
I don't agree with this myself, and I use proportional font (Lucida 
Sans). Users usually prefer different settings.
> - I dont know if we can set a regexp to automatically detect CamelCase
> words and colors them. Very often, one has to use custom contexts in
> LilyPond, such as TimeSig, or whatever, and unfortunately these
> contexts are left uncolored.
>   
Hm. It is not completely impossible to do this, however there are 
problems: jEdit's syntax coloring is not dynamically redefinable (as far 
as I know, or at least it is hard), and I would not like to use naive 
regexps for this, because that way many other words could be colored 
wrongly.
> BUGS TO BE ADDRESSED:
>
> - the last versions of jEdit seem to be somehow broken. I don't know
> if there is anything that we can do (I doubt it). Lots of Beanshell
> errors, etc.
>   
Yes, in jEdit 4.3pre12 they broke almost all the plugins for fixing one 
bug :-|
> - jEdit under linux is full of bugs. the auto-completion popup window
> open in the background (hence it is placed *behind* the jEdit window,
> and therefore is not useable); the small hint-boxes that apperar when
> you enter a barcheck do not disappear (after a while, the screen gets
> full of these, and you have to close jEdit and open it again.
>   
I never use linux, however all of these might be a problem with the 
linux display driver and/or the java virtual machine.
> - lots of bugs with the swing interface (the windows are not correctly
> placed, the mouse is not placed at the same place than the actual
> cursor, etc). I have reproduced these bugs with jre 1.5, 1.6 and 1.7.
> Then again, I doubt we can do anything.
>   
Yes, bug reports are very valuable.
> - the JPedal viewer is completely buggy on my computer, even with a
> fresh installation (XP and Linux). The staves are not correctly
> placed, etc.
>   
That's strange. At me it is almost perfect, only dotted lines are bad.
> LONG-TERM POSSIBLE (OR NOT?) FEATURES:
>
> -i18n the whole thing. I know nobody has ever cared about localizing
> jEdit (as a matter of fact, I'm puzzled with their development
> policy), but maybe we could do something. I *am* willing to spend a
> few dozen hours on it, if someone can just tell me what to do. If the
> jEdit guys are not interested in this kind of contributions, *we*
> could really use it (for instance, we could simply fork the jEdit
> program to distribute a (partially) localized version with the
> LilyPondTool bundled with it. Just thinking out loud.
>   
Well, there are jEdit localization on the jEdit community forum or 
somewhere there. I remember I've seen a German localization there. It 
consisted only a property file: it is very simple: all plugins have 
their strings as properties in the PluginName.props file. So you only 
have to put together all the property settings in one large file, like 
frenchJedit.props and put it into the properties folder inside jEdit 
folder. That way you can localize jEdit and many plugins.
LilyPondTool's localization is much elegant: you write 
messages.properties files, like messages_fr.properties and LilyPondTool 
will choose one automatically based on the user's current locale. The 
framework for this is already there in LilyPondTool, but the hardcoded 
Strings in the java source files are not yet changed: only one place.
> - multi-languages Documentation. And examples files. In EasyLilyPond,
> the launcher detects the system Locale, and opens a translated example
> file on the first run. By translated it, I mean that not only are the
> comments localized, but even the notenames.
>   
Now that's something I must think about. Because I package the doc along 
with LilyPondTool it would need to create either a 200MB archive which 
is definitely a no-no, or create different versions of the plugin.
> - LSR integration in jEdit. As you may know, the LSR has become a
> vital resource in LilyPond documentation; for example, the "commonly
> tweaked properties" that you can see in the Notation Reference are
> directly generated by the LSR. Plus, we have now a tagged-based LSR
> browing that could be really awesome in jEdit.
>   
Very good idea. I have also started to implement a context-sensitive 
automatic help window that would enable us to list the LSR examples for 
\lyricsto if the cursor is on the word \lyricsto.
> - LSR snippets editing and posting in jEdit. This was a proposal I
> made months ago, before the LSR became such a huge thing. 
Sure, actually Java is very good at http things.
> - Forking JPedal. Currently, this viewer just sucks (this is a
> personal opinion, of course). By forking it, we would get rid of its
> partially non-free licence, and we would have the ability to add some
> nice features and interface tweaks (zooming feature, continuuous
> layout, etc). Of course it's a really long shot here.
>   
We have already forked it :-) Some day ago I tried to integrate the new 
version of it, but found that it would need to restart from zero, and 
the latest version still not fixed the dashed line bug.
> - Use a free Java implementation. (OK, now it is pure science-fiction,
> but maybe in a couple of years...?)
>   
NO! That's a very bad idea, believe me. And: the Sun implementation is 
open sourced now as well. And has a very liberal license.
> Looking forward to working with you :)
>   
Me too.

Bert

[Lily4jedit-devel] New member of the crew...

[Valentin V. <v.v...@gm...>]

Hi Bertalan, hi everybody;

I have (finally) created a new EasyLilyPond directory in trunk/

For now I have absolutely no time to work on EasyLilyPond (since I'm
working almost full time on LilyPond itself). However, I would be
interested in helping LilyPondTool development, in any way i can
(though I am absolutely not a prgorammer).

Here are a few ideas that I wanted to propose:

INTERFACE IMPROVEMENTS:

- I have put a few icons in trunk/EasyLilyPond/icons. Comments appreciated :)

- I don't know if a jEdit plugin can modify the "perspective" (the way
windows are placed, docked, etc). In EasyLilyPond I have added many
pre-defined "properties", it would be great if some of these could be
added in LilyPondTool itself (e.g. dock the Console at the bottom, the
Sidekick on the left etc.).

- I have posted a former mail to suggest making the JPedal window
dockable. I think this could be a HUGE improvement (at least, I would
be delighted), because this way we could include the graphical score
in the perspective, etc.

- maybe consider reordering some items in the LilyPondTool Toolbar, etc.

- maybe redefine some default keyboard shortcuts

EDITING IMPROVEMENTS:

- the sidekick completion popup can be annoying when the space
characters is set to accept auto-completion. We should definitely
remove this.

- It would be great if we could tell jEdit to save .ly files with
UTF-8 encoding by default. Maybe this would prevent thousands of users
to ask questions on the LilyPond mailinglist. In EasyLilyPond, I have
set it in the default properties (with ISO 8859-1 as fallback
encoding).

- Similarly, I'd like to set the default indentation as "Soft indent
(emulate spaces with tabs)", with a 2 spaces indentation. It makes
LilyPond files look much nicer, especially when users copy/paste their
code in a mail or in a LSR snippet.

- I dont know if we can set a regexp to automatically detect CamelCase
words and colors them. Very often, one has to use custom contexts in
LilyPond, such as TimeSig, or whatever, and unfortunately these
contexts are left uncolored.

BUGS TO BE ADDRESSED:

- the last versions of jEdit seem to be somehow broken. I don't know
if there is anything that we can do (I doubt it). Lots of Beanshell
errors, etc.

- jEdit under linux is full of bugs. the auto-completion popup window
open in the background (hence it is placed *behind* the jEdit window,
and therefore is not useable); the small hint-boxes that apperar when
you enter a barcheck do not disappear (after a while, the screen gets
full of these, and you have to close jEdit and open it again.

- lots of bugs with the swing interface (the windows are not correctly
placed, the mouse is not placed at the same place than the actual
cursor, etc). I have reproduced these bugs with jre 1.5, 1.6 and 1.7.
Then again, I doubt we can do anything.

- the JPedal viewer is completely buggy on my computer, even with a
fresh installation (XP and Linux). The staves are not correctly
placed, etc.

LONG-TERM POSSIBLE (OR NOT?) FEATURES:

-i18n the whole thing. I know nobody has ever cared about localizing
jEdit (as a matter of fact, I'm puzzled with their development
policy), but maybe we could do something. I *am* willing to spend a
few dozen hours on it, if someone can just tell me what to do. If the
jEdit guys are not interested in this kind of contributions, *we*
could really use it (for instance, we could simply fork the jEdit
program to distribute a (partially) localized version with the
LilyPondTool bundled with it. Just thinking out loud.

- multi-languages Documentation. And examples files. In EasyLilyPond,
the launcher detects the system Locale, and opens a translated example
file on the first run. By translated it, I mean that not only are the
comments localized, but even the notenames.

- LSR integration in jEdit. As you may know, the LSR has become a
vital resource in LilyPond documentation; for example, the "commonly
tweaked properties" that you can see in the Notation Reference are
directly generated by the LSR. Plus, we have now a tagged-based LSR
browing that could be really awesome in jEdit.

- LSR snippets editing and posting in jEdit. This was a proposal I
made months ago, before the LSR became such a huge thing. I don't know
if there's a jEdit plugin that can already handle https transactions,
but if there's any, it would be great to think about a possible way to
add snippets in the LSR directly *from* jEdit. The current LSR online
interface is ugly, and not really pleasant to use; this could be an
interesting alternative.

- Forking JPedal. Currently, this viewer just sucks (this is a
personal opinion, of course). By forking it, we would get rid of its
partially non-free licence, and we would have the ability to add some
nice features and interface tweaks (zooming feature, continuuous
layout, etc). Of course it's a really long shot here.

- Use a free Java implementation. (OK, now it is pure science-fiction,
but maybe in a couple of years...?)

OK, that's about all.

Looking forward to working with you :)

Valentin

[Lily4jedit-devel] A suggestion about the integrated JPedal viewer

[Valentin V. <v.v...@gm...>]

Hello Bert, hello everybody,

I don't know if I'm the only one to think this way, but I've been
using LilyPondTool every day for months, and suddenly I realize my
life would be much, much simpler and nicer if... the PDF view could be
dockable!
Currently, it's not, and therefore I have to constantly Alt-Tab to see
the result of my compilations. It's a PITA, and could be easily
avoided.

I'm not a coder, so I've read jEdit documentation, browsed the
sources, and eventually found the dockables.xml in LilyPondTool.jar.
Theorically, if I understand correctly, it would be enough to add
three lines in this file:

	<DOCKABLE NAME="jpedal-viewer">
		new org.jpedal.Display(something);
	</DOCKABLE>

I'm not sure about the "jpedal-viewer" name, I made it up; besides,
I've looked into Display.java but couldn't find the correct function
(which opens the windows).

This is a wild guess; can anyone who knows Java tell me if the PDF
viewer can (and should) be made dockable?

Thank you very much,
Valentin

[Lily4jedit-devel] the Lilypond Snippet Repository and LilyPondTool...

[Valentin V. <v.v...@gm...>]

Hi Bert, hi everybody,

I've just seen that Graham wants to include a snapshot of the LSR in
LilyPond's Documentation.As one of the editors of the LSR, I find this
is a great idea, and I wonder if it will be added to LilyJHelp.jar...

I have another idea, but you might find it inappropriate: how about a
possibility to send a snippet to the LSR _through_ LilyPondTool? I've
seen that some plugins for jedit already support network transactions,
so it must be possible, but is it worth it?

Regards,
Valentin

Re: [Lily4jedit-devel] Porting LilyPondTool to a PHP/JavaScript online application?

[Valentin V. <v.v...@gm...>]

2007/6/13, Bertalan Fodor <fo...@fr...>:

Hello Bertalan,

Firstable I'd like to say that LilyPondTool remains my model and as
you can see, this topic is not entitled "Creating a New Client" but
"Porting LilyPondTool". The point is *not* to make another thing from
scratch, and I agree with you to say that clients multiplicity is to
be avoided.
The point is just to focus on new users, pupils, family, friends;
people who may have heard about LilyPond but are a bit reluctant to
download and install software on their computers. This is about
bringing to these people, as far as it can be done, both LilyPond's
features and LilyPondTool's easiness, through a simple web interface.

> generally I don't agree with developing new and new clients. Why not
> make the currently existing, with hundreds of manhour in development better?

this is precisely why my first intention -as I told you- was to keep
LilyPondTool's (almost) native code by running jedit as a web embedded
Java applet; unfortunately it turns out there isn't -yet- any chance
to do so (and by the way, it would be something quite heavy for a web
application).

That said, I'll be glad to help LilyPondTool's development too if I
can; for instance by improving French localization files or other
obvious things.

[I have another question, but I'll just start a new thread to not go off-topic.]

Regards,
Valentin

Re: [Lily4jedit-devel] Porting LilyPondTool to a PHP/JavaScript online application?

[Bertalan F. <fo...@fr...>]

Hi,

generally I don't agree with developing new and new clients. Why not
make the currently existing, with hundreds of manhour in development better?

Valentin Villenave írta:
> Hi Bertalan, hi everybody;
>
> A few days ago, I've started thinking about some way to make LilyPond
> easy to use and to learn through a web interface, based on
> LilyPondTool for the features and the (good) ideas.
> A few people are interested too, such as Sebastiano Vigna from the
> LSR, some french guys who developed the LilySpip plugin, and maybe
> others (I haven't made any *real* announcement yet, and don't know if
> it's worth it).
>
> Anyway, this could be a first step: I've been trying to
> (approximatively) reproduce LilyPondTool syntax highlighting, code
> colors, etc. in an opensource JavaScript editor (CodePress). I had
> never used JScript or regex before, so it is probably a bit messy. I
> used the lilypond.xml file from LilyPondTool.jar to get a complete
> LilyPond API, and managed to somehow implement it.
>
> If you have a minute, you're welcome to have a look at the result here:
> http://valentin.villenave.info/lilypond/
> The two files I wrote are
> http://valentin.villenave.info/lilypond/codepress/languages/lilypond.js
> for the API and
> http://valentin.villenave.info/lilypond/codepress/languages/lilypond.css
> for the colors.
>
> Thank you!
>
> Cheers,
> Valentin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>
>
>
>   

Re: [Lily4jedit-devel] Porting LilyPondTool to a PHP/JavaScript online application?

[Joshua K. <jos...@gm...>]

Thats very nice. I don't think you would be able to port the entire
LilyPondTool to a web application, but a web application does it differently
eg. Microsoft Word vs Google Documents. Of course it would be good to have
the essentials stuff and shortcut stuff in it too.

I guess a good idea which you could borrow from Google Documents is to
ability to login and save the work (automatically like google) so you can
work on it anywhere.

I've not exmine CodePress closely, but its seems pretty impressive- line
numbers, auto complete, syntax highlighting. But I'm not sure how extensible
it is for your needs- basically its using an iframe.

IMHO, javascript and php issnt as difficult compared writing java
applications so I see much potential in this. You could link up with
lilypond in the back end and generate the scores online. My wishlist is
entering notes just by dragging and dropping. example:
http://www.melodyhound.com/

Over all, its seem pretty good.. I think no harm in letting others know
about your project, maybe more would give you ideas and help you need.

Joshua

On 6/12/07, Valentin Villenave <v.v...@gm...> wrote:
>
> Hi Bertalan, hi everybody;
>
> A few days ago, I've started thinking about some way to make LilyPond
> easy to use and to learn through a web interface, based on
> LilyPondTool for the features and the (good) ideas.
> A few people are interested too, such as Sebastiano Vigna from the
> LSR, some french guys who developed the LilySpip plugin, and maybe
> others (I haven't made any *real* announcement yet, and don't know if
> it's worth it).
>
> Anyway, this could be a first step: I've been trying to
> (approximatively) reproduce LilyPondTool syntax highlighting, code
> colors, etc. in an opensource JavaScript editor (CodePress). I had
> never used JScript or regex before, so it is probably a bit messy. I
> used the lilypond.xml file from LilyPondTool.jar to get a complete
> LilyPond API, and managed to somehow implement it.
>
> If you have a minute, you're welcome to have a look at the result here:
> http://valentin.villenave.info/lilypond/
> The two files I wrote are
> http://valentin.villenave.info/lilypond/codepress/languages/lilypond.js
> for the API and
> http://valentin.villenave.info/lilypond/codepress/languages/lilypond.css
> for the colors.
>
> Thank you!
>
> Cheers,
> Valentin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>

[Lily4jedit-devel] Porting LilyPondTool to a PHP/JavaScript online application?

[Valentin V. <v.v...@gm...>]

Hi Bertalan, hi everybody;

A few days ago, I've started thinking about some way to make LilyPond
easy to use and to learn through a web interface, based on
LilyPondTool for the features and the (good) ideas.
A few people are interested too, such as Sebastiano Vigna from the
LSR, some french guys who developed the LilySpip plugin, and maybe
others (I haven't made any *real* announcement yet, and don't know if
it's worth it).

Anyway, this could be a first step: I've been trying to
(approximatively) reproduce LilyPondTool syntax highlighting, code
colors, etc. in an opensource JavaScript editor (CodePress). I had
never used JScript or regex before, so it is probably a bit messy. I
used the lilypond.xml file from LilyPondTool.jar to get a complete
LilyPond API, and managed to somehow implement it.

If you have a minute, you're welcome to have a look at the result here:
http://valentin.villenave.info/lilypond/
The two files I wrote are
http://valentin.villenave.info/lilypond/codepress/languages/lilypond.js
for the API and
http://valentin.villenave.info/lilypond/codepress/languages/lilypond.css
for the colors.

Thank you!

Cheers,
Valentin

Re: [Lily4jedit-devel] Localization improvement: fixed JPedal messages_fr.properties

[Bertalan F. <fo...@fr...>]

We can fork it for our own case, as it is GPL. Actually I have already 
made some modifications to it. I also found that the new version is 
changed so much that I couldn't integrate it.

Bert

Valentin Villenave írta:
> Hi everybody, hi Bert;
>
> I've found the JPedal localization file (which isn't better than the
> Wizard one I corrected yesterday). So here's a correct French
> version...
>
> That said, I am a little disappointed to see all the limitations this
> demo version seems to have. Since this version is free, maybe it would
> be worth it to fork their library in a 100% GPL way?
>
> Besides, if someone on this list wants to forward the corrected
> messages_fr.properties file to IDRsolutions, I have no problem with
> that.
>
> Cheers,
> Valentin
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>   

[Lily4jedit-devel] Localization improvement: fixed JPedal messages_fr.properties

[Valentin V. <v.v...@gm...>]

Hi everybody, hi Bert;

I've found the JPedal localization file (which isn't better than the
Wizard one I corrected yesterday). So here's a correct French
version...

That said, I am a little disappointed to see all the limitations this
demo version seems to have. Since this version is free, maybe it would
be worth it to fork their library in a 100% GPL way?

Besides, if someone on this list wants to forward the corrected
messages_fr.properties file to IDRsolutions, I have no problem with
that.

Cheers,
Valentin

Re: [Lily4jedit-devel] Localization improvement: fixed i18n_fr.properties

[Bertalan F. <fo...@fr...>]

Hi, that's great, thank you. I commit it.

Bert

Valentin Villenave írta:
> Hello everybody,
>
> I'm new to this list though I've been using LilyPondTool for a long
> time. I am also a member of the LilyPond French team and of the LSR
> crew.
>
> There is a thing you should know: the Babel translator which was used
> to translate the Jwizardcomponent buttons really *sucks* and every
> French LilyPondTool user outthere <ho uses the Document Setup Wizard
> must be hilarious when seeing such things as "Dos", "Aprës" or
> "Finition", which are not even French words! :)
>
> So since I've just discovered this list, here is a modified
> i18n_fr.properties file which *does* sound French. If someone can
> commit it to the SVN...
>
> Thanks
>
> Valentin
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Lily4jedit-devel mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-devel
>