> Robert> (1) A list of non-channel section names in the ini is declared. > > I suggest to put the list in the INI, so it could be updated without > recompiling the plucker-desktop. > > Maybe later there will be some other tools that need also some > sections and wan't reserve there name.
Will any of them be having a home_url key? The only time that we are iterating through the sections to pick out the channel ones is the initial loadup of the rows in the main listctrl. There are two tests: (1) is it not [DEFAULT], [MACINTOSH], etc, and (2) does it have a home_url key. If passes both, it loads into list. I agree there should be extensibility and easy operability with other future components. All the updating etc is being written as a module to pull it off for easier API interface if some other program wants to control similar functions. Both in the source file so not adding more things around the ini file, and having a list of reserved in the ini are good approaches. Probably should manage future Plucker add-ons, in the manner that Palm/Apple did: just get a unique string to describe the new app so it doesn't conflict with other apps in the plucker.ini file. Then either add the strings of these apps to the included reserve list text file in the CVS or the .ini text file in the CVS. Usually both binaries and .ini file are packaged and released together to users. configuration.cpp was rewritten to allow the checks for sections to be rewritten at any time without affecting any code, so we can drop in at any time whatever solution ends up fitting best. Does that sound okay? During the configuration.cpp, code was also added to look up /The Plucker Team/Plucker from your key in registry and then use that for the PluckerHome that is used to find rest of programs for the duration of the execution of plucker-desktop.exe. Is that okay? > Robert> (2) Then we are looking through the remaining sections > and if it has a key > Robert> of home_url, then it is a considered to be a channel. The > reason for this is > Robert> that there can be "modifier sections" of the .ini which > add can be combined > Robert> with an actual channel section at the command line (like > the pluck-comics > Robert> examples). > > Can you give an example please. The section 4.5.2.2 buried deep down in the Plucker Help has a brief description. In the example command string there of: Spider.py -s comics -s sunday Only one section has content to pluck, the other section is a modifier to add/overrule settings in the original section. > Robert> #define NON_CHANNEL_SECTIONS "DEFAULT", "POSIX", "OS2" "WINDOWS", > Robert> "MACINTOSH", "PLUCKER-DESKTOP", "PLUCKER-DAEMON" > > Add CONTEXT_DEFAULT please. And maybe another one if i get the > InstallBuddy plugin i'm working on ready. Sure thing. > Robert> I was plan > Robert> ning on when pressing the 'Add Channel' on main dialog, > it goes directly to > Robert> channel name dialog, the 'Channel Name' field is given > the focus, and the > Robert> 'Unnamed channel' text within the textbox is highlighted > ready to be > Robert> replaced. On clicking 'OK' button, a legal, > non-conflicting section name is > Robert> generated based on the value of channel name filed, and > its subdirectory is > Robert> made and its section is added to the .ini file. > > Agree, that's the way an GUI should work. Will have a prototype of this running soon, so can give it a spin, to see if this is acceptable in practice also. Best wishes, Robert
