Tom Schindl <[EMAIL PROTECTED]> wrote on 04/24/2008 02:31:08 PM:
> If JSON is the interface we want to match this is IMHO a bad decision.
> It always boils down to the fact that by concentrating so much on
> Scripting-Community that we forget about there are still a lot of people
> who want to interface with our model using plain old java and JSON is
> nothing more than a little bit more than HashMapWrapper. In my last
> project I did AJAX and it's like hell if your model get's a bit more
> complex.
>
Ok, now we're getting somewhere. Can you talk a bit more about this? What
were the pain points? How do we address them?
Fundamentally, my view has been -- yes, I know I need to do a position
paper -- that we are moving to a model where the underlying functionality
the workbench provides is accessed like it was being provided via services
over the web. Of course, you would use a more reasonable Java (or
JavaScript) mapping of those services, and maybe that's how we avoid some
of the "hell" you hit, but that split would still be there.
McQ.
_______________________________________________
eclipse-incubator-e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
