> Robert> Is a subfolder called > 'C:\<Programs>\Plucker\plucker-desktop' okay? > Robert> Easiest to code/maintain if there is as few forks as > possible with the > Robert> Linux/Mac versions. > > Yes, it seams OK. But why not the root of the PluckerHome > "C:\<Programs>\Plucker\"? IMHO there are the best place.
Just using /Plucker/plucker-desktop/ so all the files and components for the plucker-desktop are contained in a single directory that is kept separate from other aspects like /Plucker/viewer. Using the same directory structure as the Unix and Mac versions of the desktop for easier maintenance, and a clearer indication of what does what. Agree that there should be something clickable in the /Plucker folder so people know what they click on to do things if they are looking in the root directory for stuff to do...Perhaps a shortcut(Win) and alias (Mac)in the root Plucker directory that points to the plucker-desktop executable? Or, technically, the executable should be written so that it can find things anywhere on the system and not just relying on relative paths--Can do this by using your Plucker Team registry key of where Plucker is installed, and then using that to get the filepath locations of resources, channel folder, etc. This finding of paths have already been pulled out into a get_plucker_directory( RESOURCES ) or get_plucker_directory( CHANNELS ) function throughout the code, to be used for such a purpose. The folders for individual channels should probably certainly off root as the /Plucker/channels/..., since probalby these would be a shared resource used by other applications that want to interface with Plucker. > Robert> Probably easier if all rolled into one installer. What are your > Robert> considerations? > > Yes, IMHO it should be included there. Just as a mention here, I must say I tried out your installer last month when I was upgrading to PIL, and the installer sure looks slick. Very nicely done! > >> > BTW: Is it allowed to redistribute the cygwin1.dll alone? IIRC i have > >> read something about this DLL long time ago, but i'm not sure? > > Robert> Yes. Source code for any distributed .exe needs to be > available with the > Robert> .exe Include a zip file archive of the .cpp and .h source > files of plucker > Robert> desktop (resource folder is already distributed for > runtime execution). > Robert> PilRC (the PalmOS Resource compiler) does this also. > > This means if the plucker-desktop are included in the installer all > the source need also included? I guess the most people like a small > download but not interested in the source. Would it be also OK if the > are only an Link to the Source in the installer included? This is the approach PilRC uses on their official download page. I should verify with RedHat myself though, that this is a reasonable fulfillment. I would agree that even more so for this app than PilRC, people aren't going to be looking for the source code, since its primary target is people who are casual users. That said, the source of plucker-desktop is 58k zipped if it does need to be included in distributions. > BTW some comments from my first tests: > > for the "install PalmOS software" function (not yet implemented i > guess). You will find the PalmOS Files always in the Subfolder > "Handheld Software" together with the file Software.ini that contain > the info about the files the and the language id mapping, you may > wan't use this file. Or you could call the "Install.exe <Win Handle>" > to do the PalmOS Install Stuff (Could be improved if you think there > are something missing). Sure thing, sounds good (Installing is not yet implemented). > It seams not a good idea to use the Channel name the user enter as the > section name for the plucker.ini. Because if the user for example call > the channel "Default" you overwrite the Default section. Whats about > the idea to add the string "CHANNEL-" in front of the Section Name, so > the Channel Named "News" will be Stored in "CHANNEL-News"? This seems like an excellent idea. Will still allow power-users to call their channel sections whatever they want and they will be read as a channel as long as there is a starting page key. However, will implement this new idea, so that new channels are prefixed CHANNEL-. This adds no overhead, since already have to reformat the channel name to section name to get rid of illegal characters to create a subdirectory name that works on all platforms. > In CVS there are this file exclusionlist.txt in the plucker_desktop > subdirectory. There is the same in parser\defaults\. I suggest to > remove the one in plucker-desktop. There are also the plucker.ini. I > suggest here also to remove this Definately. Only one plucker.ini should exist, and be in the root directory. Ditto for the global exclusionlist.text The ones in /Plucker/plucker-desktop will be removed in final version, and instead the application will find and use the ones in /Plucker. I was considering also having the option adding some extra channel-specific exclusion lists though, and seems logical if the new exclusion list with the new entries to append are created that they go into their channel directory, such as /Plucker/channels/news/exclusionlist.txt > and enter the sections and keys with > the descriptions in the pluckerrc.sample in the Default dir (Take care > that plucker-deskop get all the files it need it its own directory are > IMHO part of the Installer). What do you think? Definately. Will do. Probably the best examples would be 3 usage scenarios, with the recommended settings for each?: -Just a single website to download -An ebook (with -nourl info and other ebook type stuff) -A set of URLS to start from and crawl (as an example of using home.html) Best wishes, Robert
