Well, here are the two problems I see with this:
        
        - The canvas widget isn't really designed for fast immediate graphics 
rendering, but it is still capable of it. It works much like Tcl/Tk's canvas widget.
        - The client side looks so ugly now because pgWriteCmd is the low-level 
interface to widgets like canvas and terminal, and the high-level interface hasn't 
been built yet.

So, I'll start on a new addition to the client library, PicoGUI Client Side Graphics 
Library or something. It will have much more friendly primitives that look 'normal', 
abstracted from the underlying rendering method. Rendering methods will include stored 
groplists with the Canvas, immediate rendering with the Canvas, and fast graphics with 
shared memory. (not implemented yet)

(BTW, usually I'd be in school now, but we have a blizzard over here and it got 
cancelled. Lots of electrical disturbances though, thank goodness for my UPS :)

On Wed, 11 April 2001, Olivier Bornet wrote:

> 
> Hi Micah (and other developers),
> 
> I'm (allways) porting Waba to PicoGUI. At this time, my most important
> problem is the "grop node" list. Due to the way Waba work now, all
> graphics are very simple draw (like line, rect, polyline,
> draw_chars...). And the draw mechanisme inside Waba work as we can work
> in a bitmap. This mean no memorisation of what was drawed. So, for
> example, if Waba want to clear the screen, it just draw a filled
> rectangle on the full screen.  Doing this with PicoGUI make the grop
> list every time bigger and bigger. And this is very slow, even on
> my PIII 500.
> 
> What I suggest (as mentionned in my last emails) are :
> 
> - use a command like "pgWriteCmd( w, PGCANVAS_MK_BITMAP, 0 );"
>   to convert all the grop list to one bitmap (or pixmap)
>   element.
> 
> - use of the PG_WIDGET_BITMAP instead of the PG_WIDGET_CANVAS.
>   This implied having support for pgWriteCmd(...) for it.
> 
> - use a grop node PG_GROP_BITMAP, and have support for drawing
>   directly in it, when it is in the grop list of the
>   PG_WIDGET_CANVAS. (I think it's the most great way)
> 
> As this point is a blocking point now for me (for continuing the Waba
> port to PicoGUI), I must know when I can have something like this in
> PicoGUI. I don't want to use now at every place some pgWriteCmd(...)
> with canvas, and change with another programming technics in some days.
> 
> I hope you understand my question.
> 
> Good day, and thanks in advance.
> 
>         Olivier
> -- 
> Olivier Bornet                      SMARTDATA SA
> [EMAIL PROTECTED]         Centre du Parc
> http://www.smartdata.ch             av. des Pr�s-Beudin 20
> Phone +41-27-723'55'03              1920 Martigny
> Fax   +41-27-723'55'19              Phone +41-27-723'55'18
> 
> _______________________________________________
> Pgui-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/pgui-devel

--
perl -e'socket S,2,1,tcp;connect S,pack(H16,"0200029a80692d32").\0x8;print 
grep!/=/,<S>'


_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to