At 03:55 PM 11/17/2002  +0000, Robert O'Connor wrote:
On 16 Nov 2002 at 20:44, Fringe Ryder wrote:

Hi Tony, thanks for your letter.

So anyways, in summary then, 2 keys in the ini in a section to specify either a b64 encoding or
a PNM of images.

Probably new keys instead of overloading the existing ones used for icon filenames, something
like big_icon_inline= / small_icon_inline= or similar.
Sounds good. I was planning to allow the icon name to stay the same, plopping the file in the channel directory or the Plucker directory and updating the path appropriately.

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.

> 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. I was stunned that in a discussion 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.

-Tony McNamara-

_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to