- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New address for the Spec jenkins

by Tudor Girba

Thanks. I would definitely want to look at this in more details. Doru On Mon, Aug 11, 2014 at 1:48 PM, stepharo <stepharo(a)free.fr> wrote: > 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 > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 11, 2014

Re: [Pharo-dev] NBWin32 vs OSWindows

by Tudor Girba

Thank you very much, Torsten! It works great. For the moment, I can live with only spawning a command line, but if I hit a wall I will look into the ReadFile API. In the meantime, I already committed a little addition for spawning a blocking process in a given directory. Cheers, Doru On Mon, Aug 11, 2014 at 12:00 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Tudor, > > first I created the classes/APIs you are talking about directly as part of > NativeBoost. > After that there was a suggestion from Igor that NB should be reduced to > it's core > (so only FFI functionality, no wrapping) and as we want to reduce the core > Pharo to > a minimum I agree with this opinion. > > Therefore I created the separate OSWindows project and continued my work > there > (also with the idea that other OSxxx may follow). > > OSWindows is an external loadable package - also better structured from > the package > side and well tested. Havent found the time to deprecate the older parts > like > NBWin32Shell in NB itself or the Pharo 3.0 image yet. Hope to be able to > do for 4.0. > > If you just want to open an explorer or browse an URL you can therefore > (currently) still > use NBWin32Shell in 3.0 directly but if you require more (like calling an > external process > or work with Commandline) then go for OSWindows. > > If you want to call/run an external executable just check WinProcess class > in OSWindows. > #createProcess: or #createAndWaitForProcess: > > If you just want to do output on the command line check out the examples > in class > WinConsole. For instance > > WinConsole example4 > > will do some colored output. > > Reading from the console is not yet integrated (as ever for time reasons) > - basically it > would mean to just wrap the ReadFile API ( > http://msdn.microsoft.com/en-us/library/windows/desktop/aa365467(v=vs.85).a… > ) > and call it. > > I've added you to the OS team if you want to help. > > Bye > T. > > > > > Gesendet: Samstag, 09. August 2014 um 14:33 Uhr > Von: "Tudor Girba" <tudor(a)tudorgirba.com> > An: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] NBWin32 vs OSWindows > > Hi, > > I am working on a little tool that requires a couple of interactions with > either a command line interface or a DLL whose API I do not know :). > > First, I would like to thank the authors for both NBWin32 and OSWindows. > Having these possibilities at our fingertips makes the difference. > > Second, I am still not clear how to judge the difference between these > two. For example, the functionality of WinShell (from OSWindows) seems to > exist one-to-one in NBWin32Shell. Is it correct to assume that I should > just focus on NBWin32? > > Third, how do I trigger a custom command line with a blocking call and how > do I capture the output of the command? For example, suppose I just need to > do a "dir" and capture the output. How do I do that? Are there examples? > > Cheers, > Doru > -- > www.tudorgirba.com[http://www.tudorgirba.com] > > "Every thing has its own flow" > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 11, 2014

Re: [Pharo-dev] DFlow needs you

by Tudor Girba

When you press Stop, it uploads to the server. Doru On Mon, Aug 11, 2014 at 2:18 PM, stepharo <stepharo(a)free.fr> wrote: > Hi roberto > > once I run your tool how do I give you information? > > Stef > > > On 29/7/14 10:01, Roberto Minelli wrote: > >> Hi guys, >> >> As part of my research, I am conducting an experiment on how Pharo >> developers use the IDE and I really need you. >> >> My final goal, as we discussed at ESUG last year, is to improve the UI of >> our IDE to better fit our needs. >> To do so, I first need to collect interaction data from real developers. >> >> I would like to ask you if you and your team could install DFlow, my >> interaction profiler, and record your >> development sessions on a daily basis. The tool is not intrusive and >> requires minimal effort to be used. >> There is a simple UI that lets you start/pause/stop the recording. When >> you stop the session >> it automatically shares the data with me (through HTTP requests). >> >> If I manage to collect enough data and discover some insights I will >> share them in my ESUG talk! >> >> I am looking forward to hearing from you! >> >> Cheers, >> >> Roberto >> >> P.s. You can find installation instructions at the following link: >> http://goo.gl/ZKYNUI >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 11, 2014

Re: [Pharo-dev] DFlow needs you

by stepharo

Hi roberto once I run your tool how do I give you information? Stef On 29/7/14 10:01, Roberto Minelli wrote: > Hi guys, > > As part of my research, I am conducting an experiment on how Pharo developers use the IDE and I really need you. > > My final goal, as we discussed at ESUG last year, is to improve the UI of our IDE to better fit our needs. > To do so, I first need to collect interaction data from real developers. > > I would like to ask you if you and your team could install DFlow, my interaction profiler, and record your > development sessions on a daily basis. The tool is not intrusive and requires minimal effort to be used. > There is a simple UI that lets you start/pause/stop the recording. When you stop the session > it automatically shares the data with me (through HTTP requests). > > If I manage to collect enough data and discover some insights I will share them in my ESUG talk! > > I am looking forward to hearing from you! > > Cheers, > > Roberto > > P.s. You can find installation instructions at the following link: http://goo.gl/ZKYNUI >

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by stepharo

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

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by stepharo

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).

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by Benjamin

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 <stepharo(a)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 >

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by Tudor Girba

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. 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 <tudor(a)tudorgirba.com> wrote: > Hi Stef, > > > - 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 did not see the video, but I am very interested in this. Could you point > me to it? > > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by Tudor Girba

Hi Stef, - 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 did not see the video, but I am very interested in this. Could you point me to it? Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 11, 2014

Re: [Pharo-dev] New address for the Spec jenkins

by stepharo

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

Aug. 11, 2014