Re: [dev] libdraw development

I know that copypasting is probably not related to drawing, but afaik
libdraw aims to be a graphical backend API.

It works with text, colors and not many things more. There's no
functions to draw pixels, lines, circles, pixmaps, etc..

But it does for font loading and measuring of char width/height.

If the purpose of libdraw is to provide a common drawing facilities we
should think about extending it's features. Having more backends would
be nice, but things like clipboard make it incompatible with backends
like sdl..

As far as libdraw is distributed as a static library with one function
per file it makes it good for adding more features without making
resulting bins bigger.

In swk for example I'm implementing multiline text support which is in
fact a text editor widget. The text manipulation functions are in
text.c and I don't think a widget kit should provide a text processor.
But where's the place for this? Libdraw maybe? Splitting each feature
in different libs it makes the development harder ( more dependencies).

I think that we should implement the features where we see they can
produce less damage to the programs using them and the development
(less deps as possible, but keeping a coherence)

sselp could be deprecated or rewritten as a test program for libdraw.
Or we can just implement sselp functionality as sselplib which is
probably more suckless... What do you guys think?

On Aug 31, 2010, at 6:24 PM, v4hn <me_AT_v4hn.de> wrote:

> ok,
>
> you're a great programmer as far a I can see,
> so don't take the following personally.
>
> I suppose I _kind of_ get why you're proposing such things,
> but excuse me?? What is wrong with you?
>
> On Mon, Aug 30, 2010 at 06:44:36PM +0200, pancake wrote:
>> I would like to have functions in libdraw to work with clipboard,
>> [...]
>
> from the README:
>> libdraw is a simple dynamic drawing library.
>
> What's the connection between support for X clipboard and _simple
> drawing_?
> And what the HELL would be suckless about that?
> If you like to write an X library based on X, call it X12,
> but I'm quite sure, this wouldn't become suckless software.
>
>
> v4hn
>
Received on Tue Aug 31 2010 - 20:53:02 CEST