|
|
|
Jean Marc : can you test the currentWorkspace feature and if it's OK, I will had the same stuff for Sections.
OK, I'm testing it with workspaces and I restrict the "theme" tab to workspaces for now.
What is needed then is an abstraction in the API so that it doesn't matter if the nearest unit is a section or a workspace, or a room, or a space ... Maybe we need a new facet for the Workspace and Section types? How should it be named? PlacefulArea? ThemeArea?
Just call it 'space', that would include workspaces, sections, ... but not simple folders. It should be possible for other document types to tell that are a type of 'space'.
then no need to refer to 'theme' or 'placeful', since that has to do with the use that we do of it. also a new Seam context variable is needed to replace 'currentWorkspace' with 'currentSpace' or call it 'area', 'currentArea', ... Ok, let's go with currentSpace, I'll do it ASAP.
New Seam context variable : currentSuperSpace
new getter on navigationContext : getCurrentSuperSpace SuperSpace document are all documents that have the SuperSpace facet. For now : - Workspace and Section types - Roots (Workspaces, Sections, Templates) - Domain If not found the Root of the repository is returned. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- via the context variable : currentWorkspace
- via navigation Context : navigationContext.getCurrentWorkspace
I think it does work OK for worspaces.
It is not implemenyed for now for sections.