On 12 February 2015 at 11:27, Dan Haywood <[email protected]> wrote:
> Hi Martin, > > you are correct... there is no very satisfactory way to do this at the > moment; instead is necessary to suppress the service and add a replacement. > > The .layout.json isn't appropriate here... that deals only with the layout > of an entity. > > I'm currently working through the addon modules to make sure that they all > group "sensibly"... I have sessionlogger/command/auditing/publishing under > "Activity", and all the security services under "Security". Haven't yet > decided where to put devutils or settings... was thinking perhaps > "Prototyping" and the tertiary menu respectively? > Yeah, devutils should reside onder Prototype. > Also, I'm ensuring that all properties/collections/actions emit an > appropriate domain event, making it easy for subscribers to easily suppress > actions visibility by vetoing on the hide phase. > > But what is needed here is some sort of menu.json file that has an > equivalent role. I think there's a ticket on JIRA for this, but it's just > a placeholder, no real thinking been done on it. > > As for the schema of .layout.json, at some point was thinking we should > define a json-schema for it; some IDEs support that (though not IntelliJ, > surprisingly). And/or, might be worthwhile supporting .layout.xml and > writing a new implementation that reads from XML with corresponding XSD > (since much more widely supported in editors). > It might be easier to start with supporting XML layouts and provide schemas for that. There is a tool that can create JSON schemas from XSD's [1] so by the time JSON schemas are supported by the IDE's no or little additional work has to be done. Meanwhile developers can leverage code completion creating layouts using XML. [1] https://github.com/fnogatz/xsd2json
