On 17 Nov 2002 at 9:56, Fringe Ryder wrote: > >Another option would be to directly use TBmp's inline, such as > >big_icon_inline=\000\040\000\040\000\004\000\.. > >small_icon_inline=\000\017\000\011\000\... > >and then just add an extra "if" condition after the "get_icon" function in > >PQAAppInfo.py of the > >Python parser to check to see if there is a value for big_icon_inline. If > >there is, use the > >big_icon_inline value, else use the default icon. > > That sounds fine too. Historically there -used- to be a limit on the > length of an INI string. If wxWindows is not handicapped by that, this > will work. Otherwise I was thinking of just tossing the pseudo-binary > images in at the end, with a length word in front of them. But inline > encoding is fine too - easier to read, equally hard to edit by hand.
This would I think be the nicest solution. > > > Sheesh, Robert, there's a forest > > > hidden in those trees! > > > >Probably not the altogether most helpful comment to aid discussion. > > Perhaps not; I apologize for the tone. > No problemo. We all raise tones sometimes. Glad we can stay focused instead around here for the 99% of the time. > of a tool to simplify adding sites to Plucker you would expect Joe-User to > build their .plkrdata tool by hand-coding it and then running a bitmap > mapping tool to append to the file a encoded icon. The whole idea of this > is to make it easy for corporates and other non-techies to put up > easy-to-use Plucker Channel files on their sites. Sorry, perhaps I was making things unclear, which I sometimes do with my low number of words. Just to sort that out, I was wagering that not many of the Joe-Users would be willing to hand- code a .plkrdata file. (The previous outing of the Windows distro used manual configuration of ini files for the different channels, and it was not what many of the users were used to doing, unless they remembered their Soundblaster/DOS game days). The .plkrdata should also allowed to be hand-coded though, because INI editing is familiar to some people. So the Joe-User, no ini- writing-needed approach would be, to generate a .plkrdata file is: -Start Plucker Desktop. -Set up a channel with the parameters that are desired for the site. If a custom icon file is wanted, Joe fills in the filename of the bitmap in the boxes for large and/or small icon. -From the menu, click Import/Export > Export selected channel(s). -A prompt is asked for a filename to save it as, with a suitable default filename given, such as a generated <channel_name>.plkrdata. As part of the export, the software writes a key of the icon in a text TBmp format. Now there is a .plkrdata file, ready to be put online for one-click downloads by webusers via the 1-click tool. That .plkrdata file can also be sent via email to someone, or shared with others who want to load them on. Either a double-click on a .plkrdata file on the desktop adds the channel to plucker.ini, or the web download as you described. An export from openurls.plkr.org/my.plkr.org would work the same, except instead of GUI widgets to fill in the parameters, there is form elements to fill. The non Joe-User, hand-code way, is just to open up a textfile and write the keys by hand. The big_icon_inline is certainly hard to code by hand, but that key (like the others) is optional anyways. Because it is in .ini format, shall we allow support for multiple channels inside, or only a single one in a .plkrdata file? If multiple, then perrhaps before the addition of the sections to the .ini, if there are multiple sections, have a prompt to check off those in the wxCheckListBox that are desired to be installed. (And have an option to turn off this prompting if so desired). This would make it easier for people to distribute a list of their known subject, such as all the astronomy PDA sites if they were an astronomy expert and PDA-savvy? The other possiblilty for an icon is just to use the big_icon keys, and start supporting in the parser http:// URLs to the icons, and the parser downloads and converts using the image parsers? The downside is that many sites aren't too careful about not breaking their URLs to things: many can't even keep their main URL consistent for more than a few months. Best wishes, Robert _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
