You can comment the entry (as well as every one) so we can gather all the idea and have a backlog of the discussion
Then the output will be moved into a wiki page Ben On 11 Aug 2014, at 13:00, stepharo <steph...@free.fr> wrote: > Roadmap can be discussed here: > https://github.com/spec-framework/spec/issues/16 > > Great > Do you mean that I should edit the file? > > Here is my wishlist > > - check the extensions. I analyzed many Spec extensions and moved the > extensions that were simply missing methods to their > respective packages. But may be I missed some of them. I paid attention to > conserve layers (model not getting in the widgets). > > - I would like that ReactiveVariable get renamed as NewValueHolder > (because we have 15 years of books and concepts that use that name) > It should take you less than 5 min to do it and it would be great that > Spec does not diverge from concepts for the sake of it. > > - to do a pass over the different layers to ensure the separation of > concerns between models <-> adapters <-> widgets > => i imagine that this point is related to > > Could we remove the interpretation layer between Morphic adapter and > Morphic. From a **Morphic**-adapter point of view I know that I'm talking to > a Morph > because this is my reason d'etre. I can help creating the > delegating methods. > > - to implement a Magritte like meta-description mechanism to build UI > easily > => I will see if gary can show what he is doing. I hope that he > will attend ESUG. > Because he has all the widgets described with a kind of > metadescription based on that he can build interactively UI > and with some "type information" provide panes to control widgets. > Did you watch the video is colleague from pinesoft sent around? > They could build a new UI in a couple minutes. > > - I do not remember exactly but while I was studying polymorph I saw that > some widgets where only used once by Spec and I would like to see how we can > remove this dependency (may be it was about menu). > > Stef >
