We're currently slating that for 1.2, which targets the second quarter of 2015.

On Dec 20, 2014, at 12:58 PM, Traun Leyden 
<[email protected]<mailto:[email protected]>> wrote:


Hey Brandon,

I can tell you that having a model layer is on our roadmap, but I don't know 
the exact priority.  (@Zack want to chime in on this?)

Creating a model layer that everyone loves is actually kind of tricky.  It's 
made even trickier by the fact that reflection is very expensive on Android, 
and so would have to be used extremely sparingly.

There is already quite a lot of things that can be done using Jackson to make 
the "model <-> docuement" translation fairly seamless, so I think we really 
need to be exploiting that to the max in our examples and try to get an idea of 
exactly what is missing.  We don't want to end up re-inventing the Jackson 
wheel here.

A few design considerations I'll throw out, since I'd love to hear your 
feedback:

* Would you be OK having to extend a CBLModel class, or would this interfere in 
your existing class hierarchy?

* Does the annotations approach as used in ORMLite seem to be a good approach 
for you?

* What are the biggest pain points that you want a model layer to solve for you?







On Fri, Dec 19, 2014 at 9:28 AM, Brandon Rosenbaum 
<[email protected]<mailto:[email protected]>> wrote:
Is there any sort of summary timeline available for the Java/Android API? 
Mostly I'm curious to see if any model layer work is in the pipeline for parity 
with iOS and their CBLModel functionality.

Apologies in advance for asking "do we have it yet?", but I can't seem to find 
anything recent regarding the roadmap.

--
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/a79e5836-929c-4d4c-afde-45826f0145f3%40googlegroups.com<https://groups.google.com/d/msgid/mobile-couchbase/a79e5836-929c-4d4c-afde-45826f0145f3%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/CACSSHCEPYHb3eo8t%2BWJQEkfYSysMZvusCGyHJbQDHBccw1QfrA%40mail.gmail.com<https://groups.google.com/d/msgid/mobile-couchbase/CACSSHCEPYHb3eo8t%2BWJQEkfYSysMZvusCGyHJbQDHBccw1QfrA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/0B3FC9CB-5DC2-4B28-9C65-2BE918E5DFD8%40couchbase.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to