October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Commit rights to Pharo30Inbox

by Camillo Bruni

done On 2013-10-18, at 22:26, Attila Magyar <m.magyar3(a)gmail.com> wrote: > Hi list, > I want to submit a SLICE to the pharo inbox, can you grant me commit rights? > > username: zeroflag > > thanks!

Oct. 19, 2013

Re: [Pharo-dev] Anyone else teaching programming in Pharo?

by Hilaire Fernandes

Hi Jeff, Just to mention you can do Euclidean geometry programming with DrGeo from the a Workspace[1] to build math model. Hilaire [1] http://www.dailymotion.com/video/xrqjvx_1300-programmed-sketch_tech Le 18/10/2013 16:43, J.F. Rick a Ã©crit : > MicroWorlds for beginners to use (jumping directly into the browser is > too difficult for complete programming novices). One is for doing turtle > graphics. I've gone ahead and shared that for Pharo 2.0. You can get it > in the Configuration Browser under the name EduTech. If you have some > interest, let me know and I'll see what I can do. -- Dr. Geo http://drgeo.eu

Oct. 19, 2013

Re: [Pharo-dev] introduce Morphic-Core package

by StÃ©phane Ducasse

Ok I will have a look when I'm done with the color integration (I thank again fernando for leaving like that. Basically I had to redo everything :)). Stef > Hi, > > I created a slice that moves the most basic Morphic classes to the new > package named Morphic-Core. If we want to integrate it, it would be > better to do it soon to make the slice merging easier. > > https://pharo.fogbugz.com/f/cases/11901/introduce-Morphic-Core-package > > -- Pavel >

Oct. 19, 2013

Re: [Pharo-dev] Is there a Roadmap for Pharo 3.0 and Pharo 4.0

by StÃ©phane Ducasse

marcus I went up to chpater 4 I guess then my hd crashed On Oct 16, 2013, at 7:46 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Oct 16, 2013, at 4:32 AM, btc(a)openinworld.com wrote: >>> >>> >>> >>> >> Stef, >> >> A few weeks back I had occasion to review the Pharo Vision document again. In the process of adding an additional Use-Case, I ended up marking lots of small editorial improvements throughout the document. My focus was not on eliminating grammar mistakes by non-native-english authors (it was pretty good) - but more on trying to find the 'best' way to phrase something. Eliminating the sort of things that creep into my own writing until the third or fourth review, along the lines of that saying about the writing process... "The job is not done until there is nothing left to remove" >> >> cheers -ben >> <pharovision-btc-markup-2013-09-11.pdf> > > very nice! Thanks! > > I will make a pass to integrate your suggestions. > > Marcus

Oct. 19, 2013

can Spec applications add additional items to standard SystemWindow menu

by btc＠openinworld.com

I want a Spec application to add an additional item to the System Window Menu. Is this possible? So far I have missed how it might be done. This System Window Menu seems to come from... SystemWindow>>offerWindowMenu | aMenu | aMenu := self buildWindowMenu. model ifNotNil: [model addModelItemsToWindowMenu: aMenu]. aMenu popUpEvent: self currentEvent in: self world where #buildWindowMenu produces a standard menu from pragmas and custom model specific menu items can be added with #addModelItemsToWindowMenu:. In the case of PharoLauncher, 'model' is a MorphicWindowAdapter for which #addModelItemsToWindowMenu: is a null-method inherited from Object. So maybe 'model' needs to be a different class somehow? Alternatively, I see that SpecWindow inherits from SystemWindow, so maybe #buildWindowMenu can be overridden to add menu items from subclasses of ComposableModel ? cheers -ben

Oct. 19, 2013

Re: [Pharo-dev] enclosing compile errors & <PrintIt> in double quotes

by Tudor Girba

Exactly. There is no need anymore to have an "in-text" printed error. A non-modal popup (similar to a menu) would be a better solution. We should treat the result of print-it in the same way and offer it non-invasively. I put together a visual description of how such a widget would look like here: https://dl.dropboxusercontent.com/u/18323746/Tmp/coder/coder-pop-print.pdf Would anyone be interested to work on this widget? Doru On Sat, Oct 19, 2013 at 12:14 AM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Why not a small popup placed correctly ? > > Then it doesn't even corrupt your source code > > Ben > > On Oct 18, 2013, at 4:08 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > That is the first step :), if you have a decent text editor, > > you could add a real print-it or do-it token, which is not regarged as > source code, but just > as meta information. I think we could quite easily do this in Amber right > now ;). > > But yes, why not, sounds like a reasonable idea to put print-its and > compilation errors in double quotes. > > > On 2013-10-18, at 14:59, btc(a)openinworld.com wrote: > > > Just a random idea flitting thought my mind... When trying to <Accept> > some code with an error in it, the error message gets inserted into the > code such that it screws up syntax highlighting and also you need to use > <Undo> to remove it. I wonder if the error might be inserted between > double-quotes making it a comment. The same could be said for if you > <PrintIt> from a debugger. It seems such a simple and obvious idea that I > presume its been considered before and there are good reasons not to do it. > I am curious what others think might be the pros/cons of it. > In the case of <PrintIt> one benefit might be that the code could still be > saved, with the result left as a kind-of example. This might be good for > temporary code development in a Workspace. > > cheers -ben > > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 19, 2013

Re: [Pharo-dev] enclosing compile errors & <PrintIt> in double quotes

by Benjamin

Why not a small popup placed correctly ? Then it doesn't even corrupt your source code Ben On Oct 18, 2013, at 4:08 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > That is the first step :), if you have a decent text editor, > > you could add a real print-it or do-it token, which is not regarged as source code, but just > as meta information. I think we could quite easily do this in Amber right now ;). > > But yes, why not, sounds like a reasonable idea to put print-its and compilation errors in double quotes. > > > On 2013-10-18, at 14:59, btc(a)openinworld.com wrote: > >> >> Just a random idea flitting thought my mind... When trying to <Accept> some code with an error in it, the error message gets inserted into the code such that it screws up syntax highlighting and also you need to use <Undo> to remove it. I wonder if the error might be inserted between double-quotes making it a comment. The same could be said for if you <PrintIt> from a debugger. It seems such a simple and obvious idea that I presume its been considered before and there are good reasons not to do it. I am curious what others think might be the pros/cons of it. >> In the case of <PrintIt> one benefit might be that the code could still be saved, with the result left as a kind-of example. This might be good for temporary code development in a Workspace. >> >> cheers -ben >> >

Oct. 18, 2013

Commit rights to Pharo30Inbox

by Attila Magyar

Hi list, I want to submit a SLICE to the pharo inbox, can you grant me commit rights? username: zeroflag thanks!

Oct. 18, 2013

Re: [Pharo-dev] recovering from a deep disc crashâ¦.

by Nicolas Cellier

beautiful link 2013/10/18 Torsten Bergmann <astares(a)gmx.de> > Hardware that runs without problems must be from the "good old days". > > If Nico is right then I guess Pharo is already running on an "Ural-1"? > Where can I download the VM? > > http://en.wikipedia.org/wiki/Ural_(computer) > > I try to imagine the size of the apartment and the way it was stolen... ;) > > Thats why Native Boost is so fast on newer machines, it was handcraftet > on an old machine to speed it up... :) > > Bye > T. > > > Nico wrote: > >Igor, > >your hardware never failed? > >It must be some special brand crafted in former soviet union ;) > > > >2013/10/18 Igor Stasenko <siguctua at gmail.com> > > > >> thankfully, i never had problems with hardware: it serves me well. > >> But still didn't prevented from losing precious data: the humans who > break > >> into my apartment and stole the machine, > >> with all data it has :( > >

Oct. 18, 2013

Re: [Pharo-dev] [Vm-dev] Mac VM Maintainer resignation (for the general purpose VM, not for PharoVM)

by David T. Lewis

Esteban, Thank you very much for your contributions, and thank you also for clarifying your position. I know there is much more that you will be contributing to our community at large and I appreciate what you have done so far. Dave > > Hi, > > This is an announce for VM-dev and Squeak-dev list, Pharo-dev list is copy > to keep people informed. > > Last years I tried to keep a working version of the Mac builds of VM while > at the same time trying to keep my job going. It was a hard work but I did > my best. > When I assumed the responsibility I said that my first task was going to > be to automatize the builds and at the same time Igor was doing the same > so I joined that effort. Since then the VM is buildable even by the not so > good at VM level and I never seen the point in keeping the manual build or > the non-smalltalk-generated configuration files. > Nevertheless, I preferred to work on the new builds of Eliot than in the > old interpreter and when keeping all working became more work that what I > could manage, I choose to keep Stack and Cog VM working. > > Maybe because of that, or because the animosity between communities, or > because what I'm doing just does not match Squeak vision, or because since > Eliot is providing regular builds mine are not needed, truth is that I've > seen my work mostly ignored in squeak community and for some of the people > in vm-dev list. > > That's why I resign as a maintainer. I have a process that does not match > squeak vision and is fair for squeak community to look for someone who > does. > > I have no bad feelings, I'm complete grateful to the community for give me > the opportunity (specially to John, who thrusted me) and to all the rest. > > I also know that there is great people both in vm-dev and in squeak-dev, > but I cannot your mac-guy anymore (and I think this is obvious since > ever). > > And of course I will continue working in the pharo flavor of VM :) > > Cheers, > Esteban

Oct. 18, 2013