> Some minor issues I think should be changed for the plucker_desktop > dir in CVS: > > - COPYING should be removed (we have a COPYING file in the top dir)
Sounds good. > > - REQUIREMENTS could be removed. I have updated the file in the top > dir with the new info. However, I removed the part saying that the > same compiler is used to compile the desktop tool and the viewer -- > it's true that GCC can be used in both cases, but you can't use the > *same* compiler (need a cross-compiler for the viewer). Just to avoid > any confusion... No problem. > - makefile_temp.g95?? How did that get there. Must have been drunk. > - plucker.ini, exclusionlist.txt seems kind of misplaced. The Linux/Unix > version should use $HOME/.pluckerrc and exclusionlist.txt found in > PLUCKERHOME, PLUCKERDIR and any extra exclusionlists added to the > current section. I'd guess the Windows version also has some kind of > default plucker.ini and exclusionlist.txt files. Plucker.ini and exclusionlist.txt most certainly are misplaced. Didn't know where in structure to put them, as directory tree wasn't set up yet. I believe Getting current working directory all the time is also somewhat painful anyways, since have to keep resetting back to the old working directory, everytime the working directory changes from an operation. For exclusion lists, I was actually thinking today that most likely usage of multiple exclusion lists for most people is to have a global exclusion list for all the usual stuff (like real audio files, flash, doubleclick), and a channel-specific exclusion list with a few entries of directories/pages to finish cutting the crap off from that one website. To that end, it might serve practical on 'channel configuration dialog->limits tab' to have the limits checkbox split into 2 checkboxs: one for "use shared exclusion list" and "use channel-specific exclusion list" (each with an edit button to load them up), then save the channel's exclusion list in that channels directory, and on saving of the dialog to prefs, add it to the exclusion list for that channel's section. > - plucker_showcase.htm is a resource file, so it might be a better idea > to put it in the resource dir Sounds reasonable to me. I don't know if langs also would be best off as /resource/langs and /icons would be best off as /resource/icons since those will be resources too. Maybe there should be a /resource/showcase directory too, as one of the feature requests was to allow multiple files and sources to be used/imported. For langs, I guess the way it will end up is with a script to replace the strings with a translation, like the viewer currently does, to write out XML files for the translation. Probably would be less diskspace if the XML files are read from inside a zip file (this is supported, but should make sure supported on all platforms). Then a startup wizard (and an advanced option) can specify which language resource to load up on runtime. For the user-visible strings within the C code, I don't know whether best strategy is to (a) Use .po files (this seems to be the most common way). (b) Use a script to replace them, like the viewer. (c) Pull all strings from the XML (haven't looked at this yet. Might be painful, might not). > I also think the channels dir created by the tool should be put in > PLUCKERHOME (defaults to ~/.plucker on Linux/Unix). Right now it > creates the channels dir in the current dir, so if you run the desktop > tool from different dirs you will create new channels dirs all over the > place ;-) Definately. Good to have a common area, also for other things that wish to manipulate the sections data in the future, that they know where to find it. > I have updated the config scripts to also build the plucker desktop tool. > This includes replacing the makefile.unix file with a Makefile.in file. I > don't know if/how Windows can use the configure scripts, though. If it is > possible to use autoconf and friends with Windows we could update the > Makefile.in to create different Makefiles for Linux/Unix and Windows. Certainly worth giving it a run-through. The script for setting up the viewer works well. There probably should be the rest of the supported makefiles added eventually (like Borland, etc), so can just spit them all out. > For the Linux/Unix version I have selected to install the resource files > together with the other shared Plucker data, i.e. in > > <TOP_INSTALL_DIR>/share/plucker/desktop/ > > This would require a setting in the config file, so that the desktop tool > knows where to find the resources. That could be added to the config file > at installation. Sounds good. Drop in whatever you think would be best. > None of these changes have been added to the code in CVS, yet. Feel free to drop in the improvements straight away. Your things are always make good sense. I am in eyeballs in medicine for the next 3.5 weeks as the final exams approach, and will continue playing with this on Dec 14. Best wishes, Robert
