> How 'bout we keep the Features list open for another week, and then
put
> it into a somewhat final form. In other words, if there's something
you
> want included or excluded, now is the time to put your two cents in!
>
The features list looks great. Here are some comments/questions:
One issue that is not totally clear for me: the (internal) format in
which we are going to save "works in progress". If we can save the works
in .java format it is fine, but for me it seems that coding of this kind
of feature (saving, loading and parsing of java files) is very big and
difficult work.
What do you think about the following:
There is an "internal" model which stores all the data related to
components, containers, locations of components etc (I thing this is
needed regardless of implementation principle). The model will be
updated "automatically" when user edits the "GUI" graphically.
The model (which in practice is "work in progress") can be saved and
loaded e.g. in XML format or in any other format (.java file). If it
seems reasonable, it can be done so that it is easy to add/remove new
classes that implement the saving/loading of certain format. I am not
sure is this really needed but in this way it might be possible to add
new formats if needed.
I thing the XML (or similar) format is what should be implemented first
but we can still implement a new class that stores the model in .java
format. For me the format doesn't matter, both are ok but XML (or
similar) seems more easy to implement at the first phase.
--
Another question about the views: Is it so that there will be "editing"
view and "runtime" view. I didn't see this in the features list but I
assume those are needed?
Timo
|
