0
Completed

fully portable version?

Anonymous 11 years ago updated by Michael (Ramen Software) 9 years ago 8
I'm wondering whether there's much chance that this fine little app might be rendered fully portable - that is: no registry entries added / changed; no temp files (nor any other traces) used / left behind - perhaps in collaboration with the folks at PortableApps.com, so that it could be used on any computer, from just the one installation on a USB drive?


Answer

Answer
Completed

A "fully" portable version is available, read the FAQ for more info:

http://rammichael.com/7-taskbar-tweaker#faq

Answer
Completed

A "fully" portable version is available, read the FAQ for more info:

http://rammichael.com/7-taskbar-tweaker#faq

@ RaMMicHaeL: First, I want you to know that I love what 7tt does for me; and, I greatly appreciate all of your effort to develop & maintain this fine little app. Now, then, I'm the one who posted the initial question, after having read the FAQ to which you direct me, and trying to install 7tt to a USB drive (7tt is already installed on this computer's HDD).  Your FAQ states: "The only registry keys the tweaker modifies are it’s own settings."  Even though this indicates to me that 7tt is not fully portable (that is: can be installed to USB drive & used on any computer / user account without any Windows-registry entries being added / changed, etc.), I tried installing 7tt to a USB drive, anyway, only to get the "Already Installed" screen, allowing me only to "Reinstall" or "Uninstall" -- neither of which did I really wish to do with 7tt on the HDD.  But, I figure I'll try the "Reinstall" option, thinking that the installer will then allow me to choose Portable mode, and where to then install 7tt.  As you probably know, no such result occurred.  So -- even though I didn't wish to remove 7tt from C: drive -- I find that I must uninstall 7tt from HDD before I can then choose Portable mode after restarting 7tt's installer; then can I reinstall 7tt to C: drive

> Your FAQ states: "The only registry keys the tweaker modifies are it’s own settings."

This statement only applies to the non-portable version.

The portable version uses an .ini file to store it's settings.


> So -- even though I didn't wish to remove 7tt from C: drive -- I find that I must uninstall 7tt from HDD before I can then choose Portable mode after restarting 7tt's installer;

Unfortunately there is no option for portable installation in case the tweaker is already installed on your PC.

One workaround is to use the /portable command line switch, but it's probably not mentioned anywhere.

I've added it to the FAQ.

@ RaMMicHaeL: Thanx for both responses.

Hello, I really want to see a PortableApps.com release of 7+ Taskbar Tweaker, and I was looking at the information you've posted to the PortableApps.com thread about it, and wondering if your 'launcher' (7+ Taskbar Tweaker.exe) could take a command-line parameter like -ini "X:\PortableApps\7+TaskbarTweakerPortable\Data\7+ Taskbar Tweaker.ini" and pass that information to the 'main executable file', then the PortableApps.com launcher could simply launch your launcher with the appropriate argument(s) and I think the rest of your issues would be taken care of, except for the Start with windows option, which honestly, the control in the settings window shouldn't enabled when run in portable mode anyway.

I really hope to see 7+ Taskbar Tweaker Portable officially released on PortableApps.com soon. ☺
Hi,

As you can see on that thread, I provided a solution to the problem by allowing to set an alternative .ini file path in the original .ini file.
I also hope that the tweaker will get integrated into PortableApps in the near future.
I do see that you provided a possible solution, I meant this as an alternative implementation which you could consider, as portablizing with CLI options is often preferred as opposed to double config file data redirects by the PortableApps.com developers.

I don't think that this is the case here, as I'd have to redesign many aspects of the app to work correctly. For example, after an update, the tweaker is being relaunched. I'd have to relaunch it with the same path as the command line argument.
I think that the .ini redirection is a good solution for this use.