February 2019 - Pharo-users

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

by Tim Mackinnon

Hi Guille - thanks for taking the time to write this upâ¦ in the middle there I finally spotted the crucial bit âclone the original, push to your forkâ. I think thats what Iâve been doing wrong - and it leads to all kinds of confusion (at least Iâm hoping this is what it is). As I have cloned from my Fork (and in my defence - its because we were given a repository that collides with the pharo one - exercism/pharo - and P7 doesnât let us clone from that) - so Iâve had to clone from my fork. It all seemed to work until I started submitting my PRâs and then they seem to include commits going much further back than I think they should need Even wen I thought I was being careful and syncing to master - it still seems to go back to some of my earliest work. Now that we have managed to get the repo renamed - I will try working like you have suggested and make sure that it is working like you describe - as it shouldnât be as complicated as this to make clean isolated changes and then submit them as a PR. (otherwise Pharo would fall apart). One question I do have however - is what is the best procedure if you realised when making changes that A) you forgot to make changes in a branch (so are working on master) B) you are working in a branch but decide some of your changes should go in another branch itself based on master (how to stash?) These are 2 common scenarios Iâve found when trying to be a good citizen for my little project. Do I have to go to the terminal to do this stuff - or can I cleanly do these kinds of operations in Pharo (which I think you should be able to do, as its so easy to get into either of those states). Thanks in advance. Tim > On 18 Feb 2019, at 08:56, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi! > > On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > > When you did your clone, did you clone the original repository or your fork's? > One way to simplify this workflow is: > - you clone always the original repository > - you create a branch and work there > - then you'll push your branch to your fork + fork > > That way your branch will be always up to date with the original repository, and no need to sync (actually the sync is done automatically when you push to your fork). > > Of course this assumes you're doing a new clone every time you work :). > > > So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? > > It would, there are several places where we could simplify the workflow for common cases, I agree. > > It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) > > I'd say its mandatory :). Otherwise you will not be able to push directly to it because of permission problems (actually all main dev branches are now blocked so **nobody**, not even admins, push to them directly). > > - and then at some point you need to catchup with that origin again? Or am I missing something? > > Well, it really depends on the workflow you use. Above I've explained a workflow that works when you clone every time. > Git is so complex and so low level that you can do lots of different things with it. > > First thing is to understand what "catch up with origin" means. In my head it only means: > - checkout your "to-catchup" branch > - merge the remote "to-catchup" branch and merge it > > All the rest is workflow dependent. Even (!!) I would argue that merging is not, strictly speaking, a correct way to catch up: If you have made changes into "to-catchup", then merging will not make both branches the same, but your "to-catchup" branch may have extra commits that you did not want to introduce... > > And here I'm not saying you should not merge, actually I do it most of the times because I know that 90% of the times it will be ok, and I do rollback when I realize I was in the other 10%... > > I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. > > Yes, and no. The "lots of stuff can go wrong" can be translated in most of the cases to "I had a merge conflict". But this is not git, this is git+pharo. > > The thing is that with Git, your code is dead in files. With Iceberg, your code is in the files but it also may be alive in your image too. So updating code for what you have existing instances, or announcement subscriptions or other could (and probably will) mess up with the running code... > So to the typical merge conflict, you may add breaking your running system. > > It just seems that for normal situations - it would be handy to run this straight in Pharo. > > Thoughts from the git experts? > > For these cases, you can do exactly as the command line from Iceberg's UI > > - change your branch to your "to-catchup" master > - fetch > - now you can go to the merge option, and choose to merge your remote branch into your checked-out branch. > - and push > > Of course, this simple workflow works most of the times, but you may find edge cases. > For those edge cases (typically updating iceberg itself, or trying to update pharo itself), in the checkout preview you will have the combo with the checkout strategy: choose the expert mode "do not load the code". This option will change the branch on git's world, but it will not load the code in your image. > > That is useful if you have living instances for example. > This option will though make a diff between the checked out version and your image code and show you differences. (think this as a git reset --soft) > > To me the fact that we are manipulating live code loaded in the image and not dead files makes a huge difference, and this makes that extrapolating git commands to iceberg is not so straight forward :). Also, understanding that git is stateful/context dependant, and applying an operation means changing your current state (modify your current branch, change your current branch) is useful to see the consequences. > > In any case, any more concrete suggestions for enhancing this workflow are welcome. I think that neither Esteban, Pablo, me nor other contributors are skilled UI designers, and thinking about the best way to present a usecase to a user is super super hard :). > > Guille, from his vacations >

Feb. 19, 2019

Re: [Pharo-users] Should epicea help me recover changes in a system crash?

by Tim Mackinnon

Ok - if its supposed to work in this situation, I will zip up that image and put it somewhere to try and figure out what happened. > On 18 Feb 2019, at 17:54, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi tim > > this is strange. Normally epicea logs all the changes. In the past I got missing classes. > Epicea is git ignorant. So I do not see how it could interact. > I would love to see your bug solved. Could you keep your image and may be martin > has some time to have a look (he got flying back to chile). > > Stef > >> On 18 Feb 2019, at 18:13, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve got mixed experiences with epicea - having had a few image seg faults recently its presented some of my changes and let me recover them. >> >> However just now, I had been working for an hour and my whole laptop went black (and then had the apple logo). I took the opportunity to apply the latest HighSierra updates (it has been a while) - but when I relaunched my image - epicea detected missing code however what it shows me is nothing like the changes I had recently made - it just showed me a merge change? >> >> Is it possible that if Iâm on the wrong branch - it wonât show me changes I made recently? >> >> I find Iâm kind of missing the old changes text file (which we say we are getting rid of) as at least it let me see an historic account of what I had done - as now things are a bit all of over the place (do-its you have to find in the playground history) and epicea is supposed to show the rest - execpt it doesnât appear to do so? >> >> Tim > > >

Feb. 19, 2019

Re: [Pharo-users] Pharo 7: Problems with the new file chooser UI

by Sven Van Caekenberghe

Are you really sure ? It works for me, Pharo 7.0.1 macOS. > On 18 Feb 2019, at 22:57, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using chooseExistingFileReference: title extensions: exts path: path). It returns a FileReference but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. > > For example if you run: > > [1]~~~~ > > (FileLocator documents / 'test.ston') ensureCreateFile writeStreamDo: [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. > > ~~~~ > > You will get a file on your Documents folder called test.ston, but If I choose that file using: > > [2]~~~~ > > file := UIManager default > chooseExistingFileReference:'Choose a file' > extensions: #('ston') > path: FileLocator documents. > > ~~~~ > > and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. > > Am I missing something? > > Thanks, > > Offray >

Feb. 18, 2019

Re: [Pharo-users] Running pharo in daemon mode

by Sven Van Caekenberghe

There are many options. Did you read https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… ? You can also study this https://github.com/svenvc/pharo-server-tools nohup is an easy to use, quick and dirty solution. > On 18 Feb 2019, at 22:39, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Hey, all.. > > I found my issue.. I need to be running in daemon mode.. i was running with &, but as soon as my connection lets go, the app dies.. > > I tried using daemon tools, but it looks like the site stays up for one second, and a new PID is generated.. > > Anyone have any hints on how people are doing this lately? > > Thanks! > > > > ---- > 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

Pharo 7: Problems with the new file chooser UI

by Offray Vladimir Luna CÃ¡rdenas

Hi, While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using |chooseExistingFileReference: title extensions: exts path: path|). It returns a |FileReference| but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. For example if you run: [1]~~~~ (FileLocator documents / 'test.ston') ensureCreateFileÂ writeStreamDo:Â [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. ~~~~ You will get a file on your Documents folder called test.ston, but If I choose that file using: [2]~~~~ file := UIManager default Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â chooseExistingFileReference:'Choose a file' Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â extensions: #('ston') Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â path: FileLocator documents. ~~~~ and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. Am I missing something? Thanks, Offray

Feb. 18, 2019

Running pharo in daemon mode

by sergio ruiz

Hey, all.. I found my issue.. I need to be running in daemon mode.. i was running with &, but as soon as my connection lets go, the app dies.. I tried using daemon tools, but it looks like the site stays up for one second, and a new PID is generated.. Anyone have any hints on how people are doing this lately? Thanks! ---- 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] Measuring memory usage

by Sven Van Caekenberghe

> On 18 Feb 2019, at 21:42, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Snap! i forgot about that! > > I really need to get that put behind a password Yes, and especially disable the dev tools as they contain doit functionality ! > On February 18, 2019 at 1:56:23 PM, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: > >> Do you know about Seaside's Status page/dev tool. >> >> It is there by default, it has many tabs that give you more information about the running image, including memory info, as well as a space tally (but that is very slow). > ---- > 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] Measuring memory usage

by sergio ruiz

Snap! i forgot about that! I really need to get that put behind a password On February 18, 2019 at 1:56:23 PM, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: Do you know about Seaside's Status page/dev tool. It is there by default, it has many tabs that give you more information about the running image, including memory info, as well as a space tally (but that is very slow). ---- 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] Calypso documentation? Or understanding menu building

by Denis Kudriashov

Hi Tim. Ð¿Ð½, 18 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 14:48, Tim Mackinnon <tim(a)testit.works>: > 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? > You simply need two annotations. One for context of RPackage and another for context of tag. > > 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] [PharoRemote] View remote Transcript

by Denis Kudriashov

Hi Serge. if it is related to TelePharo then you can register local transcript in remote image. Evaluate following code in playground: localTranscript := Transcript. remotePharo evaluate: [ Smalltalk globals at: #Transcript put: localTranscript ]. It will be not optimized solution because every message to transcript will send remote request to client. But it should work. Also all messages will go to main Transcript in you client image which is probably not desired. So the better solution requires real implementation of remote transcript. Ð¿Ð½, 18 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 15:33, sergio ruiz <sergio.rrd(a)gmail.com>: > Hi, all.. > > Is it possible to use PharoRemote to watch the remote siteâs Transcript? > > Thanks! > > ---- > 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