Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve export generation #23

Open
pkubatrh opened this issue Feb 18, 2016 · 2 comments
Open

Improve export generation #23

pkubatrh opened this issue Feb 18, 2016 · 2 comments

Comments

@pkubatrh
Copy link
Contributor

Currently the export is generated on demand.
It should however exist as a static text that gets updated only when something is changed (events, schedule, speakers).

pkubatrh pushed a commit that referenced this issue Feb 18, 2016
related to #23

Signed-off-by: Petr Kubat <xkubat11@stud.fit.vutbr.cz>
pkubatrh pushed a commit that referenced this issue Feb 21, 2016
related to #23

Signed-off-by: Petr Kubat <xkubat11@stud.fit.vutbr.cz>
@jmlich
Copy link
Contributor

jmlich commented Feb 22, 2016

Toto reseni podle meho nazoru neni idealni. Export se sklada ze strasne moc dat a bude potreba dohlidat pregenerovani vseho kdyz zmenim jednu polozku sdilenou pres vic konferenci (napriklad uzivatele, bod na mape, jmeno mistnosti).

@pkubatrh
Copy link
Contributor Author

Souhlasim. Na druhou stranu stavajici reseni, kdy by se napr. pri pristupu k seznamu konferenci musely generovat vsechny jsony vsech prednasek jen kvuli checksumu, mi take neprijde idealni.
Osobne se mi vice zamlouva toto reseni. Mozna by ale bylo lepsi nehlidat vsechny zmeny, ale napr. jen zmeny v programu (prijdou mi jako nejdulezitejsi) a v pripade jinych zmen vytvorit tlacitko pro manualni vygenerovani exportu, pripadne export generovat periodicky.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants