From: Henry S. <henryst@MIT.EDU> - 2001-11-27 07:45:49
|
I really don't know anything about MAKE files and such, so I don't know how hard or easy it is. But do you guys think it would be a problem to have the binaries after a compile be in the main directory instead of in "gui" and "sequencer" If it is a problem don't worry about it, because I can live with it...I just thought it may be a convenience that might as well be implemented early if at all. The reasons are: I have the old rosegarden installed, so I can't do a "make install" (well I'm sure with some tweaking I could get them to co-exist...but I don't like having development stuff actually installed anyway) Secondly, since I'm not doing a "make install" it can't find the sequencer if I run rosegarden (well it does now because I created a link to it). Thirdly, I like to use KDevelop and it assumes that the binary is going to be in the main directory. ********************************************************************* I'm still just looking through the code to get an understanding. But I don't know if I'll really have much time with finals coming up and all. I've also been thinking what could be done to really make rosegarden stand out. I'm really into good user interfaces, but can't think of anything that would be better than the interface EVERY existing program has...which is [Track View] NAME VOLUME PAN INPUT | Meas1 Meas2 Meas3 Meas4.... Then you right click on these and you can get new windows with staff view, piano roll or audio view. As I mentioned before I don't like lots of little windows around(it overwhelms users). I'm still trying to think of ways to reduce these. One idea I've had is having a collapsable sidebar for the option-type stuff. It is pretty rare that you need to tweek those things, so you don't need to see them constantly (I'm talking about things like PAN and INPUT) I've got other ideas. Whenever they get more concrete I'll let you guys know. Regards, Henry Stanaland |
From: Guillaume L. <gla...@te...> - 2001-11-27 10:41:06
|
On Tuesday 27 November 2001 08:38, Henry Stanaland wrote: > I really don't know anything about MAKE files and such, so > I don't know how hard or easy it is. But do you guys think > it would be a problem to have the binaries after a compile > be in the main directory instead of in "gui" and "sequencer" Yes. The whole automake/autoconf mess is something which we get from KDE and works "well enough" at the moment. It will not be touched unless absolutely necessary. > I have the old rosegarden installed, so I can't do a > "make install" (well I'm sure with some tweaking I > could get them to co-exist...but I don't like having > development stuff actually installed anyway) I don't understand this. As far as I know, at the moment Rosegarden will not function unless installed in your regular KDE directory, which should be different from where the old rosegarden is installed (unless you're using a distrib which puts KDE in /usr, but then you can put RG2.1 in /usr/local. It's perfectly alright for both applications to be installed at the same time. > Thirdly, I like to use KDevelop and it assumes > that the binary is going to be in the main > directory. I'm not sure how kdevelop can be configured to be a bit more clever than that... -- Guillaume http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2001-11-27 13:29:11
|
Guillaume Laurent wrote: > On Tuesday 27 November 2001 08:38, Henry Stanaland wrote: > >>could get them to co-exist...but I don't like having >>development stuff actually installed anyway) > > [...] As far as I know, at the moment Rosegarden will not > function unless installed in your regular KDE directory That was my understanding too, although it's a situation I very much dislike. At the moment I usually run "make install" first, and then go and delete the Rosegarden binaries and shared libraries from the KDE directories (leaving the pixmaps and .rc files), then run the application from the build directory. Otherwise I find myself getting horribly confused when a library changes and the wrong shared library file gets picked up. Even this way, I get horribly confused when I forget to update a pixmap or .rc file. And of course you're absolutely stuffed if KDE is installed as root and you don't have root privileges. Chris |
From: Guillaume L. <gla...@te...> - 2001-11-27 23:56:40
|
On Tuesday 27 November 2001 14:28, Chris Cannam wrote: > At the moment I usually run "make install" first, and then go and > delete the Rosegarden binaries and shared libraries from the KDE > directories (leaving the pixmaps and .rc files), then run the > application from the build directory. Mmm, only the sequencer uses a dynamic library, and then if I recall correctly it's an aRTS module. I'm not sure I understand why you remove the rosegarden binaries and shared libs from the install dir. I just run 'make install' whenever something in the structure has changed (new icon, change in rc file), and always run from the gui directory. I don't think I had a problem... > And of course you're absolutely stuffed if KDE is installed as > root and you don't have root privileges. I think you can put things in your ~/.kde then. -- Guillaume. http://www.telegraph-road.org |
From: Henry S. <henryst@MIT.EDU> - 2001-11-28 03:25:44
|
> and always run from the gui directory. Doesn't it complain about not finding the sequencer then? Or did you add that directory to your path. Henry |
From: Guillaume L. <gla...@te...> - 2001-11-28 09:41:40
|
On Wednesday 28 November 2001 04:18, Henry Stanaland wrote: > > Doesn't it complain about not finding the sequencer then? No, the sequencer is normally installed in my KDE dir, which is where it looks for it. -- Guillaume http://www.telegraph-road.org |
From: Guillaume L. <gla...@te...> - 2001-11-28 10:07:55
|
On Wednesday 28 November 2001 00:56, Guillaume Laurent wrote: > On Tuesday 27 November 2001 14:28, Chris Cannam wrote: > > > And of course you're absolutely stuffed if KDE is installed as > > root and you don't have root privileges. > > I think you can put things in your ~/.kde then. Even simpler, you can use KDEDIRS. -- Guillaume http://www.telegraph-road.org |