X-LibreOffice

[Danix]

How is it handling Java? If its installing, that's definitely not portable and I'm not aware of WinPenPack releasing a portable Java package.

We have developed a winPenPack utility called "JavaGet". This program, now contained in each X-Software that requires Java, manages the automatic installation or upgrade of the Java Runtime Environment (JRE) directly in the \Lib\Java folder. Then, at X-LibreOffice Portable first run, JRE is automatically downloaded and extracted in $Drive$\X-LibreOffice\Lib\Java\ folder (but only if JRE is not present in this directory). You can easily verify this by downloading and running X-LibreOffice (details..).



Please note that the folder "\Lib\Java" can be used by more X-Software. So, if in the winPenPack "Lib" folder are already present the "bin" and "lib" Java folders, or if you run the programs from a wpp suite, you don't need to re-install it anymore. In fact, the Java "installation" present in "\Lib" folder will be used by all X-Software requiring it.

What is the correct documents folder? What is the expected behavior? I ask because if you're suggesting C:\Documents and Settings\User\My Documents I don't think that's the most portable-friendly option.

The default "Documents" folder for X-LibreOffice is always within the X-Software structure, even if the drive letter or the software position changes: $Drive$\X-LibreOffice\Documents\. You can verify this by opening or saving a document and also from Options >> Paths.

Note that the "Documents" folder is also a folder shared by multiple X-Software.

Some users might not want a recent files listing, although admittedly that functionality should be capable of being turned on or off under preferences.

Honestly, I have not tested whether it is possible to turn on or off this option under preferences. But, anyway, I think this feature is an advantage: if you save/open files in \Documents folder (as well as the portabilization is prepared), all paths of recent files are normalized when the drive letter or the software position changes.

Hey guys, have a look here, at the top of homepage...
http://www.winpenpack.com/en/news.php
IMHO a NEW very nice package!

Thank you, stoned!
Now I moved the announcement here.

[webfork]

How is it handling Java? If its installing, that's definitely not portable and I'm not aware of WinPenPack releasing a portable Java package.

We have developed a winPenPack utility called "JavaGet".

Glad there's work on a portable Java happening. I've done a lot of work here in the forums on trying to get Java Portable / jPortable working portably with existing freeware.

Has anyone tested JavaGet for portability?

[webfork]

if I change the name of the folder containing the program, I get another very strange error: "The path to LibreOffice Portable has changed...some features may not work":

I just verified naxalite's problems with path portability.

[JohnTHaller]

I just verified naxalite's problems with path portability.

That's just a warning shown by the launcher itself because LibreOffice Portable is relatively new and path moving wasn't rigorously tested. It's not based on any known issues, just a precaution which is shown by default before we're positive the app can be properly moved. It will be disabled in the next update of LibreOffice Portable as no issues have cropped up with path moving since we launched it.

You can disable the warning by editing the LibreOfficePortable.ini file in App\AppInfo\Launcher and adding a line to the [Launch] section as follows:

DirectoryMoveOK=yes

That's the only change necessary, it affects nothing else other than showing that warning and is the exact change we'll be making to that file in the next release.

[webfork]

I just verified naxalite's problems with path portability.

That's just a warning shown by the launcher itself because LibreOffice Portable is relatively new and path moving wasn't rigorously tested.

Correction: I verified that this warning message pops up, not that there are actual issues with path portability.

[JohnTHaller]

Correction: I verified that this warning message pops up, not that there are actual issues with path portability.

Yeah, I knew what you meant

Incidentally, LibreOffice Portable will also work just fine from a path with spaces now. It was an old bug in earlier builds of OpenOffice.org and LibreOffice itself that we had the launcher trapping for to prevent users running and it just crashing. So, as with my previous post, you can edit the LibreOfficePortable.ini file in App\AppInfo\Launcher and alter the [Launch] section to be:

[Launch]
ProgramExecutable=libreoffice\program\soffice.exe
MinOS=2000
DirectoryMoveOK=yes

You remove the NoSpacesInPath line and add the DirectoryMoveOK line. LibreOffice Portable will now run from a path with spaces in it and work just fine when the relative path changes. We just left that check in for this release as the previous one still had some issues. The current LibO release seems to handle spaces properly now. We'll be making these changes to the next official LibreOffice Portable release as well.

[Danix]

X-LibreOffice has been updated to 3.4.0 version.

P.S.: I known (and I' m sorry) this isn't the right section of forum for the updates signallings. If you want I can start a new thread here.

[SYSTEM]

X-LibreOffice has been updated to 3.4.0 version.

Thanks!

P.S.: I known (and I' m sorry) this isn't the right section of forum for the updates signallings. If you want I can start a new thread here.

Eh, X-LibreOffice doesn't have a separate database entry. That subforum is designed for reporting updates of applications which have entries of their own.

This thread is exactly the right place to report updates of X-LibreOffice, at least for now.

[carbonize]

Isn't Java only required for the database stuff though?

[SYSTEM]

Isn't Java only required for the database stuff though?

You're right, one can usually use LibreOffice just fine without Java. Only some relatively complex functionality, like macros, requires Java.

[Danix]

If you don't wish to use Java in X-LibreOffice, open X-LibreOffice.ini and deactivate JavaGet.exe by placing a ; before RunFile:

[RunBefore]
;RunFile=$Lib$\Java\JavaGet\JavaGet.exe

[webfork]

Has anyone tested JavaGet for portability?

So this discussion hit sort of a stopping point because JavaGet hasn't been tested for portability. As the main WinPenPack launcher went dotNET recently, this is something that should get checked.

I could swear JavaGet was mentioned in some other article here on the site but I can't seem to find it.

[Danix]

So this discussion hit sort of a stopping point because JavaGet hasn't been tested for portability.

JavaGet itself has the only function to download and install JRE into \Lib\Java\ directory, therefore it does not have portability problems. But if you're referring to the portability of Java, when X-Software run, it creates a key in HCU (HKEY_CURRENT_USER\Software\JavaSoft) that, for our choice, we have preferred to leave unchanged.

As the main WinPenPack launcher went dotNET recently, this is something that should get checked.

About this part, the situation is long to explain..
Have you already seen this post?

[JohnTHaller]

As the main WinPenPack launcher went dotNET recently, this is something that should get checked.

About this part, the situation is long to explain..
Have you already seen this post?

He's referring to the fact that products that require .NET are not considered to be portable as the majority of Windows PCs do not have .NET pre-installed. Only Windows Vista and Windows 7 have it installed. Windows 2000 and Windows XP (about 60% of PCs) do not and only an administrator can install it. You can see a full analysis of it here: http://johnhaller.com/jh/useful_stuff/d ... able_apps/

[webfork]

So this discussion hit sort of a stopping point because JavaGet hasn't been tested for portability.

JavaGet itself has the only function to download and install JRE into \Lib\Java\ directory, therefore it does not have portability problems. But if you're referring to the portability of Java, when X-Software run, it creates a key in HCU (HKEY_CURRENT_USER\Software\JavaSoft) that, for our choice, we have preferred to leave unchanged.

A single, non-settings reg key affects stealth status, not portability so that shouldn't be an issue.

As the main WinPenPack launcher went dotNET recently, this is something that should get checked.

About this part, the situation is long to explain..
Have you already seen this post?

Yes, I posted your link here on the site back in December. I mention it in that context to say that what WinPenPack considers portable clashes with some users here and thus should see a bit more analysis. My issue with dotNET represents only some users here including myself and doesn't reflect site policy.