April 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Esteban Lorenzano

> On 13 Apr 2015, at 13:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > demarey wrote >> It is always better to have the full documentation instead of relying on >> people knowledge. > > For example, Ruby gives a one-liner for each package manager > https://www.ruby-lang.org/en/documentation/installation/ <https://www.ruby-lang.org/en/documentation/installation/> yes, but ruby has also lot more resources :) I wanted (and still want) to use this: http://openbuildservice.org <http://openbuildservice.org/> to produce packages for all available distributions, but sadly I did not have the time to sit and learn it. if someone already knows it and wants to do some remote pair programming with meâ¦ I would be really grateful :) Esteban > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Shorter-Pharo-Launcher-download-link-tp4818944p481928… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 13, 2015

Ubuntu PPA - How current is it?

by Sean P. DeNigris

Is this built automatically via CI (I can't check bc it's down) or manually? If the latter, how often? I ask because Ruby mentions that the package manager versions are usually a bit out of date and I want to give accurate info to our users... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ubuntu-PPA-How-current-is-it-tp4819292.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Sean P. DeNigris

EstebanLM wrote > yes, but ruby has also lot more resources :) Of course, not complaining, just pointing to an example... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Shorter-Pharo-Launcher-download-link-tp4818944p481929… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Christophe Demarey

Le 13 avr. 2015 Ã 14:00, Damien Cassou a Ã©crit : > > Sean P. DeNigris <sean(a)clipperadams.com> writes: > >> Damien Cassou wrote >>> This is already possible on Gentoo... and Nix. >> >> What are the instructions? To be added to http://pharo.org/download ... > > > I'm not sure we should pollute the Pharo website with instructions that > should be known by the user. For example, Gentoo users know how to > install packages on Gentoo hopefully. We can however add a sentence > saying that there are dedicated packages for these platforms. I would like to have these instructions because they could be different from a version of your distribution to another. It is always better to have the full documentation instead of relying on people knowledge. Maybe it should not be on the default download page but the information should be available easily.

April 13, 2015

Re: [Pharo-dev] [Vm-dev] Re: [Pharo-fuel] Binding semantics of SystemDictionary

by Martin Dias

On Sun, Apr 12, 2015 at 12:41 PM, Max Leske <maxleske(a)gmail.com> wrote: > > > On 10 Apr 2015, at 11:28, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hmm, there is something that I'm missing: > > do you have a real case where fuel is failing? :) > > > No :) But itâs something that has the potential to fail at any time. > > > if so, I'd focus on that: where does it come from, how was that class > created, maybe it's a very specific case that you can handle in an ad-hoc > way (and then leave fuel as it is right nowâ¦) > > > Thatâs why I suggested signalling an exception. It wouldnât change > anything about Fuel. But in case someone encounters the problem, Fuel will > fail early (during serialization) instead of (very) late (during > materialization). > +1 I agree with signaling an error, if there are no real cases. However, I don't defend the "all class names are byte strings" assumption of Fuel. Of course, it could be optimized for such cases, but it should also support other objects... MartÃn > Cheers, > Max > > > El vie., 10 de abr. de 2015 a la(s) 11:24 a. m., Max Leske < > maxleske(a)gmail.com> escribiÃ³: > >> On 07 Apr 2015, at 13:30, vm-dev-request(a)lists.squeakfoundation.org >> wrote: >> >> Hmm, I think we are mixing stuff here ^^ >> >> Method Dictionaries and system dictionary accept any object as keys. >> >> To execute code, the VM only checks for identity (+ identity hash that >> does >> not change) in method dictionaries. The VM never looks up in the system >> dictionary. >> Actually the VM does not make any assumption on the objects you put as >> keys. This makes the VM simpler. >> Then tools enforce that we put there symbols as keys in both. But, we >> could >> put anything we would like. >> >> >> Interesting. >> >> >> So, answering your questions: >> >> 1. Are bindings with keys that are not ByteString or ByteSymbol valid? >> >> Theoretically yes, but nobody uses this for real for now. Camille has >> some prototypes that uses this to enforce modularity. >> >> 2. Should we keep allowing ByteString as keys to globals (ByteSymbol >> guarantees identity)? >> >> Well, usually the tools will make sure that you transform them to a >> symbol before. >> >> 3. If we allow ByteString, do we also allow WideString? >> >> Any object ^^ >> >> 4. Would âtype checksâ on SystemDictionary incur a big performance >> penalty? >> >> Maybe, but not only that. It makes the code more messy also, and >> hardcode tool assumptions. I don't put any type checks in any of my code >> usually, why start there... We should fix fuel to not make that assumption >> instead I think. >> >> >> I agree. I donât like type checks. Just wanted to have talked about the >> option. >> >> Thanks for your input Guille. Iâm still not sure how to solve this issue >> for Fuel though. I see several options: >> - signal an exception when the key to a global is not a symbol >> - simply serialize a string representation of the key, which will lead to >> a lookup failure on materialization - > not good >> - serialize the identityHash of the key. The identity hash of a symbol is >> stable across different images and VMs but not across Squeak and Pharo -> >> not good >> - serialize the actual key. This requires us to rewrite the global >> handling logic and it will once again break backwards compatibility. This >> might be something for the future. >> >> So maybe we should: >> 1. signal an exception -> no change for users >> 2. In a future version rewrite the global handling logic to allow for >> arbitrary global keys. >> >> Opinions? >> >> Cheers, >> Max >> _______________________________________________ >> Pharo-fuel mailing list >> Pharo-fuel(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel >> > > >

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Damien Cassou

Sean P. DeNigris <sean(a)clipperadams.com> writes: > Damien Cassou wrote >> This is already possible on Gentoo... and Nix. > > What are the instructions? To be added to http://pharo.org/download ... I'm not sure we should pollute the Pharo website with instructions that should be known by the user. For example, Gentoo users know how to install packages on Gentoo hopefully. We can however add a sentence saying that there are dedicated packages for these platforms. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 13, 2015

[pharo-project/pharo-core]

by GitHub

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

April 13, 2015

[pharo-project/pharo-core] 4044d2: 40603

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4044d2905336b545fc8a188ec79e9c0f15bac73c https://github.com/pharo-project/pharo-core/commit/4044d2905336b545fc8a188e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-13 (Mon, 13 Apr 2015) Changed paths: M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version2012_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version211_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version121_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version301_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version311_.st A GT-Playground.package/GTPlayBook.class/class/accessing/customDirectory_.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorder.class/class/accessing/version.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/class/accessing/storeSerializedAnnouncementIntoMethod_.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/accessing/allPragmaVersions.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/accessing/materializePragmaVersion_.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/enumerating/versionsDo_.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/serialized data/version2.st A GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/tests/testDateAndTime.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorderTest.class/instance/tests/testMaterializeVersions.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderActOnEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderCategorySelectedEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderContextChangedEvent.class/instance/accessing/currentTextSizes.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderContextChangedEvent.class/instance/accessing/currentTextSpecials.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderContextChangedEvent.class/instance/testing/hasCurrentTextSpecials.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderContextChangedEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderDiveInCategoryEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderDiveInElementEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderDiveOutEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderEvent.class/instance/accessing/dateAndTime.st M GT-Spotter-EventRecorder.package/GTSpotterRecorderEvent.class/instance/accessing/timestamp.st M GT-Spotter-EventRecorder.package/GTSpotterRecorderEvent.class/instance/initialization/initialize.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderExitAnnouncementEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderHidePreviewEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderOpenEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderSearchFinishedEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderSelectedCandidateChangedEvent.class/instance/visitor/accept_.st A GT-Spotter-EventRecorder.package/GTSpotterRecorderShowPreviewEvent.class/instance/visitor/accept_.st M GT-Spotter.package/GTSpotter.class/definition.st A GT-Spotter.package/GTSpotter.class/instance/accessing/history.st A GT-Spotter.package/GTSpotter.class/instance/accessing/history_.st M GT-Spotter.package/GTSpotter.class/instance/actions api/historize_.st A GT-Spotter.package/GTSpotterCandidateLink.class/instance/printing/gtDisplayOn_.st M GT-Spotter.package/GTSpotterResultsBrick.class/instance/event handling/onCandidateSelected_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/concreteMethodsInContext_usingFilter_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/spotterForStashedPlaygroundPagesFor_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/spotterHistoryFor_.st A GT-Tests-Spotter.package/GTSpotterTest.class/instance/tests/testHistorizingTheSameObjectRemovesPreviousOccurences.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/actOnHighlightAndEvaluate_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/debugHighlightedText.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/evaluateAndPopPrintHighlight.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/profileHighlightedText.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script602.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script603.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40602.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40603.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40603 ConfigurationOfRubric http://files.pharo.org/image/40/40603.zip

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Sean P. DeNigris

demarey wrote > It is always better to have the full documentation instead of relying on > people knowledge. For example, Ruby gives a one-liner for each package manager https://www.ruby-lang.org/en/documentation/installation/ ----- Cheers, Sean -- View this message in context: http://forum.world.st/Shorter-Pharo-Launcher-download-link-tp4818944p481928… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015