Some Background and Important Details
There are 4 Developer panes (that get shown when a user selects 'Developer' in their preferences. The reason I think we may want to consider moving at least RDFXML and N3 is that I think the 3 dot menu is going to become a bit too long.
User Preference Screen

In the new design we are moving away from the tray of icons shown here
Instead it will look like this:
A regular resource/file:

A container resource:
The Current Developer Panes, all currently read-only
- RDFXML - serializer from rdflib used to converts resources with statements such as Turtle, N3, RDF/XML, JSON-LD, and similar RDF resources
- N3 - serializer from rdflib used to convert resources with statements
- Data - also works on resources with statements (walks the RDF graph and displays it as a tree/table)
- Default/About - renders the subject’s direct statements plus inverse statements, and it also shows the add-new-triple control when the document is editable, so it is more of the general-purpose outline pane than a file-type-specific pane.
Where should we put these in the new design?
There are a few options.
- We could keep them all together and show them in the 3 dots menu for both resources and resource Containers, again they would be shown only for users with 'Developer' selected.
- We could include them as part of the source pane instead, but still look at User preferences for the Developer role. the RDFXML and N3 could be easily written to show them in the editor. The other 2 would need to be shown in a different div I think since they have links and the default has some edit functionality that probably wouldn't transfer easily to an editor. But basically we could move all these panes (they would no longer be a pane) into source pane where a Developer would probably want to work anyway.
- Perhaps we could do a combination (moving RDFXML and N3 to source pane) and the other 2 (dataContent and default) in the 3 dots menu.
Some thoughts/questions:
- Is there a possibility for other developer panes to be created? If so by moving them to source pane and not having them as panes it would be harder for someone to create a new one/new functionality. They'd need to modify source pane.
- We still have the 'Pretty' functionality - could we allow Developers to edit files in RDFXML and N3 (a new feature). Easy to do technically if they use the editor.
- If we keep RDFXML and N3 as panes I think we need to add the Editor from source pane to the panes themselves so we can have syntax highlighting, I think it would look nicer.
Some Background and Important Details
There are 4 Developer panes (that get shown when a user selects 'Developer' in their preferences. The reason I think we may want to consider moving at least RDFXML and N3 is that I think the 3 dot menu is going to become a bit too long.
User Preference Screen

In the new design we are moving away from the tray of icons shown here
Instead it will look like this:
A regular resource/file:

A container resource:
The Current Developer Panes, all currently read-only
Where should we put these in the new design?
There are a few options.
Some thoughts/questions: