If you think of event names as "messages", it becomes clearer. For
example, you might want to route messages to different objects to handle
them, or, as in my case, route specific events to the server. In my
current implementation, I have an event monitor which listens for events
starting with "ser
Hello,
I use qooxdoo on multiple hosters and the PHP configuration is not the same
all the time.
To have the same behavior with RPC calls with the current
[qooxdoopath]/backend/php/services/index.php file , I have updated this
script to work with magic_quotes_gpc parameters set to "On" or set to "
> The problem with a whitelist is that one should be able to use a monitor to
> determine what events are being dispatched. In other words, we don't always
> know which events are interesting ahead of time. To set up the whitelist,
> you
> have to already know, so that pretty much defeats that p
Concerning the purposes that I need, I wouldn't mind having a separate
message bus which is unconnected to the event system - as long as it
gets implemented before 0.7 comes out. I am interested in *events* only
as far as I use them to dispatch global messages carrying data with
them. I can eas
The same in qx.ui.core.Widget, property "dropDataTypes".
Please add "nullable: true".
Maybe a better solution is to automaticly set nullable to true if no
init-value is given?
Erich
Erich Konicek schrieb:
> Please can somebody add "nullable: true" to the "value" property in
> qx.ui.form.ListIte
Sebastian Werner <[EMAIL PROTECTED]> writes:
> Am 18.05.2007 um 14:11 schrieb [EMAIL PROTECTED]:
>
>> Sebastian Werner <[EMAIL PROTECTED]> writes:
>>
>>> I don't like the solution to be integrated in qx.core.Target. I would
>>> like it better to add specific events to a special event router which
Am 18.05.2007 um 14:11 schrieb [EMAIL PROTECTED]:
> Sebastian Werner <[EMAIL PROTECTED]> writes:
>
>> I don't like the solution to be integrated in qx.core.Target. I would
>> like it better to add specific events to a special event router which
>> then informs registered objects about any of thes
Another question would be if this would not work better at all using
a MessageBus class comletely separated from "Target". Is it really
useful to have events and bus informations combined. Why not use one
of them exclusively? Or let the MessageBus fire additional events for
registered objec
> Christian Boulanger wrote:
>> I think the event system is powerful and can be used as a general
>> message
>> bus for non-time-critical business logic. Instead of objects calling
>> each
>> others' methods, objects issue messages with data which are then picked
>> up
>> by other objects for handl
> Christian Boulanger wrote:
>> I think the event system is powerful and can be used as a general
>> message
>> bus for non-time-critical business logic. Instead of objects calling
>> each
>> others' methods, objects issue messages with data which are then picked
>> up
>> by other objects for handl
> Christian Boulanger wrote:
>> I think the event system is powerful and can be used as a general
>> message
>> bus for non-time-critical business logic. Instead of objects calling
>> each
>> others' methods, objects issue messages with data which are then picked
>> up
>> by other objects for handl
Sebastian Werner <[EMAIL PROTECTED]> writes:
> I don't like the solution to be integrated in qx.core.Target. I would
> like it better to add specific events to a special event router which
> then informs registered objects about any of these events. This is a
> lot cleaner than exclude table
Hello Sebastian,
sounds good to me - I also think that additional computing load must be
avoided at all costs - Derrell and I have been talking about it here:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=422
I have implemented a custom event routing mechanism which forwards
specific events to the
Hi Joe,
there is no widget imho, but Google Maps works well for me now - please
visit the thread
HTML+JS contents inside qooxdoo components (
http://www.nabble.com/HTML%2BJS-contents-inside-qooxdoo-components-tf3685998.html
)
or ask me for more, if you need to.
Cheers
Torsten
Joe Hudson-2 wro
Hi Laurent,
Google Maps works well for me now - please visit the thread
HTML+JS contents inside qooxdoo components (
http://www.nabble.com/HTML%2BJS-contents-inside-qooxdoo-components-tf3685998.html
)
or ask me for more, if you need.
Cheers
Torsten
Laurent RAHUEL-3 wrote:
>
> Hi,
>
> Playing
Christian Boulanger wrote:
> I think the event system is powerful and can be used as a general message
> bus for non-time-critical business logic. Instead of objects calling each
> others' methods, objects issue messages with data which are then picked up
> by other objects for handling.
That is,
Hi Fabian,
thank you, that does the job right :-)
Cheers
Torsten
Fabian Jakobs-2 wrote:
>
> Hi Torsten,
>> based on this solution I want to show a google map in a
>> qx.ui.pageview.tabview.Page .
>> My code looks like this:
>>
>> var gmaps = function() {
>> ...
>> map = new GMap2(docume
Hi Torsten,
> based on this solution I want to show a google map in a
> qx.ui.pageview.tabview.Page .
> My code looks like this:
>
> var gmaps = function() {
> ...
> map = new GMap2(document.getElementById("map"));
> ...
> }
>
> var container = new qx.ui.basic.Atom('');
> container.addEventLi
I don't like the solution to be integrated in qx.core.Target. I would
like it better to add specific events to a special event router which
then informs registered objects about any of these events. This is a
lot cleaner than exclude tables and a deep integration in
core.Target. The overhea
Hi,
based on this solution I want to show a google map in a
qx.ui.pageview.tabview.Page .
My code looks like this:
var gmaps = function() {
...
map = new GMap2(document.getElementById("map"));
...
}
var container = new qx.ui.basic.Atom('');
container.addEventListener("appear",
f
Hi,
My solution is for all tables.
Derrell's solution is the right one for specific cells/tables
Jose Leon wrote:
>
> Would that work for a single table object or for all the objects in
> the application? I need different customizations for different tables,
> not change the whole theme, for e
21 matches
Mail list logo
