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

Re: [Lily4jedit-devel] New features

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

Yes I have an idea. You could help me finding the problem. 
When you start jEdit in the log you should find something like this:
The interesting is when Velocity's JarResourceLoader is trying to add LilyPondTool.jar and the lines
where something differs.

[message] Velocity: ************************************************************** 
[message] Velocity: Starting Jakarta Velocity v1.3.1-rc2
[message] Velocity: RuntimeInstance initializing.
[message] Velocity: Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties
[message] Velocity: Trying to use logger class velocity.jEditLogSystem
[message] Velocity: Using logger class velocity.jEditLogSystem
[message] Velocity: Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl)
[message] Velocity: Resource Loader Instantiated: org.apache.velocity.runtime.resource.loader.FileResourceLoader
[message] Velocity: FileResourceLoader : initialization starting.
[message] Velocity: FileResourceLoader : adding path 'D:\prog\jEdit 4.1\jars\LilyPondTool\lilytool\templates\'
[message] Velocity: FileResourceLoader : initialization complete.
[message] Velocity: Resource Loader Instantiated: org.apache.velocity.runtime.resource.loader.JarResourceLoader
[message] Velocity: JarResourceLoader : initialization starting.
[message] Velocity: JarResourceLoader # of paths : 1
[message] Velocity: JarResourceLoader : trying to load: jar:file:/D:\prog\jEdit 4.1\jars\LilyPondTool.jar
[message] Velocity:   JarHolder : attempting to connect to jar:file:/D:\prog\jEdit 4.1\jars\LilyPondTool.jar!/
[message] Velocity:   JarHolder : initialized JAR: jar:file:/D:\prog\jEdit 4.1\jars\LilyPondTool.jar!/
[message] Velocity: JarResourceLoader : initialization complete.
[message] Velocity: ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCacheImpl)
[message] Velocity: Default ResourceManager initialization complete.
[message] Velocity: Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[message] Velocity: Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[message] Velocity: Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[message] Velocity: Loaded System Directive: org.apache.velocity.runtime.directive.Include
[message] Velocity: Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
[message] Velocity: Loaded User Directive: velocity.directives.Prompt
[message] Velocity: Loaded User Directive: velocity.directives.BeanShell
[message] Velocity: Loaded User Directive: velocity.directives.Caret
[message] Velocity: Loaded User Directive: velocity.directives.Today
[message] Velocity: Loaded User Directive: velocity.directives.BufferMode
[message] Velocity: Created: 1 parsers.
[message] Velocity: Velocimacro : initialization starting.
[message] Velocity: Velocimacro : adding VMs from VM library template : VM_global_library.vm
[error] Velocity: ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[message] Velocity: Velocimacro : error using  VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm'
[message] Velocity: Velocimacro :  VM library template macro registration complete.
[message] Velocity: Velocimacro : allowInline = true : VMs can be defined inline in templates
[message] Velocity: Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
[message] Velocity: Velocimacro : allowInlineLocal = true : VMs defined inline will be local to their defining template only.
[message] Velocity: Velocimacro : messages on  : VM system will output logging messages
[message] Velocity: Velocimacro : autoload off  : VM system will not automatically reload global library macros
[message] Velocity: Velocimacro : initialization complete.
[message] Velocity: Velocity successfully started.

Re: [Lily4jedit-devel] New features

[Johannes S. <Joh...@gm...>]

Hi,

when trying to run the document wizard, I get the text below.
Any ideas why?

Ciao,
Dscho


[error]   JarHolder : error establishing connection to JAR
java.net.UnknownHostException: mnt
[error] Error processing template 'lilytool/templates/documentWizard.vm'
[error] java.lang.NullPointerException
[error]         at
org.apache.velocity.runtime.resource.loader.JarHolder.getEntries(JarHolder.java:158)
[error]         at
org.apache.velocity.runtime.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:184)
[error]         at
org.apache.velocity.runtime.resource.loader.JarResourceLoader.init(JarResourceLoader.java:152)
[error]         at
org.apache.velocity.runtime.resource.ResourceManagerImpl.initialize(ResourceManagerImpl.java:187)
[error]         at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(RuntimeInstance.java:502)
[error]         at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:268)
[error]         at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:441)
[error]         at
org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:148)
[error]         at templates.TemplatesPlugin.getEngine(Unknown Source)
[error]         at templates.TemplatesPlugin.processTemplate(Unknown
Source)
[error]         at
lilytool.LilyToolPlugin.runTemplate(LilyToolPlugin.java:552)
[error]         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[error]         at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[error]         at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[error]         at java.lang.reflect.Method.invoke(Method.java:324)
[error]         at bsh.Reflect.invokeMethod(Unknown Source)
[error]         at bsh.Reflect.invokeStaticMethod(Unknown Source)
[error]         at bsh.Name.invokeMethod(Unknown Source)

[Lily4jedit-devel] New features

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

Hello guys,
 
Do you have some thoughts about the new features in LilyTool?
I have good news: user-defined templates can use the document wizard
now. I've written a bit documentation for it.
 
My idea is that LilyTool's documentation should not be only LilyTool's,
but a beginner's guide to LilyPond using LilyTool. For example it would
start with a "hello, LilyPond world" score, built with document wizard,
using some of lily4jedit's feature? Is it a stupid idea?
 
Bert

[Lily4jedit-devel] Templates preferred over macros

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

Hello,

if you'd like to generate some lily code based upon user input it is better
write templates than macros. 
Their development is easier, because you can set the directory where
Templates plugin is looking for templates.
And with templates you can do anything what with  Beanshell, because the
Templates plugin provides a #beanshell tag

For example I've checked out LilyPondTool's sources to :
c:\prog\jEdit 4.1\jars\LilyPondTool (actually this is mandatory for jEdit
plugins)

This way I can test the templates without rebuilding LilyPondTool and
restarting jEdit.

Bert

[Lily4jedit-devel] Snapshots

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

Hello,
 
I decided to make weekly builds available on the project page (now that
the package is less than 1 MB). I want to exclude jhall.jar as well in
the future, but now LilyToolPlugin is dependent on it. I will change it
to be dependent instead on LilyJHelp, which can be separately (and not
so rarely) updated.
 
Bert

[Lily4jedit-devel] Macros

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

Hello,

I've added a new directory in lilytool: macros.

New macros that are intended to be integrated with lily4jedit should be put
there.
 So these macros will be packaged in the LilyPondTool.jar file.
They can be called by using the static method
LilyToolPlugin.runMacro(macroName).

So, if you have macros that you are working on, check them into CVS:
LilyTool/LilyPondTool/lilytool/macros

Thanks,

Bert

[Lily4jedit-devel] Weekend works

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

Hello, I've been working hard in the weekend, so I can present you some new
features.

* Templates are now integrated - you get a brand new documentWizard now -
with lyrics support.
* Lily Toolbar working

And my favorite:
* automatic lyrics hyphenation using LaTeX's hyphenation engine. It's not
finished yet but working (language and encoding settings are hardcoded), but
you can try it. Thanks goes to Dscho for the LilyPondShell.waitFor() method.

See the new Plugin menu.

Bert

[Lily4jedit-devel] RE: What did I messed out?

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

> Cant figure where to configure the path to the correct 
> directory.   I'm not using the cvs version of j-dvi. Has the 
> cvs version fix it?
Yes, see private mail.

> ps: Bert, I still not on your mailing list. Please add me if 
> its possible. 
Sure, you were deleted by mailman for your mailbox has been filled.

Bert

Re: [Lily4jedit-devel] Beam slopes fixed.

[Johannes S. <Joh...@gm...>]

Hi,

On Fri, 4 Jun 2004, Fodor Bertalan wrote:
> I found that the beam slope got scaled but it shouldn't.

Of course!

> Now the beams are nice.

Thank you,
Dscho

[Lily4jedit-devel] Beam slopes fixed.

[Fodor B. <fod...@fr...>]

Hello, 

I found that the beam slope got scaled but it shouldn't.
Now the beams are nice.

Checked in.

Bert

Re: [Lily4jedit-devel] jDvi distortion

[Johannes S. <Joh...@gm...>]

Hi,

On Fri, 4 Jun 2004, Fodor Bertalan wrote:

> Hello, I think I've eliminated the first-time distortion problem
> (JDviPanel.java). The problem was that only dviDpi was set not
> lilySpecial.dvi

Thanks! Though I didn't experience problems with it. I checked and it does
not break my setup.

Ciao,
Dscho

[Lily4jedit-devel] jDvi distortion

[Fodor B. <fod...@fr...>]

Hello, I think I've eliminated the first-time distortion problem
(JDviPanel.java). The problem was that only dviDpi was set not
lilySpecial.dvi
Checked in CVS.

Bert

[Lily4jedit-devel] More JDvi fixes

[Johannes S. <Joh...@gm...>]

Hi,

I implemented handling of tuples in JDvi and added handlers for
PageUp/PageDown, Escape or Q. All checked into CVS

Bert, could you please test with attached file if the distortion is still
there? Of course, your problem could be something Windows specific, when
it shouldn't.

Ciao,
Dscho

Re: [Lily4jedit-devel] Problem with point-and-click positioning

[Johannes S. <Joh...@gm...>]

Hi,

On Tue, 1 Jun 2004, Fodor Bertalan wrote:
> If you type three tabs, then the note will be on the 4th position, however,
> in jDvi it says: goto src:x:24, and it jumps to x:15-24.

There is also a similar problem with chords. I am quite sure Lilypond does
not do it correctly. If I look directly into the dvi it says src:0:0,
which is obviously wrong.

I'll add the problem to my personal TODO...

Ciao,
Dscho

RE: [Lily4jedit-devel] jdvi text fonts not found

[Johannes S. <Joh...@gm...>]

Hi,

On Mon, 31 May 2004, Bertalan Fodor wrote:

> I found the problem:
>
> Text fonts are generated in /var/cache/fonts/pk/ljfour/public/cm and so on
> and not directly in /var/cache/fonts/pk/ljfour.

Seems like you ran the "MakeFonts" after running JDvi for the first time.
I made a quick hack to speed up looking for font paths: the first time the
font path is scanned, it gets stored in a property. This is so, because
starting a bash in Windows 98 is *slow*.

I will think of a fix later this week; I am quite busy right now :-(

> One more thing: when jDvi is opened it us ugly. WHen I zoom in and out it
> gets nice.

Can you send me a screen shot? With my setups, I am only not happy with
the default size and zoom...

Ciao,
Dscho

[Lily4jedit-devel] Problem with point-and-click positioning

[Fodor B. <fod...@fr...>]

Hello,

how does it handle tab-s?

If you type three tabs, then the note will be on the 4th position, however,
in jDvi it says: goto src:x:24, and it jumps to x:15-24.

Bert

[Lily4jedit-devel] Problem with point-and-click positioning

[Fodor B. <fod...@fr...>]

Hello,

how does it handle tab-s?

If you type three tabs, then the note will be on the 4th position, however,
in jDvi it says: goto src:x:24, and it jumps to x:15-24.

Bert

RE: [Lily4jedit-devel] jdvi text fonts not found

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

I found the problem:

Text fonts are generated in /var/cache/fonts/pk/ljfour/public/cm and so on
and not directly in /var/cache/fonts/pk/ljfour.

One more thing: when jDvi is opened it us ugly. WHen I zoom in and out it
gets nice.

Bert

[Lily4jedit-devel] jdvi text fonts not found

[Fodor B. <fod...@fr...>]

I just tried jdvi with scores containing lyrics. It can't find lyrics fonts.

Bert

[Lily4jedit-devel] Midi playing

[Johannes S. <Joh...@gm...>]

Hi,

I just checked in a 1st version of Midi Playing. Planned feature is a seek
bar (slider), which is updated regularly. Also planned: seeking with the
cursor keys. It is implemented, but does not work correctly... no idea
why.

Ciao,
Dscho

P.S.: You can access it as usual in Plugins/LilyTool/

[Lily4jedit-devel] Upgrading edit mode (fwd)

[Johannes S. <Joh...@gm...>]

Hi,

I will have a look at the new mode later.

> We will upgrade to jEdit 4.2 as soon as it gets stable.

The problem here seems to be that the interface of the SideKick plugin has
changed dramatically.

> > >	Dscho: sorry i havnt not tried jdvi. my cygwin is
> > installed some where other than the default directory. also
> > because I just installed jedit 4.1 and 4.2 concurrently, i
> > running into errors im trying to solve.

No problem, I have changed a lot since we have CVS on sf.net... The cygwin
thing: You should only set the full path in LilyTool's "bash" option.
Everything else will (should) work out of the box after that ...

As for the problems of 4.1 and 4.2 concurrently: I had that, too (Windows
only: Linux was fine with it), until I decided to directly link to the
jedit.jar files. Since then: No problem.

Now a riddle for you Ant hackers: How can I change the build.xml so that
depending on some test (preferably in java), a different set of source
files gets compiled into the jar file? We will definitely need this, once
jedit 4.2 is stable, because there will still be a lot of people not
willing to upgrade (me, for once, because when Bert forced me to downgrade
I realized that 4.1 starts up much faster than 4.2, and while the list of
features of 4.2 is impressive, I am not going to use them every day, but I
am going to start jedit almost every day several times).

Ciao,
Dscho

[Lily4jedit-devel] Upgrading edit mode

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

I've attached Joshua (zz85)'s lilymode.xml

My notes:

I think that when notes are colored then all notes in all languages should
be colored but nothing in lyrics. I think that this is impossible to
achieve, so I wouldn't colorize note names. However, having the rests and
skips be emphasized and the durations colored is a good idea. And if you
find a way to have only notes colored, they can be. (But why wouldn't we use
the black normal style for them?) 

Bert 

p.s.: We will upgrade to jEdit 4.2 as soon as it gets stable.

Fragments from Joshua's letter:

> >	Anyway, wonder if i can attach files to the mailing 
> list, but im trying. Attached a (not so well) modified 
> lilymode, as I wanted to make the syntax hightlighting 
> better. A warning though.... ly files would appear much more 
> colorfully than before ;) I left some comments inside the 
> file, please take a look, and modify it in whatever way it 
> can for the best for everyone.

> >	Another thing you may be already aware of it is that 
> lilytool doesnt not seems to work with jedit 4.2 pre 13. im 
> using the latest version of the file releases on the project 
> page. i also dl the files from the cvs, but havnt not figured 
> out how to compile or use the files. 

> >	Dscho: sorry i havnt not tried jdvi. my cygwin is 
> installed some where other than the default directory. also 
> because I just installed jedit 4.1 and 4.2 concurrently, i 
> running into errors im trying to solve.

[Lily4jedit-devel] New completion feature

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

Hello, 
 
There is a new cool experimental feature in the parser:
 
It will provide automatic property list with description.
Now only the Grobs and most of their properties are included.
 
To try:
 
Type for example 'Beam.' and select Plugins/SideKick/Show completion
popup
 
Now you get all the properties of the Beam grob. Now hover with the
mouse on one of the properties: TADA! The property's description is in a
tooltip box. 
 
Bert

[Lily4jedit-devel] New parsing features

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

Hello, 

I've made some new parsing features: it will check immediately on
saving:

- unclosed blocks and unexpected "}" and ">>"
- commands are known (this feature should be more sophisticated, because
it will not recognise commands declared in included files - well, the
wordlist should contain that commands)

Now the identifiers are directly on the root of the structure browser.
Maybe it is better this way.

I hope you'll like these,

Bert

RE: [Lily4jedit-devel] Re: My (rather huge) TODO

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

> Yes, you are right. It does not make sense to distribute such a small
xml
> separately. I really hope they add it soon!
I sent it to jEdit's author (and renamed to lilypond.xml to make it
consistent with the other edit mode).

> P.S.: Bert, have you checked that zz85 is on the list, too?

I don't think so, because he is now on duty of resurrecting his data
from his burnt HDD. But I'll send him a letter if he'd like to be.

Bert