June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

Thanks Gabriel, yeah I thought so. Houston we have a problem. I changed the SqueakSource chapter to SmalltalkHub but I have 2 problems a) Even though I can generate the pdf for the First Application chapter. the pdf for the entire book does not generate , instead it errors complaining that it cannot find a png that I added which is where it should be and with the correct and appropriate filename. I dont see why it has a problem with this. b) The layout is really messed up , it puts the image inside a code I have included and it looks very messy in the pdf. No clue how to solve these problems . I committed with these problems so you can see for yourselves. On Fri, Jun 13, 2014 at 9:24 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Yes.. I usually remove the previous content before using the zero conf > script.. (I'm not using pillar but the basic script don't work if you > already have the vm and tries to download it again, at least on my Linux > box). > > Hope it helps > > > On Fri, Jun 13, 2014 at 2:25 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> what "clean the directory" mean ? And how I do that ? Do I need to delete >> the directory and reclone it ? >> >> >> On Fri, Jun 13, 2014 at 7:57 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> >> wrote: >> >>> Clean the directory where you're running the script. If some of the >>> files already exists the zero conf script won't work. >>> >>> >>> On Fri, Jun 13, 2014 at 12:14 PM, kilon alios <kilon.alios(a)gmail.com> >>> wrote: >>> >>>> thanks Damien that works. >>>> >>>> However running ./update.sh afterwards creates this error >>>> >>>> "2014-06-13 18:07:52 (1,01 MB/s) - written to stdout [5311/5311] >>>> >>>> Downloading the latest pharoVM: >>>> http://files.pharo.org/vm/pharo/linux/stable.zip >>>> mkdir: cannot create directory âpharo-vmâ: File exists >>>> " >>>> >>>> is this normal ? >>>> >>>> >>>> On Fri, Jun 13, 2014 at 5:17 PM, Damien Cassou <damien.cassou(a)gmail.com >>>> > wrote: >>>> >>>>> On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> >>>>> wrote: >>>>> > So how I proceed ? >>>>> >>>>> >>>>> the Ubuntu PPA is made for this: >>>>> >>>>> sudo add-apt-repository ppa:pharo/stable >>>>> sudo apt-get update >>>>> sudo apt-get install pharo-launcher >>>>> >>>>> Can't be more simple than that >>>>> >>>>> >>>>> >>>>> -- >>>>> Damien Cassou >>>>> http://damiencassou.seasidehosting.st >>>>> >>>>> "Success is the ability to go from one failure to another without >>>>> losing enthusiasm." >>>>> Winston Churchill >>>>> >>>>> >>>> >>> >> >

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Ben Coman

June 14, 2014

MacOS | Cmd-Q is not working

by Noury Bouraqadi

Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Eliot Miranda

Hi Sven, On Sat, Jun 14, 2014 at 4:09 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Jun 2014, at 12:18, Ben Coman <btc(a)openInWorld.com> wrote: > > > Sven Van Caekenberghe wrote: > >> In any case, the server socket used is normally listening on all > interfaces [0.0.0.0] > >> > >> Sven > >> > >> > > > > Maybe it matters that [0.0.0.0] is the IPv4-Unspecified-Address > > and it might make a difference to use IPv6-Unspecified-Address > [0:0:0:0:0:0:0:0] or [::] > > > > cheers -ben > > I guess it all depends on the Socket plugin. ZnServer has #bindingAddress: > which eventually calls Socket>>#listenOn:backlogSize:interface: but the > question is, what is acceptable as last argument. And how is the difference > between v4 and v6 handled. There is a 'primitives-ipv6' category, but no > #listenOn with an interface there. > I wonder whether this commit is relevant: r2552 | eliot | 2012-05-02 16:13:02 -0700 (Wed, 02 May 2012) | 19 lines CogVM source as per VMMakerr.oscog-eem.159 ... Fix limitation in platforms/unix/plugins/SocketPlugin/sqUnixSocket.c which could cause NetNameResolver localHostAddress to answer 0 (if host has a set hostname not being honoured by local DNS servers). Fix falls back to localhost. ... Here's the relevant part of the platforms/unix/plugins/SocketPlugin/sqUnixSocket.c change: -sqInt sqResolverLocalAddress(void) { return nameToAddr(localHostName); } +sqInt sqResolverLocalAddress(void) +{ sqInt localaddr = nameToAddr(localHostName); + if (!localaddr) + localaddr = nameToAddr("localhost"); + return localaddr; +} This fixed several socket tests on my Mac OS box. I think it affects systems behind a broadband router, at least that's how it asffected me on my laptop at home. And here's what is probably the root cause in platforms/unix/plugins/SocketPlugin/sqUnixSocket.c: ... static char localHostName[MAXHOSTNAMELEN]; static u_long localHostAddress; /* GROSS IPv4 ASSUMPTION! */ ... /* start a new network session */ sqInt sqNetworkInit(sqInt resolverSemaIndex) { if (0 != thisNetSession) return 0; /* already initialised */ gethostname(localHostName, MAXHOSTNAMELEN); localHostAddress= nameToAddr(localHostName); thisNetSession= clock() + time(0); if (0 == thisNetSession) thisNetSession= 1; /* 0 => uninitialised */ resolverSema= resolverSemaIndex; return 0; } ... and so if gethostname answers something weird, attempts to access localHost are screwed from initialization on. HTH -- best, Eliot

June 14, 2014

[pharo-project/pharo-core]

by GitHub

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

June 14, 2014

[pharo-project/pharo-core] 94143d: 40022

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 94143dbbba2d877cfc4a0a922e6d1f72367fac8c https://github.com/pharo-project/pharo-core/commit/94143dbbba2d877cfc4a0a92… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-14 (Sat, 14 Jun 2014) Changed paths: A Gofer-Core.package/Gofer.class/instance/operations/loadBleedingEdge.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script22.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40022.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/AbstractTool.class/instance/class/createInstVarAccessorsOf_.st M Tools.package/AbstractTool.class/instance/class/moveInNewPackage_.st M Tools.package/AbstractTool.class/instance/method/categorizeMethods_of_from_.st M Tools.package/AbstractTool.class/instance/method/findMethodIn_.st M Tools.package/AbstractTool.class/instance/method/moveMethodsToPackage_in_from_.st M Tools.package/AbstractTool.class/instance/package/findPackageIn_.st M Tools.package/AbstractTool.class/instance/package/renamePackages_.st M Tools.package/AndreasSystemProfiler.class/class/spying/spyOn_.st M Tools.package/Browser.class/instance/class functions/renameClass.st A Tools.package/CPUWatcher.class/class/accessing/currentWatcherProcess.st R Tools.package/CPUWatcher.class/class/as yet unclassified/currentWatcherProcess.st R Tools.package/CPUWatcher.class/class/as yet unclassified/dumpTallyOnTranscript.st R Tools.package/CPUWatcher.class/class/as yet unclassified/startMonitoringPeriod_rate_threshold_.st A Tools.package/CPUWatcher.class/class/monitoring/dumpTallyOnTranscript.st A Tools.package/CPUWatcher.class/class/monitoring/startMonitoringPeriod_rate_threshold_.st M Tools.package/ChangeList.class/class/System-FileRegistry/browseCompressedChangesFile_.st M Tools.package/CodeHolder.class/instance/diffs/toggleDiffing.st M Tools.package/CodeHolder.class/instance/diffs/togglePlainSource.st M Tools.package/CodeHolder.class/instance/traits/spawnHierarchy.st M Tools.package/DialogItemsChooserUI.class/instance/build items/buildSelectedItemsList.st M Tools.package/FileContentsBrowser.class/class/instance creation/browseCompressedCodeStream_.st A Tools.package/FileList.class/class/accessing/searchList.st R Tools.package/FileList.class/class/as yet unclassified/searchList.st R Tools.package/FileList.class/class/modal dialogs/modalFileSelectorForSuffixes_.st R Tools.package/FileList.class/class/utility/textRow_.st R Tools.package/FileList.class/instance/private/directoriesMatching_.st R Tools.package/FileList.class/instance/private/getSelectedFile.st R Tools.package/FileList.class/instance/private/resort_.st R Tools.package/FileList.class/instance/user interface/wrapFile_.st M Tools.package/Finder.class/instance/private-example/constructDictionaryWithMethodFinder_.st M Tools.package/FinderUI.class/definition.st M Tools.package/FinderUI.class/instance/text areas behavior/compileSource_notifying_.st M Tools.package/MethodFinder.class/definition.st M Tools.package/QSystemTally.class/instance/report/into_fromSender_.st M Tools.package/QSystemTally.class/instance/tallying/tallyPath_by_.st M Tools.package/Spotlight.class/definition.st M Tools.package/TimeProfiler.class/instance/UI specific/reportOtherProcesses_.st M Tools.package/TimeProfiler.class/instance/UI specific/showLeavesOnly_.st M Tools.package/TimeProfiler.class/instance/accessing-computed/leaveItems.st M Tools.package/TimeProfiler.class/instance/compiling/selectedMethodCode_notifying_.st M Tools.package/VersionsBrowser.class/instance/items creation/buildDiffCodePane.st M Tools.package/extension/SystemNavigation/instance/browseAllReferencesToPool_from_.st M Tools.package/extension/SystemNavigation/instance/browseHierarchy_selector_.st Log Message: ----------- 40022 12860 valueOfProperty: #fileListModel. https://pharo.fogbugz.com/f/cases/12860 13326 Gofer: Add loadBleedingEdge https://pharo.fogbugz.com/f/cases/13326 13330 Small code critique cleanup in Tools https://pharo.fogbugz.com/f/cases/13330 http://files.pharo.org/image/40/40022.zip

June 14, 2014

Re: [Pharo-dev] Brainstorming Pharo4

by stepharo

> I can subscribe to most what others have said. Your list is pretty good and I like even the order of things. Only a few additions. > > âImproving toolsâ: One aspect is making the tools aware of new achievements in the core. Another aspect is to finish things that did change in the past like e.g. keybindings. Nautilus uses new keyboard shortcut while other tools use old ones. That is killing the development experience. I cannot agree more on that one :) > > âModularizationâ: I think this should be _the_ goal for pharo4: Changing the whole build process to a bootstrap+module approach. This is a huge step IMHO. To make it more modular also means things can get smaller and smaller. This also raises the necessity of having remote debugging tools because UI is suspect to not being there. This step will also improve the way we can manage deployed images which is especially important for a company like mine. And I hope having decent remote enabled model will also open new possibilities for image interoperation. that too. > > 64bit vm: Like sven said it is necessary for us to have at least a 64bit vm with a 32bit address space. Without that we are somewhat way behind what is normal for others. 64bit address space should be a goal for pharo5. > > Slots: I would like it to see Slots being usable. It enables people to play with new things without having to tweak the vm. And I like all magritte like stuff being handled by slots which will improve the situation a lot. And thatâs one thing that sets us way ahead of what is normal for others. > > Remove old compiler for obvious reasons. > > So that would be one to two tasks for areas of improve existing (maintenance), change for the better, distribution and cleanup. That would be all for pharo4 for me. > > Norbert > > > Am 04.06.2014 um 17:36 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hi, >> >> A couple of weeks ago we started to plan Pharo4. This work became stagnated for many reasons, but mainly because I needed to travel to Argentina. >> Now I'm slowly resuming the work and I wanted to share with you what we have been talking/dreaming. >> In esence, we have two important drivers for this release: >> >> 1) Improving tools >> Turns out that we have introduced a lot of kernel improvements (opal compiler, layouts, slots, etc.) and tools are still not aware of them. Even worst: we have traits since a lot of time and our tools are still now aware enough to provide good interoperability. >> But not just that: we have introduced things that are not well used yet: keybindings (who do not want a better keybindings structure... coherent and editable?), spec should allow us to continue enhancing existing tools and to replace old ones. >> >> 2) Modularisation >> One of the fundamental ideas behind Pharo is to provide a modular environment. But well... since Pharo start to the moment, we prepared things to allow it, but still few direct effort has been made. >> In our dreams, Pharo should be built starting for a small kernel image and adding different modules to get a complete version. In this idea Pharo=Kernel+GUI(Morphic)+Tools. >> This has huge advantages (I do not think is necesary to explain them, isn't ;)?) >> >> We brainstomed around this and we get this list of issues (not all of them directly related to the objectives, but well... good stuff also :) ) >> >> Web site: >> - add catalog >> - add videos >> - enhance it in general >> >> Infrastructure: >> - support more vm platforms >> >> VM: >> - spur >> - 64bits >> - make vm embedable and UI independent (with SDL2 and OSWindow) >> >> Image: >> - Modularisation >> - Removing old compiler >> - Repackage Morphic (to allow better modularisation) >> - Athens (replace old bitblt) >> >> Tools >> - Replace changes with Ombu/Epicea >> - Replace sources with a better abstraction >> - Git support inside image (with libgit2 + tools) >> - Pass on Spec >> - Include Glamour? >> - Make Ring unloadable >> - Fonts with FreeType >> >> And lots of bugfixes :) >> >> We would like to exchange ideas with you. >> So, what do you think? >> >> Esteban >> >> > >

June 14, 2014

Re: [Pharo-dev] [website] new news entry: talk NDC Oslo

by Tudor Girba

I think you are referring to the playground/inspector. Indeed it takes more space than the other inspector, but only if you want to see multiple objects at the same time. You can choose to see just one object at a time, and then you get in a situation similar to the existing tool. It's just that it turns out that once you can see more related objects, you choose to do so and you get more aggressive in exploration. And then you do not want to go back :). Doru On Fri, Jun 13, 2014 at 9:38 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 13 Jun 2014, at 09:31, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > If the fonts get much larger, having several panes side-by-side makes > things look ugly and you kind of lose the perspective :(. > > I think the GTTools take up too much screen space. I know that today we > have bigger screens and we should use them, but still. > > This is of course a subjective opinion, a feeling. > -- www.tudorgirba.com "Every thing has its own flow"

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

On 14 Jun 2014, at 12:18, Ben Coman <btc(a)openInWorld.com> wrote: > Sven Van Caekenberghe wrote: >> In any case, the server socket used is normally listening on all interfaces [0.0.0.0] >> >> Sven >> >> > > Maybe it matters that [0.0.0.0] is the IPv4-Unspecified-Address > and it might make a difference to use IPv6-Unspecified-Address [0:0:0:0:0:0:0:0] or [::] > > cheers -ben I guess it all depends on the Socket plugin. ZnServer has #bindingAddress: which eventually calls Socket>>#listenOn:backlogSize:interface: but the question is, what is acceptable as last argument. And how is the difference between v4 and v6 handled. There is a 'primitives-ipv6' category, but no #listenOn with an interface there.

June 14, 2014

Re: [Pharo-dev] Brainstorming Pharo4

by stepharo

> As Kilon say, this is a personal wishlist. Any direction you mentioned > is worth and will have impact. > > However, here's my personal top 5: > > - **Git in the image**, that would be awesome to be able integrate the > gitflow way of developing in team. Easy branching/merging is a must. > - **Slots**. I still need to check the current implementation and see > what's possible (Property slots?) but as I have understood you've > planned even more for pharo4? > - **Text Editor with sensible keybindings**. > - **ARM support** > - **Athens** We are getting there. > > > On Wed, Jun 4, 2014 at 9:06 PM, jannik laval <jannik.laval(a)gmail.com > <mailto:jannik.laval@gmail.com>> wrote: > > Hi all, > > >From my point of view, I like the progrss on the ARM VM. > I hope to have an Android VM that works. > Also I hope to see Pharo3.0 and Pharo4.0 working on iOS. > > Another question is about two interesting plugins: Mpeg3Plugin and > CameraPlugin. > Is it possible to integrate them in the VM build ? > > Thank you guys for all the work done. > Jannik > > > 2014-06-04 20:53 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > Hi Esteban, > > As you mentioned a lot of new tools and protocols were > introduced, > people (me included) does not well about those ones. > As an example I am slowly discovering announcement and now > AFAIK the > image use three different protocols for this: > change/update, observer > and Announcement! > > Yes we know that the situation is not ideal. > We started to move more to announcement. The problem is that > some of the widgets > requires the change/update. For the observer I do not know > what you mean. > > > Personally I beg for a great Pharo 4.x series of iterative > cleaning+consolidations. > > Thanks > > Hilaire > > Le 04/06/2014 17:36, Esteban Lorenzano a Ã©crit : > > Hi, > > A couple of weeks ago we started to plan Pharo4. This > work became stagnated for many reasons, but mainly > because I needed to travel to Argentina. > Now I'm slowly resuming the work and I wanted to share > with you what we have been talking/dreaming. > In esence, we have two important drivers for this release: > > 1) Improving tools > Turns out that we have introduced a lot of kernel > improvements (opal compiler, layouts, slots, etc.) and > tools are still not aware of them. Even worst: we have > traits since a lot of time and our tools are still now > aware enough to provide good interoperability. > But not just that: we have introduced things that are > not well used yet: keybindings (who do not want a > better keybindings structure... coherent and > editable?), spec should allow us to continue enhancing > existing tools and to replace old ones. > > 2) Modularisation > One of the fundamental ideas behind Pharo is to > provide a modular environment. But well... since Pharo > start to the moment, we prepared things to allow it, > but still few direct effort has been made. > In our dreams, Pharo should be built starting for a > small kernel image and adding different modules to get > a complete version. In this idea > Pharo=Kernel+GUI(Morphic)+Tools. > This has huge advantages (I do not think is necesary > to explain them, isn't ;)?) > > We brainstomed around this and we get this list of > issues (not all of them directly related to the > objectives, but well... good stuff also :) ) > > Web site: > - add catalog > - add videos > - enhance it in general > > Infrastructure: > - support more vm platforms > > VM: > - spur > - 64bits > - make vm embedable and UI independent (with SDL2 and > OSWindow) > > Image: > - Modularisation > - Removing old compiler > - Repackage Morphic (to allow better modularisation) > - Athens (replace old bitblt) > > Tools > - Replace changes with Ombu/Epicea > - Replace sources with a better abstraction > - Git support inside image (with libgit2 + tools) > - Pass on Spec > - Include Glamour? > - Make Ring unloadable > - Fonts with FreeType > > And lots of bugfixes :) > > We would like to exchange ideas with you. > So, what do you think? > > Esteban > > > > > > > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://www.phratch.com > http://car.mines-douai.fr/ > >

June 14, 2014