If people are interested having the latest
Spec bleeding image, it can now be retrieved at: http://benjamin.is-a-geek.com:8080/job/Spec/ :) Ben |
Hi ben
do you have a roadmap that we can discuss for spec? Because there are several points I would like to fixed. Stef On 10/8/14 17:19, Benjamin wrote:
If people are interested having the latest |
Roadmap can be discussed here: https://github.com/spec-framework/spec/issues/16
Ben On 10 Aug 2014, at 20:58, stepharo <[hidden email]> 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 |
Hi Stef,
- to implement a Magritte like meta-description mechanism to build UI easily I did not see the video, but I am very interested in this. Could you point me to it? Doru "Every thing has its own flow"
|
I found it. It's this one: Quite cool. If understand correctly, the bottom part of the widget shows the Features of a current step. This is very similar to what we have in Glamour, only the cool thing is that it also provides the ui for visual editing (as opposed to Glamour which only offers scripting now). The widgets are quite cool.
Do you know if the upper part of the window is meta-described as well? Cheers, Doru On Mon, Aug 11, 2014 at 1:30 PM, Tudor Girba <[hidden email]> wrote:
"Every thing has its own flow"
|
In reply to this post by stepharo
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 <[hidden email]> wrote: Roadmap can be discussed here: https://github.com/spec-framework/spec/issues/16 |
Ok I added that to the comments.
On 11/8/14 13:37, Benjamin wrote: > 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). |
In reply to this post by Tudor Girba-2
Glad you find it.
> I found it. It's this one: > http://www.youtube.com/watch?v=Izg_Dr2Cg7k&feature=youtu.be > > Quite cool. If understand correctly, the bottom part of the widget > shows the Features of a current step. I do not know. What I know is that there are two aspects - each widget is described by a "description objects" and widget property pane and other are based on this. - then on top of that they have a data flow engine. > This is very similar to what we have in Glamour, only the cool thing > is that it also provides the ui for visual editing (as opposed to > Glamour which only offers scripting now). The widgets are quite cool. > > Do you know if the upper part of the window is meta-described as well? I do not know I just got a 15 min demoe and browse the code a while ago. Normally gary should attend ESUG. Stef |
Thanks. I would definitely want to look at this in more details. Doru On Mon, Aug 11, 2014 at 1:48 PM, stepharo <[hidden email]> wrote: Glad you find it. "Every thing has its own flow"
|
Free forum by Nabble | Edit this page |