> > > And python on the computer the parser runs on. That's not common on > > > Windows platforms. (They are minor things to install, and Plucker still > > > come out ahead with a smaller PDA footprint.) > > > > Windows is exactly the same in this regard. When you use something > > written in VisualBasic, don't you also need to install the VBRUN300.DLL (or > > newer) VB Runtime environment? "Scripting" languages aren't native on > > Windows platforms, but that doesn't mean the requirements differ. > > I didn't mean Windows was different because it needed Python. I > meant a Windows installation of Plucker involves installing Python and > then the Plucker parser, while a Windows installation of AvantGo is just > one setup program. For Linux and OS X computers, python is preinstalled, > so Plucker does not appear, to the end user, to require any prerequisites.
I feel that Plucker Windows distribution should have the components for the Python parser too. Although many other runtimes are aleady on the machine from other programs, python dlls are most likely not. The package is a bit heavier to download, but it should work out of the box. Click to start the installer answer questions, start. Dirk has done a good job of this. I suppose an optional live download installer, like Mozilla has, would be a good choice eventually, so can combine the ease of use of a single setup start with no extra downloads. > 21. AvantGo has a conduit, meaning the synchronization is started > by the same hotsync process Palm users are accustomed too. The plucker > parser must be run before a hotsync is started. (Again, there are > advantages and disadvantages to each.) I feel there should be an option to do live syncing for people how choose it. It's not too bad to implement, as it doesn't need to do any work, as plucker_controller classes have already been written, it just needs to call them on a sync event. A kind contibutor has also written a GPL one already for plucker (listed in archives). > Most plucker users have found ways to use it. The majority of > people who don't care how their computer works, and just want it to, don't > want to have to deal with scripts, configuration files, etc. I ask myself > the question, which is, am I going to be able to tell my sisters or my > parents about Plucker, and can they easily install and use it to satisfy > their needs without having to call me up cross-country to talk them > through it? That is on the the mark. There is no reason for using AvantGo, other than the out-of-the-box ease-of-use factor that they have. While most of the people on plucker-dev enjoy playing with their computer and learning how it works, a large slice of people see a desktop as a tool to get something else done that they want to enjoy. That is bank machines for myself: I have zero interest in going up to some bank machine, spending a few hours reading a tome next to it on how these bank machines work, and all the switches that can be used on that particular type. I want some bills out of the teller. From prior experiences with them, I expect there to be some sort of slot to put my card in, I type in a PIN, select an available action from the familiar interface, and get my result that I can then later start using. Prolonging the process takes my away from the things I enjoy. > > > You still get most of the functionality, and the interface is much better. > > > > Most of the functionality of.. what? Plucker? The interface is much > > better than what? > > Most of the functionality of Plucker, and the interface for > Plucker-desktop is much better than the default Plucker parser interface. > Just think if you're a new user and you don't know or care about how HTML > works. You setup a database and open the "edit" icon, which opens > home.html, and then what? Guess at the correct format? Most people don't > want to go have to think to use a program. > > Plucker-desktop gives a simpler, nicer interface to most, if not > all, of the configuration options for Plucker databases. I suppose the decision of whether graphical or not is a better interface for a tool is in the hands of who is using it. If one spends their whole day at the command line looking up argument and typing out their commands, that is often the easier way. If the familiar environment is graphical, graphical is often the easier way. Letting Plucker be used both via command line and visually seems like a logical way about things. For functionality, the desktop has all but three things of command-line only, that were cut to avoid anguish of visual users: (1) No control on dialogs to change the file extension (discussed on plucker-dev why this was cut). This may go back in on the POSIX port as pilot-link doesn't care about the extension and will install anyways. (2) There is no inherited section names of channels (ie have a section called [news] with some keys, and a section called [cnn] and then call plucker-build -s news -cnn) as the interface implementation is just too confusing (also discussed on plucker-dev as to why). (3) No basename output file changing (discussed on plucker-dev as to why that was cut). Everything else of the parser (url-filter, user-agent, owner-id, etc) is up and functioning correctly. There is an issue with command_before and command_after, but Bill says he would prefer these are moved out of the distiller anyways. Am working on some UI polish at the moment and writing the docs of the newly added components. A download will be made available in the next few days for stress testing. An according to their documentation, a number 21 is Plucker supports mailto:. AvantGo does not. ;-) Best wishes, Robert
