2014-07-17, 12:51
1) profile is on db so all xbmc read the info from there, in the config file or UI just the db address is needed.
2) if you use transactions the data on db is always statefull and users will be saved correctly. Like every system the first user you create is the "admin" able to create and/or modify other users. The other users can be admin or user (no mod on users). Admin can decide who sees what's.
This management is very flexible so you can associate content,menu items, etc...to a profile. Its more on the UI side than on the db. This is another advantage in terms of flexibility on the UI
3) once we build a structure that is correct and flexible as a first step probably we can simply "migrate" actual behavior and then evolve.
4) totally agree with you, no dreams but challenging objectives . I do not think is a trivial change but is mandatory to bring xbmc to the next level and the more we wait the more it will be bad/impactfull because will continue to grow in time. A "design flaw" (aka requirement changed over time, not saying it was wrong) need to be fixed as soon as possible.
anyway started to download all code, trying to get a successful run and this thread and other info is helping me a lot. Will start to analyze queries and data then will try to propose something to the team, starting from design...
2) if you use transactions the data on db is always statefull and users will be saved correctly. Like every system the first user you create is the "admin" able to create and/or modify other users. The other users can be admin or user (no mod on users). Admin can decide who sees what's.
This management is very flexible so you can associate content,menu items, etc...to a profile. Its more on the UI side than on the db. This is another advantage in terms of flexibility on the UI
3) once we build a structure that is correct and flexible as a first step probably we can simply "migrate" actual behavior and then evolve.
4) totally agree with you, no dreams but challenging objectives . I do not think is a trivial change but is mandatory to bring xbmc to the next level and the more we wait the more it will be bad/impactfull because will continue to grow in time. A "design flaw" (aka requirement changed over time, not saying it was wrong) need to be fixed as soon as possible.
anyway started to download all code, trying to get a successful run and this thread and other info is helping me a lot. Will start to analyze queries and data then will try to propose something to the team, starting from design...