Morning all, > Philipp> Good idea - this would eliminate the need to select the DB's to be > Philipp> synced manually. How far is the development of this GUI from being > Philipp> stable and distributed? > > Don't know how are Roberts plan for this.
OK, I've hacked together a little GUI, maybe that can help somebody. Quite simple, though. You can get it on my page where the conduit stuff is (http://plkrcond.extrareto.de), if it's of any use for anybody. > Well what's about the idea to use an new ini key called > "build_on_sync_" and put it in the channel ini in the default > section. This key contain an list of the user names where > the checkbox are marked. I feel the idea is very good, as I anyway will have to go through all the plucker.ini files probably to display a bit more info and allow for advanced features. > For example: > > build_on_sync=first user;second user Can I add more than one user to the user key in the ini file? Cool... good to know :-) > Or use the "user" key. I have just updated the conduit.exe to support > installing for more than one user. Hm, I'd prefer a seperate key to make it a bit more clean - it allows for one user to trigger building when he syncs, but will install the built DB to all users in the user key. Like a centralized build for all users on the current PC or something like this. > But since you need to know the plucker directory to read this ini, you > also know the RunSync.exe location. So there are no reason to save > this here :-) If it's reliable to get the RunSync path from the registry, it's no problem to only store the RunHidden key and other conduit specific information in the main ini. If the installer takes care that the path is there, no problem. Philipp
