Friday, July 30, 2010

Where to put 3.0

Since the network folder is no longer needed in 3.0... a new location for the onePOS system is in order.

Initially, I was going to put it in the Program Files folder, just like any other Windows application, but then there was the Windows 7 (and likely Vista) issue with writing in the Program Files folder. As much as none of us may like it, Windows 7 is now the "standard" OS since Windows XP is 7+ years old. One of the newer things since XP is that a "Standard User" cannot write to files in the Program Files directory... thats a big issue for a POS system. So where to put the onePOS data?

Well, since it cannot go where I was hoping, and the Network folder is gone, the next logical place is just in the root of c:\ on the machine, which is where it has always been on a stand alone machine and now can be there on both terminal 1 and terminal 2. If installed to c:\onePOS, both Admin and non-Admin users can run the software and modify data as needed. Since our application can be considered "server" software, and the primary use of the machine it is loaded on, putting it in the root is acceptable. I think it will also be an easy mindset change to adjust to from 2.x to 3.x.

Our new launcher application similarly cannot be in Program Files, so it is going to be in \users\public\onePOS Launcher. While this is not exactly a standard directory on XP, it is very standard on Windows 7, early versions of Windows NT, and most every other OS out there. The launcher application is used by every user on every machine (except a locally installed system) to connect to the server and run onePOS. Since it is also used on manager workstations and laptops along with many other applications, it is hard to justify placing the launcher application in the root drive (in fact it would take Admin rights initially then to load the software there and this could be an issue in corporate environments).

The magic behind the launcher application will take a bit to get used to, but its really simple stuff to install and support. More on that later...

No comments:

Post a Comment