If you do decide to write your own, ask me for my JavaScript json-rpc
server. It's modern and full-featured, so is likely a good example on which
to base your php server.
Derrell
On Tue, May 12, 2015, 17:49 voger wrote:
> Thanks. I will look for this. Otherwise maybe I can write something
> my
Thanks. I will look for this. Otherwise maybe I can write something
myself. I hope it is not a overwhelming task for someone who learns as
it goes. If nothing else it will be a great learning exercise. I do have
your old code as a guide. :D
On 12/05/2015 11:43 μμ, Derrell Lipman wrote:
> Volger
Volger, look for a JSON-RPC server that someone has already created for
elgg. It's highly likely that one exists. Back in the day, the qooxdoo
JSON-RPC client was not quite standards compliant, but the current version
is, I believe, compliant (but not entirely complete, e.g., it doesn't
support bat
Dear Derrell and Christian
I thank you very much for your trouble and the time you took to help me
with my question. I suppose I have to make these two frameworks,
somehow, speak the same language. At least now I know which path should
I take. Thank you both very much.
voger
On 12/05/2015 10:
That address for Christian didn't work. Let's try a different one...
On Tue, May 12, 2015 at 3:28 PM Derrell Lipman <
derrell.lip...@unwireduniverse.com> wrote:
> Hi Voger,
>
> Having now looked at elgg, I understand your confusion. The issue is that
> elgg does not provide a standards-based JSO
Hi Voger,
Having now looked at elgg, I understand your confusion. The issue is that
elgg does not provide a standards-based JSON-RPC server; rather, they
provide, as they describe it, a REST/RPC hybrid. In other words, it appears
that their server won't interoperate with anything that sends standa
I am one of the original authors of that rpc code. It's been a long time
since I looked at it. I'll review, and see what elgg is, when I get home,
and post a response.
Derrell
On Tue, May 12, 2015, 14:02 voger wrote:
> Sorry for the very nobish question but I don't know how to proceed with
> th
Sorry for the very nobish question but I don't know how to proceed with
this. I have built a basic UI for my app and naturaly now I want to
communicate with the server. I understand the way to go is JSON-RPC and
yes I have seen the jsonrpc_server_specs page in the documentation.
I am using in t
Thank you Mustafa, but in this sample, drag emitter and drop receiver are
very tight (they know each other, so you can directly give the image to
move).
If you want them completely independent, you have to ask e.getData("image")
in the drop event after the dialog replies yes. The problem is that t
Tinyurl is not working with my code example, so feel free to copy it from this
email:
qx.Class.define("Modal", {
extend : qx.ui.window.Window,
construct : function(image, targetWidget)
{
this.base(arguments, "Confirm");
this.set({
modal : true,
layout : new qx.ui.layo
Hello Mustafa,
Thanks a lot for how to circumvent the issue, it works perfectly. I report
the bug #9136.
I have another question around drag&drop:
I would like to make a drag&drop with a modal dialog box in the "drop"
listener method, so that the drop takes place if the user agrees.
The problem
Hi,
would you please report a bug for this issue?
But for the mean time you could bootstrap by setting an attribute to the image
DOM element:
Img.getContentElement().setAttribute(“draggable”, “false”);
Gruß
Mustafa Sak
Applications & Integration
1&1 Internet AG | Ernst-Frey-Straße 10 | 76135 K
Hello,
I sent this some days ago but I've had no reply since.
Meantime, I was able to bring some details:
I'm trying a drag&drop of an image in IE 10, qooxdoo 4.0.1, and the drop
target is never activated. I think this is due that IE creates a shallow
copy of the image in the dragging operation.
13 matches
Mail list logo
