It's been six years and I'm also looking for a solution to bind User 
Interface with layouts stored on a remote server and i was wondering if you 
ever managed to solve this issue

Thanks.

-Carlos

El lunes, 23 de marzo de 2009, 1:10:22 (UTC-6), Daniel escribió:
>
> Hi all, 
>
> Q: What is the recommended way to build user interfaces on the device 
> based on layouts provided by a server at runtime? 
>
> I am aware of this: 
> <snip source="http://developer.android.com/reference/android/view/ 
> LayoutInflater.html 
> <http://developer.android.com/reference/android/view/LayoutInflater.html>"> 
>
> For performance reasons, view inflation relies heavily on pre- 
> processing of XML files that is done at build time. Therefore, it is 
> not currently possible to use LayoutInflater with an XmlPullParser 
> over a plain XML file at runtime; it only works with an XmlPullParser 
> returned from a compiled resource (R.something file.) 
> </snip> 
>
> I could imagine these possibilities: 
> - Parse XML by myself and build the ui tree. (Seems inappropriate to 
> me since there is already maintained code which is able to do this.) 
>
> - Transform XML on server to a simpler format which is cheaper to 
> parse on the device. (Inappropriate  as above.) 
>
> - Preprocess the XML layout on the server the same way the build does. 
> Transmit it to the client, and then try to load it. But how? 
> android.content.res.XMLBlock is hidden (@hide) and I don't know how 
> to 
> classify the stuff in package com.android.layoutlib.bridge. 
>
> Any help would be appreciated. 
> Daniel 
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/c09b3558-e006-436c-a1dd-2b0266a2ba7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to