Re: [hpoj-devel] xojpanel compiled-in pixmaps

[<pa...@rc...>]

Joe Piolunek wrote:
> I modified the xojpanel code to compile in the *.xpm's instead of loading 
> them at runtime.
Hi, Joe.  Thanks for looking into this.  It will help simplify the build
and install sequence.

> I get compiler errors when using the default *.xpm array declaration. The 
> only way I could make it work was to hand-modify the declaration inside each 
> pixmap.  It was quite simple to do, but is there a better way to #include 
> *.xpm's? It would need to be something that Qt will accept.
That's unfortunate.  What is the exact error you got (perhaps something about
the "static" keyword?), and what specifically did you have to change to make
it work?

> I'm working on a different 'cover graphic' that can be substituted for the 
> one that reads 'HP OfficeJet for Linux'. The new one reads 'HP OfficeJet LCD 
> Monitor' in the same style and color as the older one. The only change is a 
> substitution of 'LCD Monitor' for 'for Linux'. Which one would be better for 
> the next release, or would something else be more appropriate?
The new one sounds good, since it better conveys the function of xojpanel,
and it doesn't make it sound Linux-specific.

> I should be able to make the code and pixmaps available a couple of days 
> after your answer, unless I get lost in a snowdrift. We're expecting a really 
> big storm here on the east coast.
If you're not ready to provide the code changes yet, perhaps you could post
a screenshot on your webpage, which I link to from a couple of places on the
hpoj website.

BTW, when I check in the new I/O driver I will have to temporarily disable
xojpanel in the build sequence, since I'm removing ojlib but haven't finished
the PTAL PML code yet.  You'll probably want to keep your current source tree
around for now if you decide to try out the new code.  The PML support is
next on my TODO list, and once I finalize the API then you can make those
changes too, or I can help out if you'd like.

BTW#2, I think your clock may be set to the wrong time zone (GMT instead of
EST), or else KMail might be getting it wrong in the message header.

David