- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

Documentation for Ephestos is now located here ---> https://www.gitbook.io/book/kilon/ephestos documentation will be kept updated with latest features from now on. I was succesfull in implementing python errors. Now Blender Python errors trigger the Pharo debugger that will allow you to fix the faulty code and resume as you do with regular Pharo code. I am also looking into Phratch to create a visual language for Ephestos. On Tue, Jul 22, 2014 at 2:35 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Yeah !!! I did it !!! :D > > Apparently I was doing it wrong , by returning the message in > doesNotUnderstand , this is why the next MNU was returned by Object instead > of my parser class. > > Say bye bye to ugly nil syntax , Ephestos now supports normal pharo > messaging. > > This ugly thing > > EphParser bpy:nil data:nil objects:'[ "Cube" ]' location: > '=(0.0,0.0,0.0)' . > > has turned to this > > EphCParser bpy ; data ; objects:'["Cube"]' location:'=(0.0,0.0,0.0)' ; e. > > or this > > EphCParser bpy data objects:'["Cube"]' location:'=(0.0,0.0,0.0)'; e. > > or you can use parentheses . You can send all keywords as single message > as I do in the example or separate them with parentheses to different > messages , it does not matter because the parser unites them into a single > string anyway. Message e, formulates the python string and marks the end of > pharo command. > > Means that now I offer full python support with no weird pharo syntax :) > New parser is called EphCParser if you want to give it a try, I am still > working on it to make sure it works well in all scenarios. > > this is an example of using python globals for making the code shorter > > EphCParser x:'=1.0' ; e. > EphCParser cube:'=bpy.data.objects["Cube"]';e. > EphCParser cube ; location:'=(x,0.0,0.0)' ; e. > > You may wonder , "why not use pharo variables instead ?" . Well you can do > that too ;) > > cube := EphCParser bpy data objects:'["Cube"]'. > cube location:'=(x,0.0,0.0)' ; e. > > I will try to test the new parser a bit more and I will work on 1) > receiving data from Blender 2) python errors triggering the pharo debugger > and 3) buffer together multiple lines of python code for complex stuff > like class and function definition etc 4) support BGE . > > > On Sun, Jul 20, 2014 at 10:06 PM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> On Sun, Jul 20, 2014 at 7:34 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> > With the help of Damien I was successful in creating a parser for pharo >> to >> > python syntax. Using pharo messages you can now construct automagically >> > python strings and pass it to blender . This way you no longer need to >> type >> > in python syntax to do python stuff. So a big thanks to Damien. Note >> this >> > method of course is slower because of parsing and heavy usage of regex >> > string matching. >> >> >> are you sure you need to pass 'nil' everywhere? In >> #doesNotUnderstand:, you could check for the number of arguments and >> generate something appropriate based on that. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >

Aug. 14, 2014

[pharo-project/pharo-core] d077cb: 40168

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d077cb74420d3720e112e223835d58324bb3e3df https://github.com/pharo-project/pharo-core/commit/d077cb74420d3720e112e223… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-14 (Thu, 14 Aug 2014) Changed paths: R NECompletion.package/NECContext.class/instance/private-roel-typer/findCommonSuperclass_.st R NECompletion.package/NECContext.class/instance/private-roel-typer/guessWithRoelTyper_class_.st M NECompletion.package/NECContext.class/instance/private/guessInstVarClass_.st M NECompletion.package/NECMenuMorph.class/instance/drawing/drawLine_on_rectangle_.st M NECompletion.package/NECPreferences.class/definition.st R NECompletion.package/NECReadMe.class/README.md R NECompletion.package/NECReadMe.class/definition.st M NECompletion.package/NECSymbols.class/README.md M NECompletion.package/NECSymbols.class/definition.st R NECompletion.package/NECTestClass.class/class/as yet unclassified/initialize.st A NECompletion.package/NECTestClass.class/class/initialization/initialize.st R NECompletion.package/NECTestSuperClass.class/class/as yet unclassified/initialize.st A NECompletion.package/NECTestSuperClass.class/class/initialization/initialize.st R NECompletion.package/NECUnseparatedModel.class/README.md R NECompletion.package/NECUnseparatedModel.class/definition.st R NECompletion.package/NECUnseparatedModel.class/instance/action/completionAt_.st R NECompletion.package/extension/Workspace/instance/guessTypeForNameFromOCompletion_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private/selectPackageFor_.st R RecentSubmissions.package/MessageList.class/README.md R RecentSubmissions.package/MessageList.class/definition.st R RecentSubmissions.package/MessageList.class/instance/accessing/lastEntry.st R RecentSubmissions.package/MessageList.class/instance/accessing/methodReferenceList.st R RecentSubmissions.package/MessageList.class/instance/accessing/methodReferenceList_.st R RecentSubmissions.package/MessageList.class/instance/actions/addMethodReferenceSilently_.st R RecentSubmissions.package/MessageList.class/instance/actions/addMethodReference_.st R RecentSubmissions.package/MessageList.class/instance/actions/clearAll.st R RecentSubmissions.package/MessageList.class/instance/actions/removeMethodReference_.st R RecentSubmissions.package/MessageList.class/instance/actions/revertLastMethodSubmission.st R RecentSubmissions.package/MessageList.class/instance/initialization/initialize.st R RecentSubmissions.package/MessageList.class/instance/userinterface/open.st R RecentSubmissions.package/MessageList.class/instance/userinterface/updateView.st M RecentSubmissions.package/RecentMessageList.class/README.md M RecentSubmissions.package/RecentMessageList.class/class/instance creation/resetUniqueInstance.st R RecentSubmissions.package/RecentMessageList.class/class/setting/recentMessageListMenuOn_.st A RecentSubmissions.package/RecentMessageList.class/class/tool registration/recentMessageListMenuOn_.st M RecentSubmissions.package/RecentMessageList.class/definition.st A RecentSubmissions.package/RecentMessageList.class/instance/accessing/lastEntry.st M RecentSubmissions.package/RecentMessageList.class/instance/accessing/maxListSize.st M RecentSubmissions.package/RecentMessageList.class/instance/accessing/maxListSize_.st A RecentSubmissions.package/RecentMessageList.class/instance/accessing/methodReferenceList.st A RecentSubmissions.package/RecentMessageList.class/instance/accessing/methodReferenceList_.st A RecentSubmissions.package/RecentMessageList.class/instance/actions/addMethodReferenceSilently_.st A RecentSubmissions.package/RecentMessageList.class/instance/actions/clearAll.st A RecentSubmissions.package/RecentMessageList.class/instance/actions/removeMethodReference_.st A RecentSubmissions.package/RecentMessageList.class/instance/actions/revertLastMethodSubmission.st M RecentSubmissions.package/RecentMessageList.class/instance/event handler/aClassHasBeenCommented_.st M RecentSubmissions.package/RecentMessageList.class/instance/initialization/initialize.st M RecentSubmissions.package/RecentMessageList.class/instance/initialization/registerToAnnouncements.st A RecentSubmissions.package/RecentMessageList.class/instance/private/createAClassReference_.st A RecentSubmissions.package/RecentMessageList.class/instance/private/createTheMethodReference_.st M RecentSubmissions.package/RecentMessageList.class/instance/private/removeAMethod_.st R RecentSubmissions.package/RecentMessageList.class/instance/ring creation/createAClassReference_.st R RecentSubmissions.package/RecentMessageList.class/instance/ring creation/createTheMethodReference_.st A RecentSubmissions.package/RecentMessageList.class/instance/userinterface/open.st A RecentSubmissions.package/RecentMessageList.class/instance/userinterface/updateView.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script168.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40168.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Changes.package/ChangeSet.class/class/cleanup/cleanUp_.st R System-Changes.package/ChangeSet.class/class/current changeset/noChanges.st R System-Changes.package/ChangeSet.class/class/enumerating/existingOrNewChangeSetNamed_.st M System-Changes.package/ChangeSet.class/class/enumerating/gatherChangeSets.st R System-Changes.package/ChangeSet.class/class/enumerating/removeEmptyUnnamedChangeSets.st M System-Changes.package/ChangeSet.class/class/filein%2Fout/fileOutChangeSetsNamed_.st M System-Changes.package/ChangeSet.class/class/instance creation/new.st M System-Changes.package/ChangeSet.class/class/scanning/scanFile_category_class_meta_stamp_.st M System-Changes.package/ChangeSet.class/class/scanning/scanFile_from_to_.st M System-Changes.package/ChangeSet.class/class/services/newChangeSet.st M System-Changes.package/ChangeSet.class/class/services/newChangesFromStream_named_.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/checkForUnclassifiedMethods.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/checkForUncommentedMethods.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/checkForUnsentMessages.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOutChangesFor_on_.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOutPSFor_on_.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOutPostscriptOn_.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOutPreambleOn_.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/lookForSlips.st M System-Changes.package/ChangeSet.class/instance/method changes/hasAnyChangeForSelector_.st M System-Changes.package/ChangeSet.class/instance/printing/printOn_.st M System-Changes.package/ChangeSet.class/instance/private/fileOutClassDefinition_on_.st M System-Changes.package/ClassChangeRecord.class/instance/definition/checkCoherence.st M System-Changes.package/ClassChangeRecord.class/instance/removal/forgetChangesIn_.st M System-Changes.package/extension/PositionableStream/instance/backChunk.st M System-Changes.package/extension/PositionableStream/instance/basicNextChunk.st M System-Changes.package/extension/PositionableStream/instance/copyPreamble_from_at_.st M System-Changes.package/extension/PositionableStream/instance/nextChunk.st Log Message: ----------- 40168 13825 MNU: receiver of protocolsFor: is nil https://pharo.fogbugz.com/f/cases/13825 13835 Small cleanup in System-Changes https://pharo.fogbugz.com/f/cases/13835 13836 Clean up RecentSubmissions more https://pharo.fogbugz.com/f/cases/13836 13834 Small Completion Cleanup https://pharo.fogbugz.com/f/cases/13834 http://files.pharo.org/image/40/40168.zip

Aug. 14, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40168 Home: https://github.com/pharo-project/pharo-core

Aug. 14, 2014

Re: [Pharo-dev] Pharo 3 backports

by Esteban Lorenzano

no, fixes in 3.0 goes in Pharo30Inbox. the one that is bad is the validatorâ¦ but AFAIK, it even shouldnât be running :P I will take a look tomorrow at your changes. Esteban On 13 Aug 2014, at 19:08, Ben Coman <btc(a)openinworld.com> wrote: > Where should we be putting slices for Pharo 3 backports. I am proposing my fix for "Extended Search... Implementors fooled by block variables" be backport for Pharo 3. I took a guess that Pharo30Inbox would be the place to put the slice, but the the report [1] from the monkey reports: > > Jenkins Job jenkins-Pharo-3.0-Issue-Validator-27054 > Could not Find Change: > http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main > > > So should Pharo 3 backports be put in Pharo40Inbox? (probably easiest short term workaround?) > Or does something with the monkey need to be changed? (maybe longer term goal?) > > cheers -ben > > [1] https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/27054//artifact/val… >

Aug. 13, 2014

Re: [Pharo-dev] Faster ThreadSafeTranscript Re: [pharo-project/pharo-core] 06d05b: 40165

by Eliot Miranda

On Wed, Aug 13, 2014 at 8:24 AM, Ben Coman <btc(a)openinworld.com> wrote: > Eliot Miranda wrote: > > On Tue, Aug 12, 2014 at 5:27 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> GitHub wrote: >> >> Branch: refs/heads/4.0 >> Home: https://github.com/pharo-project/pharo-core >> Commit: 06d05bd822deee4a79736d9f99d4a666ca1637eb >> https://github.com/pharo-project/pharo-core/commit/06d05bd822deee4a79736d9f… >> Author: Jenkins Build Server <board(a)pharo-project.org> <board(a)pharo-project.org> >> Date: 2014-08-11 (Mon, 11 Aug 2014) >> >> >> 13806 Remove ThreadSafeTranscriptPluggableTextMorph >> https://pharo.fogbugz.com/f/cases/13806 >> >> >> >> For anyone concerned about the performance of writing to Transcript from >> higher priority threads, just reporting that altering ThreadSafeTranscript >> to be safe for Morphic without ThreadSafeTranscriptPluggableTextMorph had a >> side effect of enhancing performance by 25x. With two runs of the >> following script... >> >> Smalltalk garbageCollect. >> Transcript open. "close after each run" >> [ Transcript crShow: ( >> [ >> | string | >> string := '-'. >> 1 to: 2000 do: >> [ :n | >> string := string , '-', n printString. >> Transcript show: string. >> ]. >> (Delay forMilliseconds: 10) wait. >> ]) timeToRun. >> ] forkAt: 41. >> >> >> >> Build 40162 reports timeToRun of 0:00:00:02.483 & 0:00:00:02.451 >> Build 40165 reports timeToRun of 0:00:00:00.037 & 0:00:00:00.099 >> >> >> Now I had meant to ask... I notice that FLFuelCommandLineHandler installs >> ThreadSafeTranscript, so I wonder it is affected by this change. Can some >> Fuel experts comment? >> >> >> Also I am looking for some advice for a minor downside I just noticed. >> The whole script above can complete between steps, so the entire output >> ends up in the PluggableTextMorph its size without being culled, which >> causes making a selection become really slow. Normally the excess text >> shown by Transcript is culled in half [1] by >> PluggableTextMorph>>appendEntry each time #changed: is called. >> >> PluggabletextMorph>>appendEntry >> "Append the text in the model's writeStream to the editable text. " >> textMorph asText size > model characterLimit ifTrue: "<---[0]" >> ["Knock off first half of text" >> self selectInvisiblyFrom: 1 to: textMorph asText size // 2. >> "<---[1]" >> self replaceSelectionWith: Text new]. >> self selectInvisiblyFrom: textMorph asText size + 1 to: textMorph >> asText size. >> self replaceSelectionWith: model contents asText. "<----[2]" >> self selectInvisiblyFrom: textMorph asText size + 1 to: textMorph >> asText size >> >> That works fine when #appendEntry is being called with lots of small >> changes, but for a single large change the entire change ends up in >> PluggableTextMorph via [2]. In this case >> model characterLimit "--> 20,000" [0] >> model contents size "--> 5,671,343" [2] >> where model == Transcript. >> >> So what is the behaviour you'd like to when too much is sent to >> Transcript? >> a. Show all content however briefly. >> b. Only the last 20,000 characters are put into the PluggableTextMorph, >> and the earlier data thrown away. >> I see a few ways to deal with this: >> 1. Limit the stream inside Transcript to a maximum 20,000 characters by >> basing it on some circular buffer. >> 2. Have "Transcript contents" return only the last 20,000 characters of >> its stream. >> 3. Limit to text sent to #replaceSelectionWith: [2] to 20,000 characters. >> >> Thoughts anyone? >> > > IMO 20,000 characters is way too little. I routinely set my limit to > 200,000. So b) but with a higher limit. a) is pointlessly slow. > > Thanks Eliot. Its good to know what is expected from Transcript. > > > In your implementation list, surely 2. is the only thing that makes > sense? > > > I agree, (2.) would be efficient. It just would have been precluded if > (a) was required. > > If the limit can remain soft then anyone that wants to see more simply > raises their limit. > > > Do you mean you'd like Transcript characterLimit to be a Preference ? > I'm not sure. If it was a preference I'd use it, but few others may find it useful. As I say, I need at east 20,000 chars on the transcript to effectively develop Cog; the VM simulator produces lots of output and realistically a transcript is the only convenient place to view it. So whether it was a preference ofr not I'd make sure the limit was >= 20k. 1. & 3. are implementation details left up to you. > > > I can do (1.) with Steph's new circular list. Doing (2.) means (3.) wont > be required for this, but its probably beneficial so I'll log it as > separate Issue. > > As long as the transcript is reasonably fast and has the same protocol > as WriteStream (it needs to support printOn: and storeOn: et al) implement > it as you will. BTW, the Squeak transcript is appallingly slow. > > -- best, Eliot

Aug. 13, 2014

Pharo 3 backports

by Ben Coman

Where should we be putting slices for Pharo 3 backports. I am proposing my fix for "Extended Search... Implementors fooled by block variables" be backport for Pharo 3. I took a guess that Pharo30Inbox would be the place to put the slice, but the the report [1] from the monkey reports: Jenkins Job jenkins-Pharo-3.0-Issue-Validator-27054 Could not Find Change: http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main So should Pharo 3 backports be put in Pharo40Inbox? (probably easiest short term workaround?) Or does something with the monkey need to be changed? (maybe longer term goal?) cheers -ben [1] https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/27054//artifact/val…

Aug. 13, 2014

Re: [Pharo-dev] Faster ThreadSafeTranscript Re: [pharo-project/pharo-core] 06d05b: 40165

by Ben Coman

Aug. 13, 2014

Re: [Pharo-dev] Faster ThreadSafeTranscript Re: [pharo-project/pharo-core] 06d05b: 40165

by Ben Coman

stepharo wrote: > HI Ben > This is really cool that you spend time on it! Thanks thanks thanks! > Really thanks! > > if you need a circularList I'm coding one for the systemLogger. > Just ask. This would be useful to limit the size of the underlying stream if high priority thread should fill too much before the UI thread can clear it. Can you point me at it. Will I be able to do something like... stream := WriteSteam on: CircularList new. cheers -ben > > (I'm about to change the API of the new linked list I wrote (I never > like the Link and ValueLink that we have in the system) > but Link for a linkedList is as good as Cell (if I do not like Link > :)) so I'm about to stop thinking that I prefer Cell and I will make > sure that both classes use the > same vocabulary as our ancient linkedList. :) > May be I'm becoming wise after all :) > > Stef > > >

Aug. 13, 2014

Re: [Pharo-dev] Faster ThreadSafeTranscript Re: [pharo-project/pharo-core] 06d05b: 40165

by Ben Coman

Aug. 13, 2014

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

by Esteban Lorenzano

Hi, On 13 Aug 2014, at 13:42, Tim Mackinnon <tim(a)testit.works> wrote: > Thanks Esteban, thatâs definitely (minor point: you didnât use the same text I gave you below, so there are some grammatical errors on the site). actually, I did not wrote anything (that was Stef :)â¦ I just fixed the links :) the format for pharo site is pillar (same as pier). I will include your changes now. cheers, Esteban > > If you want to keep control of how things are published - maybe it makes sense, and is much easier to set the rule: âGive me a complete page with changes in XXXX formatâ (you tell me what XXX is - markdown?). And then we can send you full pages you can paste in (and diff?) > > For now - can you also change the first paragraph, I think it makes more sense to say that Pharo.org is the main place for information, and so its much better to write: > > #How to propose a bug fix or enhancement > First check if your change has already been entered into [Fogbugz](https://pharo.fogbugz.com/), and consider watching the [overview video](https://www.youtube.com/watch?v=iFomI-7h4qQ) of the steps documented below. > > Can you also change the Pre-reqs section to fix some minor typos (and match the formatting of the text further down) > > ##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 commit 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… >> > > Tim > > > > > On 12 Aug 2014, at 12:30, EstebanLM [via Smalltalk] <[hidden email]> wrote: > >> >> On 11 Aug 2014, at 18:28, Tim Mackinnon <<a href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote: >> >>> Bump? The text on http://pharo.org/contribute-propose-fix is still wrong - can someone include the text I fixed up below? >> >> fixed >> >> Esteban >> >>> >>> Also - do we want to make pharo.org the primary place for docs (and hence change the first paragraph to: >>> >>> #How to propose a bug fix or enhancement >>> First check if your change has already been entered into Fogbugz, and consider watching the [overview video](https://www.youtube.com/watch?v=iFomI-7h4qQ) of the steps documented below. >>> >>> If we want to move away from the Fogbugz wiki, I will also simplify some of the text and point it back to pharo.org. >>> >>> Tim >>> >>> On 8 Aug 2014, at 08:40, Tim Mackinnon <<a href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=1" target="_top" rel="nofollow" link="external">[hidden email]> wrote: >>> >>>> 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 <<a href="x-msg://7/user/SendEmail.jtp?type=node&node=4772981&i=2" target="_top" rel="nofollow" link="external">[hidden email]> 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]" <<a href="<a href="x-msg://28/user/SendEmail.jtp?type=node&amp;node=4772414&amp;i=0">x-msg://28/user/SendEmail.jtp?type=node&node=4772414&i=0" target="_top" rel="nofollow" link="external">[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. >>>> >>> >> >> >> >> 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. 13, 2014