- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] First attempt at submitting a simple contribution

by Nicolai Hess

2014-07-22 17:48 GMT+02:00 Tim Mackinnon <tamackinnon(a)gmail.com>: > Hi guys - Iâve tried to submit a very simple contribution for Pharo. I > followed the steps in the video about submitting on Fogbugz - although I > wonder if I missed a step by not asking for commit rights to the > Pharo40Inbox? As I already had a smalltalk hub account - it asked for that > name and password and it didnât complain when I entered them and pressed > accept in Pharo. > I think Marcus changed the access rights. pharo inbox is now publicy writeable. > > The issue is: 13653 > > Its a very simple contribution, just a class with some wiki help and the > wiki method pragma to get it to appear in the System help. > > As I didnât know if there was already a class that might better hold this > text, I created a new one - but happy to move it onto something else if > there is somewhere obvious (or maybe its cleaner that it lives in its own > place?). > > Tim > Looks good. Some notes: I would change the title to "Pharo environment" or "Pharo Tools" or "First steps" or something like that. The shortcut list is not available in most browsers. Only in the default system browser. MessageBrowser, Finder, Monticello Browser ... don't have this. Topic "Searchlight": should be Spotlight There are some subtopics under "Workspace" that belong to the System browser. Changing the title and color of the system browser is an artefact of older (other) browsers. It doesn't work anymore. (the changes don't persist) A good collection of topics for newcomers. I like the descriptions of the icons and code pane color. As far as I know this was not documented elsewhere. nicolai

July 22, 2014

the basic image in the Zeroconf scripts

by Pavel Krivanek

Hi, the shrinked image [1] reached the state when it is able to eval code, accept configurations via command line [2] etc. I think it is time to more deeply join it with the Pharo release workflow to make it easier for people to use it in their projects and improve it. Would be nice to to test if the new updates are breaking it, upload new builds to the file server and provide Zeroconf script options to download it. First of all we need to find some fitting name. It is not the kernel image because it contains a lot of packages that can be removed. It is headless image with Metacello support. [1] https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-1… [2] for example ./pharo Pharo-4.0-Shrink.image config http://smalltalkhub.com/mc/Pharo/SystemConfigurations/main ConfigurationOfSUnit --group=Core,Tests --install=bleedingEdge Cheers, -- Pavel

July 22, 2014

First attempt at submitting a simple contribution

by Tim Mackinnon

Hi guys - Iâve tried to submit a very simple contribution for Pharo. I followed the steps in the video about submitting on Fogbugz - although I wonder if I missed a step by not asking for commit rights to the Pharo40Inbox? As I already had a smalltalk hub account - it asked for that name and password and it didnât complain when I entered them and pressed accept in Pharo. The issue is: 13653 Its a very simple contribution, just a class with some wiki help and the wiki method pragma to get it to appear in the System help. As I didnât know if there was already a class that might better hold this text, I created a new one - but happy to move it onto something else if there is somewhere obvious (or maybe its cleaner that it lives in its own place?). Tim

July 22, 2014

Re: [Pharo-dev] WhatsUp from: 2014-07-21 until: 2014-07-31

by Esteban A. Maringolo

2014-07-22 12:19 GMT-03:00 Paul DeBruicker <pdebruic(a)gmail.com>: > Did you know it was already part of the JQueryWidgetBox package? > http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox > at least up to Full calendar version 1.6 ish..... Yes I did. But I couldn't make it work. And I didn't want to build new software based on a deprecated (and old) version. But I'll look into that old version before I releasing the newer version. Regards, Esteban A. Maringolo

July 22, 2014

Re: [Pharo-dev] WhatsUp from: 2014-07-21 until: 2014-07-31

by Paul DeBruicker

Did you know it was already part of the JQueryWidgetBox package? http://smalltalkhub.com/#!/~Seaside/JQueryWidgetBox at least up to Full calendar version 1.6 ish..... Esteban A. Maringolo wrote > 2014-07-21 2:00 GMT-03:00 < > seaside@.inria > >: >> Hi! We're sending this automatic email twice a month, to give the >> community an opportunity to easily know what's happening and to >> coordinate efforts. Just answer informally, and feel free to spawn >> discussions thereafter! >> >> ### Here's what I've been up to since the last WhatsUp: >> >> - >> $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > > Successfully integrated FullCalendar > <http://arshaw.com/fullcalendar/> > within Pharo/Seaside application, with tons of JS callbacks. > >> ### What's next, until 2014-07-31 (*): >> >> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > Clean out code and release FullCalendar integration with Seaside as > open source. Eventually (aka "when I have time"). > > Lots of other "internal" refactorings in our ongoing Pharo based software. > > Esteban A. Maringolo -- View this message in context: http://forum.world.st/WhatsUp-from-2014-07-21-until-2014-07-31-tp4768945p47… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 22, 2014

Re: [Pharo-dev] RIP PackageInfo

by Tudor Girba

Yupeee! Thank you! Doru On Mon, Jul 21, 2014 at 3:53 PM, stepharo <stepharo(a)free.fr> wrote: > Finally! Let us savor this moment. > Yes it was a boring but important task. > We have some other trolls to kill :) > > Stef > > > On 21/7/14 15:32, Esteban Lorenzano wrote: > >> Today I finally managed to accomplish this task. >> It was just a couple of hours work now, but is the result of years of >> hard work cleaning the system and introducing RPackage. >> This âsmall and random changeâ was in my TODO list since I joined the >> Pharo team, two and a half years ago, and now I can finally mark it as >> accomplishedâ¦ >> So I can say this is an important milestone :) >> >> Esteban >> >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Sean P. DeNigris

Clara Allende wrote > Finally the metaLink-based breakpoints are "ready"... All sounds very exciting! Thank you!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/SmartBreakpoints-alpha-release-tp4769266p4769371.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 22, 2014

Re: [Pharo-dev] WhatsUp from: 2014-07-21 until: 2014-07-31

by Sean P. DeNigris

Esteban A. Maringolo wrote > Successfully integrated FullCalendar... within Pharo Cool :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/WhatsUp-from-2014-07-21-until-2014-07-31-tp4768945p47… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 22, 2014

Re: [Pharo-dev] RIP PackageInfo

by Sean P. DeNigris

Max Leske wrote > whoop whoop! +1 :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/RIP-PackageInfo-tp4769085p4769368.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Clara Allende

Fixed! Thanks for the feedback (and for spotting my bugs ^^) 2014-07-22 15:28 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > Wow :O > Ok, I will investigate it. > > > 2014-07-22 15:23 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > Yes, this works now. >> >> >> But I just found out, that a methods version list is empty after adding a >> break point. >> Just go to a method (for example FileList>>initialize). Show the version >> of this methdo. >> Add a break point. >> Now the version list is empty. >> >> >> >> 2014-07-22 14:53 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >> >> Ok, same that I did :) >>> >>> So I've spotted this one: I was using an old version of Spec-Debugger, >>> which uses a deprecated method. >>> Can you try again now? I've just commited the fix and updated the >>> configuration. >>> >>> Thanks again :D >>> >>> >>> 2014-07-22 14:40 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >>> >>> No real use case, I just read your blog entry, installed your package >>>> and choosed a random method and add a breakpoint :) >>>> >>>> >>>> >>>> >>>> >>>> >>>> 2014-07-22 14:32 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >>>> >>>> I have downloaded a new fresh image (40114) and I get a deprecation >>>>> warning. So I will check it out, but could you tell me your use case as >>>>> well (maybe send me an email so we don't spam the list)? >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >>>>> >>>>> Weird, I tried loading it in 40111 and it was working. >>>>>> Was it a fresh image? >>>>>> >>>>>> >>>>>> 2014-07-22 14:16 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >>>>>> >>>>>> The current version from >>>>>>> Gofer it >>>>>>> smalltalkhubUser: 'ClaraAllende' project: 'SmartBreakpoints'; >>>>>>> configurationOf: 'SmartBreakpoints'; >>>>>>> loadStable . >>>>>>> >>>>>>> raises some deprecation warnings and missing classOrMetaClass >>>>>>> selector with pharo 40111 >>>>>>> can you put a link on your blog for a working pharo 4.0 image? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2014-07-22 14:05 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >>>>>>> >>>>>>> >>>>>>>> On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 22/7/14 10:41, Clara Allende wrote: >>>>>>>> >>>>>>>> Hi guys! >>>>>>>> Finally the metaLink-based breakpoints are "ready". I have made >>>>>>>> some explanations on my blog >>>>>>>> <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, >>>>>>>> but basically now you have the option "break here" in SmartSuggestions menu. >>>>>>>> So it's still experimental, and even though I have some tests, it >>>>>>>> would be nice if you can test it, because I can't cover all possible use >>>>>>>> cases :) >>>>>>>> And any feedback is most appreciated! >>>>>>>> >>>>>>>> Specially, since eventually we will have several kinds of >>>>>>>> breakpoints, I would like to ask in which way would you like to choose them >>>>>>>> (a pop menu? a sublist?) >>>>>>>> >>>>>>>> Thanks in advance! >>>>>>>> >>>>>>>> PS: The script for downloading the code is in the blog post :P >>>>>>>> PS2: After talking with Anne and Baptiste, things that are not >>>>>>>> there *yet* but I want to have: >>>>>>>> * a highlight on the method/messageSend where the breakpoint is >>>>>>>> inserted >>>>>>>> * expose persistent breakpoints (it is there but the default is to >>>>>>>> halt once) >>>>>>>> * line breakpoints (not sure when, for now the breakpoints are AST >>>>>>>> based) >>>>>>>> * integration with TextEditor, once it is done ;) >>>>>>>> >>>>>>>> >>>>>>>> Can you grab igor and sit with him to get this point? >>>>>>>> >>>>>>>> Another idea would be to use the editor in Moose (Rubrik?). >>>>>>>> Better a solution now than to wait forever for perfectionâ¦ >>>>>>>> >>>>>>>> Marcus >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

July 22, 2014