- Pharo-users - lists.pharo.org

Re: [Pharo-users] Porting Transducers to Pharo

by Steffen MÃ¤rcker

I assumed so. I used file-outs only to get something working quickly. =) Properly published code will follow as soon as I am more familiar with code management in Pharo. Am .06.2017, 09:05 Uhr, schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > We do not work with fileouts :) > You should produce packages with also a configuration and published them > on > smalltalkhub or git and > in the MetaRepository. > You can also add package comments > > On Sat, Jun 3, 2017 at 10:29 PM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Dear all, >> >> attached are updated file-outs. I fixed a couple of annoyances that >> slipped through yesterday evening. Most notable: >> >> 1) Random generator now works. >> 2) Early termination via Reduced exception does MNU anymore. >> 3) Printing a transducer holding a block does not MNU anymore. >> >> Please, give it a spin and tell me your impressions. (At least) The >> coin-flipping the example from the package comment works now: >> >> scale := [:x | (x * 2 + 1) floor] map. >> sides := #(heads tails) replace. >> count := 1000 take. >> collect := [:bag :c | bag add: c; yourself]. >> experiment := (scale * sides * count) transform: collect. >> "experiment cannot be re-used" >> samples := Random new >> reduce: experiment >> init: Bag new. >> "transform and reduce in one step" >> samples := Random new >> transduce: scale * sides * count >> reduce: collect >> init: Bag new. >> "assemble coin (eduction) and flip (reduction) objects" >> coin := sides <~ scale <~ Random new. >> flip := Bag <~ count. >> "flip coin =)" >> samples := flip <~ coin. >> >> Cheers! >> Steffen >> >> >> >> Am .06.2017, 23:08 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >> >> Thanks, this appears to work. Attached you'll find the file-out from >>> VisualWorks and the file-out from Pharo (includes package comment). >>> >>> Cheers! >>> Steffen >>> >>> >>> Am .06.2017, 20:06 Uhr, schrieb Yanni Chiu <yanni.code(a)gmail.com>: >>> >>> To get the extension methods into the Transducers package, the >>> following >>>> worked for me - edit the category to have the prefix '*Transducers-' >>>> >>>> 2710c2710 >>>> >>>> < !Number methodsFor: 'transforming' stamp: ' 2/6/17 15:38'! >>>> >>>> --- >>>> >>>> !Number methodsFor: '*Transducers-transforming' stamp: ' 2/6/17 >>>> 15:38'! >>>>> >>>> >>>> >>>> On Fri, Jun 2, 2017 at 11:05 AM, Steffen MÃ¤rcker <merkste(a)web.de> >>>> wrote: >>>> >>>> Dear all, >>>>> >>>>> thanks for the many suggestions. I didn't had time to test all >>>>> import/export ways yet. But for now, I can report on two: >>>>> >>>>> 1) NGFileOuter >>>>> Unfortunately It raised several MNUs in my image. I'll investigate >>>>> them >>>>> later. >>>>> >>>>> 2) FileOut30 (VW Contributed) >>>>> I was able to file out the code except for the package definition. >>>>> Replacing {category: ''} in the class definitions with {package: >>>>> 'Transducers'} fixed that. However, methods that extend existing >>>>> classes >>>>> did not end up in the Transducers package. Is there a similar easy >>>>> change >>>>> to the file-out making that happen? Also I'd like to add the package >>>>> comment if that's possible. >>>>> >>>>> Most things appear to work as far as I can see. Two exceptions: >>>>> 1) Random is a subclass of Stream in VW and in Pharo it is not. >>>>> Hence, >>>>> I'll have to copy some methods from Stream to Random. >>>>> 2) I used #beImmutable in VW but I couldn't yet figure out how to >>>>> make >>>>> objects immutable in Pharo. >>>>> >>>>> However, until the tests are ported, I cannot guarantee. Porting the >>>>> test >>>>> suite will be another beast, since I rely on the excellent >>>>> mocking/stubbing >>>>> library DoubleAgents by Randy Coulman. I am not sure how I will >>>>> handle >>>>> that. In general, I think it would be really worth the effort to be >>>>> ported >>>>> to Pharo, too. DoubleAgents is pretty powerful and produces easy to >>>>> read >>>>> and understand mocking/stubbing code. Personally, I prefer it >>>>> clearly, >>>>> e.g., over Mocketry (no offence intended!). >>>>> >>>>> Attached you'll find the file-out that I loaded into Pharo. The >>>>> issues >>>>> above are not addressed yet. However, the following example works: >>>>> >>>>> | scale sides count collect experiment random samples coin flip | >>>>> scale := [:x | (x * 2 + 1) floor] map. >>>>> sides := #(heads tails) replace. >>>>> count := 1000 take. >>>>> collect := [:bag :c | bag add: c; yourself]. >>>>> experiment := (scale * sides * count) transform: collect. >>>>> random := #(0.1 0.3 0.4 0.5 0.6 0.7 0.8 0.9). >>>>> >>>>> samples := random >>>>> reduce: experiment >>>>> init: Bag new. >>>>> >>>>> samples := random >>>>> transduce: scale * sides * count >>>>> reduce: collect >>>>> init: Bag new. >>>>> >>>>> coin := sides <~ scale <~ random. >>>>> flip := Bag <~ count. >>>>> >>>>> samples := flip <~ coin. >>>>> >>>>> >>>>> Best, Steffen >>>>> >>>>> >>>>> >>>>> Am .06.2017, 08:16 Uhr, schrieb Stephane Ducasse >>>>> <stepharo.self(a)gmail.com >>>>> >: >>>>> >>>>> There is a package for that NGFileOuter or something like that on >>>>> cincom >>>>> >>>>>> store. >>>>>> We used it for mobydic code. >>>>>> >>>>>> On Wed, May 31, 2017 at 6:35 PM, Alexandre Bergel < >>>>>> alexandre.bergel(a)me.com> >>>>>> wrote: >>>>>> >>>>>> If I remember correctly, there is a parcel in VisualWorks to export >>>>>> a >>>>>> file >>>>>> >>>>>>> out (Squeak format). >>>>>>> >>>>>>> @Milton, can you give a hand to Steffen? >>>>>>> >>>>>>> Alexandre >>>>>>> -- >>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>>> Alexandre Bergel http://www.bergel.eu >>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On May 31, 2017, at 10:32 AM, Steffen MÃ¤rcker <merkste(a)web.de> >>>>>>> wrote: >>>>>>> >>>>>>> Thanks for the encouraging response! First question: Which is the >>>>>>> recommended (friction free) way to exchange code between VW and >>>>>>> Pharo? >>>>>>> >>>>>>> Cheers! >>>>>>> Steffen >>>>>>> >>>>>>> Am .05.2017, 16:22 Uhr, schrieb Alexandre Bergel < >>>>>>> alexandre.bergel(a)me.com >>>>>>> >: >>>>>>> >>>>>>> I second Sven. This is very exciting! >>>>>>> >>>>>>> Let us know when you have something ready to be tested. >>>>>>> >>>>>>> Alexandre >>>>>>>

June 6, 2017

Re: [Pharo-users] Bloc/Brick/Spec

by Peter H. Meadows

What does 'Bloc Zeroconf Script' do? What is the difference between the 4 different metacello lines here? https://github.com/pharo-graphics/Brick

June 6, 2017

Re: [Pharo-users] Bloc/Brick/Spec

by Peter Uhnak

* Bloc - low level library (think basic shapes, rectangles, ...) * Brick - widget library on top of Bloc akin to the widget part of Morphic (buttons, checkboxes, ...) * Spec - UI framework with adaptable backend; currently using Morphic as a backend, however once Bloc/Brick matures, Bloc/Brick will be added as another backend (without affecting Spec users) (and below Bloc is Sparta, which is a vector canvas) Peter On Mon, Jun 05, 2017 at 06:20:47PM -0700, Brad Selfridge wrote: > I'm confused. I see the latest news and documentation about Bloc. Is Brick > now dead and Bloc the default? I thought Brick was a layer on top of Bloc > and Spec was layer on top on Brick? What is the direction now? > > Brad Selfridge > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/Bloc-Brick-Spec-tp4949591.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

June 6, 2017

Slant question

by john pfersich

Slant has a question/poll out there It's at https://www.slant.co/topics/25/~best-programming-language-to-learn-first?ut… Let's pile on it! Sent from my iPhone

June 6, 2017

Re: [Pharo-users] [Pharo-dev] GSoC Week 3 update - Enhancing Pharo Command Line

by Ben Coman

On Thu, Jun 1, 2017 at 5:06 PM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: > Hi all, > > It has been about three weeks, I started working on my GSoC project. The > first task I am working on is the new implementation for Current Working > Directory. I have written the new implementation. Currently, I am testing > the new code. Will soon share the work here. > Meanwhile, for the week three, I have written a blog post > <https://vineetreddy.wordpress.com/2017/05/29/cross-platform-with-pharo/> > on OSPlatfrom. Please do take a look and give your feedback. > > Thanks, > Rajula > > > Hi Rajula, Great to see an article on this subject. Probably its at a good level for pharo-users mail list as well, so I've copied there. Don't worry about the limited response. Many in pharo-dev probably know this subject well. It is still good to have it laid out like you did for newcomers to google when they need to know. cheers -ben

June 6, 2017

Bloc/Brick/Spec

by Brad Selfridge

I'm confused. I see the latest news and documentation about Bloc. Is Brick now dead and Bloc the default? I thought Brick was a layer on top of Bloc and Spec was layer on top on Brick? What is the direction now? Brad Selfridge ----- Brad Selfridge -- View this message in context: http://forum.world.st/Bloc-Brick-Spec-tp4949591.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 6, 2017

Re: [Pharo-users] How to deploy headless app without changes and source files?

by Andreas Sunardi

I had my changes and sources files in the bundle but has their write permission removed, and that causes the error. Simply deploying the tool without the changes file seems to fix it. Pharo5 doesn't complain if the changes file isn't there. However, without the sources file, I get this warning that pharo cannot locate the sources file. Including the sources file in the deployed tool is fine with me. So, I think that's my solution. Thanks! On Mon, Jun 5, 2017 at 5:07 PM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > I found this StackOverflow question: > https://stackoverflow.com/questions/14737695/is-it- > possible-to-deploy-a-pharo-image-without-changes-and- > sources-files/14747328 > > and this older forum thread: > https://www.mail-archive.com/pharo-project@lists.gforge. > inria.fr/msg21170.html > > I'm using Pharo5.0 and neither of these options is available anymore. What > is the new way to do this? > > -- > Andreas Sunardi >

June 6, 2017

Re: [Pharo-users] Wiring objects, IoC and Service Locator

by Ben Coman

On Tue, Jun 6, 2017 at 5:11 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx ben. > When I see all this complexity for something that looks not that complex: > I prefer to pass the class and get done. > May be I missed something obvious... but when I see something too complex > I start to get worried. > > I think that thinking about the contract between classes at runtime is > important and to me a MovieLister should be using at runtime and instance > of the *Finder* > Now needing an extra class just to set this should really be evaluated > with the tradeoff: "flexibility win" (our simple solution is still really > flexible - I decide when I want to pass the correct finder) vs. the code > and conceptual bloat. > > > I'm happy not to face the hyper super over engineering of Java "solutions". > > I like the "Of course this just shifts the burden a tad, we still have to > get the locator into the lister" > but the solution is super simple let us use another "Singleton and a > Factory...." :) > > Stef > > On Mon, Jun 5, 2017 at 8:43 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Tue, Jun 6, 2017 at 1:26 AM, Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> >>> Thanks for the answer Ben and Stephane. >>> >>> I already read A Mentoring Course on Smalltalk, Valloud, there is >>> nothing there I could use in this case :( . I will look after for The >>> Design Patterns Smalltalk Companion. Most of the sources provided I already >>> know of or went in the same lines lines of what I have already found. >>> >>> About TDD, I am experienced with the discipline and have tested it on >>> Pharo living system already, but I could not understand how this is related >>> with object wiring, DI and service locator. >>> >> >> I guess I don't properly understand your need and those topics. That was >> my quick pass. Now if I take the time to actually read Fowler's long >> article >> >> "the inversion is about how they lookup a plugin implementation ... to >> ensure that any user of a plugin follows some convention that allows a >> separate assembler module to inject the implementation into the lister." >> >> "The basic idea of the Dependency Injection is to have a separate object, >> an assembler, that populates a field in the lister class with an >> appropriate implementation for the finder interface. There are three main >> styles of dependency injection. The names I'm using for them are >> Constructor Injection, Setter Injection, and Interface Injection." >> >> Now there was too much syntactical noise in those Java examples for me to >> think clearly, so I converted them all to Smalltalk. >> >> >> ##CONSTRUCTOR INJECTION >> >> Object subclass: MovieLister >> instanceVariables: 'finder' >> >> >> MovieLister class >> newWith: aFinder >> ^ self basicNew initializeWith: aFinder >> >> MovieLister >> initializeWith: aFinder >> finder := aFinder >> >> >> ColonMovieFinder class >> newWith: aFilename >> ^ self basicNew initializeWith: aFilename >> >> ColonMovieFinder >> initializeWith: aFilename >> filename := aFilename. >> >> >> ConstructorInjectionContainer >> new >> container := DefaultContainer new. "the article doesn't specify >> where this comes from" >> finderParams := ConstantParameter newWith: 'movies1.txt'. >> container registerComponentInterface: MovieFinderInterface >> implementation: ColonMovieFinder >> params: finderParams. >> container registerComponentImplementation: MovieLister >> ^container >> >> to be used like this... >> ConstructorInjectionTest >> testWithContainer >> container := ConstructorInjectionContainer new. >> lister := container getComponentInstance( MovieLister ). >> movies = lister moviesDirectedBy: 'Sergio Leone'. >> self assert: (movies includes: 'Once Upon a Time in the West') >> >> The article poorly defines registerComponentXXX: or getComponentInstance: >> methods, so I don't dwell on them. I presume its little relevant to the >> main theme. >> >> >> ##SETTER INJECTION >> >> MovieLister >> setFinder: aFinder >> finder := aFinder. >> >> ColonMovieFinder >> setFilename: aFilename >> filename := aFilename. >> >> SetterInjectionTest >> testWithConfigurationFile >> ctx := SomeXmlApplicationConfiguration on: 'config.xml'. >> lister := ctx getConfigOf: 'MovieLister'. >> movies = lister moviesDirectedBy: 'Sergio Leone'. >> self assert: (movies includes: 'Once Upon a Time in the West') >> >> >> ##INTERFACE INJECTION >> >> MovieLister >> injectFinder: aFinder >> finder := aFinder >> >> ColonMovieFinder >> injectFilename: aFilename >> filename := aFilename >> >> InterfaceInjectionTest >> configureContainer >> container := InterfaceInjectionContainer new. >> self registerComponents. >> self registerInjectors. >> container start. >> >> InterfaceInjectionTest >> registerComponents >> container registerComponent: 'MovieLister' with: MovieLister. >> container registerComponent: 'MovieFinder' with: ColonMovieFinder. >> >> InterfaceInjectionTest >> registerInjectors >> container registerInjector: Injector with: (container lookup: >> 'MovieFinder'). >> container registerInjector: InjectorFinderFilename with: >> FinderFilenameInjector new. >> >> ColonMovieFinder >> inject: anObject >> anObject injectFinder: self. >> >> FinderFilenameInjector >> inject: anObject >> anObject injectFilename: 'movies1.txt'. >> >> InterfaceInjectionTester >> testInterface >> self configureContainer. >> lister := container lookup: 'MovieLister'. >> movies = lister moviesDirectedBy: 'Sergio Leone'. >> self assert: (movies includes: 'Once Upon a Time in the West') >> >> The article doesn't define InterfaceInjectionContainer, but I guess it >> could look like this... >> >> InterfaceInjectionContainer >> registerComponent: componentName with: >> aComponent >> container ifNil: [ container := Dictionary new]. >> container at: componentName put: aComponent >> >> InterfaceInjectionContainer >> lookup: componentName >> ^ container at: componentName >> >> >> ##SERVICE LOCATOR >> >> "The basic idea behind a service locator is to have an object that knows >> how to get hold of all of the services that an application might need. So a >> service locator for this application would have a method that returns a >> movie finder when one is needed. Of course this just shifts the burden a >> tad, we still have to get the locator into the lister" >> >> MovieLister >> initialize >> finder := ServiceLocator movieFinder. >> >> >> Object subclass: ServiceLocator >> instanceVariable: 'movieFinder' >> classVariable: 'SoleInstance' >> >> ServiceLocator class >> load: aServiceLocator >> SoleInstance := aServiceLocator >> >> ServiceLocator class >> soleInstance >> ^ SoleInstance >> >> ServiceLocator class >> movieFinder >> ^ self soleInstance movieFinder >> >> ServiceLocator >> movieFinder >> ^movieFinder >> >> >> ServiceLocatorTest >> configure >> ServiceLocator load: (ServiceLocator newWith: (ColonMovieFinder >> newWith: 'movies1.txt')) >> >> >> ServiceLocator class >> newWith: aMovieFinder >> ^ self basicNew initializeWithFinder: aMovieFinder >> >> ServiceLocator >> initializeWithFinder: aMovieFinder >> movieFinder := aMovieFinder >> >> >> ServiceLocatorTest >> testSimple >> self configure. >> lister := MovieLister new. >> movies = lister moviesDirectedBy: 'Sergio Leone'. >> self assert: (movies includes: 'Once Upon a Time in the West') >> >> So it seems that a service locator is just a Singleton pattern having a >> class variable for each service of interest ?? >> > It was late and I mispoke here, of course this should have said... * a Singleton pattern having an instance variable for each service of interest * a Singleton pattern having a getter method (with hidden implementation) for each service of interest > So in good faith** I ask... "Is it any more complicated than that?" >> >> **Since its taken me a couple of hours to convert the Java to this point >> so I stopped reading to seek your feedback. >> > but I'll add, it was so much simpler to understand without all that Java typing boiler plate. cheers -ben > Is that enough insight to adapt to your needs, or is there something else >> further down the article that invalidates my analysis? >> >> >> >> >> >>> >>> From ben: >>> >>> "I'm not really familiar with IoC or DI patterns, so just taking your >>>> example at face value, in Pharo I'd do... >>>> >>>> MovieLister>>moviesDirectedBy: director >>>> allMovies := finder allMovies. >>>> ^ allMovies select: [ :movie | movie getDirector = director ]. >>>> "although typically #getDirector would be renamed #director" >>>> >>>> MovieLister>>finder: movieFinder >>>> finder := movieFinder. >>>> >>>> to be used like this... >>>> lister := MovieLister new finder: (ColonDelimitedMovieFinder on: >>>> 'movies1.txt'). >>>> movies := lister moviesDirectedBy: 'Tarantino'." >>> >>> >> >> So per Fowler, the above is equivalent to "Setter Injection with Spring" >> >> >>> >>> and Stephane: >>> >>> Why don't you simply pass the class and use that class in your >>>> MovieLister? >>>> >>>> MovieLister new >>>> finderClass: MySuperCoolFinderClass >>>> >>>> ... >>>> MovieLister finder >>>> finderClass new ..... >>>> >>>> What is wrong with that. >>> >>> >>> That was what I meant when I said: "I know that in Smalltalk I can make >>> MovieLister to receive, upon construction, a class representing MovieFinder >>> and call it construction message.". The code I had in mind is a bit of >>> mix from the one provided by you both: >>> >>> MovieLister>>moviesDirectedBy: director >>> allMovies := finder allMovies. >>> ^ allMovies select: [ :movie | movie getDirector = director ]. >>> "although typically #getDirector would be renamed #director" >>> >>> MovieLister>>finder: aMovieFinderBuilder >>> finder := aMovieFinderClass new. >>> >>> to be used like this... >>> lister := MovieLister new finder: (ColonDelimitedMovieFinder >>> builderOn: 'movies1.txt'). >>> movies := lister moviesDirectedBy: 'Tarantino'." >>> >>> But that means I will have to wire dependencies by hand whenever I >>> create a MovieLister and seek through code when and if those dependencies >>> change. When there are lot's of dependencies it's is a considerable and >>> tedious work. Let's see an image from Fowlers article: >>> >>> [image: Inline image 1] >>> >>> In this case, the service locator provides me with an instance and I >>> configure the instance in the assembler, the scheme is alike for an IoC, >>> and that would mean my implementation could be like this: >>> >>> >>> MovieLister>>moviesDirectedBy: director >>> allMovies := finder allMovies. >>> ^ allMovies select: [ :movie | movie getDirector = director ]. >>> "although typically #getDirector would be renamed #director" >>> >>> MovieLister>>initialize >>> finder := ServiceLocator locate: FinderClass <--- This would >>> bring the instance of finder class configured by the assembler >>> >> >> No, like this... >> finder := ServiceLocation movieFinder. >> >> Now if you want to store a class rather than an instance as I did higher >> up, you just do this... >> >> Object subclass: ServiceLocator >> instanceVariable: 'movieFinderClass' >> classVariable: 'SoleInstance' >> >> ServiceLocator class >> movieFinder >> ^ self soleInstance movieFinderClass new >> >> >> >>> >>> >>> to be used like this... >>> lister := MovieLister new. >>> movies := lister moviesDirectedBy: 'Tarantino'." >>> >>> and the assembler: >>> >>> Assember class>>configure: >>> aMap put: (ColonDelimitedMovieFinder builderOn: 'movies1.txt') at: >>> FinderClass >>> >> >> Assembler class>>configure >> ServiceLocator load: >> (ServiceLocator new >> movieFinder: (ColonMovieFinder newWith: 'movies1.txt') >> otherService: MyCustomService new) >> >> >>> >>> My assembler and service locator could be even more elaborated, and >>> provide a different MovieFinder in test scope, for different classes or >>> wharever. >>> >> >> Really, the test should not be updating the class variable global like >> this... >> ServiceLocatorTest >> configure >> ServiceLocator load: (ServiceLocator newWith: (ColonMovieFinder >> newWith: 'movies1.txt')) >> >> you probably want something like (its rough but shows the point...) >> Object subclass: #MovieLister >> instanceVariables: 'serviceLocator' >> >> MovieLister >> initialize >> serviceLocator ifNil: [ serviceLocator := ServiceLocator soleInstance >> ]. >> finder := serviceLocator movieFinder. >> >> MovieLister class >> newWithServiceLocator: aServiceLocator >> ^ (self basicNew initializeWithServiceLocator: aServiceLocator) >> initialize. >> >> MovieLister >> initializeWithServiceLocator: aServiceLocator >> serviceLocator := aServiceLocator >> >> ServiceLocatorTest >> testSimple2 >> lister := MovieLister newWithServiceLocator: (ServiceLocator newWith: >> (ColonMovieFinder newWith: 'movies1.txt')). >> movies = lister moviesDirectedBy: 'Sergio Leone'. >> self assert: (movies includes: 'Once Upon a Time in the West') >> >> >> cheers -ben >> >> >>> >>> It is a little convenience for Smalltalk, I will give that, but I was >>> wandering if there was something alike in Pharo, by your answers I assuming >>> there is nothing like that. >>> >>> >>> >>> On Mon, Jun 5, 2017 at 6:41 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> >>>> Why don't you simply pass the class and use that class in your >>>> MovieLister? >>>> >>>> MovieLister new >>>> finderClass: MySuperCoolFinderClass >>>> >>>> ... >>>> MovieLister finder >>>> finderClass new ..... >>>> >>>> What is wrong with that. >>>> >>>> If you do not want to have a reference at runtime to a Finder then you >>>> need to use announcement and registration. >>>> >>>> Stef >>>> >>>> >>>> >>>> On Sun, Jun 4, 2017 at 11:17 PM, Vitor Medina Cruz < >>>> vitormcruz(a)gmail.com> wrote: >>>> > Hello, >>>> > >>>> > I would like to know how people in Pharo ecosystem do to deal with >>>> object >>>> > wiring, as described by Marting Fowler in >>>> > https://martinfowler.com/articles/injection.html#FormsOfDepe >>>> ndencyInjection: >>>> > >>>> > "A common issue to deal with is how to wire together different >>>> elements: how >>>> > do you fit together this web controller architecture with that >>>> database >>>> > interface backing when they were built by different teams with little >>>> > knowledge of each other." >>>> > >>>> > He gives an example, I will leave it in java as it is simple enough to >>>> > understand: >>>> > >>>> > "class MovieLister... >>>> > >>>> > public Movie[] moviesDirectedBy(String arg) { >>>> > List allMovies = finder.findAll(); >>>> > for (Iterator it = allMovies.iterator(); it.hasNext();) { >>>> > Movie movie = (Movie) it.next(); >>>> > if (!movie.getDirector().equals(arg)) it.remove(); >>>> > } >>>> > return (Movie[]) allMovies.toArray(new Movie[allMovies.size()]); >>>> > >>>> > }" >>>> > >>>> > The question is how to provide the finder object in a decoupled >>>> matter, a >>>> > naive approach would be: >>>> > >>>> > " private MovieFinder finder; >>>> > >>>> > public MovieLister() { >>>> > finder = new ColonDelimitedMovieFinder("movies1.txt"); >>>> > >>>> > }" >>>> > >>>> > Which couples the MovieLister to the specific >>>> ColonDelimitedMovieFinder >>>> > class. >>>> > >>>> > Fowler explains how to decouple using an IoC framework or a Service >>>> Locator. >>>> > In Java and .Net IoC is used most of the time. I Googled how this >>>> problem is >>>> > approached in Smalltalk/Pharo, and I generally I found answers "that >>>> is easy >>>> > to do in Smalltalk, so there is no need of a framework", what I miss >>>> is a >>>> > description on *how* to do that: >>>> > >>>> > https://stackoverflow.com/questions/243905/smalltalk-and-ioc >>>> > https://stackoverflow.com/questions/2684326/is-there-a-depen >>>> dency-injection-framework-for-smalltalk >>>> > https://stackoverflow.com/questions/243905/smalltalk-and-ioc >>>> /347477#347477 >>>> > >>>> > I know that in Smalltalk I can make MovieLister to receive, upon >>>> > construction, a class representing MovieFinder and call it >>>> construction >>>> > message. As long an object that responds to this message is provided, >>>> I can >>>> > create as many derivations I want and the MovieLister will be >>>> decoupled from >>>> > the MovieFinder. That way, however, I still have to wire things by >>>> hand, and >>>> > I am not sure if this is what I am supposed to do in order to solve >>>> the >>>> > decouple problem. >>>> > >>>> > Can you explain me how this is done in Pharo? It's is usually wiring >>>> by >>>> > hand? Is there a simple construction that deals with the wiring >>>> problem that >>>> > I cannot foresee? >>>> > >>>> > Thanks in advance, >>>> > Vitor >>>> > >>>> > >>>> > >>>> >>>> >>> >> >

June 6, 2017

Re: [Pharo-users] XPath has unresolved dependencies

by monty

June 6, 2017

How to deploy headless app without changes and source files?

by Andreas Sunardi

I found this StackOverflow question: https://stackoverflow.com/questions/14737695/is-it-possible-to-deploy-a-pha… and this older forum thread: https://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg21170.h… I'm using Pharo5.0 and neither of these options is available anymore. What is the new way to do this? -- Andreas Sunardi

June 6, 2017