Hi,
We had out eighth client meeting. It went pretty well. There was some consternation at a few things, but overall the demo succeeded. Ackley also told us that this would be the final client meeting; that classes resume normally next week.
There's not much to say other than that the functionality is complete, and it's just bugfixes.
One issue popped up for the serializer/deserializer. It appears that the menu objects are represented as Java objects (as they probably rightly should be). The issue is that their internal representation is a canvas. So, when we serialize the webpage, we serialize that canvas. But, when we deserialize it, the canvas is deserialized, but the menu's object is not recreated.
I was not aware of this problem, and my group members only let me know about it around 10pm or so Tuesday night (the night before the client meeting). I wondered why this was.
But, in any case, there wasn't time to fix it. My solution was to deserialize normally, and then simply pick the canvas out, and add it to a new menu object. However, Theo proposed treating the menu canvases as special primitively serializable types (like Integer and String). I objected, but we eventually went with Theo's plan. Ackley independently suggested the two solutions and made effectively the same value judgments we had about them.
So, we're working on the deserialization of menus.
Ian
No comments:
Post a Comment