- Pharo-users - lists.pharo.org

Metacello does not load the expected version from ConfigOf

by Usman Bhatti

Hi all, I am trying to load a specific version of PetitParser in a Moose image. A Moose image comes with the latest development version of PetitParser. So, I am trying to downgrade to an older version. So, when I load the version manually, older versions of the packages are loaded: (ConfigurationOfPetitParser project version: '1.51') load But when I try to load the same version within my ConfigOf the expected packages are not loaded and list of the PetitParser packages loaded remains unchanged. Here is how my baseline looks like: ConfigurationOfDummyParser>>baseline01: spec <version: '0.1-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec project: 'PetitParser' with: [ spec className: #ConfigurationOfPetitParser; versionString: '1.51'; repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/' ]. ]. I also tried creating a version but it didn't help. ConfigurationOfDummyParser>>version10: spec <version: '1.0' imports: #('0.1-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 1.0'. spec author: 'usmanbhatti'. spec timestamp: '12/19/2014 16:35'. spec project: 'PetitParser' with: '1.51'. ]. I also had a look at the package the configuration tries to load and the list shows correct packages to be loaded (see screenshot). Does anyone have an idea what may be problematic in my code or that of Metacello? I am attaching the code of my ConfigOf for a Moose image. Thanks in advance. Usman[image: Inline image 1]

Dec. 19, 2014

Re: [Pharo-users] Question about Morphic in Pharo 4

by Sean P. DeNigris

Daniel Lyons wrote > My impression is that Morphic must have started out as a small and > beautiful core. Otherwise you wouldn't find so many people talking about > how amazing it was in writings dated 10 years ago and earlier The idea is revolutionary and beautiful - that everything you see on the screen can be dealt with like a physical object in the real world; you would "pick up" a picture from a web page or "pick up" a menu item to anchor to the desktop as easily as you can pick up a file icon and drop it in another folder. It was originally implemented in Self, so "small and beautiful" buzz may have been from that setting. From what I understand, Squeak's Morphic was stuffed with experiments from very early on. Daniel Lyons wrote > I have also heard that Morphic made more sense in its original habitat in > Self, because you really could just clone a UI component and start > customizing it, because Self only has instances, no classes. The "direct > manipulation" argument is slightly sabotaged by the intrusion of a class > hierarchy and textual coding. I have heard that a lot too, but don't think it's really true. If you define the state that makes a morph a morph, why can't you implement a way to save that current state to a subclass or update the current class? It's just that no one's implemented it yet, probably because few people remember the Dynabook and Morphic visions that make direct, live, uniform manipulation important, and the blue plane ideas have degenerated to pink plane "how do we easily make business UIs; not that that's not an important goal, too, but I would hate to forget the revolutionary power we have underneath! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Question-about-Morphic-in-Pharo-4-tp4796331p4796438.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 19, 2014

Re: [Pharo-users] [ANN] RProjectConnector V1.0

by Blondeau Vincent

De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de HernÃ¡n Morales Durand EnvoyÃ© : jeudi 18 dÃ©cembre 2014 05:31 Ã : Any question about pharo is welcome Objet : Re: [Pharo-users] [ANN] RProjectConnector V1.0 Hi Vincent, Hi, 2014-12-17 6:02 GMT-03:00 Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>>: Hernan, To detect the R installation path is complicated. Yes, I am currently working in a NBWin32Registry so we can do: (NBWin32Registry hKeyLocalMachine at: 'Software\R-core\R') values the reason I didn't committed a solution is I am having ERROR_INVALID_FUNCTION with RegEnumValueA apiRegEnumValue: hKey with: dwIndex with: lpValueName with: lpcchValueName with: lpReserved with: lpType with: lpData with: lpcbData " http://msdn.microsoft.com/en-us/library/windows/desktop/ms724865%28v=vs.85%… " <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> ^ self nbCall: #( long RegEnumValueA( HKEY hKey, DWORD dwIndex, LPTSTR lpValueName, LPDWORD lpcchValueName, LPDWORD lpReserved, LPDWORD lpType, LPBYTE lpData, LPDWORD lpcbData)) module: 'advapi32.dll' Where is the Windows registry access project? I think that to set the libraries available to download on a server is currently a better idea. Do you know where it can be hosted? An option to upload library files could be http://files.pharo.org/ but I don't have access to. Foy my configurations I am currently using DropBox although not charming it serves well. But AFAIK you cannot link multiple accounts to one DropBox. There are other reliable options? http://files.pharo.org/ seems to be a good solution. Vincent HernÃ¡n ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Dec. 19, 2014

Re: [Pharo-users] Question about Morphic in Pharo 4

by kilon alios

> > " Then I guess it grew rapidly and radically out of control and became > this monstrosity " Where are the people running screaming , where are the superheroes to save the day ? Think about it, if Morphic was really ugly that started as something beautiful then someone would have rebooted Morphic by now and started something from scratch and replaced Morphic by now. I have been very closely following pharo lists for a couple of years now and I have not seen so many people complain about Morphic. Sure Morphic has its own messes to deal with but please find me a library of the size of Morphic that is not messy in some areas. You think that QT , GTK , Winforms etc are not heavily criticized ? Think again. GUI APIs are big ugly and prone to confusion and bad designs. The problem with modern GUI APIs are that the demands for them are super complex. Looks at web browser which are now the forefront of GUI design is a ton of mess because the demands are really that complex . Take a look at 3d applications, 2d app, audio apps and music apps and you will find that many of them use their own GUI APIs. Why people tolerate these big messy GUIs APIs , why they tolerate the ugliness of html/css ? The answer Is simple . because they offer what they need . Same applies with Morphic, its big and complex because we need it to be big and complex. Could the design being improved ? sure and Morphic is constantly improving , I make my own contribution as well because its an area that heavily interests me. But make no mistake about it, you will never have a shoe that fits all. For me its much better to have several tools and libraries that help us deal with the complexity of Morphic than simplifying Morphic by removing useful features in sake of simplifying. If you want to see what real monstrosity looks like take a look at MFC, its the only library of any kind that I know that desperately needs an exorcism. "Following the Spec tutorial (which is excellent, by the way!)" See this is where we get in the area of personal preference, I find Spec very ugly. I mean really , really ugly. I used it to develop my theme manager Nireas and I definetly dont like its workflow and now I am seriously looking into porting Nireas back to Morphic and developing my own library to fix Morphic shortcomings. However this is what is amazing about Pharo we live in a time that because of the active development and contribution you have many choices and you can choose the one that fits you better or the one you like the most. For the example even though I dont like html/css as you may have guessed by now, I would love to have webkit or some other web browser engine embeded inside the pharo image and so being able to display websites from inside pharo. None can question the incredible value of diversity of options. "I have also heard that Morphic made more sense in its original habitat in Self, because you really could just clone a UI component and start customizing it, because Self only has instances, no classes." I think prototype based programming is great because offers to the developer more power in more elegant way than classes. I think you will find few people not agreeing on this, even one of the creators of Smalltalk , Ingalls, said something along the lines that if he had to redesign Smalltalk would have made it prototype based. But and thats a big but in practice I seriously question the usefulness of prototype based programming. Take a look at Pharo its class based but still easy to hack , right ? Yet people are reluctant to hack and for a good reason. Because you have to deal with merge hell , people hacking the same thing as you or you do something and system misbehaves because you hacked an object that another object depended on. So classes for me are there to provide a more concrete implementation and area that is labeled "modify with extreme care" . Afterall its not that hard to take a Morph class subclass it and create your own class instead of changing that Morph class directly. But as I said I agree that prototype based programming is more elegant but in the end it does not matter as much as you think it does, because if it did then Prototype based would be dominant by now. So to summarize , no Morphic fits Pharo like a glove. "Spec seems to be promising non-Morphic backends, is that an active development interest and if so what targets are being explored?" Spec is a wrapper meaning knowing spec does not require to know Morphic and that means also it can exist without Morphic, not currently, but probably one day. PolyMorph is an extension of Morphic meaning you have to know Morphic and depends on it. So they are two very fundamentally different things. I think however this is a moot point. The bottom line is that GUI development is an extremely important part of Pharo and any other programming language. If you can bet on anything is that GUI APIs of any kind will keep evolving , so yes Morphic will keep improving, Spec will keep improving and we will see new kids in the block like we already see with Bloc and Brick, Some of them will be small and elegant solutions but limited, other will be big and complex but powerful. But hey who can predict the future ?

Dec. 19, 2014

[ANN] WKHTML2PDF for Pharo

by Torsten Bergmann

Need an easy way to convert HTML into PDF for printing? The project http://wkhtmltopdf.org can help you here. If you want to use it from Pharo just check out: http://smalltalkhub.com/#!/~TorstenBergmann/WKHTML2PDF This project allows you to easily use the library. First select the engine: HTML2PDFConverter useExecutable. or HTML2PDFConverter useLibrary. and then convert: HTML2PDFConverter convert: 'http://www.pharo.org' toFile: 'pharo.pdf' to get a printable version of the Pharo homepage. As ever docu is on the STHub project website. It uses NativeBoost to call the library and OSProcess to call the executable. Bye T.

Dec. 19, 2014

Re: [Pharo-users] Question about Morphic in Pharo 4

by Daniel Lyons

> On Dec 18, 2014, at 3:31 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > You never know but in general we pay attention not to break for the shake of it. > Then Morphic is several things > - low level > - widgets > - polymorph > So this is difficult to be fully affirmative. What I can say is that we did not change much. Not the OP, but I've been confused about the history and future plan for some time. My impression is that Morphic must have started out as a small and beautiful core. Otherwise you wouldn't find so many people talking about how amazing it was in writings dated 10 years ago and earlier. It must have been much faster and easier to work with than the earlier MVC. Then I guess it grew rapidly and radically out of control and became this monstrosity sitting in the Squeak image, which has been pared down significantly in the Pharo image but is still basically huge. Squeak mostly evolved by shared changes to the image, so there was no concept of separate packages adding this or that method to this system class, so everything eventually wound up depending on everything. As our infrastructure is inherited, we inherit this problem, even as we go about breaking everything down and simplifying it, there is a long way to go to get back to the original small and beautiful coreâand that may not even really be a goal for Pharo and Morphic. Is this fair and accurate? I have also heard that Morphic made more sense in its original habitat in Self, because you really could just clone a UI component and start customizing it, because Self only has instances, no classes. The "direct manipulation" argument is slightly sabotaged by the intrusion of a class hierarchy and textual coding. I'm just regurgitating a wisp of a memory though, I don't know if anybody who used it a lot would agree or not. (I'm not sure how one is able to make comprehensive principled changes in such a system, but that's an unnecessary diversion.) It seems to me that as Morphic halos get harder to get access to, direct manipulation becomes harder to effect; on the other hand, halos are probably a lot more confusing to beginners than helpful to anyone. Comments? From there I'm not quite sure what Polymorph is and what its development status/future outlook are like. Is it actively developed and are we happy with people building new stuff with it? Seems like it was the preferred UI paradigm a few years ago but now we have Spec. Spec seems to be promising non-Morphic backends, is that an active development interest and if so what targets are being explored? Historically, Morphic itself seems to promise multiple backends (the comment on Canvas says "A canvas is a two-dimensional medium on which morphs are drawn in a device-independent manner"), did that ever come to fruition, or did they just mean it supported different kinds of monitors? In the old books I see a lot of mentions of things like "pluggable" widgets, and in the image I see things like PluggableTextMorph. Following the Spec tutorial (which is excellent, by the way!), it feels like I have a lot of manual copying around of data in whenTextChanged: handlers. In fact, the old books also talk about the changed/changed:/changed:with: observer system, which I see is still in the image but it's not clear to me if any of these systems make use of that or if this whole system is considered deprecated. My suspicion is that it is deprecated because there is NewValueHolder. Is it? I'm mostly asking for history as I try to get my bearings and not trying to deprecate anyone or anything, so if anything in the above is offensive, it is an accident, please correct me. Thanks, â Daniel Lyons

Dec. 19, 2014

Re: [Pharo-users] New Pharo Collections

by stepharo

In the Design Pattern iterator there are some nice examples about iterators. Stef Le 17/12/14 08:49, ClÃ©ment Bera a Ã©crit : > > > 2014-12-17 7:42 GMT+01:00 Damien Cassou <damien.cassou(a)gmail.com > <mailto:damien.cassou@gmail.com>>: > > > Le 16 dÃ©c. 2014 22:48, "dboeren" <boerend(a)gmail.com > <mailto:boerend@gmail.com>> a Ã©crit :. > > Off the top of my head, I would be interested in support for > "slices" > > meaning taking being able to treat a subset of a larger > OrderedCollection as > > its own OrderedCollection rather than using copyFrom:to: to create a > > duplicate object to work with. It seems to me that this would > be a more > > efficient method and should not be difficult to implement I think. > > Here is an email I sent about that : > > I see you are working on new collections for Pharo. That's great news, > I'm convinced we can do much better (even if what we already have is > already much better than what can be found in most other languages). > One thing you could work on is the notion of iterator. There are > plenty of ways to iterate over a collection: > > 1/ from the first to the last item > 2/ from the last to the first > 3/ from the 2nd item to the 5th > 4/ only even items (2, 4, 6, ...) > 5/ ... > > Currently, we have to create new collections to iterate in strange > ways. For example, to iterate from the last to the first item, we > create a new collection by sending #reversed to the original > collection. I think that is bad because it creates a copy and that > should not be necessary. > > I don't understand that example. #reverseDo: do not create a copy and > do not send reversed. To iterate over items from last to first I > always do, as recommended in Smalltalk best practice pattern: > > mySequenceableCollection reverseDo: [:item | .. ]. > > #reverseDo: is implemented on SequenceableCollection but iterating > from last to first item does not make sense in the case of non > sequenceable collection. > > What we miss is the notion of iterator. An > iterator is an object that is specialized in iterating over any kind > of collection and has methods like #select:, #reject:, #allSatisfy:. > >From a collection, you can access different kinds of iterators > (reusing the same ordering as before): > > 1/ aCollection iterator > 2/ aCollection reverseIterator > 3/ aCollection from: 2 to: 5 > 4/ aCollection iterator select: [ :each | each isEven ] --> that > returns an iterator as well, so you can call #select:/#reject: > multiple times without creating any intermediate collection > 5/ ... > > That makes sense and would be lovely. What is the syntax for multiple > operations ? Have you already think and find something nice about it ? > > aCollection iterator > select: [ :each | each isOdd ]; > reject: [ :each | each is isPrime ]; > iterate > > ??? > > Of course there are backward compatibility issue which needs to be > very well adressed here or one would crash every single framework in > the system. > > Lukas Renggli implemented a prototype that looks really nice but is > unfinished: > http://source.lukas-renggli.ch/unsorted/Container-lr.7.mcz. > > I think the notion of Sequences in Clojure is very related as well. > Sequence functions are very generic and can be applied to any kind of > collection. http://clojure.org/sequences >

Dec. 18, 2014

Re: [Pharo-users] Question about Morphic in Pharo 4

by stepharo

Hi You never know but in general we pay attention not to break for the shake of it. Then Morphic is several things - low level - widgets - polymorph So this is difficult to be fully affirmative. What I can say is that we did not change much. stef Le 18/12/14 15:28, nacho a Ã©crit : > Hi folks, > I'm doing some project in Morphic in Pharo 3. I was wondering if big changes > are expected in Moprhic in Pharo 4 or if it will remain relatively > unchanged. > Thanks in advance. > Nacho > > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: http://forum.world.st/Question-about-Morphic-in-Pharo-4-tp4796331.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Dec. 18, 2014

Re: [Pharo-users] Question about SUnit

by Sven Van Caekenberghe

You need to check out TestResource (see it's class comment), it was designed specifically for that purpose. > On 18 Dec 2014, at 20:00, Demian Schkolnik <demianschkolnik(a)gmail.com> wrote: > > Greetings. > > I have to do a bunch of tests, where the initial set up is quite costly (launching ROS system and a bunch of nodes). Therefore, I don't want to set it up each time before a test (like with the standard setUp function). How can I make it so that the setUp function is called only once overall before ALL tests? (And aditionally, so that the tearDown function is called only once after all tests have run?) > > Thank you all in advance, > best,

Dec. 18, 2014

Question about SUnit

by Demian Schkolnik

Greetings. I have to do a bunch of tests, where the initial set up is quite costly (launching ROS system and a bunch of nodes). Therefore, I don't want to set it up each time before a test (like with the standard setUp function). How can I make it so that the setUp function is called only once overall before ALL tests? (And aditionally, so that the tearDown function is called only once after all tests have run?) Thank you all in advance, best,

Dec. 18, 2014