Hi Robert, Thanks for the hint with regards to the terms "clone" and "git". So from now on I will try not to use the term "clone", but "git" when I refer to a new git version of MusE. Yes, I know what cloning means within MusE: one can clone parts instead of copying them.
> When you don't have the git source code 'git clone' is used > to get the complete repo, after that it is better to use 'git pull' > to only get the updates to what you already have. And building and > installing again I already know this, but nevertheless thanks ;-) > If someone feels up to making a nice splash that would be good :) I just tried to create a splash image for the 3.0 release, by using the current splash image of version 2.2, but there is a problem: The background color in the splash image of version 2.2 is a grey-to- nearly-white gradient if one looks at this image from the left to the right. If I want to replace the characters "2.2" in the middle of the splash screen of version 2.2 in GIMP., then I first need to cover these characters with a grey tone. But because the background color is a grey- to-nearly-white gradient, it is merely impossible to cover these characters with a single grey tone without the effect that the result of such an operation looks ugly. If we want to keep the splash image of version 2.2. and replace the characters "2.2" in the middle of that image by the characters "3.0", then we need the original pciture editing file of that image, possibly created with GIMP. Because I guess that this orginal picture editing file contains different layers where one of these layers contains that grey- to-nearly-white gradient. If this would be the case, then it would be easy to replace "2.2" by "3.0". Does anybody have the original pciture editing file of the splash image of version 2.2? > Tim's things are not merged yet, Oh, I did not know that. > It is > hard to point at specific things to test, just trying to use the git > master for creating music goes a long way to help us. Shall I wait with creating a new complete song for testing purposes after Tim's implementations have been merged into the git master, or shall I create a new complete song now? Regards, Jens Am Samstag, 24. Oktober 2015 schrieb Robert Jonsson: > Hello Jens, > > 2015-10-23 15:41 GMT+02:00 Jens Radloff <[email protected]>: > > Hi guys, > > > > I successfully could compile the latest clone version of MusE. > > This might seem like a small thing, well it is a small thing ;) but > could you call it MusE git (master if you want to be explicit) > instead of clone? Someone, can't remember if it was you had a > problem with the muse feature 'clone' and it got confusing. > > And when it comes to cloning, usually you don't need to redo this > step when someone has added a fix or improvement to the development > version. When you don't have the git source code 'git clone' is used > to get the complete repo, after that it is better to use 'git pull' > to only get the updates to what you already have. And building and > installing again. > > > Small detail: that splash screen that shows up when starting MusE > > 3.0 still shows version number 2.2. > > If someone feels up to making a nice splash that would be good :) > > > I could play the three complete MusE songs that I created so far > > without any error. > > Great! > > > If I should test something, then please tell me. Probably I would > > need some assistance to create songs that can be tested against > > the new features of the new MusE version because I consider myself > > not yet to be an advanced user of MusE. > > Tim's things are not merged yet, these will need more targeted > testing but for now the main change is the move to Qt5 which may > have broken things in the gui that we haven't noticed yet. It is > hard to point at specific things to test, just trying to use the git > master for creating music goes a long way to help us. > > > Regards, > Robert ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
