Hi,
An important missing point in the current documentation, is the lack of
examples for automatic layout. Nearly all the samples use hard-coded pixel
values for the position and size. I find this style easy at first, but
complicated to maintain, when you add, modify or delete widgets.
I offer
Sebastian Werner schrieb:
> Til Schneider schrieb:
>>> Well, almost happy camper, I still can't get it to run in FireFox
>>> but it works in IE. And in IE the images are messed up in the tree. But
>>> I wasn't too worried about the images because the rest of the info
>>> displays fine in IE. I w
Til Schneider schrieb:
>> Well, almost happy camper, I still can't get it to run in FireFox
>> but it works in IE. And in IE the images are messed up in the tree. But
>> I wasn't too worried about the images because the rest of the info
>> displays fine in IE. I would rather use it in FireFox, b
> Well, almost happy camper, I still can't get it to run in FireFox
> but it works in IE. And in IE the images are messed up in the tree. But
> I wasn't too worried about the images because the rest of the info
> displays fine in IE. I would rather use it in FireFox, but not sure yet
> why it i
Excellent! I had not seen that check box, so I took another look and it is there and it works like I would like it to. Now all I am looking for would be the event information and I will be a happy camper with the docs. Well, almost happy camper, I still can't get it to run in FireFox but it works i
> I have a small suggestion to the new documentation API... is it possible
> to get the methods and properties to be accumulative? What I mean is
> that when I look at the docs for a given widget, I see it's methods and
> properties as well as all those that it inherits. Perhaps the new
> prope
Howdy!
Jim Hunter wrote:
> I have a small suggestion to the new documentation API... is it possible to
> get the methods and properties to be accumulative? What I mean is that when
> I look at the docs for a given widget, I see it's methods and properties as
> well as all those that it inherits. P
[EMAIL PROTECTED] wrote:
Chris Banford <[EMAIL PROTECTED]> writes:
Great! Post a note when you're available to start, and also post any
suggestions you have for documentation organization and necessary content. I
hope you'll comment on the "Outline" in the next week or so.
Chris Banford <[EMAIL PROTECTED]> writes:
> I'd also like to see if I can help out with some doc writing. In the
> beginning it would be limited to the area of *getting started* how to's, as
> I am still a qooxdoo newbie :-) . I'd guess that I could start to put some
> time in around mid-end of Au
Erik A. Onnen wrote:
[EMAIL PROTECTED] wrote:
Erik, do you have any desire to help document qooxdoo? There is enough to do
that we could certainly use additional people helping! Dividing the work up
into manageable parts and distributing the parts to interested contributors
would
"Jim Hunter" <[EMAIL PROTECTED]> writes:
> I have a small suggestion to the new documentation API... is it possible to
> get the methods and properties to be accumulative? What I mean is that when
> I look at the docs for a given widget, I see it's methods and properties as
> well as all those tha
I have a small suggestion to the new documentation API... is it possible to get the methods and properties to be accumulative? What I mean is that when I look at the docs for a given widget, I see it's methods and properties as well as all those that it inherits. Perhaps the new properties and meth
"Erik A. Onnen" <[EMAIL PROTECTED]> writes:
> Derrell,
>
> I do have a desire to help although my free time over the next few
> weeks is sparse. What sort of commitment are you looking for? I could
> perhaps spare three to five hours a week beginning on August 24th. If
> you think that can be prod
[EMAIL PROTECTED] wrote:
>
> Erik, do you have any desire to help document qooxdoo? There is enough to do
> that we could certainly use additional people helping! Dividing the work up
> into manageable parts and distributing the parts to interested contributors
> would be a good way to accomplis
Hi, Erik!
Erik A. Onnen wrote:
> Derrell,
>
> Thanks for the helpful post, but I think your response echoes the OP's
> point that more needs to be done towards documentation. Not only is
> the namespace documentation light to non-existent, but the
> documentation you site on how to generate the d
"Erik A. Onnen" <[EMAIL PROTECTED]> writes:
> Derrell,
>
> Thanks for the helpful post, but I think your response echoes the OP's
> point that more needs to be done towards documentation.
Yup, that's exactly what I stated in my first response:
In 'namespaces', there is "better" documentat
[EMAIL PROTECTED] wrote:
> Moving this discussion to the mailing list, for others to participate:
>
> "Alexander Trauzzi" <[EMAIL PROTECTED]> writes:
>> Qooxdoo has a lot of neat features that dojo doesn't. Qooxdoo looks a lot
>> more programmer-friendly, even in spite of dojo's their "package
>>
Hi list,
My first post in ages -- I'm still just keeping an eye on qooxdoo and
waiting until the right project comes along...
Wanted to let you all know about *Aptana* -- an open source editor for
js, html & css. It links in with a bunch of other js libs (although
not qooxdoo yet!), and altho
18 matches
Mail list logo
