First of all, I am glad that I
have passed the mid-term evaluation. Now, I have got more thrust to
move on with the project, complete the price feature, optimize the
interface and incorporate the cloud sync feature into the
app.
This week, the mean focus is
still on store-wise price calculation. It has been pointed out that
the bug in android has been fixed and after updating my source
version, I am able to run the android version smoothly. There I
finally got the full picture of the app.
There was an discrepancy
between my previous understanding of store-wise price calculation
and the one that Android is using now. My understanding was, store
would be primarily associated with items, since that is the thought
that most people have in real-live. While in the Android app,
stores were associated with list. This makes the implementation
easier. I took the second approach after considering the two.
Firstly because it is more manageable; secondly because of the
consistency crossing different platforms.
After clearing the
mis-understanding of how it is done. I continued with my
implementation.
The data-model has to be
slightly adjusted, as follow:
the list_id is a to-one type of
relationship
each store is “tied” to a list,
removing the list would remove the store.
Then I went on to realize the
interface, The challenge was, I have to use a customized a table
cell with textfield in it. The approach I took was to subclass the
text field, and add a property “store name” to each of the
textfield. So that when user modifies the price, I would always
know it is the price in WHICH store that is being
modified.
The store-wise price menu is in
the edit entry detail menu, a screen shot is attached
below.
No comments:
Post a Comment