View Single Post
Posts: 176 | Thanked: 34 times | Joined on Feb 2008
#1
Originally Posted by konttori View Post
Theme maker does change the theme details in the repackaging process. So, version number should get updated as well.
I'm running into a problem.

I made a .deb of WhiteApps. I shut down Theme Maker OS X when I was finished.

Later, I decided to fix one or two things in WhiteApps so I went to the N800, chose another theme, uninstalled WhiteApps from the Application Manager and the folder where it was stored, went back to my desktop Theme Makder folder, went into the 'images' folder for WhiteApps to make corrections, opened up Theme Maker, changed the version number to '2', repackaged the WhiteApp.deb, transferred it over to the N800 and the version number is still '1'. The .deb had been unmodified.

I tried this again by opening up Theme Maker first and then making a really obvious change in a .png that I would notice right away (in case the .deb was altered but the version number stayed the same for some reason).

But, again, Theme Maker's repackaging process didn't produce a new, modified version of WhiteApps.deb.

Repackaging didn't do anything except tell me it was successfully repackaged (when the actual .deb is, in fact, completely unaltered).

My goal is to try to figure out:

1. how I can modify and repackage a .deb even if it isn't the last theme I made in Theme Maker (so I can go back and fix some other themes) and,

2. how I can modify and repackage a .deb even if Theme Maker has been shut down after my initial .deb session for that theme.

At this point, the only way I figure I can alter a theme that is not the last theme produced and after I've shut down Theme Maker is to create a 'dummy' theme, with a different name, create a .deb, go to the 'images' folder of the 'dummy' theme and replace everything with the .pngs from my modified WhiteApps 'images' folder and repackage it under the new theme's name.