- Pharo-users - lists.pharo.org

[ESUG] Looking for a job?

by Norbert Hartl

We are looking for new developers at ZWEIDENKER (the company formerly known as 2denker :) ). So if you are at ESUG right now and you are interested please either contact me in person or reply to this email and I will get in contact with you. See you, Norbert

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

So at the moment I am fine to get it up and running using a FossilRepo. Later on I will work on replacing it with a JSON data store. On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > I understand that it makes a lot of sense to reuse the functions > implemented in the FossilRepo. > > Installation of the Fossil version control system seems to be very > simple, just put a single executable file into the pharo folder for > example > > https://fossil-scm.org/index.html/doc/trunk/www/index.wiki > > The global state of a fossil repository is an unordered set of artifacts. > > An artifact might be a source code file, the text of a wiki page, part > of a trouble ticket, a description of a check-in including all the > files in that check-in with the check-in comment and so forth. > > Artifacts are broadly grouped into two types: > - content artifacts and > - structural artifacts. > > Content artifacts are the raw project source-code files that are > checked into the repository. > > Structural artifacts have special formatting rules and are used to > show the relationships between other artifacts in the repository. It > is possible for an artifact to be both a structure artifact and a > content artifact, though this is rare. Artifacts can be text or > binary. > > https://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki > > On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> What I wanted to write is that the class FossilRepo is not included. >> >> And that the setup of the Teapot server should not be hidden in lazy >> initialisation method but made explicit with some methods in a method >> category called 'setup' or 'configuration'. >> >> HH >> >> On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> Hi Offray >>> >>> Thank you for answering and the new release. I will look at it in >>> detail. Here is a first feedback. >>> >>> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> >>> wrote: >>>> Hi, Hannes, >>>> >>>> Sorry it took so long. >>> >>> No problem. It was actually less than 14 days which is not long ..... >>> >>> :-) >>> >>>> I'm now finishing my PhD and entering into a >>>> focused writing mode, so is difficult to keep with mailing lists these >>>> days. >>>> >>>> New version contains an example. Please load the ConfigurationOfBrea as >>>> showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: >>>> >>>> BreaWebsite example >>>> >>>> and visit >>>> >>>> - http://localhost:8080/demo/ >>>> - http://localhost:8080/members/test >>>> - http://localhost:8080/members/add >>>> >>>> There are still some issues with CSS and data persistence must be >>>> implemented, but this should give you and overview of how to combine >>>> Teapot + Mustache. >>> >>> >>> I followed the instructions but encountered a problem that the class >>> FossilRepo >>> >>> BreaWebsite >>> fossilRepo >>> ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] >>> >>> >>> This made that >>> >>> BreaWebsite example >>> >>> did not complete and thus there was no website. >>> Another thing is that the port number which is currently in >>> >>> BreaWebsite>>server >>> >>> server >>> ^ server ifNil: [ server := Teapot configure: { #port ->8500 . >>> #debugMode -> true } ] >>> >>> should be at a more prominent place so that it is easier to find and >>> thus configure. >>> >>> >>> Kind regards >>> Hannes >>> >>>> Cheers, >>>> >>>> Offray >>>> >>>> On 23/08/17 13:44, H. Hirzel wrote: >>>>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>>>> Hi, >>>>>> >>>>>> On the Teapot + Mustache integration, Hannes, you may want to see my >>>>>> early >>>>>> prototype: >>>>>> >>>>>> http://smalltalkhub.com/#!/~Offray/Brea >>>>>> >>>>>> At some point, it will contain distributed wiki, backed by Fossil, >>>>>> now >>>>>> that >>>>>> we're thinking in empower community driven wiki like documentation. >>>>>> >>>>>> Offray >>>>> >>>>> Hi Offray >>>>> >>>>> I found Name: Brea-OffrayLuna.8 >>>>> Author: OffrayLuna >>>>> Time: 1 June 2017, 4:18:20.860411 pm >>>>> >>>>> There is no test to show me how to use it and I none of the class >>>>> comments of the 4 classes gives enough clues. >>>>> >>>>> >>>>> Interesting method so far >>>>> >>>>> routes >>>>> "I define how the website behaves accordingly to particular routes." >>>>> self server >>>>> serveStatic: 'demo' from: '/opt/gig/'; >>>>> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml >>>>> ]; >>>>> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >>>>> POST: 'members/summit' -> [ :req | self processNewMember: req ] >>>>> >>>>> >>>>> May I ask you to give a few hints how to start it? >>>>> Is it possible to use it without Fossil, just with image persistence? >>>>> >>>>> Regards >>>>> Hannes >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

I understand that it makes a lot of sense to reuse the functions implemented in the FossilRepo. Installation of the Fossil version control system seems to be very simple, just put a single executable file into the pharo folder for example https://fossil-scm.org/index.html/doc/trunk/www/index.wiki The global state of a fossil repository is an unordered set of artifacts. An artifact might be a source code file, the text of a wiki page, part of a trouble ticket, a description of a check-in including all the files in that check-in with the check-in comment and so forth. Artifacts are broadly grouped into two types: - content artifacts and - structural artifacts. Content artifacts are the raw project source-code files that are checked into the repository. Structural artifacts have special formatting rules and are used to show the relationships between other artifacts in the repository. It is possible for an artifact to be both a structure artifact and a content artifact, though this is rare. Artifacts can be text or binary. https://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > What I wanted to write is that the class FossilRepo is not included. > > And that the setup of the Teapot server should not be hidden in lazy > initialisation method but made explicit with some methods in a method > category called 'setup' or 'configuration'. > > HH > > On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Hi Offray >> >> Thank you for answering and the new release. I will look at it in >> detail. Here is a first feedback. >> >> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>> Hi, Hannes, >>> >>> Sorry it took so long. >> >> No problem. It was actually less than 14 days which is not long ..... >> >> :-) >> >>> I'm now finishing my PhD and entering into a >>> focused writing mode, so is difficult to keep with mailing lists these >>> days. >>> >>> New version contains an example. Please load the ConfigurationOfBrea as >>> showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: >>> >>> BreaWebsite example >>> >>> and visit >>> >>> - http://localhost:8080/demo/ >>> - http://localhost:8080/members/test >>> - http://localhost:8080/members/add >>> >>> There are still some issues with CSS and data persistence must be >>> implemented, but this should give you and overview of how to combine >>> Teapot + Mustache. >> >> >> I followed the instructions but encountered a problem that the class >> FossilRepo >> >> BreaWebsite >> fossilRepo >> ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] >> >> >> This made that >> >> BreaWebsite example >> >> did not complete and thus there was no website. >> Another thing is that the port number which is currently in >> >> BreaWebsite>>server >> >> server >> ^ server ifNil: [ server := Teapot configure: { #port ->8500 . >> #debugMode -> true } ] >> >> should be at a more prominent place so that it is easier to find and >> thus configure. >> >> >> Kind regards >> Hannes >> >>> Cheers, >>> >>> Offray >>> >>> On 23/08/17 13:44, H. Hirzel wrote: >>>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>>> Hi, >>>>> >>>>> On the Teapot + Mustache integration, Hannes, you may want to see my >>>>> early >>>>> prototype: >>>>> >>>>> http://smalltalkhub.com/#!/~Offray/Brea >>>>> >>>>> At some point, it will contain distributed wiki, backed by Fossil, >>>>> now >>>>> that >>>>> we're thinking in empower community driven wiki like documentation. >>>>> >>>>> Offray >>>> >>>> Hi Offray >>>> >>>> I found Name: Brea-OffrayLuna.8 >>>> Author: OffrayLuna >>>> Time: 1 June 2017, 4:18:20.860411 pm >>>> >>>> There is no test to show me how to use it and I none of the class >>>> comments of the 4 classes gives enough clues. >>>> >>>> >>>> Interesting method so far >>>> >>>> routes >>>> "I define how the website behaves accordingly to particular routes." >>>> self server >>>> serveStatic: 'demo' from: '/opt/gig/'; >>>> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml >>>> ]; >>>> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >>>> POST: 'members/summit' -> [ :req | self processNewMember: req ] >>>> >>>> >>>> May I ask you to give a few hints how to start it? >>>> Is it possible to use it without Fossil, just with image persistence? >>>> >>>> Regards >>>> Hannes >>>> >>>> >>> >>> >>> >>> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

What I wanted to write is that the class FossilRepo is not included. And that the setup of the Teapot server should not be hidden in lazy initialisation method but made explicit with some methods in a method category called 'setup' or 'configuration'. HH On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hi Offray > > Thank you for answering and the new release. I will look at it in > detail. Here is a first feedback. > > On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> Hi, Hannes, >> >> Sorry it took so long. > > No problem. It was actually less than 14 days which is not long ..... > > :-) > >> I'm now finishing my PhD and entering into a >> focused writing mode, so is difficult to keep with mailing lists these >> days. >> >> New version contains an example. Please load the ConfigurationOfBrea as >> showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: >> >> BreaWebsite example >> >> and visit >> >> - http://localhost:8080/demo/ >> - http://localhost:8080/members/test >> - http://localhost:8080/members/add >> >> There are still some issues with CSS and data persistence must be >> implemented, but this should give you and overview of how to combine >> Teapot + Mustache. > > > I followed the instructions but encountered a problem that the class > FossilRepo > > BreaWebsite > fossilRepo > ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] > > > This made that > > BreaWebsite example > > did not complete and thus there was no website. > Another thing is that the port number which is currently in > > BreaWebsite>>server > > server > ^ server ifNil: [ server := Teapot configure: { #port ->8500 . > #debugMode -> true } ] > > should be at a more prominent place so that it is easier to find and > thus configure. > > > Kind regards > Hannes > >> Cheers, >> >> Offray >> >> On 23/08/17 13:44, H. Hirzel wrote: >>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>> Hi, >>>> >>>> On the Teapot + Mustache integration, Hannes, you may want to see my >>>> early >>>> prototype: >>>> >>>> http://smalltalkhub.com/#!/~Offray/Brea >>>> >>>> At some point, it will contain distributed wiki, backed by Fossil, now >>>> that >>>> we're thinking in empower community driven wiki like documentation. >>>> >>>> Offray >>> >>> Hi Offray >>> >>> I found Name: Brea-OffrayLuna.8 >>> Author: OffrayLuna >>> Time: 1 June 2017, 4:18:20.860411 pm >>> >>> There is no test to show me how to use it and I none of the class >>> comments of the 4 classes gives enough clues. >>> >>> >>> Interesting method so far >>> >>> routes >>> "I define how the website behaves accordingly to particular routes." >>> self server >>> serveStatic: 'demo' from: '/opt/gig/'; >>> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml ]; >>> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >>> POST: 'members/summit' -> [ :req | self processNewMember: req ] >>> >>> >>> May I ask you to give a few hints how to start it? >>> Is it possible to use it without Fossil, just with image persistence? >>> >>> Regards >>> Hannes >>> >>> >> >> >> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

Hi Offray Thank you for answering and the new release. I will look at it in detail. Here is a first feedback. On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > Hi, Hannes, > > Sorry it took so long. No problem. It was actually less than 14 days which is not long ..... :-) > I'm now finishing my PhD and entering into a > focused writing mode, so is difficult to keep with mailing lists these > days. > > New version contains an example. Please load the ConfigurationOfBrea as > showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: > > BreaWebsite example > > and visit > > - http://localhost:8080/demo/ > - http://localhost:8080/members/test > - http://localhost:8080/members/add > > There are still some issues with CSS and data persistence must be > implemented, but this should give you and overview of how to combine > Teapot + Mustache. I followed the instructions but encountered a problem that the class FossilRepo BreaWebsite fossilRepo ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] This made that BreaWebsite example did not complete and thus there was no website. Another thing is that the port number which is currently in BreaWebsite>>server server ^ server ifNil: [ server := Teapot configure: { #port ->8500 . #debugMode -> true } ] should be at a more prominent place so that it is easier to find and thus configure. Kind regards Hannes > Cheers, > > Offray > > On 23/08/17 13:44, H. Hirzel wrote: >> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>> Hi, >>> >>> On the Teapot + Mustache integration, Hannes, you may want to see my >>> early >>> prototype: >>> >>> http://smalltalkhub.com/#!/~Offray/Brea >>> >>> At some point, it will contain distributed wiki, backed by Fossil, now >>> that >>> we're thinking in empower community driven wiki like documentation. >>> >>> Offray >> >> Hi Offray >> >> I found Name: Brea-OffrayLuna.8 >> Author: OffrayLuna >> Time: 1 June 2017, 4:18:20.860411 pm >> >> There is no test to show me how to use it and I none of the class >> comments of the 4 classes gives enough clues. >> >> >> Interesting method so far >> >> routes >> "I define how the website behaves accordingly to particular routes." >> self server >> serveStatic: 'demo' from: '/opt/gig/'; >> GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml ]; >> GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; >> POST: 'members/summit' -> [ :req | self processNewMember: req ] >> >> >> May I ask you to give a few hints how to start it? >> Is it possible to use it without Fossil, just with image persistence? >> >> Regards >> Hannes >> >> > > > >

Sept. 6, 2017

Re: [Pharo-users] [Pharo-dev] ESUG Pharo GIT BOFs

by Stephane Ducasse

Wednesday after Martin talk we will have a consortium discussions Thursday after esteban talk we will have the git Pharo BOF 16h-16h45 Git 16h45- on BOF On Wed, Sep 6, 2017 at 2:50 AM, John Pfersich <jpfersich(a)gmail.com> wrote: > Birds of a Feather, sort of an informal get-together. > > Sent from my iPad > > On Sep 5, 2017, at 14:47, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > > On Tue, Sep 5, 2017 at 9:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >

Sept. 6, 2017

Re: [Pharo-users] [Pharo-dev] ESUG Pharo GIT BOFs

by John Pfersich

Birds of a Feather, sort of an informal get-together. Sent from my iPad > On Sep 5, 2017, at 14:47, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > >> On Tue, Sep 5, 2017 at 9:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >

Sept. 6, 2017

Re: [Pharo-users] Usability issues with Calypso

by Tim Mackinnon

BTW - Is it intended that when you save a method in a Calypso tab, it shifts focus to the first non saved tab? I find this quite confusing as suddenly I'm not where I thought I was and wonder if I saved my method? This said, I love the fact you can move to a new method with unsaved changes and no nag prompt. Tim Sent from my iPhone Sent from my iPhone > On 3 Sep 2017, at 22:25, Tim Mackinnon <tim(a)testit.works> wrote: > > Ah - you are right that rename is in there (Iâd never noticed it was in the suggestions menu - which I find a confusingly named sub-menu ) - but I am missing the more appropriately named âSource Code Refactoringâ menu, which it also appears along with extract method etc. This menu is not in Calypso right? > > Tim > >> On 3 Sep 2017, at 17:24, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> Hi Tim. >> >> No. It is available by cmd+r and from suggestions menu like in Nautilus. But maybe I do not know other place which you use for this >> >> 2017-09-03 17:03 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >>> Hi Denis - I just noticed that the source refactoring menu is missing in Calypso as well? (So you canât rename a temp for example). >>> >>> Tim >>> >>>> On 2 Sep 2017, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> >>>> Hi >>>> >>>> 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com>: >>>>> I have been keen to use Calypso (I love the way it shows inherited methods) >>>>> as my browser but I am finding some usability issues. It may be just me but >>>>> some things I find off-putting. >>>> >>>> Any feedback is very important. >>>> >>>>> >>>>> I don't really like the way that adding a new class is done by a new tab >>>>> that appears now and then in the editing area. To my mind the Nautilus way >>>>> of launching a dialog to create a class seems more natural - and opens the >>>>> way in future for a class creation wizard - something that can't be done in >>>>> a code window. If we have to do it in a code tab then it would be better if >>>>> the tab remained there all the time - I don't like the way it appears and >>>>> disappears. It takes a while to learn what to click to do this. >>>> >>>> In fact current behaviour is not replacement of old context menu command. It is just rethinking of classic single source code pane of old browsers. >>>> So we will add missing command to context menu. But I think the command should open the current "New class" tab instead of old dialog request. >>>> Also old browser behaviour is still working. You can create new class from the class editor tab. Just type new class name in the definition of selected class. >>>> >>>>> >>>>> Also, all class creation presumes a subclass of Object in Calypso. i miss >>>>> the ability in Nautilus to select a class and immediately create a subclass >>>>> of it. Am I missing something here? Is there a way? >>>> >>>> You are right. It is missing command like previous one. We will add it. >>>> >>>>> >>>>> On the topic of my ignorance - what is a /project /in Calypso? How do you >>>>> create one? >>>> >>>> Now it is more like a stub. >>>> There is integration with new package management Cargo (Christophe is working on it). But it is probably not ready yet. >>>> I think we should also implement Metacello backend. >>>> Anyway project mode will become default view in future. >>>> >>>>> >>>>> And what does realize do? >>>> >>>> It creates stub implementation of abstract methods (found in superclasses). >>>> I think in Calypso this command is not needed anymore because there is "should be implemented" method group which shows all these abstract methods. >>>> >>>>> >>>>> Also I think that the pop up menus could be subdivided into categories >>>>> rather than present all the options in an unbroken list. And the order of >>>>> options seems odd. To my mind/ senders /and /implementers /are two menu >>>>> options that should always go together - not be separated by/ rename/ and >>>>> /move to class side/ et cetera. >>>> >>>> Yes, I will add it. >>>> >>>> You can report issues directly at github project https://github.com/dionisiydk/Calypso/issues. >>>> Thank's for you feedback. >>>> >>>> >>>>> >>>>> Just my two cents. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Sept. 5, 2017

Re: [Pharo-users] Brea wiki software

by Offray Vladimir Luna CÃ¡rdenas

Hi, Hannes, Sorry it took so long. I'm now finishing my PhD and entering into a focused writing mode, so is difficult to keep with mailing lists these days. New version contains an example. Please load the ConfigurationOfBrea as showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: BreaWebsite example and visit - http://localhost:8080/demo/ - http://localhost:8080/members/test - http://localhost:8080/members/add There are still some issues with CSS and data persistence must be implemented, but this should give you and overview of how to combine Teapot + Mustache. Cheers, Offray On 23/08/17 13:44, H. Hirzel wrote: > On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >> Hi, >> >> On the Teapot + Mustache integration, Hannes, you may want to see my early >> prototype: >> >> http://smalltalkhub.com/#!/~Offray/Brea >> >> At some point, it will contain distributed wiki, backed by Fossil, now that >> we're thinking in empower community driven wiki like documentation. >> >> Offray > > Hi Offray > > I found Name: Brea-OffrayLuna.8 > Author: OffrayLuna > Time: 1 June 2017, 4:18:20.860411 pm > > There is no test to show me how to use it and I none of the class > comments of the 4 classes gives enough clues. > > > Interesting method so far > > routes > "I define how the website behaves accordingly to particular routes." > self server > serveStatic: 'demo' from: '/opt/gig/'; > GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml ]; > GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; > POST: 'members/summit' -> [ :req | self processNewMember: req ] > > > May I ask you to give a few hints how to start it? > Is it possible to use it without Fossil, just with image persistence? > > Regards > Hannes > >

Sept. 5, 2017

Re: [Pharo-users] Spec "bindings"

by Stephane Ducasse

Rob Spec deserves another pass. I see your point with showOn: now I do not see how you could avoid the presenter building. But may be I'm not enough into it. So I'm interested in your feedback. Stef Stef On Tue, Sep 5, 2017 at 8:49 PM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: > Hello, > > I was wondering what more experienced users than myself thought of the idea > of an explicit Spec "connection point" to a domain model object similar to > Dolphin's "showOn:" method, like: > > CounterApp showOn: counter. > > This would perhaps trigger something like Dolphin's Presenter>>model: > message (although I've always found the use of "model" confusing when there > are so many "models" involved.) after the widgets had been created: > > ComposableModel>>initializeBindings: anObject > > In many cases, if your domain model uses ValueHolders as well (like Spec > does), making a connection could just mean replacing the Spec ValueHolder > with your domain ValueHolder so changes to the domain model would > automatically propagate to the UI presentation without providing explicit > code in ComposableModel>>initializePresenter. > > However, since I am still trying to understand and learn Spec, it's quite > possible I am missing some key point and there are reasons not to explore > this line of thinking! > > Thank you, > > Rob >

Sept. 5, 2017