>1. will the conduit be able to read out "old" ini files located in .DB >folders (some people still have old plucker ver.) or just the .ini sitting
>in the main folder and having "desktop" data No old ini files, just the desktop file. It's really easy to setup a channel so it should be a problem. I also don't the bulk of the users I am targeting will have these old databases set up. >2. is there any way that the java analog of the python code could be >compiled into winXX native exe and in that state "served" by the java >conduit (the thing is many people wouldn't like to install java VM [java >libraries for the conduit are small and install could be silent in the >background] Yes and no. I could compile the Jython stuff to a native exe. However, this can't be used by the conduit as the conduit shouldn't call out to a command line parser. It all should be internal to the conduit. That said, I believe the Palm JSync conduit includes a vm. I think if I write the installer correctly it will install everything needed without the need for a separate vm. We'll have to see what happens on a test machine with no vm installed. >3. also many people with python "distiller" could benefit from the java >conduit so is there a hope to have a conduit that simply runs plucker-build >or runsync.exe (on win) and provides a nice progress bar :) Don't think this will happen. I was hoping to incorporate the whole thing into Java. If I can hook up Bill's Jython code, then there wouldn't really be a need to have it run the command line parser. This way I can make it look like all the other conduits out there. This will also give me the stuff I need to implement getting changes in the Palm document back to the desktop as would happen if forms ever get implemented. Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
