One thing you must understand about working with a browser is that there is
no 'canvas. Thus, there is no direct 'drawing' on the canvas. The Walter
Zorn library for drawing shapes and lines etc, uses tiny DIV's for each
'point' of the line. He doesn't tell the canvas to draw a line from point A
to point B. So you can't compare creating controls in the browser with
creating controls for the Windows environment, it's just not the same.
Everything in qooxdoo is made up of standard HTML objects, some have many
objects. To see, after your page is rendered, use one of the fine tools to
see the DOM. This will show you what the final result is of your few simple
commands to draw a Table or Splitter or ???. There are hundreds of HTML
objects that get created on the page. So when you are creating totally new
controls, you have to think about how to construct them using DOM objects.
That is why I suggest creating new controls by using other qooxdoo controls
pieced together. This way all the drawing issues are done for you.
And yes you are correct in assuming that most of the borders etc are
controlled by changing the style of the object.
Hope this helps,
Jim Hunter
D4PHP.ORG
On 4/14/07, Manuel Bender <[EMAIL PROTECTED]> wrote:
Joe Hudson schrieb:
Thanks to your help, but i think my problem is not so much in creating
new widgets which only uses some other qooxdoo components (i already did
this and it works fine)...
I want to create new widgets with new graphic effects, just like a
progress bar, but which are still compatible to the qooxdoo framework so
that they can be added to a window, pane or whatever.... For things like
that i think i need core graphic routines...
Probably i have to get a bit deeper into the source code of the qooxdoo
sources to see how they paint objects.
Maybe someone knows what they use to paint their objects? For examle the
separator from the split pane or the table from the date chooser
must be painted somehow within qooxdoo... or is all done with css ?
I think the best start to understand how the painting issues works is
probably the border class cause the most widgets are some kind of border
constructs ;-)
Or does someone have another idea?
I also will take a closer look to Walter Zorns graphic package
> As a newbie here myself, I struggled with the same issue. I found
myself
> usually starting by extending other layout objects (see qx.ui.layout.*).
> Here is a simple example of an object (I'm sure the smarter people on
this
> list will have much better examples):
>
> qx.Class.define("foo.SimpleLayoutWithTabView",
> {
> extend : qx.ui.layout.CanvasLayout,
>
> construct : function()
> {
> this.base(arguments);
> this._tabView = new qx.ui.pageview.tabview.TabView;
> this.add(this._tabView);
> this._tabView.set({ top: 30, bottom: 0, width: "100%"});
> },
> destruct : function() {
> this._disposeObjects("_tabView");
> }
> });
>
> ________________________________________
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
