Discussion: Elemental Json

159 views
Skip to first unread message

Manuel Carrasco Moñino

unread,
Aug 1, 2014, 11:07:59 AM8/1/14
to google-web-tool...@googlegroups.com

Hi all

There is a patch [1] from Thomas in gerrit for spliting elemental apparently in 3 libraries:
- elemental-collections
- elemental-json
- elemental

1.- What are the plans with elemental-json and elemental-collections? 
2.- Are they though to replace some similar stuff in gwt-user like JsonUtils?
3.- Could it replace Json code in server side depending org.json?
4.- Is someone working on spliting the code?


Thanks
- Manolo


Goktug Gokdogan

unread,
Aug 1, 2014, 8:35:44 PM8/1/14
to google-web-toolkit-contributors
(Responded for the parts that I know the answer for)


On Fri, Aug 1, 2014 at 8:07 AM, Manuel Carrasco Moñino <man...@apache.org> wrote:

Hi all

There is a patch [1] from Thomas in gerrit for spliting elemental apparently in 3 libraries:
- elemental-collections
- elemental-json
- elemental

1.- What are the plans with elemental-json and elemental-collections? 

We are probably re-think everything with Elemental 2.0.
 
2.- Are they though to replace some similar stuff in gwt-user like JsonUtils?
3.- Could it replace Json code in server side depending org.json?
4.- Is someone working on spliting the code?

Not on our side.
 

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtc9z3nbmrfz0Ev%3D3SSFk%3DPZJY%2BBtk_03xOgiVwReHTrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Ray Cromwell

unread,
Aug 1, 2014, 8:55:17 PM8/1/14
to google-web-toolkit-contributors
It is likely that all of the non-collections stuff is going to be
totally redone with JsInterop.
The actual collections interfaces (ArrayOf, etc) as well as Json, we
may keep because it is useful to to have JRE implementations to work
in a shared context.

However, the implementations backing those are likely to be completely
rewritten to use JsInterop. I don't mind splitting things up in
elemental if they want. My gut feeling is that Elemental 2.0 may have
a completely different package structure.



On Fri, Aug 1, 2014 at 8:07 AM, Manuel Carrasco Moñino
<man...@apache.org> wrote:
>

Manuel Carrasco Moñino

unread,
Aug 6, 2014, 5:56:31 PM8/6/14
to google-web-tool...@googlegroups.com
On Sat, Aug 2, 2014 at 2:55 AM, 'Ray Cromwell' via GWT Contributors <google-web-tool...@googlegroups.com> wrote:
It is likely that all of the non-collections stuff is going to be
totally redone with JsInterop.
The actual collections interfaces (ArrayOf, etc) as well as Json, we
may keep because it is useful to to have JRE implementations to work
in a shared context.

Sounds well, so we can trust that they will remain in Elemental, and the API should be similar, right?
 

However, the implementations backing those are likely to be completely
rewritten to use JsInterop. I don't mind splitting things up in
elemental if they want.  My gut feeling is that Elemental 2.0 may have
a completely different package structure.

Any plans for Elemental 2.0? Someone working on it?

In the meanwhile, I've done a couple of fixes so as tests can be run in builds, next will be a patch for passing Json and Collections tests in JRE, sounds it reasonable for you? could you take a look in gerrit? 

 
Reply all
Reply to author
Forward
0 new messages