Please, do not take due on this question. It was my stupidity only. I had a mistake in the header of HTML document where my qooxdoo code resides in. You do not need any other charset specification when POSTing to the server.
Sorry.Isn't it some of Murphy's Laws? You find solution of your problem in
Hi all,
How to judge whether a TreeFolder has childern no matter whether it is
open or close ?
Thanks a lot :)
Mengya Tang
---
This SF.Net email is sponsored by xPML, a grou
ChristophDorn wrote:
If you find one that is actively being developed let me know.
Lots of XUL-related links (including to books) are at
http://xul.sourceforge.net/. Also, http://xulblog.de/xul/ has some
interesting links, including to an ActiveX control that embeds the Gecko
rendering eng
> only for my personal interrest - can you send me a link to a UI-deisgner
creating XUL?
When I was researching this I found one, but cannot remember the link.
Here is a dead one http://xulmaker.mozdev.org/
If you find one that is actively being developed let me know.
> what is the problem of t
I think the main value of using XUL is to borrow from a standard that has
many UI-related challenges solved using standard patters as Ben mentioned.
There are also a host of tools starting to spring up to edit XUL
definitions. Even visual drag and drop tools to design UI's.
only for my person
Added to SVN
Kent Olsson schrieb:
The user who wants to use the QxSplitPane class has to use the attached
patch to the QxExtend class.
I am sorry for the inconvenience, but Sebastian does not intend to use
the patch for the core.
Kent
--
This is a multi-part message in MIME format.Hello Sebastian, i'm unable to make the QxRequest work in IE, in FireFox it
works fine, as espected, but in IE it doesnt it is weird coz if i look in the
response at fiddler the request is getting the file but still the request fails
and if i put it in
the following code:
this.setHeight(QxConst.CORE_HUNDREDPERCENT);
this.setWidth(QxConst.CORE_HUNDREDPERCENT);
var searchHBL = new QxHorizontalBoxLayout();
searchHBL.setHeight(QxConst.CORE_AUTO);
searchHBL.setHorizontalChildrenAlign(QxConst.ALIGN_CENTER);
searchHBL.setVerticalChildrenAl
I can confirm this problem. QxIframeTransport just takes the
parameters and appends them to the action url of the form. See my
previous posts about accessing the _form attribute hack to workaround
this limitation in QxIframeTransport.
On 4/5/06, Oliver Vogel <[EMAIL PROTECTED]> wrote:
> @sebastian
Hi qooxdoo people,I am using 0.6-alpha1 and I want to post data to the server using QxRequest (my own implementation of JSON-RPC).But data I am posting are in utf-8 encoding and foreign character are bad when they arrive to the server.
In XML-RPC I can define charset at the beginning of the XML mes
Thanks Kent!
Applied to SVN.
Sebastian
Kent Olsson schrieb:
Here is a patch:
solving the problem!
Kent
On Tue, 2006-04-04 at 15:07 +0200, Kent Olsson wrote:
when the following is done:
var helpM = new QxMenu();
var helpMBB = new QxMenuBarButton("Help", helpM);
doc.add(helpM);
Yeah, you must pass the arguments the listview needs. They must also
added to the constructor function of sfListView.
Sebastian
Jim Hunter schrieb:
OK, I see that would be better. I made the change in my test page and got:
000390:Failed to execute "_modifyParent()":Modification of property
@sebastian
in your code you are creating a empty iframe and set the url to
"about:blanc". This works fine in HTTP - environment. but if your Site
is using SSL (HTTPS:) ans you are creating a iframe with url=about:blanc
IE thinks, your page is SSL and the iframe inside the page is
about:blanc =
@sebastian
hi sebastian i am actually changing my app from dojo to QxRequest.
now i found the following error:
i am using ONLY QxIframeTransport (not QxXMLHttpTransport!) and the
mothod QxConst.METHOD_POST (="POST").
the QxRequest object is calling my php file at the server (this ist
working fi
Reading the documentation on the way Qooxdoo does inheritance, I tried to create a simple subclass of the QxListView object and it failed. My first attempt was to simply create an exact copy of QxListView with my new object name. Here is what I did, where did I go wrong?
function sfListView = func
OK, I see that would be better. I made the change in my test page and got:000390:Failed to execute "_modifyParent()":Modification of property "parent" failed with exception(this._data has no properties)
And in my real app, this is the same error I got. In the test page I did get the border displaye
function sfListView = function(){
// no code yet, just want an exact copy.
};
sfListView.extend(QxListView, "sfListView");
--
This seems to be just wrong for a first shot.
Please try:
function sfListView(){
QxListView.call(this);
};
sfListView.extend(QxListView, "sfListView");
sebastian
I think the main value of using XUL is to borrow from a standard that has
many UI-related challenges solved using standard patters as Ben mentioned.
There are also a host of tools starting to spring up to edit XUL
definitions. Even visual drag and drop tools to design UI's.
Using the QxBuilder s
Ben Alex schrieb:
ChristophDorn wrote:
I really like the idea of using the XUL standard for qooxdoo application
layout. It makes total sense. From what I have gathered so far it
looks like
a good fit.
Hm. As much as I like XUL and the idea of qooxdoo being
"close-to-a-XUL-engine", I wonder if
Thank a lot for the help ! But no, it doesn't work ... When I read the property
I recieve always 0 :
var w2 = new QxWindow("Title");
w2.setSpace(20, 250, 20, 250);
d.add(w2);
f1 = new QxIframe();
f1.addEventListener("appear", function(e) {
this.setScrollLeft(40);
});
Hi!
I've just played some minutes with our current QxListView implementation
and tried to allow a horizontal scrollbar. You can apply this patch to
your repository. This is just a hack. It seems to work (while not
looking as well as the other qooxdoo stuff), but I'm not interested in
fixing b
junglist schrieb:
uhm, so there's no real speed difference between
myWidget.setDimension("auto","auto");
and
myWidget.setDimension(QxConst.CORE_AUTO,QxConst.CORE_AUTO);
?
yes, that's true.
Sebastian
--
View this message in context:
http://www.nabble.com/Using-constants-t1395606.html#a3
uhm, so there's no real speed difference between
myWidget.setDimension("auto","auto");
and
myWidget.setDimension(QxConst.CORE_AUTO,QxConst.CORE_AUTO);
?
--
View this message in context:
http://www.nabble.com/Using-constants-t1395606.html#a3763535
Sent from the qooxdoo-devel forum at Nabble.c
[EMAIL PROTECTED] schrieb:
Yes, sorry for the mistake. The Scrollbars will stay in the right and bottom
of the window. I want to simulate a scrolling made by the user. I've worked
many years whith Delphi, and in this language the scrollbar object has a
"Position" property. This property can be se
Attached is a patch that adds API doc comments to many files in the
script/transport subdirectory. The patch is made against revision
2742. I hope it can be useful.
--
mvh Björn
Index: QxTransport.js
===
--- QxTransport.js (revision 2
Yes, sorry for the mistake. The Scrollbars will stay in the right and bottom
of the window. I want to simulate a scrolling made by the user. I've worked
many years whith Delphi, and in this language the scrollbar object has a
"Position" property. This property can be set to 0, 50, 150, ... And the
In fact, I'll try to display some information from two web sites in a single
page, using qooxdoo. Only a small part of each Web page is interesting.
So my idea is to put the Web page in a QxWindow, and then to set the Scrollbar
position to move on the usefull part. But if the user maximize a QxWin
[EMAIL PROTECTED] schrieb:
In fact, I'll try to display some information from two web sites in a single
page, using qooxdoo. Only a small part of each Web page is interesting.
So my idea is to put the Web page in a QxWindow, and then to set the Scrollbar
position to move on the usefull part. But
Hej Mar!
I agree completely on what you say. I have discussed the problem of
access, but there is so far no interest from Sebastian et al to change
it. Today it is too much work for us here to have three different
versions. Therefore we have chosen to have our own version. Sorry about
the inconven
The demo http://qooxdoo.oss.schlund.de/public/demo/test/Builder_2.html fails
and has this in the debug log:
002223:...failed:'QxXmlHttpLoader' is undefined
The same with Builder_3. Builder_4 just has this:
004166:...failed:
Hugh
---
This S
ChristophDorn wrote:
I really like the idea of using the XUL standard for qooxdoo application
layout. It makes total sense. From what I have gathered so far it looks like
a good fit.
The IoC container approach from what I can gather would make most sense to
bring the application to life for the
Hi!
You want to move the scrollbar? Could you explain it more detailed?
What's about some screenshots/sketches?
Sebastian
[EMAIL PROTECTED] schrieb:
Hello !
I'me trying to display a Web page into a QxWindow. So I've created a QxIFrame
and I've linked it to the Window :
window.applicatio
this is not a bug. It's a feature ;)
QxText, QxHtml, QxIconHtml are just fast containers to embed content.
They don't support any type of auto-sizing or preferred width/height
calculation. This was our intention to use them for fast display of any
content to embed. (This is also used internall
When putting a QxHtml in a QxVerticalBoxLayout, the QxHtml is always
treated as if it had a height of 0.
The following snipped shows the bug, the attached picture shows how it
looks: The QxVerticalBoxLayout (red background) contains the button and
the QxHtml, both having a auto-height.
The Q
Hi Kent,
you are very productive as contributor. However many of your example
do not work directly after checkout. I patched the QxExtend.diff
however you need also to copy gif in
source/themes/widgets/windows/arrows/. Now is working.
A newbie like me think: why should I put images in
widgets/windo
> IMHO it's better to not generate noise at all than to filter it out
> later.
I think this is the best reason for eliminating the warnings. In the dim dark
distant days of C++ we always worked hard at eliminating warnings in the
compilation for the same reason.
Hugh
---
Great, I'll download it tomorrw.
Thanks for the quick response. I am having an issue with updating the data in a ListView, I'll post a message about it tomorrow.
Jim
On 4/5/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
Hi Jim,thank you for your report. This was not related to the tree itself
Hello !
I'me trying to display a Web page into a QxWindow. So I've created a QxIFrame
and I've linked it to the Window :
window.application.main = function()
{
var d = this.getClientWindow().getClientDocument();
var w1 = new QxWindow("Title");
w1.setSpace(20, 385, 20, 491);
d
Hi Jim,
thank you for your report. This was not related to the tree itself, but
to the so named "enhanced border support" for all non-gecko engines.
This is fixed in SVN now.
Sebastian
Jim Hunter schrieb:
Here is a simple page that shows the problem. If you create a QxTree and
set the init
1. use QxExtent.diff
2. do tools/make.sh
before use
Kent
On Wed, 2006-04-05 at 07:31 +, Simon Bull wrote:
> > I upload the whole directory of my machine.
> > Try it out!
> >
> > Kent
>
>
> Thanks Kent,
>
> I'll checkout and try it tonight :)
>
> Simon
>
>
>
>
>
> --
> I upload the whole directory of my machine.
> Try it out!
>
> Kent
Thanks Kent,
I'll checkout and try it tonight :)
Simon
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into we
Hi Sebastian,
first of all, the CSS errors are only a minor problem, so I don't
really mind if they stay in qooxdoo (I can easily use a locally
modified version). That said, I'd still like to address the issues
you raised (see below).
Am 04.04.2006 um 20:40 schrieb Sebastian Werner:
And
42 matches
Mail list logo
