Benjamin Reitzammer schrieb:
Hi,
Ben Alex wrote:
I think it would be valuable if there was a high-level architectural
diagram showing the layering you had in mind for this project, such as
where XML is generated, parsed, data exchanged, JavaScript written,
and language-specific callbacks used
Hi,
Ben Alex wrote:
I think it would be valuable if there was a high-level architectural
diagram showing the layering you had in mind for this project, such as
where XML is generated, parsed, data exchanged, JavaScript written, and
language-specific callbacks used. This would allow further dis
> maybe
> php-backbone
I think that is too generic and sets too high of an expectation.
It looks like there will be several projects covering different aspects of
the proposed framework. Maybe we should wait with names until we have an
exact idea what each project will do. Unless you think o
Hi!
> I am interested in leading a qooxdoo / PHP framework project. I am not
> sure what the best way to go about this is.
>
> One option is to have it as a sub-project of qooxdoo with its own SVN
> repository and mailing list. The other option is to register it as a
> new separate project.
I v
It may be a good idea to split this into two projects.
One would focus on developing an XML schema to describe a qooxdoo
application and converters to generate the javascript code. The converters
should support multiple languages (php, java) and possibly even XSL.
My main interest is on the php s
Christoph Dorn wrote:
I am interested in leading a qooxdoo / PHP framework project. I am not
sure what the best way to go about this is.
Hi Christoph
I have read the remainder of this thread, and as far as I can see the
proposed framework is XML-based. Is this correct? What PHP-centric parts
1) qooxdoo-php
2)i think a new separate project is even better, because then you are
independend and can "make your own things" - but both projects should
"link together"
Olli
Christoph Dorn schrieb:
I am interested in leading a qooxdoo / PHP framework project. I am not
sure what the b
I am interested in
leading a qooxdoo / PHP framework project. I am not sure what the best way to go
about this is.
One option is to
have it as a sub-project of qooxdoo with its own SVN repository and mailing
list. The other option is to register it as a new separate
project.
I am leanin
> This is still done. But (sorry for that but ;-) i am parsing the
> js-files and create a PHP-Array out of it.
> The second uses this array to build the MINIMAL JavaScript-File possible.
> I am creating a PHP-Array, because i
> think this is even faster than parsing a xml-file.
Ok. That will be f
remove theme.diff
add QxExtend.diff
Kent
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking i
ist that just me or is all Transport examples utterly broken
for IE? mozilla/firefox works fine thou.
i couldnt get any of these here run:
http://qooxdoo.oss.schlund.de/public/demo/test/Transport_*
yozzeff
---
This SF.Net email is sponsored by
> Yes, but again I think that using XML to describe the widgets should be
> the aim. This would also mean that you can exchange GUI templates with
> other backends implemented in other languages. I cannot sing the praise
> enough of TAL which is used in the Zope server and has implementations
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
Index: source/script/core/QxExtend.js
==
What overhead? 3 short lines? one item in the pp structure?
I don't like dirty hacks like the proposed, then the code will be
difficult to follow and not qooxdooish anymore...
I will still stay with the proposed.
Kent
---
This SF.Net email
ChristophDorn schrieb:
soon. My main focus was re-usable low-level components that any application
can benefit from. One major requirement was that you can use these
components within any other framework without conflict. I am hoping that the
components will start to establish some standards for
Dear Sebastian,
anyway, thanks a lot and i will try later, if success, i will mail you
later :)
with regards:)
=== 2006-04-03 15:34:00 您在来信中写道：===
>You can only send text data. You must convert it to text in some way. I
>haven't tried this yet. I'm sorry.
>
>Sebastian
>
Hi Mengya,
Mengya Tang schrieb:
> Hi, Sebastian,
>
> === 2006-04-03 14:19:00 您在来信中写道：===
>
>> Mengya Tang schrieb:
>>> Dear all,
>>>
>>> Is there any example to explain how to use XML parser?
>>> As i see in Transport1.html, when we click on "send", the area
hi,
honestly i dont know if this is either a bug in
- qooxdoo
- firefox
- linux
- webrick (a ruby http-server)
given the following code
var req = new QxRequest("http://localhost:8080/query";, "GET", "text/json");
req.setAsynchronous(true);
req.setParameter("params", '{"p1": "val1", "p2": "val2
You can only send text data. You must convert it to text in some way. I
haven't tried this yet. I'm sorry.
Sebastian
Mengya Tang schrieb:
> Dear Sebastian,
>>
>> === 2006-04-03 15:09:00 您在来信中写道：===
>>
>>> Hi Mengya,
>>>
>>>
>>> Mengya Tang schrieb:
Hi, Sebastian,
>>
Hi, Sebastian,
=== 2006-04-03 14:19:00 您在来信中写道：===
>Mengya Tang schrieb:
>> Dear all,
>>
>> Is there any example to explain how to use XML parser?
>> As i see in Transport1.html, when we click on "send", the area show the
>> whole requested file, how can i extract some useful
Hi, Sebastian,
>
>=== 2006-04-03 14:19:00 您在来信中写道：===
>
>>Mengya Tang schrieb:
>>> Dear all,
>>>
>>> Is there any example to explain how to use XML parser?
>>> As i see in Transport1.html, when we click on "send", the area show the
>>> whole requested file, how can i extract some
Jeronimo Milea schrieb:
What happened to it, it seems that i'm unable to find it un currens
source :S
It has gone?, needs reimplementetion?
Please take a look at these Transport_* examples. They use the new
QxRequest stuff which is the new replacement for the old QxXmlHttpLoader.
Sebastian
Dear Sebastian,
>
>
>=== 2006-04-03 15:09:00 您在来信中写道：===
>
>>Hi Mengya,
>>
>>
>>Mengya Tang schrieb:
>>> Hi, Sebastian,
>>>
>>> === 2006-04-03 14:19:00 您在来信中写道：===
>>>
Mengya Tang schrieb:
> Dear all,
>
> Is there any example to explain how to use XML
Dear Sebastian,
=== 2006-04-03 15:09:00 您在来信中写道：===
>Hi Mengya,
>
>
>Mengya Tang schrieb:
>> Hi, Sebastian,
>>
>> === 2006-04-03 14:19:00 您在来信中写道：===
>>
>>> Mengya Tang schrieb:
Dear all,
Is there any example to explain how to use XML parser?
Hi Kent,
thank you for this patch.
However we don't think it's a really useful addon. These alias stuff is
just for convenience. And therefor it's enough in my opinion to support
only one alias. We also don't support multiple types here. Probably we
will change this in the future all in one s
Hi Thomas,
I am sorry. This is really too much code. Could you please send your two
examples stripped down as much as possible as attachments which directly
work from our demo/test folder. Thanks.
Sebastian
Thomas Oeding schrieb:
Hello list,
i have a small problem with the QxMenu events
Kent Olsson schrieb:
One solution
It is needed to change the following:
1. the type of setProperty can only have one type not a list of types
for example if a label has a text string and a function retrieving
the text string as in localisation. QxExtend class.
2. then the rend
Mengya Tang schrieb:
> Dear all,
>
> Is there any example to explain how to use XML parser?
> As i see in Transport1.html, when we click on "send", the area show the
> whole requested file, how can i extract some useful informtion by parsing the
> file and then show in th
Committed to the contributed SVN folder.
Sebastian
Kent Olsson schrieb:
I hope this works in your machines right out of the box.
Known general problems:
1. add a QxListView
It is already a very buggy class, and together with QxSplitPane it
becomes worse.
2. add a QxTree
The ugly
hi,
the following code bombs my layout into oblivion.
function MyTable()
{
this.data = [];
this.columns =
{
state : { label : "state", width: 50, type: "image" },
};
QxListView.call(this, this.data, this.columns);
}
MyTable.extend(QxListView, "MyTable");
really i will se
i'm interested too
--
View this message in context:
http://www.nabble.com/Change-of-UI-to-work-with-localisation-t1384308.html#a3722054
Sent from the qooxdoo-devel forum at Nabble.com.
---
This SF.Net email is sponsored by xPML, a groundbreak
31 matches
Mail list logo
