> Files that use the plucker: 'protocol' (and aren't plucker:/home.html or > plucker:/channels/<SECTION>/home.html) are indicated as website > URLs. Seems > to be more correct to call them local files.
Very reasonable. A good catch. > If you (manually) have set home_url to "plucker:/home.html" for a section > it will be indicated as a "A list of my links:", but you will not be able > to edit those links, since the tool is hard-coded to only look in the > channels dir. I think it is a good thing to add to maintain good compatibility with existing installations. For [DEFAULT] section on config, current design is to be storing the global settings that aren't set on a channel-specific-level and also store the default settings for new channels that are set on channel-specific-level. Okay to keep this, or should default settings for new entries be loaded from [DEFAULT] on the first execution of 'set settings for new channels', then saved to a separate section (which is then ignored by the loading of rows into table). > Also, it would be nice if it was possible to edit all local files using > the HTML editor. Like that no-extra frills editoring look huh? :-) What implementation would fit you best--A second button at the end of the local file dialog (so both browse and edit buttons)? This enough, or do also need an open/save on the editor itself. For editor, looking farther way down the road (when other things are stable), two things were on: (1) For the remainder of supported plucker tags besides the existing "href" (which is the most important), having either a multi-tab toolbar (I made a prototype a while back and it looks quite slick) to choose them or grouped drop down menus (since sometimes easier just to see <p> than try to figure out what the toolbar icon is). Clicking would bring up a dialog similar to the existing add/edit exclusion item, with name/value pairs and an OK/Cancel/Help. Then, instead of having 50 specific dialogs (like the one to add/edit an exclusion item), use a constructor to generate the dialog passing the name of the name/value pairs and what kind of value each accepts (integers get a spin box, strings a textctrl, etc). "OK" button then inserts the tag with the parameters from the name value pairs. (2) Remap the html tag rendering behavior using the wxWindows macros (such as were used for the exclusion list html file loading into a table) so that the preview tab shows more closely of how the plucker engine will render it (eg support for named color tags, tables are linear cells, b&w images can have a color tag). Best wishes, Robert
