Hello
Because there is no general update and upgrade function for the installed apps, when i want to update i go on the portableapps site. i have to open every programm and check which version is installed and if there is some newer one (exept some progs like firefox or thunderbird which can make update themselfes)
It would be great to be able to see the programm version in portable apps for all programmes installed via paf.exe archives.
my idea:
for example add one more txt file called version.txt in the App or Data Folder of every app.
Now for example when doing mouseover with the cursor in the portable apps main menu on an application it dont show "Click to launch this app" but for example
Gimp v2.6 - Click to launch this app.
For exe files which dont have a version.txt it only showes "Click to launch this app"
Or insteat of showing the versions with mouseover maybe one point in the menu
"Programm Versions" where they are listed, or maybe one general text file where the versions are listed - but this is not good because to difficult when erasing a program folder f.x.
maybe we can find a easy solution
Its being worked on this.
First, never use the built in uzpdater in Mozillas Applications. It will break portability and mess with your locally installed version of the programm (if you have one).
Second, there is an Updater in the beta forums. But its still in the beta stage, that means it could be having issues although it works pretty stable for a lot of us.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
>First, never use the built in uzpdater in Mozillas Applications. It will break portability and mess with your locally installed version of the programm (if you have one).
ah okay i didnt know that - i thought he updates the portable version
maybe ff should be recompiled without this update function or modificied update function.
>Second, there is an Updater in the beta forums. But its still in the beta stage, that means it could be having issues although it works pretty stable for a lot of us.
ahhhhhhhhhhh very cool
even its still beta it feels a little bit like a package manager in linux
i like it!
A single death is a tragedy; a million deaths is a statistic.
Dur to Mozillas licensing, it cant be recompiled without nameiong it differently. John T. Haller, the guy who started this website and its head developper, has a special agreement so we can redistribute Firefox and still call it Firefox.
It says it right on the support page and in the forum, but unfortunately not on the Applications page itsfel.
I used to work but somwhere in version 2.?.?.? it got borked and now creates entries in your registry.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
right firefox policy changed but i didnt know this point.
this makes me sad that open when open source is very succesfull the policy changes and becomes commercial
other browser using the same engine like the iceweasel under linux dont have this problem right? thats all because we want to keep the name Firefox and the famouse logo right?
A single death is a tragedy; a million deaths is a statistic.
Its all so we can use the logo & name.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
I've always done the auto update and it works fine for me. Anyone else have experience with this. I usually only let it update at home so I doesn't do something while I'm doing something important and it doesn't affect my local version (running two profiles if that makes a difference) at all.
Release Team Member
but, if you use same version localy and update this one the same time, you might not notice it at first when using it home only.
The autoupdate will write half of its things to the hard drive instead to the stick and this is then where the mess starts.
Otto Sykora
Basel, Switzerland
I thought they fixed this? I remember it being marked as resolved on Bugzilla before FF3 was released...
Because I use FF portable a ton and haven't had this problem. I'd like to get Patrick or John to clarify this if they will.
Release Team Member