Responsible = Luis Daniel Fernandes Rotger
theme =
property | type | required | format checking | state of implementation (master branch) in terms of attributes added and connected with the frontend |
---|---|---|---|---|
_id | integer, autoincrement | yes | isInteger | not implemented |
user_id | integer | yes | isInteger | not implemented |
name | string | yes | not implemented | |
scss_varfunc | string | yes | not implemented | |
scss | string | yes | ||
css | string | yes | not implemented | |
timestamp | date | yes | datetime | not implemented |
comment | string | no | not implemented | |
based_on | integer (id ) | no | isInteger | not implemented |
Talking with Huw Fryer we realized that there are some things that are not very clarified and should be taken in count before proposing a concrete model for this service. There are many open question regarding this matter.
The questions are:
1) Which properties are really required for our purposes in this slidewiki?
The properties scss_varfunc, scss and css are not well defined yet, we don't know yet what's the relation between them, is the css property generated through scss_varfunc and scss? If there is someone who has some knowledge of this matter from the original slideWiki it would be very helpful. Also, are properties like timestamp, comment and based_on required? This lead to other questions.
2) Can users share themes between them?
For example, is a user allowed to use other user's theme for his own deck?
3) Can themes be derived from other theme?
Will be possible for users to create new themes editing a previous one but also remaining the original? In that case the based_on property would make sense.
4) Will be the reveal.js themes stored using this model or will be treated apart only in frontend?
5) When the themes become extracted (somehow) by the import service (at some point), will they be stored also using this model?
Depending on the information that could be extracted from pptx/odp themes the model could change and contain other properties.