On Stripped 2.4.1, we can see "stripped Theme v2.3 Configuration" on top of the configuration screen. I think that displaying the version number of a theme (or a plugin) is a bad idea:
1) in this case the version number is false
2) users think it is the version of Piwigo
Version numbers are debug tools for advanced technical users.
Zaphod, can I remove this version number from the configuration page title?
Offline
In fact the number corresponds to the version of the file parameter.
v2.4 is the same as v2.3 so there is no update in the number displayed.
I agree it's purely a developer information...
It has to be displayed for now (but it can be displayed only in the code & not on screen) because I need it to know in which parameter version is the theme when I make the adaptation from one version to the other.
(anyway the parameter update system is too complicated... so I think I'll start from scratch with the next version (that will make user configure again the parameters if they update))
Offline
I just propose to remove it from display, not from code :-)
Offline
I am a little 'alarmed' at these proposed changes!
I find the Theme Version Number useful to know what version I am using. To put it another way, if I am on an old version and there are some new features that I want to use. In this case I alerted Pierrick as it said I was on v2.3 when it should be v2.4
Zaphod, you propose forcing the user to re-input the parameters after an upgrade. I think this would be a retrograde step! How are we supposed to remember the parameters we might have set up say a year ago and happily used since then?
(I did say a 'little' alarmed;)
Last edited by Tadjio (2013-04-04 14:32:07)
Offline
Hi :-)
I thinks we should add the 'i' tooltip on theme and language pages like on the plugin page
Offline
ddtddt wrote:
Hi :-)
I thinks we should add the 'i' tooltip on theme and language pages like on the plugin page
+1
remove the current display specific to stripped and use the "i" tooltip
Offline
Tadjio wrote:
Zaphod, you propose forcing the user to re-input the parameters after an upgrade. I think this would be a retrograde step! How are we supposed to remember the parameters we might have set up say a year ago and happily used since then?
What is complicated is when someone upgrades to 2.4 for example, he could be upgrading from 2.3 or from 2.2 or from 1.8 or from any other version...
When you have 10 previous versions or more, it becomes very complicated to manage.
A few versions ago, I introduced a paramater which clearly states the version (that's what is displayed if I'm correct), I'll probably continue to manage the parameters upgrade from this point.
The only way someone will have to reenter the parameter is when he upgrades from an old version of stripped linked to an old version of piwigo.
Offline
To manage (automatic) upgrade, check the way plugin Skeleton works with call to skeleton_init() in main.inc.php. This should be useable for themes too.
Offline
flop25 wrote:
ddtddt wrote:
Hi :-)
I thinks we should add the 'i' tooltip on theme and language pages like on the plugin page+1
remove the current display specific to stripped and use the "i" tooltip
Offline
done for themes
for languages, I don't know if it's really usefull
Offline