| Summary: | [repetitive] Schedule colours are hardcoded to CSS files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Denis Roy <denis.roy> | ||||
| Component: | Dash Submission System | Assignee: | Denis Roy <denis.roy> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | anne.jacko | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
(In reply to comment #0) > > It would be great if the sub system could allow us to define the colours when > we define tags and categories -- that way, when the schedule is rendered, we > could just generate a <style> block and define the CSS styles there, from the > database. That would be great! |
Created attachment 178834 [details] Screenshot Sub system talks can be of a type (long, short, symposia, etc) and can be in one category (e4, modeling, runtime, etc). Both of these attributes can change from one conf to the next. When rendering the schedule, the cell colours are tagged according to both of these attributes. In return, one must hardcode the proper tags in the CSS (static/conferencesytles). It would be great if the sub system could allow us to define the colours when we define tags and categories -- that way, when the schedule is rendered, we could just generate a <style> block and define the CSS styles there, from the database.