On Tue, 30 Oct 2001, Asger K. Alstrup Nielsen wrote: > I write to you because there is interest in supporting NoteEdit in LyX.
First of all: I'm interested in all improvements. BTW: Some users wrote me whether I could implement a closer association between Noteedit and the TeX tools to achieve a more useable printing procedure. (An unwanted side effect is: A closer association would hide the fact that the beautiful music sheets are a (La)TeX result not a Noteedit result.) The problem is: I'm not a LyX user and so I didn't comprehend all exactly. > > The general idea is this: The user can choose to insert a NoteEdit > document in a special inset in LyX. This will appear in the shape of a > button with the name of the file in the user's document in LyX. When > he clicks on this, LyX will invoke NoteEdit with the NoteEdit file for > editing. I.e.: The noteedit main widget with some (all ?) buttons. > Then, when the user wants to preview or print his document, LyX has to > create the needed output in the background. For this purpose, LyX has to > convert the NoteEdit file to Lilypond format, This is important: The file format or the internal data structures ? If Noteedit is embedded into a LyX widget and a score is loaded then there exists an internal main memory presentation of the score. And this I could easy convert into LilyPong (or MusiXTeX) data. Whereby "data" could be a file of a long string in main memory. > > However, we can not automate this completely, because it seems that it > is not possible to export a NoteEdit file to Lilypond format from the > command line. Therefore, we would politely ask if it was possible for > you to implement this feature. Perhaps I could supply an option "--hidden" (or so) which causes noteedit to not show any window but to perform some operations (for instance reading an input file and export to a LilyPond file. But if I comprehended this right: Noteedit runs in an embedded LyX widget (?) and in this case LyX could send a signal (or so) to cause Noteedit to produce the LilyPond ouput from main memory structure.(?) > > If we had this, both NoteEdit and LyX would be more interesting products: > LyX would be the first word processor that supported very beautiful music, > and NoteEdit on the other hand, could benefit from the ease of use that > LyX provides, which would make it easier to produce complete documents > with music in them. Yes, of course! > > I had a brief look at your source code, and it seemed that you already > have done a lot of the work as part of the KParts architechture. However, > we would prefer a solution that is independent of the KDE infrastructure, It is possible if you mean: "independend of KParts" but "independend of KDE" won't be possible. > because we would not want LyX to link to the KDE libraries. I think it is possible to make the "NoteeditFactory" more flexible. It could create a KDE/Qt widget which can be placed as child of another Qt/KDE widget somewhere on LyX surface. -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED])
