I'm sure there are tools which would make it easier for us, simple not hackers,
but software engineers, grown up on Microsoft Visual Studio end Eclipse. I
remember that at university I did use some ide for linux cpp development.
That's why I was seeking recommendation.
Bert
Original mes
On 6/13/09 8:43 AM, "Bertalan Fodor" wrote:
> What tools can be used to develop? To debug, browse the source, etc?
Compiling: gcc
Debugging: gdb
Guile/Scheme testing: guile
Browse the source: more, vi
Search the source: git grep
HTH,
Carl
___
l
>From NR 6.5.2 Running a function on all layout objects:
#(define (blanker grob grob-origin context)
(if (and (memq (ly:grob-property grob 'interfaces)
note-head-interface)
(eq? (ly:grob-property grob 'staff-position) 0))
(set! (ly:grob-property grob 'transparent) #
Le 14/06/2009 01:33, Graham Percival a écrit :
Umm, I'm expecting to almost-completely rewrite the website in the
next few days. I'm really not certain that starting to
translating the website now is a good idea.
Tentative new website ready (i.e. start translating): late June.
If this ca
On Sun, Jun 14, 2009 at 01:04:13AM +0200, John Mandereau wrote:
> After that, it would be best translating the lilypond.org main web site
> before translating the rest of the documentation, as the former has much
> more audience than the latter.
Umm, I'm expecting to almost-completely rewrite
Le 13/06/2009 19:25, Federico Bruni a écrit :
I've read that page and started the first steps.
Dear Federico,
Sorry for the slightly delayed reply, and congratulations for your
involvement in translation of our (huge) documentation. Carl answered
your questions quite well; I'll apply your pa
On 6/13/09 11:25 AM, "Federico Bruni" wrote:
> Carl D. Sorensen wrote:
>>
>>
>> On 6/9/09 10:39 AM, "Federico Bruni" wrote:
>>
>> Great!
>>
>> John Mandereau is the translation meister. I've copied him on this reply.
>>
>> The first step toward developing a translation is to read the
Graham Percival wrote:
3) Ok, so why do I want to use texinfo so much?
- makes pdfs+info. I personally *never* use those formats, but I
know that some people still use them. IMO, if we're going to
support those formats for the manuals, we should support them
for the information that's o
On Sat, Jun 13, 2009 at 11:14 AM, Graham
Percival wrote:
> To counter-act the "texi2html looks boring" idea, here's a new
> version:
> http://percival-music.ca/blogfiles/out/lilypond-general_1.html
Cool! I think this is a definite improvement to the website's
organization. I really wish we could
2009/6/13 Graham Percival :
> To counter-act the "texi2html looks boring" idea, here's a new
> version:
> http://percival-music.ca/blogfiles/out/lilypond-general_1.html
You haven't asked for comments but here they are anyway:
-- The garish colours and backgrounds look bad.
-- Red-text-on-black-im
To counter-act the "texi2html looks boring" idea, here's a new
version:
http://percival-music.ca/blogfiles/out/lilypond-general_1.html
1) *NO*, I don't think the garish colours and backgrounds look
good. I'm showing that we can do whatever we want, not proposing
that red-text-on-black-image is ea
What tools can be used to develop? To debug, browse the source, etc?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
12 matches
Mail list logo
