one workspace per score?

[Marc Mouries]

I've been using Elysium with 100 of lilypond files in one Eclipse workspace and the performance is bad.

Elysium does not support all of lilypond features and as such Elysium reports errors for files that compile correctly with lilypond.

A side effect is that overtime i make a change in one file, Elysium tries to recompile those files with errors.

What do you use?

[Harmath Dénes]

On 2011.07.20., at 3:23, Marc Mouries wrote:

> I've been using Elysium with 100 of lilypond files in one Eclipse workspace and the performance is bad.

Performance is a major issue as e.g. http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=16 shows, and I intend to improve on this, but this needs some investigation. Meanwhile, the normal use case is to add not your whole collection to the Score Library, but those projects one by one which you are working on. Creating separate workspaces per score is hopefully not necessary. :)

> Elysium does not support all of lilypond features and as such Elysium reports errors for files that compile correctly with lilypond.

With the latest release, the language coverage is meant to be pretty comprehensive. All built-in initialization files (in share/lilypond/current/ly) for 2.14.1 compile well except toc-init.ly due to some markup commands (see http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=29). Please report issues about the remaining false errors. Elysium's design principle is to evolve the parser incrementally starting from accepting general constructs in the direction of being more structured and semantic while always trying to be more permissive than not.

> A side effect is that overtime i make a change in one file, Elysium tries to recompile those files with errors.
>
> What do you use?

LilyPond compilation is a lengthy process, so Elysium only compiles changed files and files which (even indirectly) include them. Also, source files are validated when added to the Score Library or when edited, but this is much quicker than compilation. You can try closing projects that you do not currently use, or even disabling automatic building and manually recompiling editing files, but this is of course discouraged - automatic incremental build is one of the main and unique features of Elysium.

Thank you for the constant testing and feedback on this piece of software clearly in alpha stage:
thSoft

[Marc Mouries]

Memory is not an issue for me. The problem i have is that everytime i open my workspace with lilypond files, it tries to compile all the files with errors as shown by the number of lilypond executable in the task manager (see attached screen shot)

2011/7/21 Harmath Dénes <harmat...@gmail.com>

[Bernardo Barros]

2011/7/21 Harmath Dénes <harmat...@gmail.com>:

> LilyPond compilation is a lengthy process, so Elysium only compiles changed files and files which (even indirectly) include them. Also, source files are validated when added to the Score Library or when edited, but this is much quicker than compilation. You can try closing projects that you do not currently use, or even disabling automatic building and manually recompiling editing files, but this is of course discouraged - automatic incremental build is one of the main and unique features of Elysium.
>

Not unique. In emacs you can do:

(add-hook 'after-save-hook (
lambda ()
(when (equal major-mode 'LilyPond-mode)
(LilyPond-command-lilypond)
)))

[Harmath Dénes]

Yes, emacs can do this. What is unique is the transitive compilation: you don't have to maintain e.g. build files for updating both the score and the part when editing the music definition - Elysium automatically recompiles all the files and just those files which are affected by the change (if you have used Eclipse for Java development, this behaviour might be familiar to you). See this screencast for demonstration.

[Harmath Dénes]

Sorry, the missing link: http://www.youtube.com/watch?v=49hwbXHuVwo