RSSOwl 2M9 Portable Dev Test 4

Your launcher has a bug as it searches for Java Portable in $EXEDIR, but not in the default common files directory, try getting the root and give path manually in your code on line 94.

The final edited and tested code for the Java Portable:

lines:93-97
${GetRoot} "$exedir" $R0
StrCpy $DRIVELETTER $R0 1

UsePortableVM:
StrCpy $EXECSTRING `"$PROGRAMDIRECTORY\$PROGRAMEXECUTABLE" -vm "$DRIVELETTER:\PORTABLE APPS\COMMON FILES\Java\bin"`

Great addition to the PA portfolio! Thanks.

Have installed Java Portable and RSSOwl on a portable device and want to direct RSSOwl to use only that JVM. Adding the -vm launch parameter as described in the thread you reference involves a known, fixed drive letter. How would you adjust parameters for a drive letter that varies? Is there a relative drive variable, or similar method, that the RSSOwl launcher will parse in order to explicitly use the portable JVM, rather than a local JVM, when the assigned portable device drive letter changes?

Yeah, I tried that too. It uses Iron as the external browser, but does nothing internally. lol

Yup - it worked that way. Now I have to find the feeds database and delete it maybe - I guess that's where the problem is most likely to be.

EDIT: I found the DB file Data\.rssowl2\.metadata\.plugins\org.rssowl.core\rssowl.db and deleted it - it all worked afterward. Of course all my subscriptions were lost but good that I have a backup OMPL file... just in case.

im confused, how exactly can i pass -noSplash switch to portable launcher??

Java is supposed to ONLY be located at this location at the current time in relation to the platform.

Damned ! It's very limited.

However OpenOffice Portable Edition doesn't work that way.

CheckJavaCommonFiles:
${GetParent} $EXEDIR $PORTABLEAPPSDIRECTORY
IfFileExists "$PORTABLEAPPSDIRECTORY\CommonFiles\Java\javaportable.ini" "" LaunchNow
StrCpy $JAVADIRECTORY "$PORTABLEAPPSDIRECTORY\CommonFiles\Java\"
ReadINIStr $JAVAVENDOR "$PORTABLEAPPSDIRECTORY\CommonFiles\Java\javaportable.ini" "JavaPortable" "Vendor"
ReadINIStr $JAVAVERSION "$PORTABLEAPPSDIRECTORY\CommonFiles\Java\javaportable.ini" "JavaPortable" "Version"


Why don't you use the same technique for RSSOwl Portable Edition ?

For the caching issue, why don't you force RSSOwl Portable Edition to use an External Browser (Preferences->Browser->Use the following external Browser) ? Firefox Portable Edition for instance. What do you think ?

But may I insist to not modify any file in the RSSOwl distro. Eclipse RCP provides an easier solution to apply customization. As stated in my previous post, you could provide a custom "RSSOwl.ini" file to "RSSOwl.exe" to apply the same effect.

1) Please don't touch anything in original "RSSOwl.ini" (folder "$PROGRAMDIRECTORY"):

-vmargs
-Xms15m
-Xmx192m
-Dosgi.requiredJavaVersion=1.5


Instead create a copy of "RSSOwl.ini" in folder "$SETTINGSDIRECTORY". And apply any modification you might require. But you could keep it without any modification if you want.

Then to use this copy instead of the original file in folder "$PROGRAMDIRECTORY" you must pass the following parameter to "RSSOwl.exe":

--launcher.ini "$SETTINGSDIRECTORY/RSSOwl.ini"


RSSOwl will now use this customized file rather than the original one.

2) Keep also "config.ini" untouched (folder "$PROGRAMDIRECTORY/configuration"):

# RSSOwl 2.0 runtime configuration file
#
# This file contains a number of key/value pairs that are merged into the
# System properties on system startup. The values control the way the
# runtime is structured and runs.

# End of file marker - must be here
eof=eof


Instead you must pass the additional following parameters to "RSSOwl.exe":

-data "$SETTINGSDIRECTORY/.rssowl2"
-configuration "$SETTINGSDIRECTORY/.rssowl2/config"


This will overwrite at runtime the original values of the following parameters setup in the original file "config.ini" (folder "$PROGRAMDIRECTORY/configuration"):

osgi.instance.area.default=@user.home/.rssowl2
osgi.configuration.area=@user.home/.rssowl2/config200


Please note also that it is recommended to use "$SETTINGSDIRECTORY/.rssowl2/config" instead of "$SETTINGSDIRECTORY/.rssowl2/config200".

It is always a bad idea to hardcode a version in the folder name. What will happen when RSSOwl will be upgraded to version 2.0.1 ? You will have to migrate all the settings from "$SETTINGSDIRECTORY/.rssowl2/config200" to "$SETTINGSDIRECTORY/.rssowl2/config201".

If you follow all my recommandations, you will not have to change anything to you portable launcher nor to the settings. All you will have to do is to upgrade the RSSOwl distro without changing anything. Easy, isn't it ?

If you don't understand any part of my recommandations, don't hesitate to contact me directly for assistance

Cheers,

Bertrand

So the X:\PortableApps\CommonFiles\Java is an absolute path then? I thought it was looking in a relative path like dir-where-rssowl-and-commonfiles-are/CommonFiles/Java... in other words I thought the X:\PortableApps\ part didn't matter as long as both RSSOwlPortable and CommonFiles were in the same folder.

My bad.