February 2019 - Pharo-users

Re: [Pharo-users] Streams for FileReference in Pharo 7

by ducasse

> > I have been thinking a bit more about this, and I have a lot of problems with > > Integer>>#putOn: aStream > aStream isBinary > ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] > ifFalse: [ self asString putOn: aStream ] > > I think we should simply remove this method. It is ugly and wrong. I agree > #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. > > The following two are OK for me: > > String streamContents: [ :out | out << 'Hello' << $! ]. > ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. > > But the following most definitively not: > > (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. > > When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). > > Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. yes. > > I think that if we remove Integer>>#putOn: I could live with > > ZnEncodedStream>>#<< anObject > anObject putOn: self Yes :) and remove the ugly one? Yes > > The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. > > Sven > >

Feb. 18, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by ducasse

Hi sven what I do not really with asString is that it potentially created another stream. with << the implementation of camillo (if I remember correctly) manages correctly both single object and collection and it is nice to have. I do not know if his implementation does not create additional stream. Stef > On 15 Feb 2019, at 10:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Jan, > > I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. > > IMHO, you better stick to #print: in that case. > > Consider the follow, that all fail: > > String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. > > String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. > > In other words: #<< works in bizar ways (check the implementors of #putOn:). > > I would be inclined to change > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection > > to > > ZnEncodedStream>>#<< collection > ^ self nextPutAll: collection asString > > but it would technically not be the same as the original #<< for in-memory streams. > > Opinions ? > > Sven > >> On 15 Feb 2019, at 09:52, Jan BlizniÄenko <jan.bliznicenko(a)fit.cvut.cz> wrote: >> >> Hello everyone >> >> I am trying to use Pharo 7 for my project and I noticed that most of my >> streams related code does not work anymore. Reason is that API for streams >> received from writeStream of FileReference changed and I think it changed >> for the worse in my case, because << does not properly handle any other >> objects than strings anymore. >> >> In both Pharo 6 and 7 I can write >> String streamContents: [ :s | s << 'hello' << 42 << $! ]. >> and get 'hello42!'. >> I can write in Pharo 6 but cannot in Pharo 7 >> 'hello.txt' asFileReference writeStreamDo: [ :s | s << 'hello' << 42 << $! ] >> In Pharo 6, I get same result in both examples (written to the file in >> second case of course), but in Pharo 7, the second example results in >> exception because << does not work with anything other than strings, so it >> seems I have to manually convert everything to strings. >> >> This change to streams seems to me like a setback for 2 reasons: >> 1) API amongst streams is no longer consistent in this case >> 2) streams for files lost useful functionality and to make my project >> compatible with Pharo 7, I have to make lots of effort to make my code >> uglier and longer >> >> I would like to ask for the reason of this change and whether is there >> anything that can be done with it. Or do I just misuse or misunderstand >> anything? Thank you. >> >> Best regards, >> Jan >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Feb. 18, 2019

Re: [Pharo-users] [TelePharo] Error in remote playground..

by Denis Kudriashov

Yes 18 ÑÐµÐ²Ñ. 2019 Ð³. 14:37 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "sergio ruiz" <sergio.rrd(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: Awesome! is this the one i should be using? https://github.com/pharo-ide/TelePharo Thanks! On February 17, 2019 at 3:06:18 PM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: I released new version of TelePharo adopted for Pharo 7. So now it should work out of the box ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by horrido

Whoa! This works! Thank you very much. Andrei Chis wrote > In the same image you can do that from the Iceberg user interface. You can > open Iceberg from the Tools menu. > Then right click on the Tutorial project and from the context menu select > Pull. > > On Mon, Feb 18, 2019 at 12:29 AM horrido < > horrido.hobbies@ > > wrote: > >> So how do I force Iceberg to reload? >> >> >> Andrei Chis wrote >> > If you use repositories that start with `github://` in Metacello you >> are >> > using Iceberg. Iceberg is used to clone and load the code. Metacello is >> > just the interface through which that is done. >> > >> > Running the loading instruction does not pull new changes from remote >> > repositories. >> > >> > On Sun, Feb 17, 2019 at 10:11 PM horrido < >> >> > horrido.hobbies@ >> >> > > wrote: >> > >> >> ??? >> >> >> >> I'm not using a cloned repository. I'm using Metacello just like in >> the >> >> snippet I showed you. Shouldn't it pull in the latest repo? >> >> >> >> I've never used Iceberg; I don't know how to use it. I don't really >> want >> >> to >> >> fuck around with GitHub. I don't want to be pulled into a rabbit hole. >> >> >> >> >> >> >> >> Andrei Chis wrote >> >> > If you already have the repository cloned, running the code that you >> >> > mentioned does not update the content of the repository. >> >> > Hence, the existing version will be loaded again. >> >> > >> >> > Instead you need to do a pull using Iceberg to update the content of >> >> the >> >> > repository and the code. >> >> > >> >> > Cheers, >> >> > Andrei >> >> > >> >> > On Sun, Feb 17, 2019 at 8:06 PM horrido < >> >> >> >> > horrido.hobbies@ >> >> >> >> > > wrote: >> >> > >> >> >> If you're referring to this: >> >> >> >> >> >> Metacello new >> >> >> baseline: 'BlocTutorials'; >> >> >> repository: 'github://pharo-graphics/Tutorials/src'; >> >> >> load >> >> >> >> >> >> It made no difference. Same error message. >> >> >> >> >> >> >> >> >> >> >> >> Andrei Chis wrote >> >> >> > Hi, >> >> >> > >> >> >> > Thanks for the bug report. >> >> >> > Can you try loading the latest version for the code of the >> tutorial. >> >> I >> >> >> > fixed the deprecation warning. >> >> >> > >> >> >> > Let us know if you encounter any other issues. >> >> >> > >> >> >> > Cheers, >> >> >> > Andrei >> >> >> > >> >> >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < >> >> >> >> >> >> > horrido.hobbies@ >> >> >> >> >> >> >> wrote: >> >> >> > >> >> >> >> I'm following the tutorial in the MemoryGame booklet. When I run >> >> the >> >> >> game >> >> >> >> and click on any square, I get: >> >> >> >> >> >> >> >> The method BlBaseAnimation>>#startOn: called from >> >> >> >> MgCardElement>>#onFlippedFace has been deprecated. >> >> >> >> Use BlElement>>#addAnimation: >> >> >> >> >> >> >> >> The tutorial is out of sync. How can I proceed? >> >> >> >> >> >> >> >> Is there another way to learn how to use Bloc? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Sent from: >> http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2019

Re: [Pharo-users] Calypso documentation? Or understanding menu building

by Tim Mackinnon

Hi Dennis - Iâve been reading the book you mentioned and looking through the code as well as your examples and I feel a bit more comfortable with whatâs going on - however I am stumped about how you do an OR context (vs. an AND context). I would like my menu item to appear for either a selected RPackage OR a ClyTaggedClassGroup - I thought I had it with: RPackage asCalypsoItemContext, ClyTaggedClassGroup asCalypsoItemContext (to get a composite context) but then I realised that the composite is an AND. Is there some way to create an OR context, or do I simply have to create multiple commands? Tim > On 12 Feb 2019, at 19:32, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim > > Ð²Ñ, 12 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 13:42, Tim Mackinnon <tim(a)testit.works>: > Is there any documentation on Calypso application contexts? I am trying to add a menu item to a package tag (the bit underneath a package - which I often call a sub-package). > > Only class comments are available for Calypso. Also there are a Commander booklet <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>which describes contexts and ClassAnnotation github readme <https://github.com/pharo-ide/ClassAnnotation> (together with class comments). > > > Iâve specified: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: RPackage asCalypsoItemContext > > > The #for: argument of command activations is a context where command should be available. Context describes condition where given command (its activation strategy) should be visible for users. > In your example "RPackage asCalypsoItemContext" is an instance of ClyBrowserItemContext which matches any selected package in the browser (when a kind of RPackage is selected). > And that's why you do not see it on selected tag because the tag is not a package. > > But that puts my menu on the package and not the tag > - and if I use the inspect extra menu in calypso, I get what looks to be something that could help me determine what I want but Iâm struggling to understand what ClyTaggedClassGroup does, and what a context is all about. > > Inspect command opens inspector of actually selected object which is an instance of ClyTaggedClassGroup in that case (try inspect selected method and you will get a CompiledMethod). > Children of package in browser are instances of ClyClassGroup and subclasses. So they are not raw tags. If you need a command for a tag you should add a command for ClyTaggedClassGroup items: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: ClyTaggedClassGroup asCalypsoItemContext > > Look for example at SycPromotePackageFromTagCommand class>>#fullBrowserMenuActivation which is defined this way. > > There are other kind of contexts which can be used in command annotations. For example if you want a command for selected method only in full browser then you should use ClyMethodContextOfFullBrowser: > > ^CmdContextMenuActivation byItemOf: ClyQueryMenuGroup for: ClyMethodContextOfFullBrowser > > it can be confusing that simple class is used in this case. But underhood it is converted to the instance of context where command should be available. > > > Has anyone else played around with this at all? > > Ideally I want to have a menu appear on all the tags underneath a particular package - and possibly including that package (or maybe not - I havenât decided as I want to try it in the wild). > > While Iâm at it - I have quite understood how to create submenuâs either - as Iâd like to have several commands all as sub items of a menu item âExercismâ. > > Look at commander booklet. It includes example. > > > Tim > > >

Feb. 18, 2019

Re: [Pharo-users] [TelePharo] Error in remote playground..

by sergio ruiz

Awesome! is this the one i should be using? https://github.com/pharo-ide/TelePharo Thanks! On February 17, 2019 at 3:06:18 PM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: I released new version of TelePharo adopted for Pharo 7. So now it should work out of the box ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 18, 2019

Re: [Pharo-users] Bloc Tutorial

by Andrei Chis

In the same image you can do that from the Iceberg user interface. You can open Iceberg from the Tools menu. Then right click on the Tutorial project and from the context menu select Pull. On Mon, Feb 18, 2019 at 12:29 AM horrido <horrido.hobbies(a)gmail.com> wrote: > So how do I force Iceberg to reload? > > > Andrei Chis wrote > > If you use repositories that start with `github://` in Metacello you are > > using Iceberg. Iceberg is used to clone and load the code. Metacello is > > just the interface through which that is done. > > > > Running the loading instruction does not pull new changes from remote > > repositories. > > > > On Sun, Feb 17, 2019 at 10:11 PM horrido < > > > horrido.hobbies@ > > > > wrote: > > > >> ??? > >> > >> I'm not using a cloned repository. I'm using Metacello just like in the > >> snippet I showed you. Shouldn't it pull in the latest repo? > >> > >> I've never used Iceberg; I don't know how to use it. I don't really want > >> to > >> fuck around with GitHub. I don't want to be pulled into a rabbit hole. > >> > >> > >> > >> Andrei Chis wrote > >> > If you already have the repository cloned, running the code that you > >> > mentioned does not update the content of the repository. > >> > Hence, the existing version will be loaded again. > >> > > >> > Instead you need to do a pull using Iceberg to update the content of > >> the > >> > repository and the code. > >> > > >> > Cheers, > >> > Andrei > >> > > >> > On Sun, Feb 17, 2019 at 8:06 PM horrido < > >> > >> > horrido.hobbies@ > >> > >> > > wrote: > >> > > >> >> If you're referring to this: > >> >> > >> >> Metacello new > >> >> baseline: 'BlocTutorials'; > >> >> repository: 'github://pharo-graphics/Tutorials/src'; > >> >> load > >> >> > >> >> It made no difference. Same error message. > >> >> > >> >> > >> >> > >> >> Andrei Chis wrote > >> >> > Hi, > >> >> > > >> >> > Thanks for the bug report. > >> >> > Can you try loading the latest version for the code of the > tutorial. > >> I > >> >> > fixed the deprecation warning. > >> >> > > >> >> > Let us know if you encounter any other issues. > >> >> > > >> >> > Cheers, > >> >> > Andrei > >> >> > > >> >> > On Sun, Feb 17, 2019 at 6:49 PM Richard Kenneth Eng < > >> >> > >> >> > horrido.hobbies@ > >> >> > >> >> >> wrote: > >> >> > > >> >> >> I'm following the tutorial in the MemoryGame booklet. When I run > >> the > >> >> game > >> >> >> and click on any square, I get: > >> >> >> > >> >> >> The method BlBaseAnimation>>#startOn: called from > >> >> >> MgCardElement>>#onFlippedFace has been deprecated. > >> >> >> Use BlElement>>#addAnimation: > >> >> >> > >> >> >> The tutorial is out of sync. How can I proceed? > >> >> >> > >> >> >> Is there another way to learn how to use Bloc? > >> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >> >> > >> >> > >> > >> > >> > >> > >> > >> -- > >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >> > >> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 18, 2019

Re: [Pharo-users] Monticello diff between image and tonel repo

by Hilaire

I confirm again this issue, while annoying, flushing Monticello helps to get a proper diff. https://github.com/pharo-project/pharo/issues/2583 Hilaire Le 16/02/2019 Ã 11:56, Hilaire a Ã©critÂ : > Closing Monticello windows and opening a fresh one helped to get the > changes right, sometime... Other time, forcing flush cash on Monticello > helps. -- Dr. Geo http://drgeo.eu

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

On Mon, Feb 18, 2019 at 7:50 AM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > Am 18.02.19 um 01:19 schrieb Tim Mackinnon: > > > Hey Ben - Iâm not sure that this actually does the same thing. I just > > tried it now, and it resulted in an extra merge in my forked repo - as I > > think this effectively pulls down from upstream into pharo and then if > > you have any differences in your local image copy they might cause some > > changes which then you would push back into your fork origin. > > > > If you just want a verbatim copy in your fork - you have to resort the > > command line? > > That's at least what I do: > > git pull upstream master > git push origin master > > I am pretty sure these basic operations are somewhere accessible in the > Iceberg code, but I have no idea how. > You can do these two from the UI :) You cannot do (from the UI) - a push --force - a reset You can do the reset from Iceberg's API, but you the force is not implemented yet... > > Iceberg would definitely gain from having a documented programmer's > interface. Git is way too complicated for a point-and-click interface to > be sufficient. I'd even say that "scriptable git" could become a Pharo > killer feature if done well. > This will soon come ;) At least the documented API for the most common features (then ones that are stable enough ^^). It's just people in our team is super busy... > > Konrad. > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 18, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Guillermo Polito

On Mon, Feb 18, 2019 at 2:45 AM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tim Mackinnon wrote > > wouldnât it be helpful if this was a command in Iceberg? > > Yes! This is a super common task and for easy cases would be great to > automate > https://help.github.com/articles/syncing-a-fork/ > > > That's useful as long as you don't find you have extra commits in your branch [image: image.png] Which AFAIU, it's Tim's case.

Feb. 18, 2019