You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RDFauthor needs a own stylesheet. At the moment rdfauthor uses the ontowiki dom structure for windows like propertypicker or any popup widgets. Outside of the OntoWiki environment the popup style is corrupted. Therefore it is necessary to create an own rdfauthor stylesheet.
Below are some screenshots of popups, which needs an own style (including one corrupted):
The text was updated successfully, but these errors were encountered:
First, indepentent from this task we need an improved OntoWiki GUI and OW Javascript API anyway. There is already one branch, even if I think that the simple approach using just the Twitter Bootstrap stuff won't be successful longtime.
Second, I think that RDFauthor do not need just other styles. It needs JS-Templates/Views and a separation between functional markup (classes and IDs used for RDFauthor JS) and layout markup (used to style).
I would suggest a dev meeting to discuss the future of OW/RDFauthor GUI/JS, with all active developers on one table (should be possible b/c the most of them working in Leipzig/AKSW). Maybe in January? I would collect all my suggestions on future GUI/JS developments and present them as foundation to discuss it.
it is urgent in the sense that it is the base of a deliverable of LOD2 so we should have that soon.
Can make an abstract which component we should use on a general refactoring?
RDFauthor needs a own stylesheet. At the moment rdfauthor uses the ontowiki dom structure for windows like propertypicker or any popup widgets. Outside of the OntoWiki environment the popup style is corrupted. Therefore it is necessary to create an own rdfauthor stylesheet.
Below are some screenshots of popups, which needs an own style (including one corrupted):
The text was updated successfully, but these errors were encountered: