> Our releases are pretty silent to the user, they either see no dialogs or > dialogs where they can just keep clicking next and accept all the defaults. > We will pre load a channel into Plucker Desktop for them. We also plan to > use links on a web site to allow adding more channels if needed (via > plkrdata). We also have the requirement to make everything as simple as > possible - a one click install with no options and then sync the content > when hotsync is pushed. We've been successful so far with our previous > release.
Sounds good. > Also, Robert has the Windows installer Innosetup > script available too. It also is in the Plucker CVS. > I agree with Robert in that the other parsers haven't been tested nearly as > much as the Python one. In my case, I just plan to test it on our specific > pages for now. When you feel it is ready, feel free to drop a note, and we can set in the CVS. > Also, since the Plucker Desktop menus/dialogs/etc are based on XML resource > files, it might even be possible to disable all the options you don't want > people messing with just by modifying the XML resource files. I'm not > certain of this however. Most of the text and image resources are in XML resources for better maintainability. Quite a bit of the strings though, and configuration options were included in the code, these will be brought outside the executable in the next CVS update, for easier maintainability. Best wishes, Robert _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
