Open GoogleCodeExporter opened 9 years ago
Unfortunately, as appinfo may contain child nodes, supporting it presents a
significant challenge. defer to future.
We will need to come up with a way to do this *without* introducing <N>ode
parameterization. Perhaps we could do so by storing the information as a
character stream (string), and supply a fragmentbuilder as an argument to the
getAppInfo() call?
Original comment by aale...@gmail.com
on 24 Oct 2012 at 3:23
If we introduce an object that pairs the bridge and the node (or perhaps just
support the use of cursor for this use-case?) then the schema model can contain
the app-info without being parameterized based on the kind of tree used for
parsing the schema.
Shouldn't be too hard to do, but deserves being deferred until we have a
specific use case that requires it.
Original comment by eric%tib...@gtempaccount.com
on 24 Oct 2012 at 4:30
Original issue reported on code.google.com by
yury.ska...@gmail.com
on 15 Oct 2012 at 3:09