PokerTracker4 "Portable"

[_dave_]

I would love to see a PT4 "portable" version, similar to Firefox, VLC, and many other large applications have available.

It used to be like this in the days of PT3. Onc could comfortably install a new version to a different folder, and they they would not interfere with each other. These days it is awkward to set up a PokerTracker in a controlled environment, without sacrificing your current "known good" setup. A Portable version would solve this brilliantly. A simple ZIP that can be extracted and run from any folder, that doesn't go near %APPDATA% or any other shared locations on the file system.

Fingers crossed :)

[kraada]

Interesting request. Can you give me a few reasons why you might want to use this on a system with a known good working copy of PT4?

[_dave_]

Now is an appropriate moment - 4.11 Beta just released, tons of new features for people like me, would like to check it out asap! but reports of problems surface as always. I require to have a working PT4 at all times, otherwise I cannot play poker, and I cannot provide support for my students. I could juggle config files and such to ensure I can always roll back, but it's more trouble than I'd like.

Another benefit is that as a hud/stat developer, it would be nice to maintain some kind of separation between setups. As an example let's say you install Kraada's hand rage popups, coffeehud, propokerhuds, and a few others and also some reports from the Download Warehouse. Now there are thousands of custom stats in "configure statistics", hard to tell where they are from. Even harder to remove them accurately. If I want to install someone's HUD as a test, someone has asked me "hey, I made this HUD can you check it out, let me know what you think, any tips?". I'd like to say "Sure!", but I'm thinking ugg, do I really want more junk in my PT4 that I can't easily remove... It'd be awesome to just unzip a portable to a new folder, connect to a test database and check it out in isolation without any contact whatsoever to my normal PT4 setup. Even more so now that any superflous custom stats will increase the rebuild cache / hand import time (probably negligible on their own, but in their hundreds/thousands not so confident). Would also be nice for testing hud releases and the like.

[StevenM]

-dave_ : Interesting idea, but I see a flaw with the concept, lets see if we can flesh this out with you. How would you get around the need to access existing PostgreSQL databases? For example when we release an update there may contain database revisions, once those revisions are rolled out the database cannot be reverted. Of course this also opens up the issues such as how PostgreSQL credentials are stored.

If we can come up with answers to questions we have here, and the answers are feasible and easy to work out, then I am certainly willing to take this idea to others within our company to get a consensus. Balls in your lap, its not just the storage of the User Data Folder, there are other issues to consider to assure a working solution. Thnx

[PJs Ronin]

@ _dave_
I am of the same opinion (need for a 'lite' or 'portable' version of PT) but never thought the developers would follow this route, so I started isolating my PT/poker client setup into different VMs. Hell, I even have an old setup with PT3 sitting in splendid isolation in a Windows XP VM (worked a treat). However, despite my best efforts there comes a time when the poker clients do an upgrade that forces PokerTracker to follow suit and that results in the whole setup within a VM going to the dogs.

From what I've seen of the problems highlighted with PT4.11, I believe there are two causes; the proliferation of custom stats (of dubious value) and the multi-Gb databases of 'bought' data. I'm not sure PT can, or should, do anything when updates to these systems either takes forever or grinds a users computer to a halt. However, I do not believe that SnG/MTT players need a fraction of the functionality contained in PT4 and that a 'lite' tourney version is worth consideration. Perhaps the same argument could be used for a rec cash player.

I seem to remember an old quote about Microsoft Excel. "80% of users only use 10% of the applications functions" and the same could apply to PT4. Then again, 79% of all statistics are made up as required.

In re-reading your op, I am more inclined to believe that VMs are probably the way to go for you. A master VM with PT4 and clients set up bog standard. When you want to try something new, clone the VM and test in the clone. At the end, light a match and 'poof' clone be gone and your original config is still intact. Sorry if I'm telling you how to suck eggs.

[_dave_]

PJs - yes VMs would provide a similar benefit, but it's a lot of duplication to create multiple working environments. Added performance penalties too, which when dealing with PT4 is something preferably avoided! VMs also do nothing to prevent the ridiculous situation of the last few days.

Steven - what you point out as a flaw, is basically the point!By default a fresh installation to a new folder (not an upgrade) knows nothing of existing databases. If you want a new version PT4 to access an existing database, you would add it with the "this database already exists" button on database management -> new. A sensible method would be to duplicate a databse in postgres before doing this. Postgresql credentials and the like are stored in pokertracker.cfg, same as always. Except pokertracker.cfg is not a single file shared between any pokertracker on the system, it is in the folder tree with the rest of that PT4's files.

An example use case from yesterday:
- PT 4.11 / 4.11.1 is a problem, many players cannot grind on a weekend.
- open 4.10.x, connect to 4.10.x database, wait for dust to settle.
- continue being able to open 4.11.1, connected to it's own database, to investigate

Without the need to juggle config files, and run the risk of saved stats / huds / databases being irrevocably altered

[StevenM]

To simplify your suggestion, you sugest we just need to unify the storage location of pokertracker4.cfg, at which point you belive PT4 can be made into a portable solution?


I see some other conflicts that would affect future features that you have yet to see, as well as problems integrating our new Premium Add-Ons which are pushed to the end user. Still an interesting topic to consider for the future. Our staff accomplishes our needs currently by using multiple VMs as PJ described, most VM hosts permit the rolling back of VMs to a previous point in time, which makes managing them very easy. Also you can keep the PostgreSQL server on the HOST computer and only use the VM for PT4 installations which makes this a convenient method - but I must admit your idea does have value.

[_dave_]

Thanks for response.

Not just pokertracker.cfg, the whole lot of files currently stored under %APPDATA%. The only exception I would suggest is \Processed, and it should probably reside in \Documents for more easy accessibility to end users.

PT3 used to be "portable", like I suggest. Probably still is, haven't checked.

Main issue is is goes against Microsoft developer guidelines to have settings stored along with the program, but those are out the window anyway when you need to run the program as administrator :)