- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] e2bcbd: 30656

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: e2bcbdcdd2a3f1b3e6ca58db7b7a7e3c39ec95ad https://github.com/pharo-project/pharo-core/commit/e2bcbdcdd2a3f1b3e6ca58db… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-20 (Fri, 20 Dec 2013) Changed paths: M KernelTests.package/ClassTest.class/instance/testing/testClassRespectsPolymorphismWithTrait.st M Nautilus.package/AbstractNautilusUI.class/instance/icon/classIconFor_.st M Nautilus.package/CategoryWidget.class/instance/private/loadPackagesCategoriesInARestrictedEnvironment_for_.st R Nautilus.package/NautilusMonticello.class/class/monticello menus/packagesSliceMenu_.st R Nautilus.package/NautilusMonticello.class/instance/monticello menus behavior/addSliceFor_.st R Nautilus.package/NautilusMonticello.class/instance/monticello menus behavior/postNewSliceFor_.st R Nautilus.package/extension/Announcement/class/nautilusIcon.st R Nautilus.package/extension/Collection/class/nautilusIcon.st R Nautilus.package/extension/Exception/class/nautilusIcon.st R Nautilus.package/extension/Magnitude/class/nautilusIcon.st R Nautilus.package/extension/Morph/class/nautilusIcon.st R Nautilus.package/extension/Object/instance/nautilusIcon.st R Nautilus.package/extension/String/class/nautilusIcon.st R Nautilus.package/extension/Trait/instance/nautilusIcon.st A Polymorph-Widgets.package/extension/Announcement/class/systemIcon.st A Polymorph-Widgets.package/extension/Collection/class/systemIcon.st A Polymorph-Widgets.package/extension/Exception/class/systemIcon.st A Polymorph-Widgets.package/extension/Magnitude/class/systemIcon.st A Polymorph-Widgets.package/extension/Morph/class/systemIcon.st A Polymorph-Widgets.package/extension/Object/instance/systemIcon.st A Polymorph-Widgets.package/extension/String/class/systemIcon.st A Polymorph-Widgets.package/extension/Trait/instance/systemIcon.st A RPackage-Core.package/RPackage.class/instance/class tags/classTagCategoryNames.st R RPackage-Core.package/RPackage.class/instance/class tags/classTagNames.st M RPackage-Core.package/RPackageSet.class/instance/accessing/categoryNames.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script309.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30656.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/AbstractEyeElement.class/instance/accessing/icon.st Log Message: ----------- 30656 11403 --all-- protocol disappears when browsing scoped https://pharo.fogbugz.com/f/cases/11403 12468 KernelTests packages are messed up on changes https://pharo.fogbugz.com/f/cases/12468 12392 EyeInspector should not depend on Nautilus https://pharo.fogbugz.com/f/cases/12392 12381 Creating slices is broken https://pharo.fogbugz.com/f/cases/12381 http://files.pharo.org/image/30/30656.zip

Dec. 20, 2013

FFI loadable in Pharo 3.0

by ClÃ©ment Bera

Hello, https://pharo.fogbugz.com/f/cases/12438/Old-FFI-Check-that-it-is-parsed-cor… I was fixing this bug with Guille today. You can load FFI with the Configuration browser. Please try to load, use it and review the issue. We also added the new configuration in the old metacello repository in squeaksource (buu old one). So, try to fix your configurations to point to the correct repository :). Thanks! Clement & Guille

Dec. 20, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 7e83c6: 30655

by Marcus Denker

On 20 Dec 2013, at 12:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > This update integrated a change that is wrong (brakes text selection). > I checked and I can not reproduce the problemâ¦ so for now we just continue. Marcus

Dec. 20, 2013

Re: [Pharo-dev] gtinspector deconstructed

by Sven Van Caekenberghe

On 19 Dec 2013, at 22:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > That is a good observation :). > > You do not like the underscore, or the "sel" entry? > > If you talk about the underscore, I just wanted a way to distinguish between special variables. You also see the same "notation" in the debugger (variables like _self and _thisContext). > > If you talk about the entry altogether, this part is more experimental. Some people did not like the printout in the comment, and then I added _self to show the print string next to it. I am still not decided on showing it. What do other think about it? > > Cheers, > Doru I guess you need self for objects without instance variables. I donât like the underscore, every Smalltalker should know about self, super and thisContext. You could make them bold or italic or gray. > > On Thu, Dec 19, 2013 at 9:57 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Ah, yes, and I donât like the _self. Why would you want to do that ?? >

Dec. 20, 2013

Re: [Pharo-dev] gtinspector deconstructed

by Sven Van Caekenberghe

On 19 Dec 2013, at 22:08, Tudor Girba <tudor(a)tudorgirba.com> wrote: > SequenceableCollection indexes would be nice. Paging is cool. > > What do you mean by indexes? The position of an item in the collection? Yes, > I miss an option to go back to less columns, like from 1 to 2 and back to 1, I canât seem to deselect something in the first one, which would be a way to let the second one disappear again. I hope I am making myself clear ;-) > > Yes, I agree. This is an extension I want for Glamour in general: to grow a pane to fill the window (similar to what happens in Eclipse). This will help you switch between floating navigation mode and more in-depth work mode. That would be cool. > We have specialised inspectors for Integer and Float (and maybe some more) standard in Pharo, showing more high level virtual fields, it would be nice if you could implement those as well, maybe as alternative views. > > Certainly. That is the whole idea: create more dedicated presentations to serve dedicated use cases. I do not know the use case for this, but let's make an exercise out of it. Can you tell me what exactly would be interested in seeing? So, if you have an Integer or a Float what code would you like to trigger and have presented? Some of this got lost when EyeInspector got introduced, here are some screenshots from an older image: I can think of alternative representations for lots of classes. > Which brings me to my final question: how do I write simple custom inspectors, given that I am not familiar with Glamour/Moose - that could maybe be another blog post ? > > At the end of the post, there is a "Be moldable" section in which I am hinting at the process. Essentially, you have to extend your object with a method that follows this pattern: > > YourClass>>gtInspectorYourPresentationIn: composite > <gtInspectorPresentationOrder: 30> > composite "followed by Glamour code to construct presentations" > > The post shows this example: > RGMethodDefinition>> gtInspectorSendersIn: composite > <gtInspectorPresentationOrder: 30> > composite list > title: 'Senders'; > display: [ self compiledMethod implementors ] > > So, to find more examples, simply search for senders of #gtInspectorPresentationOrder: (or just inspect the symbol to see what happens :)), and you will see all extensions in the image. > > I would like to make all presentation tabs to give you the possibility to jump to the implementation so that you can see more examples (like with halos). In any case, I will write another post with some more implementation examples. Yes, I read everything, and I did some code reading, but I felt a bit helpless ;-) > Anyway, thanks for pushing this ! > > Thanks for looking into it :) > > > Sven > > PS: I wonder whether it would be possible to have both types of inspectors/debuggers available at the same time, so that one can switch on the fly, compare them, use one or the other depending on the task ? > > Marcus says that there is an intention of having multiple alternative tools be described via pragmas and be switchable from the settings browser. However, I am not really convinced this is the way to go. I would be more interested in what does not work to make one work smoothly. I donât mean switching using a Setting (although that would be good to have too), I meant command-i for normal inspectors, command-shift-i for GT inspectors, or something like that.

Dec. 20, 2013

Re: [Pharo-dev] [Pharo-users] PharoLauncher as the default Pharo download on pharo.org?

by Mark Bestley

Another useful thing would be to have timestamps of when the builds were made. I would like to know if there is a newer version of a template so I should use that rather than the quicker carry on with a local image. Thanks -- Mark

Dec. 20, 2013

Re: [Pharo-dev] [Pharo-users] PharoLauncher as the default Pharo download on pharo.org?

by Mark Bestley

On 20/12/2013 10:45, Sven Van Caekenberghe wrote: > > On 20 Dec 2013, at 10:44, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> Hi guys, >> >> what do you think about setting the PharoLauncher as the default >> download for mac os x users? > In general makes sense, however I think it needs to clean up a few things. 1) Setting of the default directories - these should be more Apple standard i.e. images not in preferences and even better in a Sandbox so eventually could be available via App Store which would increase the number of people who would see it. (I have use the settings to change the directory for me.) 2) Dealing with saved images. If you do a save as.. the this new image does not show in the launcher. I think there are two ways of fixing this i) don't put images and source in sub directories ii) Make the save as in Pharo create a sub directory Point ii) leads onto making the save of an image save to an OSX bundle (i.e. a directory containing several files that OSX can see as one unit) 3) The icons need to have more responsive pop-overs to explain what they do.(I almost wrote any pop-over but after a minute I can get them 30% of the time) 4) For first time users I think the right pane needs a look at - users will not know which is the correct template to use. I would suggest making the Pharo latest stable a top level entry and highlighting that. > I would start by featuring it more prominently on the download page while explaining clearly what it does. Maybe it also needs its own documentation/promotion web page. > And add some documentation to the launcher -- Mark

Dec. 20, 2013

Re: [Pharo-dev] [ANN] JetStorm

by Sebastian Sastre

Fantastic work. Maybe you should try talking with these guys: http://www.kickstarter.com/projects/1039674461/primo-teaching-programming-l… Sounds like there is space for an intermediate product to ease the learning curve there sebastian o/ On Dec 18, 2013, at 7:09 AM, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi all, > Another announcement for Christmas. > > Do you know Lego MindStorms ? The last one is the Ev3 serie (http://www.lego.com/fr-fr/mindstorms/) > One particularity of this version compared to the previous ones is the possibility to plug a Wifi key and connect via TCP. > > So, if you have this material (one Mindstorms Ev3, one compatible Wifi key), a wireshark to obtain the TCP port to connect to Ev3 (See the process here, only to understand why we need a wireshark to know the port: http://www.monobrick.dk/guides/how-to-establish-a-wifi-connection-with-the-…) > > Now, you can control your robot with Pharo ! > Just load these lines: > â > Gofer it > url: 'http://smalltalkhub.com/mc/JLaval/JetStorm/main' > username: '' > password: ''; > package: 'ConfigurationOfJetStorm'; > load. > (Smalltalk at: #ConfigurationOfJetStorm) loadBleedingEdge. > â > > I know also that for Christmas, it is not possible to learn a new API, we all have a lot of other things to do ! So, you can play with it into Phratch. > For that, just load Phratch and the package EV3Phratch as following. > > â > Gofer it > url: 'http://smalltalkhub.com/mc/JLaval/Phratch/main' > username: '' > password: ''; > package: 'ConfigurationOfPhratch'; > load. > (Smalltalk at: #ConfigurationOfPhratch) loadBleedingEdge. > > Gofer it > url: 'http://smalltalkhub.com/mc/JLaval/JetStorm/main' > username: '' > password: ''; > package: 'EV3Phratch'; > load. > â > > Have fun ! > Jannik > > PS: for now, this package in prototype, it can change a lot and can have bugs. Do not hesitate to give feedbacks. > PS2: I hope to write a doc for it ! > <ev3.png>

Dec. 20, 2013

Re: [Pharo-dev] WhatsUp from: 2013-12-16 until: 2013-12-31

by Alexandre Bergel

>> - Continuing Roassal 2.0 > > > pushing your fixes to the collection hierarchy? Yes, I am working on that right now Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 20, 2013

Re: [Pharo-dev] [pharo-project/pharo-core] 7e83c6: 30655

by Marcus Denker

Hello, This update integrated a change that is wrong (brakes text selection). We need to either undo the change or revert the whole update. On 20 Dec 2013, at 11:13, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/3.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 7e83c66e89929bbcb749009c237a5383d7362693 > https://github.com/pharo-project/pharo-core/commit/7e83c66e89929bbcb749009c… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2013-12-20 (Fri, 20 Dec 2013) > > Changed paths: > R Deprecated30.package/extension/TBehavior/instance/methodDictionary.st > R Deprecated30.package/extension/TBehavior/instance/methodDictionary_.st > M Morphic-Base.package/PluggableTextMorph.class/README.md > M Morphic-Base.package/PluggableTextMorph.class/definition.st > A Morphic-Base.package/PluggableTextMorph.class/instance/accessing/font.st > A Morphic-Base.package/PluggableTextMorph.class/instance/accessing/setSelectionSelector.st > A Morphic-Base.package/PluggableTextMorph.class/instance/accessing/setSelectionSelector_.st > A Morphic-Base.package/PluggableTextMorph.class/instance/accessing/stylerClass.st > R Morphic-Base.package/PluggableTextMorph.class/instance/as yet unclassified/font.st > R Morphic-Base.package/PluggableTextMorph.class/instance/as yet unclassified/methodCaseSensitiveStringsContainingit.st > R Morphic-Base.package/PluggableTextMorph.class/instance/as yet unclassified/scrollToBottom.st > R Morphic-Base.package/PluggableTextMorph.class/instance/as yet unclassified/stylerClass.st > A Morphic-Base.package/PluggableTextMorph.class/instance/menu messages/methodCaseSensitiveStringsContainingit.st > M Morphic-Base.package/PluggableTextMorph.class/instance/model access/selectionInterval_.st > A Morphic-Base.package/PluggableTextMorph.class/instance/scrolling/scrollToBottom.st > A Morphic-Base.package/TextMorphForEditView.class/instance/event handling/keyUp_.st > A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script308.st > A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30655.st > M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M Spec-MorphicAdapters.package/MorphicTextAdapter.class/class/specs/defaultSpec.st > M Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/spec protocol/setSelectionFromModel_.st > R Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/spec protocol/setSelection_.st > A Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/widget API/setSelection_.st > A Traits.package/TBehavior.class/instance/accessing method dictionary/methodDictionary.st > A Traits.package/TBehavior.class/instance/accessing method dictionary/methodDictionary_.st > > Log Message: > ----------- > 30655 > 12144 TextModel>>getSelection > https://pharo.fogbugz.com/f/cases/12144 > > 12459 un-deprecated #methodDictioary > https://pharo.fogbugz.com/f/cases/12459 > > http://files.pharo.org/image/30/30655.zip > >

Dec. 20, 2013