search

GroundApps / ShoppingList_Backend

Simple Centralized Shoppinglist - php backend
GNU General Public License v3.0
27 stars 23 forks source link

Adapt backend to Api #27

Closed jklmnn closed 9 years ago

jklmnn commented 9 years ago

If https://github.com/J-8/ShoppingList/issues/27 is accepted the databases and php must be adapted. I would do the SQLite part, and the api.php.

ghost commented 9 years ago

Ok I will do MySQL part

jklmnn commented 9 years ago

I just had an idea. An item with 0 counts is possible so this just states that all of these item have been done. So we don't need to change the backend as if we just use the count also as state. This would mean that the app (and other clients, I'm currently trying to write a small Gtk+ program) just need to display 'checked' if an Item has 0 counts. What do you think about that?

ghost commented 9 years ago

I think the problem here is, when we change it like some users ask for, that you have no more count, and it is a simple list then it didn't work anymore

J-8 commented 9 years ago

Okay, get it. I like the idea of the itemCount being 0! However, we need a need way to indicate if an item is important.

J-8 commented 9 years ago

But if the item is then unchecked, the original count is lost... So maybe we do need a new column for 'checked' and 'favorite'

ghost commented 9 years ago

I think we need a table like this

Name,count,star,favourite,deleted

J-8 commented 9 years ago

Although I would not sync the favorites. So every user can have her/his own ones.

ghost commented 9 years ago

ok but wgen i have a mobile and then use the gtk client thete isno sync i think better

Create users and then share the list with them

jklmnn commented 9 years ago

Idk about favourites. I wouldn't do it now because that might be too much at once. Also user management makes things much more complicated (I still have to admit that this would make bigger installations for many people possible). User management could be also achieved by using folders, lets say like https://example.com/shoppinglist//api.php where each user has its own config but all could be pointing to the same database with different users.

J-8 commented 9 years ago

For now that seems impossible for me. I am really busy implementing all the other little things which are complicated enough.

jklmnn commented 9 years ago

I would stick with the state (I think that this state is important). The user management way I described was a way to manage users with the current state of development.

J-8 commented 9 years ago

I'll close this now as the sync for checked states is in milestone 1.2 for the app. I will open a new issue.