- Pharo-dev - lists.pharo.org

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

by phil＠highoctane.be

I've uploaded the video on my channel as well. https://www.youtube.com/watch?v=iFomI-7h4qQ â Phil

Aug. 8, 2014

Does image build process check for halts?

by Tim Mackinnon

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?). But this got me thinking - doesnât the CI process check for this and just fail the build? 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 Tim Mackinnon

Ok - Iâve fixed my faux-pas and propose the following text (a slight rework of what is published now). Taking a hint from Martin there is a notehub link here (http://notehub.org/2014/8/8/how-to-propose-a-bug-fix-or-enhancement) - although Iâve noticed notehub handles sub-bullets a bit strangely. We might also want to do another slight change if we agree that Fogbugz should be secondary content (if so - adjust the first paragraph to something like: Check if your change has already been entered into Fogbugz, and consider watching the overview video of the steps documented below.) #How to propose a bug fix or enhancement First check you meet the submission requirements and are familiar with the more detailed [contribution steps](https://pharo.fogbugz.com/default.asp?W68) (watch the [tutorial video](https://pharo.fogbugz.com/default.asp?pg=pgDownload&pgType=pgWikiAtt…, it's great!) ##Prerequisites In order to propose a bug fix or enhancement for Pharo you need: - An account for the [Fogbugz Pharo Issue Tracker]( https://pharo.fogbugz.com) - An account on [SmalltalkHub](http://smalltalkhub.com) with rights to the [Pharo Inbox]( http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) _Note, in the recent version of SmalltalkHub this is a public repository. If you encounter problems you can ask for commit rights on the [Pharo Developers mailinglist(http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.o… ##Procedure To commit a change, you will follow these steps: - Take the latest [stable or development system](http://pharo.org/download), ideally using the latest virtual machine for your OS - Ensure you have created [details of the issue in the Fogbugz issue tracker] (https://pharo.fogbugz.com) - Create a code fix (ideally with a [unit test](http://pharo.gforge.inria.fr/PBE1/PBE1ch8.html) exercising the working code) - Create a Monticello Slice (group of packages) for your changes: - Open the Monticello Browser - Open the Slice Maker by clicking the "Slice" button - In Slice Maker enter the Fogbugz issue number and "grab" the issue summary - Select all dirty packages affected by your fix - Verify your changes (click the Changes button) - Select the Pharo40 repository - Select your Slice - Press changes in the Monticello Browser and verify that your changes are correct - Publish the Slice to the inbox: - Select the whole Slice (not it's individual packages). - Select the SmalltalkHub Pharo Inbox repository. - Commit the Slice. - Verify that your fix loads: - Take a fresh image and load the Slice you just published - Update the bug entry to mention that you submitted a Slice in the inbox - Now sit back and feel good! You've helped influence a brighter future... You can also contribute to Pharo by proposing enhancements on the mailing list and/or by submitting a Fogbugz issue. Note that all code submitted to the [Pharo repositories](http://smalltalkhub.com/#!/~Pharo) is licensed under the [MIT license]http://opensource.org/licenses/MIT) Do not forget to sign the [license agreement](http://files.pharo.org/media/PharoSoftwareDistributionAgreement.…. On 8 Aug 2014, at 07:16, Tim Mackinnon <tim(a)testit.works> wrote: > Stef - I've confused you with my suggestion. Where I wrote "use link" after the text in [] - I meant put that hyperlink for the [text]. > > Sorry, I was writing my reply in a text editor and was doing a sort of pseudo markdown syntax. > > Looking at where this is going - maybe we should instead make the Pharo.org site the main source of info and not Fogbugz? We have a duplication problem - and when things change we end up with conflicting instructions as we forget to update the other copies. Essentially we need to refactor the docs. > > Is Pharo.org easily editable by others (is this the Pillar bit?). If it was then I would say let's edit the Fogbugz pages - simplify them and point them back to the more detailed Pharo.org pages. > > For now, I will find a laptop and send some cleaned up text. > > Tim > > Sent from my iPhone > > On 7 Aug 2014, at 10:45 pm, "stepharo [via Smalltalk]" <[hidden email]> wrote: > >> in fact I just did a merge with the version of Tim and it is looking great. >> On 7/8/14 22:32, stepharo wrote: >> >> > Thanks martin I will have a look tomorrow. >> > >> > Stef >> > >> > On 7/8/14 22:11, MartinW wrote: >> >> Could you extend http://pharo.org/contribute-propose-fix a bit? And >> >> add a >> >> screenshot of Slice Maker (I attach one). The following text would have >> >> helped me (I paste the markdown. I also posted it on NoteHub for a >> >> better >> >> reading experience >> >> http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix) >> >> >> >> #How to propose a bug fix: >> >> ##Prerequesites: >> >> In order to propose a bug fix or enhancement for Pharo you need: >> >> >> >> - an account at the [Pharo Issue Tracker on >> >> Fogbugz](https://pharo.fogbugz.com), >> >> - a [SmalltalkHub](http://smalltalkhub.com) account and >> >> - the commit right for the [Pharo Inbox on >> >> SmalltalkHub](http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) (Ask on >> >> the >> >> [Pharo Developers >> >> mailinglist](http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.… >> >> >> >> for the commit right). >> >> >> >> ##Procedure: >> >> - Take the latest stable or latest development system, ideally using the >> >> latest virtual machine. >> >> - Do a fix for a given bug, or a new bug you entered to the issue >> >> tracker. >> >> - Create a slice (group of packages): >> >> - Open the Monticello Browser. >> >> - Open the Slice Maker by clicking the **+Slice** button. >> >> - In Slice Maker enter the Fogbugz issue number and **grab** the >> >> issue >> >> summary. >> >> - Select all dirty packages affected by your bug fix. >> >> - Publish the slice to the inbox: >> >> - Select the whole slice (not it's individual packages). >> >> - Select the SmalltalkHub Pharo Inbox repository. >> >> - Commit your slice. >> >> - Verify that your fix loads: take a fresh image and load the slice you >> >> published. >> >> - Update the bug entry to mention that you submitted a slice in the >> >> inbox. >> >> >> >> You can also contribute to Pharo by proposing enhancements following the >> >> same process. Note that all code submitted to the Pharo repositories is >> >> licensed under the MIT license. Do not forget to sign the license >> >> agreement. >> >> >> >> <http://forum.world.st/file/n4772388/SliceMaker.png> >> >> >> >> >> >> >> >> -- >> >> View this message in context: >> >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… >> >> Sent from the Pharo Smalltalk Developers mailing list archive at >> >> Nabble.com. >> >> >> >> >> > >> > >> > >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… >> To unsubscribe from About your contributions: Improve Pharo right now, right there., click here. >> NAML > > View this message in context: Re: About your contributions: Improve Pharo right now, right there. > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

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

by Johan Brichau

Hi Doru, Have you tried using GT with the Pharo dark team? Does it work? Last time I tried using them together, it did not look very well ;-) It's not really important. Just a question... cheers Johan On 06 Aug 2014, at 07:09, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You can install GToolkit in a Pharo 3.0 image like this: > http://www.humane-assessment.com/blog/installing-gtoolkit > > Doru > > > On Wed, Aug 6, 2014 at 5:30 AM, Pablo R. Digonzelli <pdigonzelli(a)gmail.com> wrote: > Great!. How can i install GtInspector in a pharo image? > > TIA > > > Ing. Pablo Digonzelli > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > Email: pdigonzelli(a)softsargentina.com > pdigonzelli(a)gmail.com > Cel: 5493815982714 > > De: "Tudor Girba" <tudor(a)tudorgirba.com> > Para: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > Enviados: Martes, 5 de Agosto 2014 11:06:21 > Asunto: [Pharo-dev] [GTInspector] Showing object state using a tree > > > Hi, > > The GTInspector now shows the state of an object in a tree view (screenshots below). > > This tree view focuses on the internal structure of an object. > For example, when looking at a dictionary object you will see the "array" and the "tally" > attributes and not the key value pairs. Those can be accessed from another presentation > of a dictionary object. > > So the tree is meant to be used together with the finder and the other presentations of on object. > > Let us know what you think. > > Cheers, > Andrei & Doru > > > <GTInspector_Tree_View2.png> > > <GTInspector_Tree_View1.png> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 8, 2014

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

by Tim Mackinnon

Iâd never heard of notehub before - looks handy. I was initially worried we had yet another copy of documentation to worry about, but I think Iâve understood your intent was to make it easier for Stef to nab your changes. Iâll make a mental note to try it to. Tim On 7 Aug 2014, at 21:11, MartinW [via Smalltalk] <ml-node+s1294792n4772388h8(a)n4.nabble.com> wrote: > Could you extend http://pharo.org/contribute-propose-fix a bit? And add a screenshot of Slice Maker (I attach one). The following text would have helped me (I paste the markdown. I also posted it on NoteHub for a better reading experience http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix) > > #How to propose a bug fix: > ##Prerequesites: > In order to propose a bug fix or enhancement for Pharo you need: > > - an account at the [Pharo Issue Tracker on Fogbugz](https://pharo.fogbugz.com), > - a [SmalltalkHub](http://smalltalkhub.com) account and > - the commit right for the [Pharo Inbox on SmalltalkHub](http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) (Ask on the [Pharo Developers mailinglist](http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.… for the commit right). > > ##Procedure: > - Take the latest stable or latest development system, ideally using the latest virtual machine. > - Do a fix for a given bug, or a new bug you entered to the issue tracker. > - Create a slice (group of packages): > - Open the Monticello Browser. > - Open the Slice Maker by clicking the **+Slice** button. > - In Slice Maker enter the Fogbugz issue number and **grab** the issue summary. > - Select all dirty packages affected by your bug fix. > - Publish the slice to the inbox: > - Select the whole slice (not it's individual packages). > - Select the SmalltalkHub Pharo Inbox repository. > - Commit your slice. > - Verify that your fix loads: take a fresh image and load the slice you published. > - Update the bug entry to mention that you submitted a slice in the inbox. > > You can also contribute to Pharo by proposing enhancements following the same process. Note that all code submitted to the Pharo repositories is licensed under the MIT license. Do not forget to sign the license agreement. > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… > To unsubscribe from About your contributions: Improve Pharo right now, right there., click here. > NAML -- View this message in context: http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

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

by Dale Henrichs

agreed On Thu, Aug 7, 2014 at 11:17 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Dale Henrichs-3 wrote > > After a bit more thought, I believe that it should be okay to make copies > > That sounds right. For instance, the MetaRepoForPharo123 repos would be > configs certified to work in Pharo 123 that have been copied from the > canonical repo. Of course what it feels like we really want is a catalog a > la SqueakMap, but copying configs works for now. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Metacello-Projects-one-canonical-config-repo-for-all-… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Aug. 8, 2014

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

by Sean P. DeNigris

Dale Henrichs-3 wrote > After a bit more thought, I believe that it should be okay to make copies That sounds right. For instance, the MetaRepoForPharo123 repos would be configs certified to work in Pharo 123 that have been copied from the canonical repo. Of course what it feels like we really want is a catalog a la SqueakMap, but copying configs works for now. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Projects-one-canonical-config-repo-for-all-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

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

by Tim Mackinnon

Stef - I've confused you with my suggestion. Where I wrote "use link" after the text in [] - I meant put that hyperlink for the [text]. Sorry, I was writing my reply in a text editor and was doing a sort of pseudo markdown syntax. Looking at where this is going - maybe we should instead make the Pharo.org site the main source of info and not Fogbugz? We have a duplication problem - and when things change we end up with conflicting instructions as we forget to update the other copies. Essentially we need to refactor the docs. Is Pharo.org easily editable by others (is this the Pillar bit?). If it was then I would say let's edit the Fogbugz pages - simplify them and point them back to the more detailed Pharo.org pages. For now, I will find a laptop and send some cleaned up text. Tim Sent from my iPhone > On 7 Aug 2014, at 10:45 pm, "stepharo [via Smalltalk]" <ml-node+s1294792n4772394h94(a)n4.nabble.com> wrote: > > in fact I just did a merge with the version of Tim and it is looking great. > On 7/8/14 22:32, stepharo wrote: > > > Thanks martin I will have a look tomorrow. > > > > Stef > > > > On 7/8/14 22:11, MartinW wrote: > >> Could you extend http://pharo.org/contribute-propose-fix a bit? And > >> add a > >> screenshot of Slice Maker (I attach one). The following text would have > >> helped me (I paste the markdown. I also posted it on NoteHub for a > >> better > >> reading experience > >> http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix) > >> > >> #How to propose a bug fix: > >> ##Prerequesites: > >> In order to propose a bug fix or enhancement for Pharo you need: > >> > >> - an account at the [Pharo Issue Tracker on > >> Fogbugz](https://pharo.fogbugz.com), > >> - a [SmalltalkHub](http://smalltalkhub.com) account and > >> - the commit right for the [Pharo Inbox on > >> SmalltalkHub](http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) (Ask on > >> the > >> [Pharo Developers > >> mailinglist](http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.… > >> > >> for the commit right). > >> > >> ##Procedure: > >> - Take the latest stable or latest development system, ideally using the > >> latest virtual machine. > >> - Do a fix for a given bug, or a new bug you entered to the issue > >> tracker. > >> - Create a slice (group of packages): > >> - Open the Monticello Browser. > >> - Open the Slice Maker by clicking the **+Slice** button. > >> - In Slice Maker enter the Fogbugz issue number and **grab** the > >> issue > >> summary. > >> - Select all dirty packages affected by your bug fix. > >> - Publish the slice to the inbox: > >> - Select the whole slice (not it's individual packages). > >> - Select the SmalltalkHub Pharo Inbox repository. > >> - Commit your slice. > >> - Verify that your fix loads: take a fresh image and load the slice you > >> published. > >> - Update the bug entry to mention that you submitted a slice in the > >> inbox. > >> > >> You can also contribute to Pharo by proposing enhancements following the > >> same process. Note that all code submitted to the Pharo repositories is > >> licensed under the MIT license. Do not forget to sign the license > >> agreement. > >> > >> <http://forum.world.st/file/n4772388/SliceMaker.png> > >> > >> > >> > >> -- > >> View this message in context: > >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… > >> Sent from the Pharo Smalltalk Developers mailing list archive at > >> Nabble.com. > >> > >> > > > > > > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… > To unsubscribe from About your contributions: Improve Pharo right now, right there., click here. > NAML -- View this message in context: http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

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

by Tim Mackinnon

Yes it's a good video - it helped me a lot. There is one small correction I've meant to add below it - the step for getting write access to the inbox isn't currently needed (but I guess closer to a release that might change). Tim Sent from my iPhone > On 7 Aug 2014, at 10:13 pm, "stepharo [via Smalltalk]" <ml-node+s1294792n4772389h39(a)n4.nabble.com> wrote: > > I'm happy that the video made by camillo is still served by the fogbugs > web site because it explains really well the process. > > Stef > > On 7/8/14 21:48, Benjamin Pollack wrote: > > > On Aug 7, 2014, at 9:47 AM, stepharo <[hidden email]> wrote: > > > >>> 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? > > Yep, it helps. The issue isnât that it was complex; itâs that it was undocumented. The new links are helpful. > > Excellent! > You will that getting your first fixes in the system is a great and cool > feeling. > > > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… > To unsubscribe from About your contributions: Improve Pharo right now, right there., click here. > NAML -- View this message in context: http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

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

by Dale Henrichs

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. 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