[cairo] [ANN] CairoPad

[Hakki Dogusan]

Hi,

(Thanks for reply, appreciated)

Carl Worth wrote:
> On Tue, 11 Dec 2007 04:24:46 +0200, Hakki Dogusan wrote:
>> package was added in 5.1. There is a compat module, but I didn't use it
>> before. So, I tried to remove dependencies. Made a new dowload file with
>> name "linux"; also put ldd results.
>>
>> I hope you can run it now.
> 
> Thanks, and yes! I did get it running after doing "chmod a+x
> bin/lua51" at least.
> 
> Here are some comments from a tiny bit of playing:
> 
>   1. The multi-pane layout is really painful, (at least on my 1024x768
>      display). A separate window for the output might make it easier
>      to manage. Independently, it would be quite nice if the display
>      output would automatically (or optionally) scale to
>      fit. Similarly, it might be nice if the code view wrapped long
>      lines.
> 

- I re-designed interface. Except editor other panes may be hidden, 
docked, or floating.
- I don't know how to fit drawing, and I'm not sure that it is a good idea.

>   2. The display output doesn't properly handle expose events, so
>      every time the window is obscured or the layout is adjusted, the
>      drawing disappears until the "refresh" button is pressed. The
>      fancy "live" option avoids this problem. And since that's one of
>      the most compelling features, why not make live be the default?
> 

- Fixed. [Refresh] button is gone. Paint responds system events.

>   3. It looks like you copied in the contents of the old snippets with
>      that obnoxious snippet_normalize function. (It's not *as*
>      obnoxious in this environment since the full body of the function
>      is immediately available at least.) But you might instead include
>      these updated samples that don't use snippet_normalize:
> 
> 	http://cairographics.org/samples/
> 

- It seems, I missed code changes there.. I started to apply them (only 
3-4 of snippets updated). I added new samples to snippets database.


>   4. The live behavior when attempting to make a subtle change can be
>      quite jarring. (The display disappears and is replaced with an
>      error message.) This leads to lots of "flashing" of error
>      messages and output as I type. Maybe instead just put the error
>      message below the display? And leave the display there, or
>      perhaps shade it *very* subtly to indicate that it is not current
>      or something like that?
> 

- ~Applied. Error message only shown in message pane; upon error Paint 
is cleared.

> Anyway, this looks very impressive and could definitely make a nice
> tool for helping people explore how cairo works.
> 

I'm glad you find it useful.

> Thanks for your fun contribution!
> 
> -Carl

ps. There are some more changes in CairoPad. I uploaded 0.79 to site (If 
downloaded binary before, one only needs to download src 91Kb): 
http://www.dynaset.org/dogusanh/download.html#cairopad

You may like Cairo API colourizing and code complation ;)

--
Regards,
Hakki Dogusan