Okay, I'm not you and Shuman, he is unavailable, so I will try and present and his behalf
is best as I can.
He's from a web dialogue which has been on LOT, which is Libra Office Technology, because
I've prepared for this talk and I know that, so what is this?
The various dialogues in Libra Office are described in these data UI files, XML files, the
destruction properties of the dialogues, so that XML input gives you this output on the
left in detail, G2K, for example, as which points you have very graphic editor, has
glued our contemporary ones where you can edit the dialogues and you convert them and
you can interact with that structure there.
So that's just what you have in Libra Office and how those dialogues exist already, and
for the purposes of Libra Online or something like that, we have G-style x, which is a framework
for exposing those UI components over into the online LOT experience.
Hello, do you end up with there is that you have on the server side, you have the same
kind of dialogues internally, you get on the desktop situation, and the snapshot of the structure
there is dumped into a JSON thing, and it's sent over the wire to the online side, and
in the online side it takes a JSON, and similarly to what you have in the server side where
you load up your UI and you create dialogues from that, you view our builder on the online
side that takes that JSON, and it constructs dialogues from it, initially constructs dialogues
from it.
Then afterwards it can be used to update the dialogues when things changed and the server side
are transmitted across in this JSON, when you make changes, as I say, on the server side
that something is selected or the text is changed, it comes across in this JSON, and this
UI builder and whatnot updates everything on the client side.
You give you dialogues on the client side that are basically transmitted from the server
side.
There's a bit of flexibility here, and this G-style log builder, when it gets the input in,
you can unlock the limitations that can decide on different ways to express that information.
So you can have your classic notebook bar shown at the top of the online browser, the same
as similarly to get the desktop experience, are for a smaller platform for mobile device.
You can convert that and show it in different ways.
So if we take a look at the classic side bar shown in the middle, you can see on the right
side that side by information is being displayed, suitable for mobile device, in smaller,
in a different view of that data, which is very visually different than the source data
comes from.
So the layer of depth to different things, other things that are available in G-style log
is that there's backmode support at the kind of in which it level you just say, you know,
drawn backmode and we have these two various themes going on there like that.
And again, the hint is that two air layers of, when you send over your dialogue, first
you get this full update and for optimizing reasons, we try to apply minimal updates as
possible.
So if a small part of the symmetry changes, we just update that tree and update what's
required there.
And in many cases, we can get away with just updating the single widget, if we know what
the actual specific action that's been done is.
So if we know something that's been enabled, we know what's about and we can just
fire on button enabled.
And if we don't know what's going on, and there's been some kind of global refresh, you
have to do a full update, we want to minimize that.
So the partial updating of a dialogue is possible, which is dialogues.
What's relative in new for this G-style, I think, is that the style we use in desktop
for rendering the font widgets and other previews like that are now available in G-style
log as well.
So these are on-demand rendered in the sense that there's like whatever 12 or 15 entries
here that need to be shown.
And then the online says, please give me the preview images for these 15 slots and they
come back and they're shown there like that.
So there's on-demand a rendering for these new custom displays and that that.
What's also new as well, or a bleed as new as well, is the ability to show what the keyboard
accelerators are for various things like that.
So you can interact.
You can bring up this heads-up display to show you what are your shortcuts for the notebook
bar.
An accessibility front then, I think I've said in various other talks, but it's the same issue
here again, is that you want to provide as much a possible custom widgets and especially
for online where these custom widgets, you may even have accessible implementations for
them on the desktop side, but that's no particular use to in the online side.
If you have basically a canvas and you draw on various things to it, then you are just drawing
things to it from the online side as well and you can get information from us.
So this is an example where we have value sets over on the liberal upper side, which have
accessibility information, but that accessibility information isn't available on the browser
side, so it is much more convenient for us to move away from such a value set, change it
into a more standardized icon view thing as well, and then I can view thing on the browser
side, has the accessibility information to know that something is a picture and that
the text is a label for that and you get that accessibility stuff for free.
So it's an example of where we've moved value sets for that previews here into icon
views and a file that changes take place in the edges out for accuracy purposes.
And that's a big afternoon, thank you.