Active Topics

 


Reply
Thread Tools
Posts: 123 | Thanked: 457 times | Joined on Feb 2012
#41
Originally Posted by Kozzi View Post
Can I alter configurations in meegotouchhome.css or statusarea.css from base theme using custom theme that inherits blanco ?
Yes. Blanco inherits and overrides base, so if your theme inherits blanco, you can override things defined in blanco and base.

Originally Posted by Kozzi View Post
Can you post a guide how to package a custom theme to .deb using Qt Creator ? This would seriously help many users in creating themes from custom icons.
The original post mentions the example theme:

Originally Posted by Vesuri View Post
An example theme package that changes the background color of each home screen page (not recommended to be done in a theme) is provided on the support page of Theme settings.
The source package for the theme is provided as well. It includes an application which checks whether Theme settings is installed and if not, asks the user whether to install it from the Store, which of course doesn't work anymore since the application has been removed from the Store. There's also a source package which doesn't include the checker application.

Refer to the existing themes (blanco, mostly) to see where to put which files and what the modifiable items are. Most icons are in themename/meegotouch/icons and library/application specific styles in themename/meegotouch/binaryname/style. Theme wide constants are in themename/meegotouch/constants.ini.

It should be noted that if there's a problem with a CSS file the application probably won't start. This means that if you break a CSS file needed by a system application (like the home screen) the system application won't start and the device may go to an unrecoverable reboot loop. It's a good idea to do theme development on a single custom application that isn't critical for the system OR to be ready to flash the device when things go wrong.

Last edited by Vesuri; 2012-08-10 at 10:47.
 

The Following 2 Users Say Thank You to Vesuri For This Useful Post:
Posts: 216 | Thanked: 81 times | Joined on Mar 2012 @ Mars
#42
Hey vesuri,is there a way to download v 0.1.1 manually? Because i cant seem to update it,Thanks
__________________
If i helped you,please kiss the Thanks Button
Thank you
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#43
Hi Vesuri is there any limit on the number of themes that theme settings is able to display? On my device it can display a maximum of 19 themes before it stops displaying any newer themes...

I'm asking this instead of investigating whether something is wrong with the theme(s) [I've checked the theme(s) too but can't find anything irregular in them compared to the others on my system] as ThemeChanger only displays a maximum of 10 themes...


Edit: Also as you have mentioned above that blanco overrides base, it means any theme that inherits blanco should override base too then why do the boot and splash images even when placed in the custom theme still read from blanco and not the custom theme?
 
Posts: 123 | Thanked: 457 times | Joined on Feb 2012
#44
Originally Posted by ThraxZzz View Post
Hey vesuri,is there a way to download v 0.1.1 manually? Because i cant seem to update it,Thanks
It's available on the Theme Settings page.

Originally Posted by thedead1440 View Post
Hi Vesuri is there any limit on the number of themes that theme settings is able to display? On my device it can display a maximum of 19 themes before it stops displaying any newer themes...
There shouldn't be such a limit there. Interesting. It does use a standard libmeegotouch component (MComboBox) for the theme selection UI, so maybe there's a limit there. That sounds weird as well, though. Interesting :O
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#45
I've uninstalled 13 themes from my system yet newer themes don't get detected...even those that previously used to work now after uninstallation and re-installation don't get detected...Strange indeed...
Maybe I broke some functionality? The folders are in /usr/share/themes/ and both theme settings and ThemeChanger don't detect them...
 
Posts: 123 | Thanked: 457 times | Joined on Feb 2012
#46
Originally Posted by thedead1440 View Post
Also as you have mentioned above that blanco overrides base, it means any theme that inherits blanco should override base too then why do the boot and splash images even when placed in the custom theme still read from blanco and not the custom theme?
Which files do you mean exactly by boot and splash images?

If you mean the NOKIA logo shown at startup and the startup animation, those are not coming from the theme. The very first NOKIA logo comes from the boot loader (NOLO) and can't really be changed. Then the same logo gets displayed by MProgressIndicator and that stuff is under /usr/share/MProgressIndicator. It can only be changed the ugly way by modifying and replacing some files there, not by theming.
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#47
Originally Posted by Vesuri View Post
Which files do you mean exactly by boot and splash images?

If you mean the NOKIA logo shown at startup and the startup animation, those are not coming from the theme. The very first NOKIA logo comes from the boot loader (NOLO) and can't really be changed. Then the same logo gets displayed by MProgressIndicator and that stuff is under /usr/share/MProgressIndicator. It can only be changed the ugly way by modifying and replacing some files there, not by theming.
Yup I understand about /usr/share/MProgressIndicator...

I didn't know about the NOLO images...

These are the files that can't be changed using a custom theme:

/usr/share/themes/blanco/meegotouch/images/splash/*ALL*

/usr/share/themes/blanco/meegotouch/images/system-services/booting.png
 
Posts: 123 | Thanked: 457 times | Joined on Feb 2012
#48
Originally Posted by thedead1440 View Post
The folders are in /usr/share/themes/ and both theme settings and ThemeChanger don't detect them...
Check the permissions of the folders. The folders and the files in them need to be user readable, not just root. Maybe they're now only readable by root?
 

The Following User Says Thank You to Vesuri For This Useful Post:
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#49
Code:
RM696-21-3_PR_005:~# ls -l /usr/share/themes/
total 40
drwxr-xr-x    4 root     root          4096 Aug 10 21:43 base
drwxr-xr-x    3 root     root          4096 Aug 10 21:43 blanco
drwxrwxr-x    3 root     root          4096 Aug 17 01:26 faenza
drwxr-xr-x    3 root     root          4096 Aug 18 20:11 fdb-bluev7.0a8
drwxr-xr-x    3 root     root          4096 Jul 23 01:53 fdb-green
drwxr-xr-x    3 root     root          4096 Aug 18 20:12 fdb-originalv7.0a8
drwxr-xr-x    3 root     root          4096 Aug 31 00:14 fdb-originalv7.1a1
drwxr-xr-x    3 root     root          4096 Jul 23 01:43 fdb-red
drwxrwxr-x    3 root     root          4096 Aug 31 00:40 fdb-red-test
lrwxrwxrwx    1 root     root            50 Jul 31 13:28 magenta -> /opt/meegotouchtheme-settings/share/themes/magenta
drwxr-xr-x    3 root     root          4096 Aug 16 09:53 vistav2
From the above fdb-red-test has the same permissions as faenza yet faenza gets detected...

Originally fdb-red-test was drwxrwxrwx but i chmod 775 it yet no difference...Anything I'm doing wrong?

Thanks...


Edit: fdb-originalv7.1a1 doesn't get detected too while fdb-originalv7.0a8 does


Edit2: doing as user in terminal:
Code:
gconftool -s --type=string /meegotouch/theme/name fdb-originalv7.1a1
doesn't change the theme to fdb-originalv7.1a1 but theme settings shows blanco as being applied when in reality my previous applied theme (fdb-originalv7.0a8) was still applied...

Last edited by thedead1440; 2012-08-30 at 16:55.
 
Posts: 123 | Thanked: 457 times | Joined on Feb 2012
#50
Check the index.theme files in those folders as well. Those are the files that matter for the detection.
 

The Following User Says Thank You to Vesuri For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 19:57.