gtick-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gtick-devel] bigger resolution icon


From: Tomáš Hnyk
Subject: Re: [Gtick-devel] bigger resolution icon
Date: Fri, 08 Mar 2013 14:50:46 +0100
User-agent: Opera Mail/12.14 (Linux)

Hi
On Fri, 08 Mar 2013 14:11:55 +0100, Roland Stigge <address@hidden>
wrote:
Just re-checked the Debian Packaging Manual / Menu:
http://www.debian.org/doc/packaging-manuals/menu.html/ch3.html

"3.7 The icon field", 2. "The icons may not be larger than 32x32 pixels,
although smaller sizes are ok."

So the current Debian package quite fits the conventions.

Feel free to use the already existing icon64x64. If there's really sth.
bigger necessary for some reason, please tell.
Well, I am not sure what desktop you are using but both Gnome Shell and Unity use bigger icons by default (I am not sure of the size, Ubuntu is customizable but default is I think 64x64 or 48x48, Shell seems to be even bigger). This results in gtick icon looking ugly as it it either scaled out (Gnome Shell) or scaled out at once place (Launcher of unity) and small compared to others (in Unity's dash).

I am perfectly fine with copying the bigger icon so that it gets used, but I guess most people will not bother and would benefit from a bigger icon.


BTW, seeing that this project is still alive. Have you considered
implementing automatically changing meters? I have this one song where
you are supposed to start playing faster every 32 beats or so and gtick
does not help me to get it right at the moment.

How should changes be defined? By some kind of programmable tempo change?
Every beat? Every nth. beat? Freely programmable or by a certain pattern?
Supporting just a certain song wouldn't be the right thing to do...
Feel free to submit patches. :-)
I am afraid no patches from me in the foreseeable future (even though 2014 sounds nice), but the general desing I would prefer would be something like:

Profile_2_Name = Song
Profile_2_Speed_01 = 60
Profile_2_Beats_at_Speed_01 = 32
Profile_2_Speed_02 = 90
Profile_2_Beats_at_Speed_02 = 64
Profile_2_Meter = 4
Profile_2_Accents = 1

Which would produce 32 beats at speed 60 and then 64 beats at speed 90. (0 could stand for infinite number of beats) So this is freely programmable - that seems to be the easiest to implement. I do not expects this to get used so much (most of the songs keep the tempo the same throughout), but would be damn usefull for certain songs (and even maybe for general practice as one should be able to change playing speed quickly) Not sure about the gui implementation though.
Tomas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]