mugle-dev team mailing list archive

[Prageeth Silva <730086@xxxxxxxxxxxxxxxxxx>]

Yes you were correct in saying that we would have to do it for every
field manually. I can't seem to think of a way to get this done in a
generic manner.

As I was suggesting yesterday, given the use of annotations work, this
could still mean that we have to manually select which fields need to be
hidden or not. This also takes us back to the same problem; any mistake
in the selection could result in the same issue you mentioned above.

Anyhow, should I go ahead and implement what I already planned? Or
should I wait till the decision is finalized?

-- 
You received this bug notification because you are a member of MUGLE
Developers, which is subscribed to MUGLE.
https://bugs.launchpad.net/bugs/730086

Title:
  Add Serializable classes of model to be passed by GWT RPC

Status in Melbourne University Game-based Learning Environment:
  New

Bug description:
  Write serializable versions of each of the model classes to be passed
  over by GWT RPC so they can be accessed by the client side of the
  platform;  Should only have getters (and setters ?), and should only
  contain information the client side should be able to see (so there'll
  need to be 2 versions of some of the model classes according to the
  public/private nature denoted in the Platform View)