[shell-coding] added lsapi tools

On Thu, 25 Jul 2002 17:00:56 EDT Bgvinyard@xxxxxxx writes:
> Just my two cents, I think any major additions to the api should be 
> ratified 
> by the majority of code and module developers; perhaps there is a 
> better way, 
> or the functionality isnt needed at all.

On that note (and my apologies to those of you who don't care about
litestep), I'm looking for opinions and suggestions regarding the "tools"
I've added to my named monitor build:

http://www.technoirotica.com/~rabidcow/litestep/lsapi-tools.html

These are some things that I've found common to many modules, and it
seems aweful to have a copy (perhaps with slightly different bugs and
features) in each module:

LSParseStarList/LSFreeStarList, which I originally wrote for
NetLoadModule (modified from the code I used in RabidVWM, based upon
similar code in ckvwm...)  A generic routine to read lists from step.rc,
but I think it may not be flexible enough because it always reads to a
linked list.

There's a bunch of table-based things to replace long repetitive (and
usually paired) code sequences, like registering bang commands.  Mainly
to save space, it also makes it impossible to have add/remove out of
sync.

LSStringEnum, to convert a string to an enum without huge branching code.

LSTransEdgeBlt, for stretched or tiled bitmaps with a non-stretched edge,
like systray or RabidVWM.

LSPaintDesktop, about 30% of which is identical to Maduin's
PaintDesktopEx, this keeps one cache of the background instead of one per
module and lets one module provide a hook to paint the desktop itself
instead of relying on Windows' limited code.

...I'd also like to add some fancy bitmap filters, but probably after
0.24.7, so I know what style of code to use.

-rabidcow

Other related posts: