Hi Michael, Glad to hear that could compile okay!
Just to follow up on yesterday, worked on the two things you mentioned: The app icon is fixed (also now a green pacifier instead of the mondrian). Gets a proper extension name for config file, depending on os. > One major difference in Plucker's behavior on Linux and Windows is > that on Linux you have *one* config file, while Windows seems to use > one config file for each Plucker document. > > I have hacked my local copy of the desktop tool, so that it will use > the sections I have in my ~/.pluckerrc file instead of traversing the > channels directory only available in Windows. I've also added parsing > of other options to my copy. Can you explain some more to me what the organization of the configs is on Linux? This is all there is in the config file itself, which doesn't tell me too much of the details: "Under unix, this should be called 'pluckerrc' if it is the system wide config file and '.pluckerrc' if it is a user config file. This should have been installed in the correct place." Is there separate home.html's? How are the sections identified in the ~/.pluckerrc file? > BTW, I saw that the code only checks for db_name. That config key is > deprecated (replaced by doc_name) and it is also possible to only use > doc_file (or the other deprecated key, db_file). If doc_file is used > it should be run through basename to get the name of the document > without the path. This might be of less concern on Windows systems, > though. Added to to-do. > The dynamic creation of the GUI using the XML resource file is great, > e.g. change the week to start on a Monday, open the configure dialog > again (i.e. it's not necessary to recompile or restart the app) and > the schedule will show the week in a proper format ;-) Very cool! Very nice :) Should make translations easier too, later on too, I hope, since translators won't need to have a full build environment to see their changes. Best wishes, Robert
