Re: Testing requested: new manuscript viewer tool for Frescobaldi

[David Wright]

On Wed 18 Nov 2015 at 16:56:47 (+0100), Federico Bruni wrote:
> Il giorno mer 18 nov 2015 alle 16:33, Urs Liska 
> ha scritto:
> >Does sh read ~/.bashrc?
> 
> Yes, it does:
> 
> $ sh -c "echo $LILYPOND_GIT"
> /home/fede/src/lilypond-git

I'm not sure what this is meant to demonstrate. If your normal shell's
startup file has set LILYPOND_GIT, then   sh -c   will only inherit it.

You really need to know what sh is invoking. Here,   ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Nov  8  2014 /bin/sh -> dash

Running bash and dash and sh interactively (following each invocation
with ^D to exit), one gets:

west!david 10:41:39 ~ $ bash
(This is /home/david/.bashrc 2015 October 15)
(This is /home/david/.bash-1-west 2015 July 13 on jessie)
(This is /home/david/.bash-9-west 2015 August 04)
west!david 10:41:42 ~ $ exit
west!david 10:41:43 ~ $ dash
\[\e[1;33;41m\]\[\e[0;34m\]\H!\u \t \w $ \[\e[m\]
west!david 10:41:47 ~ $ sh
\[\e[1;33;41m\]\[\e[0;34m\]\H!\u \t \w $ \[\e[m\]
west!david 10:41:51 ~ $ 

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno mer 18 nov 2015 alle 17:38, Ralf Mattes 
 ha scritto:


Am Mittwoch, 18. November 2015 16:56 CET, Federico Bruni 
 schrieb:


 Il giorno mer 18 nov 2015 alle 16:33, Urs Liska 
 ha

 scritto:
 > Does sh read ~/.bashrc?

 Yes, it does:

 $ sh -c "echo $LILYPOND_GIT"
 /home/fede/src/lilypond-git


No, it doesn't (necesarily). In your test you start the shell (most 
likely
/bin/sh, which most likeliy is a link to /bin/bash or /bin/dash) from 
within
another shell runnning in a terminal emulator and _that_ shell most 
likely

read ~/.bashrc and exported those environment variables.


You are right, not necessarily: in fact it reads the environment 
variables, but it does not read the frescobaldi alias.


/bin/sh is a link to /bin/bash





 >
 > What about
 >
 > bash -c frescobaldi
 > ?

 same error


When run from a terminal (emulator)?  Hard to belive.
If run from some desktop file (or menu or whatever) then yes, that
would be expected. If you want bash to consult startup files you must
run it as a 'login' shell. So, either 'bash --login' or 'bash -l'


Well, this is what's happening here on Fedora 23 using the gnome 
terminal:


[~]$ bash -c frescobaldi
bash: frescobaldi: comando non trovato
[~]$ bash -c 'frescobaldi'
bash: frescobaldi: comando non trovato
[~]$ bash -l -c 'frescobaldi'
bash: frescobaldi: command not found




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Ralf Mattes]

 
Am Mittwoch, 18. November 2015 17:48 CET, Federico Bruni  
schrieb: 
 
> You are right, not necessarily: in fact it reads the environment 
> variables, but it does not read the frescobaldi alias.

How and where did you define that alias?
In ~/.bashrc

 alias frescobaldi=/path/to/where/git/is/frescobaldi

> Well, this is what's happening here on Fedora 23 using the gnome 
> terminal:
> 
> [~]$ bash -c frescobaldi
> bash: frescobaldi: comando non trovato
> [~]$ bash -c 'frescobaldi'
> bash: frescobaldi: comando non trovato
> [~]$ bash -l -c 'frescobaldi'
> bash: frescobaldi: command not found

All of these only work when you  either define an alias (as mentioned
above) or extend your PATH environment variable.
Again, in ~/.bashrc:

 export  PATH=/where/you/checked/out/frescobali:$PATH

HTH RalfD

BTW - I'm subscribed to the list - no need to cc a personal reply to me


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno mer 18 nov 2015 alle 17:57, Ralf Mattes 
 ha scritto:


Am Mittwoch, 18. November 2015 17:48 CET, Federico Bruni 
 schrieb:



 You are right, not necessarily: in fact it reads the environment
 variables, but it does not read the frescobaldi alias.


How and where did you define that alias?
In ~/.bashrc

 alias frescobaldi=/path/to/where/git/is/frescobaldi


Yes, like above.
In bash manual:

Aliases are not expanded when the shell is not interactive

Perhaps this is the reason?




 Well, this is what's happening here on Fedora 23 using the gnome
 terminal:

 [~]$ bash -c frescobaldi
 bash: frescobaldi: comando non trovato
 [~]$ bash -c 'frescobaldi'
 bash: frescobaldi: comando non trovato
 [~]$ bash -l -c 'frescobaldi'
 bash: frescobaldi: command not found


All of these only work when you  either define an alias (as mentioned
above) or extend your PATH environment variable.
Again, in ~/.bashrc:

 export  PATH=/where/you/checked/out/frescobali:$PATH


Probably adding it to the $PATH is the best choice.
No need to tweak frescobaldi.desktop then.



HTH RalfD

BTW - I'm subscribed to the list - no need to cc a personal reply to 
me


Replying to all is the practice recommended in this list. You can find 
discussions in the archives.

Even though I'd agree with you.





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[David Wright]

On Wed 18 Nov 2015 at 17:48:34 (+0100), Federico Bruni wrote:
> Il giorno mer 18 nov 2015 alle 17:38, Ralf Mattes
>  ha scritto:
> >
> >Am Mittwoch, 18. November 2015 16:56 CET, Federico Bruni
> > schrieb:
> >
> >> Il giorno mer 18 nov 2015 alle 16:33, Urs Liska
> >> ha
> >> scritto:
> >> > Does sh read ~/.bashrc?
> >>
> >> Yes, it does:
> >>
> >> $ sh -c "echo $LILYPOND_GIT"
> >> /home/fede/src/lilypond-git
> >
> >No, it doesn't (necesarily). In your test you start the shell
> >(most likely
> >/bin/sh, which most likeliy is a link to /bin/bash or /bin/dash)
> >from within
> >another shell runnning in a terminal emulator and _that_ shell
> >most likely
> >read ~/.bashrc and exported those environment variables.
> 
> You are right, not necessarily: in fact it reads the environment
> variables, but it does not read the frescobaldi alias.

It might be worth taking note of this line in   man bash

"For almost every purpose, aliases are superseded by shell functions."

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

[OT] Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Ralf Mattes]

 
Am Mittwoch, 18. November 2015 18:02 CET, David Wright 
 schrieb: 
 

> 
> It might be worth taking note of this line in   man bash
> 
> "For almost every purpose, aliases are superseded by shell functions."

Yes, with one important difference in favour of aliases - if I want to quickla 
find out
about the aliases I have set up I can just enter 'alias' in my shell an get a 
list of
all defined aliases. To get something similar for functions you'd need to 
resort to
'set' and that'll flood you with a _lot_ of code ;-)

 Cheers, RalfD


> Cheers,
> David.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 
 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno mer 18 nov 2015 alle 16:33, Urs Liska  ha 
scritto:

Does sh read ~/.bashrc?


Yes, it does:

$ sh -c "echo $LILYPOND_GIT"
/home/fede/src/lilypond-git




What about

bash -c frescobaldi
?


same error

I think that we should recommend the full path in the desktop file:

Exec=/full/path/to/frescobaldi/frescobaldi

As the documentation says¹:

The executable program can either be specified with its full path or 
with the name of the executable only. If no full path is provided the 
executable is looked up in the $PATH environment variable used by the 
desktop environment.


¹ 
http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s06.html



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 18.11.2015 um 16:56 schrieb Federico Bruni:
> Il giorno mer 18 nov 2015 alle 16:33, Urs Liska 
> ha scritto:
>> Does sh read ~/.bashrc?
>
> Yes, it does:
>
> $ sh -c "echo $LILYPOND_GIT"
> /home/fede/src/lilypond-git
>
>
>>
>> What about
>>
>> bash -c frescobaldi
>> ?
>
> same error
>
> I think that we should recommend the full path in the desktop file:
>
> Exec=/full/path/to/frescobaldi/frescobaldi
>
> As the documentation says¹:
>
> The executable program can either be specified with its full path or
> with the name of the executable only. If no full path is provided the
> executable is looked up in the $PATH environment variable used by the
> desktop environment.
>

Ah, that often is an issue. It's the desktops that don't read .bashrc,
not `sh` or `bash`.
IIRC I have given up on this because it's even more convenient to fire
up frescobaldi through the Alt+F2 interface ...

Urs

BTW: I've also updated the Wiki page.

> ¹ http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s06.html
>


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Ralf Mattes]

 
Am Mittwoch, 18. November 2015 16:56 CET, Federico Bruni  
schrieb: 
 
> Il giorno mer 18 nov 2015 alle 16:33, Urs Liska  ha 
> scritto:
> > Does sh read ~/.bashrc?
> 
> Yes, it does:
> 
> $ sh -c "echo $LILYPOND_GIT"
> /home/fede/src/lilypond-git

No, it doesn't (necesarily). In your test you start the shell (most likely
/bin/sh, which most likeliy is a link to /bin/bash or /bin/dash) from within
another shell runnning in a terminal emulator and _that_ shell most likely 
read ~/.bashrc and exported those environment variables.

> 
> > 
> > What about
> > 
> > bash -c frescobaldi
> > ?
> 
> same error

When run from a terminal (emulator)?  Hard to belive.
If run from some desktop file (or menu or whatever) then yes, that 
would be expected. If you want bash to consult startup files you must 
run it as a 'login' shell. So, either 'bash --login' or 'bash -l' 

HTH RalfD




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno mer 18 nov 2015 alle 13:18, Federico Bruni 
 ha scritto:

But frescobaldi.desktop still needs to be adjusted this way:

Exec=sh -c 'frescobaldi'


This is not reliable. Sometime it works, sometimes it doesn't. I mean, 
Gnome Shell finds the application but cannot launch it.


$ sh -c 'frescobaldi'
sh: frescobaldi: command not found

Weird... These commands work on command line but not anymore on the 
desktop file:


sh -c "python ~/src/frescobaldi/frescobaldi"
sh -c "~/src/frescobaldi/frescobaldi"

I'm confused.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 18.11.2015 um 16:12 schrieb Federico Bruni:
> Il giorno mer 18 nov 2015 alle 13:18, Federico Bruni
>  ha scritto:
>> But frescobaldi.desktop still needs to be adjusted this way:
>>
>> Exec=sh -c 'frescobaldi'
>
> This is not reliable. Sometime it works, sometimes it doesn't. I mean,
> Gnome Shell finds the application but cannot launch it.
>
> $ sh -c 'frescobaldi'
> sh: frescobaldi: command not found
>
> Weird... These commands work on command line but not anymore on the
> desktop file:
>
> sh -c "python ~/src/frescobaldi/frescobaldi"
> sh -c "~/src/frescobaldi/frescobaldi"
>
> I'm confused.
>

Does sh read ~/.bashrc?
What about

bash -c frescobaldi
?

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno sab 14 nov 2015 alle 23:36, Simon Albrecht 
 ha scritto:
It is a feature of Python (in which frescobaldi is written) that a 
program needn’t be compiled/installed to be run. You need to
1. get the source files for frescobaldi and python-ly from 
, either by downloading 
 
and  or using 
‘git clone’ and checking out the ‘manuscript-viewer’ branch.
2. add the following three lines to ~/.bashrc, where 
path/to/python-ly and path/to/frescobaldi are the paths to the 
respective directories:

# add python-ly to PYTHONPATH
PYTHONPATH=path/to/python-ly:$PYTHONPATH
alias frescobaldi='path/to/frescobaldi/frescobaldi'
3. and then you can just run 'frescobaldi' on the command line to 
test the feature.


Simon, this is probably the best configuration for the terminal.
But frescobaldi.desktop still needs to be adjusted this way:

Exec=sh -c 'frescobaldi'

Do you have better ideas?

I've added the wiki page:
https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-from-git

Anybody is welcomed to improve it, especially Windows users.




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 18.11.2015 um 13:18 schrieb Federico Bruni:
> Il giorno sab 14 nov 2015 alle 23:36, Simon Albrecht
>  ha scritto:
>> It is a feature of Python (in which frescobaldi is written) that a
>> program needn’t be compiled/installed to be run. You need to
>> 1. get the source files for frescobaldi and python-ly from
>> , either by downloading
>> 
>> and  or using
>> ‘git clone’ and checking out the ‘manuscript-viewer’ branch.
>> 2. add the following three lines to ~/.bashrc, where
>> path/to/python-ly and path/to/frescobaldi are the paths to the
>> respective directories:
>> # add python-ly to PYTHONPATH
>> PYTHONPATH=path/to/python-ly:$PYTHONPATH
>> alias frescobaldi='path/to/frescobaldi/frescobaldi'
>> 3. and then you can just run 'frescobaldi' on the command line to
>> test the feature.
>
> Simon, this is probably the best configuration for the terminal.
> But frescobaldi.desktop still needs to be adjusted this way:
>
> Exec=sh -c 'frescobaldi'
>
> Do you have better ideas?
>
> I've added the wiki page:
> https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-from-git
>
> Anybody is welcomed to improve it, especially Windows users.

One question, regarding the Wiki page as well as the process in general:

Running Frescobaldi from Git needs a number of other dependencies to be met.
Am I right to assume that the suggested approach will work when
Frescobaldi has previously been installed a different way? If so this
should be clearly stated on the Wiki page.


There are two more things that should be added, but I can do that when
I'll find time:
- How to update through Git
- Use the "Git" menu to checkout different branches

Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Jan-Peter Voigt]

Hi Urs,

this is indeed a nice feature :)
For now, I will run from that branch, until its merged ...
But still I won't open frescobaldi that often until xmas, when my
current job is done.

Thanks for this tools!
Best,
Jan-Peter


Am 17.07.2015 um 16:41 schrieb Urs Liska:
> Hi all,
> 
> Peter Bjuhr and I have been working on a new tool for Frescobaldi that I
> have wanted to have for quite some time now. It's only the first step of
> what it may become, but Peter was perfectly right by triggering actual
> work with saying "something is better than nothing". I think the
> "something" we have now is already a very useful enhancement in itself.
> 
> It is a new "manuscript viewer" panel that can be used to have a
> manuscript open within Frescobaldi. So if you are copying music from an
> existing score you don't have to switch applications but can see the
> "engraver's copy, the LilyPond input and the engraved output in the same
> window.
> 
> 
> Before merging it we would like to have a few people test it. If you are
> running Frescobaldi from its Git repository we'd like to ask you to pull
> the latest commits and checkout the 'manuscript-viewer' branch.
> You can then open 'Tools->Display manuscript', click on the help button
> and start your review from there.
> Please test the tool, try to crash it and find any inconsistencies in
> behaviour or interface.
> Please also see our list of open discussion items at
> https://github.com/wbsoft/frescobaldi/milestones/Initial%20Manuscript%20Viewer
> 
> Thanks and have fun
> Urs
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 18.11.2015 um 15:41 schrieb Federico Bruni:
> Il giorno mer 18 nov 2015 alle 13:21, Urs Liska 
> ha scritto:
>> One question, regarding the Wiki page as well as the process in general:
>>
>> Running Frescobaldi from Git needs a number of other dependencies to
>> be met.
>> Am I right to assume that the suggested approach will work when
>> Frescobaldi has previously been installed a different way? If so this
>> should be clearly stated on the Wiki page.
>
> You are right. I gave it for granted, but it should be stated.
> I've updated the page pointing to INSTALL.

Thanks.

>
>>
>> There are two more things that should be added, but I can do that when
>> I'll find time:
>> - How to update through Git
>
> done
>

Thanks.

>>
>> - Use the "Git" menu to checkout different branches
>
> Do you mean the Github branch button?
> I'll leave this to you when you have time.
>

I mean the "Git" menu that Frescobaldi has when run from Git. This lists
all branches that are available in your Frescobaldi repository, even
when you have acquired branches from others' forks (but so far it
doesn't do any fetching for you). Clicking on an item checks out that
branch and offers the option to restart Frescobaldi from that branch.

I thought this would be cool as a way to test branches from pull
requests. Unfortunately I didn't find a proper way to pull stuff from
the server (things break when the user's Git set-up requires manual
interaction, e.g. for passwords).

Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno mer 18 nov 2015 alle 13:21, Urs Liska  ha 
scritto:
One question, regarding the Wiki page as well as the process in 
general:


Running Frescobaldi from Git needs a number of other dependencies to 
be met.

Am I right to assume that the suggested approach will work when
Frescobaldi has previously been installed a different way? If so this
should be clearly stated on the Wiki page.


You are right. I gave it for granted, but it should be stated.
I've updated the page pointing to INSTALL.



There are two more things that should be added, but I can do that when
I'll find time:
- How to update through Git


done



- Use the "Git" menu to checkout different branches


Do you mean the Github branch button?
I'll leave this to you when you have time.




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Klaus Blum]

Hi Simon, hi Federico,

thanks for your advices. Yeah, it works! :-)
This is a really cool feature. I hope it will soon be available for 
windows as well.


Cheers,
Klaus


Am 14.11.2015 um 23:36 schrieb Simon Albrecht:
It is a feature of Python (in which frescobaldi is written) that a 
program needn’t be compiled/installed to be run. You need to
1. get the source files for frescobaldi and python-ly from 
, either by downloading 
 
and  or using 
‘git clone’ and checking out the ‘manuscript-viewer’ branch.
2. add the following three lines to ~/.bashrc, where path/to/python-ly 
and path/to/frescobaldi are the paths to the respective directories:

# add python-ly to PYTHONPATH
PYTHONPATH=path/to/python-ly:$PYTHONPATH
alias frescobaldi='path/to/frescobaldi/frescobaldi'
3. and then you can just run 'frescobaldi' on the command line to test 
the feature.


I hope that this is correct and will help; if there are any questions, 
feel free to ask.

Yours, Simon



Am 15.11.2015 um 17:54 schrieb Federico Bruni:

Install git and run the following commands in the terminal:

mkdir ~/src
cd ~/src
git clone g...@github.com:wbsoft/python-ly.git
git clone g...@github.com:wbsoft/frescobaldi.git
cp frescobaldi/frescobaldi.desktop ~/.local/share/applications/
sed -ir 's|Exec=.*$|Exec=sh -c "PYTHONPATH=~/src/python-ly python 
~/src/frescobaldi/frescobaldi"|' 
~/.local/share/applications/frescobaldi.desktop


When you want to upgrade you enter the two sources and make a pull:

cd ~/src/python-ly
git pull

cd ~/src/frescobaldi
git pull




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno sab 14 nov 2015 alle 13:23, Klaus Blum  
ha scritto:
Is there any documentation out there that tells how to run a program 
from

git?


I don't think so.
It may be added to the github wiki...



I have an Ubuntu installation, but no deeper Linux knowledge, so I've 
got no

idea what to do.


Install git and run the following commands in the terminal:

mkdir ~/src
cd ~/src
git clone g...@github.com:wbsoft/python-ly.git
git clone g...@github.com:wbsoft/frescobaldi.git
cp frescobaldi/frescobaldi.desktop ~/.local/share/applications/
sed -ir 's|Exec=.*$|Exec=sh -c "PYTHONPATH=~/src/python-ly python 
~/src/frescobaldi/frescobaldi"|' 
~/.local/share/applications/frescobaldi.desktop


When you want to upgrade you enter the two sources and make a pull:

cd ~/src/python-ly
git pull

cd ~/src/frescobaldi
git pull




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Simon Albrecht]

On 15.11.2015 17:54, Federico Bruni wrote:
Il giorno sab 14 nov 2015 alle 13:23, Klaus Blum  
ha scritto:
Is there any documentation out there that tells how to run a program 
from

git?


I don't think so.
It may be added to the github wiki...



I have an Ubuntu installation, but no deeper Linux knowledge, so I've 
got no

idea what to do.


Install git and run the following commands in the terminal:

mkdir ~/src
cd ~/src
git clone g...@github.com:wbsoft/python-ly.git
git clone g...@github.com:wbsoft/frescobaldi.git
cp frescobaldi/frescobaldi.desktop ~/.local/share/applications/
sed -ir 's|Exec=.*$|Exec=sh -c "PYTHONPATH=~/src/python-ly python 
~/src/frescobaldi/frescobaldi"|' 
~/.local/share/applications/frescobaldi.desktop


[for testing the manuscript viewer, use the following commands 
additionally:]

cd frescobaldi
git checkout manuscript-viewer



When you want to upgrade you enter the two sources and make a pull:

cd ~/src/python-ly
git pull

cd ~/src/frescobaldi
git pull


HTH, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 15.11.2015 um 20:35 schrieb Klaus Blum:
> Hi Simon, hi Federico,
>
> thanks for your advices. Yeah, it works! :-)
> This is a really cool feature. I hope it will soon be available for
> windows as well.

Actually development for this initial version came to a halt when I went
to vacation and Peter Bjuhr started a full-time job. We are not more
than two seemingly minor issues away from integrating the tool into
Frescobaldi, but as this tool is awaiting significantly more development
we think we *have* to iron them out completely.

Urs

>
> Cheers,
> Klaus
>
>
> Am 14.11.2015 um 23:36 schrieb Simon Albrecht:
>> It is a feature of Python (in which frescobaldi is written) that a
>> program needn’t be compiled/installed to be run. You need to
>> 1. get the source files for frescobaldi and python-ly from
>> , either by downloading
>> 
>> and  or using
>> ‘git clone’ and checking out the ‘manuscript-viewer’ branch.
>> 2. add the following three lines to ~/.bashrc, where
>> path/to/python-ly and path/to/frescobaldi are the paths to the
>> respective directories:
>> # add python-ly to PYTHONPATH
>> PYTHONPATH=path/to/python-ly:$PYTHONPATH
>> alias frescobaldi='path/to/frescobaldi/frescobaldi'
>> 3. and then you can just run 'frescobaldi' on the command line to
>> test the feature.
>>
>> I hope that this is correct and will help; if there are any
>> questions, feel free to ask.
>> Yours, Simon
>>
>
> Am 15.11.2015 um 17:54 schrieb Federico Bruni:
>> Install git and run the following commands in the terminal:
>>
>> mkdir ~/src
>> cd ~/src
>> git clone g...@github.com:wbsoft/python-ly.git
>> git clone g...@github.com:wbsoft/frescobaldi.git
>> cp frescobaldi/frescobaldi.desktop ~/.local/share/applications/
>> sed -ir 's|Exec=.*$|Exec=sh -c "PYTHONPATH=~/src/python-ly python
>> ~/src/frescobaldi/frescobaldi"|'
>> ~/.local/share/applications/frescobaldi.desktop
>>
>> When you want to upgrade you enter the two sources and make a pull:
>>
>> cd ~/src/python-ly
>> git pull
>>
>> cd ~/src/frescobaldi
>> git pull
>>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Simon Albrecht]

On 14.11.2015 13:23, Klaus Blum wrote:

Is there any documentation out there that tells how to run a program from
git?
I have an Ubuntu installation, but no deeper Linux knowledge, so I've got no
idea what to do.


It is a feature of Python (in which frescobaldi is written) that a 
program needn’t be compiled/installed to be run. You need to
1. get the source files for frescobaldi and python-ly from 
, either by downloading 
 
and  or using 
‘git clone’ and checking out the ‘manuscript-viewer’ branch.
2. add the following three lines to ~/.bashrc, where path/to/python-ly 
and path/to/frescobaldi are the paths to the respective directories:

# add python-ly to PYTHONPATH
PYTHONPATH=path/to/python-ly:$PYTHONPATH
alias frescobaldi='path/to/frescobaldi/frescobaldi'
3. and then you can just run 'frescobaldi' on the command line to test 
the feature.


I hope that this is correct and will help; if there are any questions, 
feel free to ask.

Yours, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Klaus Blum]

Is there any documentation out there that tells how to run a program from
git? 
I have an Ubuntu installation, but no deeper Linux knowledge, so I've got no
idea what to do.

Thanks for any hint...
Klaus





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p183545.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 13.11.2015 um 17:22 schrieb Federico Bruni:
> Il giorno ven 13 nov 2015 alle 16:11, tapani  ha
> scritto:
>> Is there any way of getting this without running Frescobaldi from the
>> Git
>> repository? I run Frescobaldin in Linux, from installation files of the
>> latest stable version.
>
> I suggest using Git and clone frescobaldi and python-ly.
> All you have to is changing your frescobaldi.desktop file. Find
> attached what I'm using on my computer (I keep the git repositories
> under ~/src).
> The file should be saved in ~/.local/share/applications/

Probably adding python-ly to the PYTHONPATH environment variable, e.g.
in ~/.bashrc

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno ven 13 nov 2015 alle 16:11, tapani  ha 
scritto:
Is there any way of getting this without running Frescobaldi from the 
Git
repository? I run Frescobaldin in Linux, from installation files of 
the

latest stable version.


I suggest using Git and clone frescobaldi and python-ly.
All you have to is changing your frescobaldi.desktop file. Find 
attached what I'm using on my computer (I keep the git repositories 
under ~/src).

The file should be saved in ~/.local/share/applications/




frescobaldi.desktop
Description: application/desktop
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[tapani]

Is there any way of getting this without running Frescobaldi from the Git
repository? I run Frescobaldin in Linux, from installation files of the
latest stable version.
Tapani



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p183515.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 13. November 2015 16:11:54 MEZ, schrieb tapani <simoj...@yahoo.com>:
>Is there any way of getting this without running Frescobaldi from the
>Git
>repository? I run Frescobaldin in Linux, from installation files of the
>latest stable version.
>Tapani

I don't think so.

But running Frescobaldi from git should be easy on Linux.
>
>
>
>--
>View this message in context:
>http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p183515.html
>Sent from the User mailing list archive at Nabble.com.
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[MarcM]

Awesome. Does both the manuscript view and the lilypond preview view scroll
simultaneously ?
 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p183523.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 13.11.2015 um 18:41 schrieb MarcM:
> Awesome. Does both the manuscript view and the lilypond preview view scroll
> simultaneously ?
>  


Well, it is a loong way to go but the long-term goal is that they scroll
simultaneously, yes.
The user has of course to mark up the manuscript so Frescobaldi can know
where the measures are.

Basically the manuscript should always "be" in the measure that is
currently edited.

And it will be able to maintain different manuscripts to display the
"current" measure in the different
sources.


Phew. One day, that is ...













___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Hi Klaus,

thank you for your interest. It's surely possible to create Windows
binaries (more or less the same process as when preparing a release).
But I don't know how that works and how involved it is. And the problem
is that review is highly iterative, that means there are/have been
always new states to check. So actually there's no reasonable way beside
using Git for that process.

But we seem nearly there by now :-)

Urs

Am 18.07.2015 um 11:10 schrieb Klaus Blum:
 Hi Urs, 

 thank you for working on that feature. This is something I'm heavily
 interested in... 

 However, I'm a Windows user with absolutely no knowledge about using github
 and compiling source code. 
 Is there any chance to get binaries for testing? 

 Cheers, 
 Klaus




 --
 View this message in context: 
 http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p178754.html
 Sent from the User mailing list archive at Nabble.com.

 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Am 18. Juli 2015 09:11:24 MESZ, schrieb Federico Bruni f...@inventati.org:
Il giorno ven 17 lug 2015 alle 16:41, Urs Liska u...@openlilylib.org ha

scritto:
 Before merging it we would like to have a few people test it. If you 
 are
 running Frescobaldi from its Git repository we'd like to ask you to 
 pull
 the latest commits and checkout the 'manuscript-viewer' branch.
 You can then open 'Tools-Display manuscript', click on the help 
 button
 and start your review from there.
 Please test the tool, try to crash it and find any inconsistencies in
 behaviour or interface.
 Please also see our list of open discussion items at

https://github.com/wbsoft/frescobaldi/milestones/Initial%20Manuscript%20Viewer

Hi Urs

The tool is already great and hope it will be merged soon.
I only have a couple of suggestions for future development:


Thank you.

1. The  session should remember and open the last opened page in the 
manuscript.

Added as https://github.com/wbsoft/frescobaldi/issues/734

2. Any way to collapse/hide the manuscript  toolbar to have more space?

I had already commented on that inreply to your comment on github.


Thanks
Federico


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Klaus Blum]

Hi Urs, 

thank you for working on that feature. This is something I'm heavily
interested in... 

However, I'm a Windows user with absolutely no knowledge about using github
and compiling source code. 
Is there any chance to get binaries for testing? 

Cheers, 
Klaus




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p178754.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Federico Bruni]

Il giorno ven 17 lug 2015 alle 16:41, Urs Liska u...@openlilylib.org ha 
scritto:
Before merging it we would like to have a few people test it. If you 
are
running Frescobaldi from its Git repository we'd like to ask you to 
pull

the latest commits and checkout the 'manuscript-viewer' branch.
You can then open 'Tools-Display manuscript', click on the help 
button

and start your review from there.
Please test the tool, try to crash it and find any inconsistencies in
behaviour or interface.
Please also see our list of open discussion items at
https://github.com/wbsoft/frescobaldi/milestones/Initial%20Manuscript%20Viewer


Hi Urs

The tool is already great and hope it will be merged soon.
I only have a couple of suggestions for future development:

1. The  session should remember and open the last opened page in the 
manuscript.

2. Any way to collapse/hide the manuscript  toolbar to have more space?

Thanks
Federico


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Testing requested: new manuscript viewer tool for Frescobaldi

[Urs Liska]

Hi all,

Peter Bjuhr and I have been working on a new tool for Frescobaldi that I
have wanted to have for quite some time now. It's only the first step of
what it may become, but Peter was perfectly right by triggering actual
work with saying something is better than nothing. I think the
something we have now is already a very useful enhancement in itself.

It is a new manuscript viewer panel that can be used to have a
manuscript open within Frescobaldi. So if you are copying music from an
existing score you don't have to switch applications but can see the
engraver's copy, the LilyPond input and the engraved output in the same
window.


Before merging it we would like to have a few people test it. If you are
running Frescobaldi from its Git repository we'd like to ask you to pull
the latest commits and checkout the 'manuscript-viewer' branch.
You can then open 'Tools-Display manuscript', click on the help button
and start your review from there.
Please test the tool, try to crash it and find any inconsistencies in
behaviour or interface.
Please also see our list of open discussion items at
https://github.com/wbsoft/frescobaldi/milestones/Initial%20Manuscript%20Viewer

Thanks and have fun
Urs

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[flup2]

For the few testing I made, it's what I was looking for :-) I would like a
larger screen to put the preview and the manuscript side by side ;-) but in
the meantime, I'll place them one above the other

Thanks for that feature :-)

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p178739.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Testing requested: new manuscript viewer tool for Frescobaldi

[Chris Yate]

Sounds a good idea, I will try to test it tonight.

Thanks

On 17 July 2015 at 16:13, flup2 phili...@philmassart.net wrote:

 For the few testing I made, it's what I was looking for :-) I would like a
 larger screen to put the preview and the manuscript side by side ;-) but in
 the meantime, I'll place them one above the other

 Thanks for that feature :-)

 Philippe



 --
 View this message in context:
 http://lilypond.1069038.n5.nabble.com/Testing-requested-new-manuscript-viewer-tool-for-Frescobaldi-tp178737p178739.html
 Sent from the User mailing list archive at Nabble.com.

 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user