August 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Tim Mackinnon

I can see how that makes sense for now - we will continue to make suggestions and then over time maybe we can help curate it it becomes too much. Although I am worried that this can create a lot of work - both to report and fix? In the meantime how do you prefer we submit changes, in Markdown format (does that help?) - or is RTF better? OR - is there any way we can commit proposed changes - which you can review and publish (e.g. could we use a Git Repo?). I'm not familiar with the underlying technology of Pharo.org - but could we modify it so there is a discussion page like on Wikipedia where changes can be proposed and applied by you? This sounds like a great BOF topic at ESUG - and maybe we should follow up on that? At the moment I can see numerous tiny fixes (grammatical and formatting - that are more time consuming to report than just fix). For now, can you apply the newer fixes I proposed (to undo Stef's misunderstanding for my "use link" suggestion). I also think on the http://pharo.org/download page we should mention the PharoLauncher project (http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher) - its really handy for managing multiple images (and getting the latest image). tim On Fri, 8 Aug 2014, at 01:14 PM, Esteban Lorenzano wrote: > Hi, > > We love to have contributions, but for the moment being (to try to keep the design, etc. and prevent too much disorderâ¦ which was a problem in the previous site). > I would prefer you to send me your contributions (or post it here), and I will upload them to the site. > > cheers, > Esteban > > On 08 Aug 2014, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > >> >> Yes - it would be better to link to the YouTube version in the text. >> >> So how is the Pharo.org site generated? Is this what Pillar is? (Is it a pier wiki?) and could we easily help with editing a subsection of it to help out? >> >> Tim >> >> Sent from my iPhone >> >> On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> I've uploaded the video on my channel as well. >>> >>> https://www.youtube.com/watch?v=iFomI-7h4qQ >>> >>> Phil > >

Aug. 8, 2014

Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

by Alexandre Bergel

Your version had been merged. But your .mcz was not in the repo. Now it is. Sorry about that. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Aug 7, 2014, at 9:31 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Hi Alexandre, > > The patch doesnât seems to be commited in Roassal2 repoâ¦ > > Vincent > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Alexandre Bergel > EnvoyÃ© : mercredi 6 aoÃ»t 2014 21:44 > Ã : Moose-related development > Cc : Pharo Development List > Objet : Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal > > Thanks Vincent! > It seems to work well. > > Included in Roassal! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > On Aug 6, 2014, at 12:29 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > > Solved ! > > You will found the changes in the attached .mcz. > > I added some sessions guards where some Athens external objects are used. Stef you were right ;) > Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path that relies on Athens external objects. > > It seems to works for me. If it is the case for you, it we be nice to integrate it quickly to be able to work fine :) > > Thanks > > Vincent > > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de stepharo > EnvoyÃ© : jeudi 31 juillet 2014 22:58 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal > > Alexandre > > may be you should try to understand what is a session. > Because this is about 2 lines of code. > > When you open an image you save 2 min ago or 2 years ago, how the system knows that an OS ressources is valid? > By checking the session id... > > Stef > > On 31/7/14 16:09, Alexandre Bergel wrote: > > Yes, and this is a mess. > I've spent quite some time in getting the session working with Roassal2 and it still does not work. I would appreciate help on this. > > Alexandre > > > On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > It looks like Trachel does not recreate athens external resources. > There is an example in AthensSceneView, on how to check and reload an > AthensSurface. > > > 2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti(a)gmail.com>: > > > > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Yes it is. But I will not do > > TRMorph allInstances do: #delete > > In command line every day... > > > It is only intended to recover your lost work in the image not for everyday use :). > > > > > Vincent > > > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > de Usman Bhatti EnvoyÃ© : jeudi 31 juillet 2014 10:59 Ã : Pharo > Development List Cc : Moose-related development > > > Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error > with Roassal > > > > This may be related to this known issue reported a few days back. > > https://code.google.com/p/moose-technology/issues/detail?id=1084 > > > > And there is a possible solution to recover your image. > > > > usman > > > > On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > > > Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image. > > And I got that : > > <image001.png> > > It is *very* unpleasant... > > > > To reproduce the bug: > > 1 - You can do either: > > | builder | > > builder := GET2Line data: (0 to: 100) . > > builder > > y: [ :x | x*x ]. > > > > builder open. > > Or > > WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened. > > 2 - don't close the graph and save the pharo image. > > 3 - Close the pharo image > > 4 - Reopen it > > > > I am under W7 x64 with the latest moose image and the VM available on the pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july. > > You will find the crash dump attached. > > > > > > Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip) > > Thanks a lot Eliot ! :) > > > > And I got this: > > <image002.png> > > > > Thanks in advance > > > > Cheers, > > Vincent BLONDEAU > > > > > > > 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. > > > > > > 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. > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > 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. > <Trachel-VincentBlondeau.180.mcz>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > 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.

Aug. 8, 2014

Re: [Pharo-dev] Metacello Projects: one canonical config/repo for all platforms

by Dale Henrichs

On Fri, Aug 8, 2014 at 3:54 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 08 Aug 2014, at 06:16, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > > Ben and Sean, > > > > After a bit more thought, I believe that it should be okay to make > copies, but there does need to be a single primary repository where the > correct and latest configuration can be found. > > > > Putting copies of configurations into repositories to make project > discovery easier is a good use of copies. Copies are also useful when > creating mirror repos.... > > > > But one must be able to determine the location of the canonical > repository for the configuration. > > > > If the configuration were always co-located with the packages then it > would relatively easy to figure out where to find the newest and > 'correctest' configuration. > > > > The canonical location should ALWAYS be used in project references. > > But can't Metacello help there ? > > I mean, each configuration, no matter where it is copied/located is the > same and knows its canonical repository, right ? > So all that is needed is a kind of double-check, or following the > reference. > > BTW, doesn't Metacello not do some latest version checking already ? > > Sven, In a project reference, the developer specifies the repository from which the configuration should be loaded: spec project: 'Zinc Project' with: [ spec versionString: #'stable'; className: 'ConfigurationOfZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents' ]. In the above case, the canonical repository for Zinc is being used, but a developer can use a different repository like http://squeaksource.com/MetacelloRepository. Metacello's job is to do what the developer specifies. The developer may have perfectly good reasons for specifying a different location than the canonical repository: - critical bug fix to configuration, but no write access to canonical repo - private fork of project ... - etc. Metacello cannot second guess the developer when it comes to loading packages:) Sean is referring to the fact that some configurations are not present in the repository where the packages are located and they should be. Also there are cases where the generic *MetacelloRepository* is used in a project reference when the canonical location should be. Dale

Aug. 8, 2014

Re: [Pharo-dev] Does image build process check for halts?

by stepharo

On 8/8/14 09:50, Tim Mackinnon wrote: > Guys - I noticed that the pharo build 40152 - has a halt when you press ALT-Tab (I assume this was accidentally left in by someone?). probably me in my chase to understand widgets are used > > But this got me thinking - doesnât the CI process check for this and just fail the build? Normally we run a set of rules and one should be looking for halt and other debugging messages but I do not know if we are doing it or not. > Maybe legitimate halts should be tagged specially somehow so they pass through - but accidental ones get noted? > > Tim > >

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Esteban Lorenzano

Hi, We love to have contributions, but for the moment being (to try to keep the design, etc. and prevent too much disorderâ¦ which was a problem in the previous site). I would prefer you to send me your contributions (or post it here), and I will upload them to the site. cheers, Esteban On 08 Aug 2014, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - it would be better to link to the YouTube version in the text. > > So how is the Pharo.org site generated? Is this what Pillar is? (Is it a pier wiki?) and could we easily help with editing a subsection of it to help out? > > Tim > > Sent from my iPhone > > On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> I've uploaded the video on my channel as well. >> >> https://www.youtube.com/watch?v=iFomI-7h4qQ >> â >> Phil

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by phil＠highoctane.be

AFAIK it is a Marina based CMS. http://astares.blogspot.be/2014/04/marina.html Now, I knew how to get in the older system but no info on how to do this in the new one. Phil On Fri, Aug 8, 2014 at 12:11 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - it would be better to link to the YouTube version in the text. > > So how is the Pharo.org site generated? Is this what Pillar is? (Is it a > pier wiki?) and could we easily help with editing a subsection of it to > help out? > > Tim > > Sent from my iPhone > > On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> > wrote: > > I've uploaded the video on my channel as well. > > https://www.youtube.com/watch?v=iFomI-7h4qQ > â > Phil > >

Aug. 8, 2014

Re: [Pharo-dev] [GTInspector] Showing object state using a tree

by phil＠highoctane.be

It works. Now, following Johan point, the debugger is hard to read in a dark theme. See attached screenshot. Phil On Fri, Aug 8, 2014 at 11:55 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Use GTGenericStackDebugger instead of GTDebugger. (it was renamed some > time ago). > > > Cheers, > Andrei > > > On Fri, Aug 8, 2014 at 11:51 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> I have been trying to install the tools in Pharo 3 (Dark/Dawn Theme). >> >> GTInspector loads and works pretty ok at first sight. >> >> Gofer new >> url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; >> configuration; >> load. >> (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. "Works >> but with a warning" >> (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. >> "Ok" >> (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools. >> "Gives: KeyNotFound: key #GTDebugger not found in SystemDictionary" >> >> Indeed there is no GTDebugger class but a set of other things. >> >> What to use ? >> >> TIA >> >> >> âPhil >> > >

Aug. 8, 2014

Re: [Pharo-dev] Metacello Projects: one canonical config/repo for all platforms

by Sven Van Caekenberghe

On 08 Aug 2014, at 06:16, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Ben and Sean, > > After a bit more thought, I believe that it should be okay to make copies, but there does need to be a single primary repository where the correct and latest configuration can be found. > > Putting copies of configurations into repositories to make project discovery easier is a good use of copies. Copies are also useful when creating mirror repos.... > > But one must be able to determine the location of the canonical repository for the configuration. > > If the configuration were always co-located with the packages then it would relatively easy to figure out where to find the newest and 'correctest' configuration. > > The canonical location should ALWAYS be used in project references. But can't Metacello help there ? I mean, each configuration, no matter where it is copied/located is the same and knows its canonical repository, right ? So all that is needed is a kind of double-check, or following the reference. BTW, doesn't Metacello not do some latest version checking already ? > Dale > > > > On Thu, Aug 7, 2014 at 8:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > Dale Henrichs wrote: >> >> >> >> On Thu, Aug 7, 2014 at 9:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> There are two things that have bothered me about our use of Metacello, but I >> couldn't explain exactly why until now. These are two guidelines that I >> think are important: >> 1. ConfigurationOfMyProject should live at repoOfMyProject. Any >> MetaRepoForXyz should only be a copy of this config >> 2. Platform-specific config sections are not optional >> >> Makes a lot of sense and I agree. >> >> Dale > I feel similar. Not that I've published any Configurations yet, but looking in from the outside the current process always made me uneasy that is violates my general principle of DON'T MAKE COPIES. > > Maybe the MetaRepoForXyz should not contain any ConfigurationOfMyProject at all, but a CatalogOfMyProject (or MetaOfMyProject) which simply points to the ConfigurationOfMyProject in the project repo. > > cheers -ben >

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Tim Mackinnon

âYou know the guy doing the video remove it because it was in rage against us.â That is a real shame - particularly given that the conversation here has been quite constructive in how to improve the situation. Anyway - its a good video, and we can alway record another one if heâs dead against us using it. For now, weâll link to it and say thank you. Tim On 7 Aug 2014, at 14:47, stepharo <stepharo(a)free.fr> wrote: > >> Okay, so thatâs good, but you guys really need to improve the documentation on the mechanical walkthrough of how to actually claim and submit a bug fix. >> >> Today, I happened to have some spare time, so I figured, what the hell, why not see if I canât fix some bugs blocking the Pharo 4 release. Itâs a reach, granted, but I used to be good at Smalltalk, Iâm still a good programmer, and I figure at least one of the blockers is in the really-annoying-but-technically-easy bucket that no one was willing to touch yet, so chances are good. >> >> Armed with my old knowledge of how Squeak contrib used to work, I at least got as far as manually downloading a VM, manually downloading a .changes/.image, and manually downloading a .sources. Then I go to pharo.org andâ¦ >> >> Well, hmm. No instructions on the submission or development process? Well, no matter, I know you guys use FogBugz, so maybe on the FogBugz wiki? The landing page is unhelpful; clicking on the word âhereâ at âReporting or Fixing a Bug?â takes me to http://pharo.org/get-involved which is a 404. Heading back, I try âDocumentationâ, which contains a lot of documentation, but none how to submit fixes. > You know the guy doing the video remove it because it was in rage against us. > We were not aware that it was linked them. > >> Likewise, I can get great info on the workflow of a bug, but not on how to move code through that workflow. >> >> At this point, by luck, I realize that thereâs a link to âContributeâ in the TOC in FogBugz. Brilliant, exactly what I want! And it has a video walkthrough, no less, which takes me to http://vimeo.com/75183993 andâ¦nope, thatâs a 404 again. Thankfully, the link below it appears to let me download a nice MP4, which does walk me throughâ¦submitting a slice. I actually have no idea if this is the right way to do things anymore, but given that you guys seem to have a super-active GitHub repo, I kind of doubt it. And while thereâs some documentation scattered around about how to use Git and Pharo, itâs not centralized or obvious. >> >> Itâs up to the community to be involved with the tools they love and to submit patches, and youâre totally right to remind everyone that itâs up to us to improve Pharo if we want to keep it alive, but itâs up to the core team to make sure that itâs easy for us to do so, and I think that Pharoâs not doing terribly well on that front right now. >> > We add a description on the old web site but he got lost. > Now in a nutshell, to submit a fix > > - donwload latest image (there is a script on download) > - do a fix for a giving bug > - publish a slice press (+ slice) in MC, add the dirty packages > - publish it in the inbox (click on inbox and press save) > - take a fresh image. > - reload it and check that it fixes the problem (open MC and click on inbox + open). > > Does it help? > Was it so complex? > >> âBenjamin >

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Tim Mackinnon

Yes - it would be better to link to the YouTube version in the text. So how is the Pharo.org site generated? Is this what Pillar is? (Is it a pier wiki?) and could we easily help with editing a subsection of it to help out? Tim Sent from my iPhone > On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > > I've uploaded the video on my channel as well. > > https://www.youtube.com/watch?v=iFomI-7h4qQ > â > Phil

Aug. 8, 2014