ZLauncherDB size and possible solution

[LukeBM]

I use ZLauncher as my favourite launcher, but besides the space it requires for the application, what concerns (and bother) me most is the space needed for the DB.

The question is: since the default launcher already stores many information in a separate DB file (e.g. program icons), is it possible to find a way to optimise ZLauncher so that it exploits this DB and adds only missing information?

We (ZL users) have for sure most of the info duplicated which eat precious RAM memory.

Any help/hint/suggestion is highly appreciated

thx

L.

[LukeBM]

alternatively I would like to get read of "psysLaunchDB" which takes up precious... some kBytes of RAM.

Is this feasible? Anyone with a workaround?

pleaseeeeeeeeeee.......

L.

[Serotta]

Yeah, between app, databases, and backgrounds ZL is using about 1.7 meg of memory on my device. 15%, but it's still worth it. But any way to whittle that down would be much appreciated.

[tanker_bob]

I use ZLauncher as my favourite launcher, but besides the space it requires for the application, what concerns (and bother) me most is the space needed for the DB.

The question is: since the default launcher already stores many information in a separate DB file (e.g. program icons), is it possible to find a way to optimise ZLauncher so that it exploits this DB and adds only missing information?

We (ZL users) have for sure most of the info duplicated which eat precious RAM memory.

Any help/hint/suggestion is highly appreciated

thx

L.
Well, that's not really practical. The default Palm launcher doesn't categorize apps on the card. It just stuffs them all in the card category. Plus, you'd have to carefully create duplicate the RAM app categories in both programs. But if you can't categorize apps on the card, what's the point?

ZL's preference dB is large because ZL has a huge number of preferences. Customizability & capability--that's the beauty of ZL over the competition. Without it, ZL wouldn't be ZL. Nothing comes free, though, especially in terms of memory/storage. As they say in Vegas, you gotta pay to play.

[LukeBM]

I agree on the setting part, but I don't see why we should have memory allocated for icons twice.

L.

[tanker_bob]

I agree on the setting part, but I don't see why we should have memory allocated for icons twice.

L.
Very practical reasons. First, if ZL were to use the Palm default application database as a source of data, then ZL would have to be modified everytime PalmOne, PalmSource, Sony, etc., changed the database format or launcher on a whim. This is what happened to third-party PIM developers when PalmOne changed to proprietary formats with the T3, TE, T5, and Treo 650, and Sony when they went to proprietary launchers and file managers. Second, access would be slower because you could never be sure that the user or the OS hadn't changed the category or location of an entry in the launcher dB using another app. You'd have to query the file every time to ensure that you could find the required icon. Also, ZL uses some different icons from the app file than the default launcher, so you'd still have to store some for every file.

Having all the information ZL needs in one location that only ZZTech can change makes sense in a host of ways. The database size penalty pales in comparison to depending on PalmOne's proven unreliability in working with third-party developers on basic database formats and access, or Sony's downright refusal to do so.