- Pharo-dev - lists.pharo.org

Re: [Pharo-project] corrupt images on gforge

by StÃ©phane Ducasse

thanks christopheâ¦. I will comment publicly. Stef On Jan 2, 2013, at 4:43 PM, Christophe Demarey wrote: > I tried to fix it. It seems we reach a disk quota on the forge :( > lsebot@ff-scm-v4-prod:/home/groups/pharo/htdocs/ci/image/20$ cp -f 20459.zip latest.zip > cp: closing `latest.zip': Disk quota exceeded > lsebot@ff-scm-v4-prod:/home/groups/pharo/htdocs$ du -sh . > 10G > > I will send an email to forge admins to ask more disk space. > > Christophe. > > Le 30 dÃ©c. 2012 Ã 16:50, Camillo Bruni a Ã©crit : > >> see http://code.google.com/p/pharo/issues/detail?id=7196 >> >> I suggest someone other than me fixes it ;) to >> - add missing documentation >> - see how complicated everything is >> > >

Jan. 2, 2013

Re: [Pharo-project] alert: not defined on non-interactive ui manager

by StÃ©phane Ducasse

>> alert:, alert:title:... are defined on MorphicUIManager but not on NonInteractiveUIManager >> so this means that we get DNU when loading packages that call it. >> >> http://code.google.com/p/pharo/issues/detail?id=7205 >> >> I thought that bringing a pop up or dun in non interactive mode was killing the system >> but not. I'm confused but any how it would be good to have these two classes a bit more >> polymorphic so tell me if I'm saying something stupid. >> >> Stef > > When i first added NonInteractiveUIManager , i made sure that all protocol in > UIManager is supported. > Then, people adding more stuff to MorphicUIManager without: I do not think that we added anything to MorphicUIManager. May beâ¦ when we merged some code of gary. > a) declaring new protocol in abstract UIManager and describing > intended behavior there > b) making sure it works (or has default behavior) in rest of classes, > not just MorphicUIManager > > UI manager has too many responsibilities. But it is hard to see how we > can avoid that It would be good to have a look at the protocol and see if we can deprecate one or two. But then in addition we can add placeholders in nonInteractiveâ¦ Stef

Jan. 2, 2013

Re: [Pharo-project] Escape key to remove a debugger...

by Chris Muller

Hi Alexandre, > Pressing "Abandon" in a pre-debugger window is cumbersome. Indeed, requiring a fine-motor gesture for something so simple wears on productivity all day long. > It would be cool to press esc to remove it. > What would be the easy way to do this? Have you tried Command+W? Any window can be easily closed by simply moving the cursor out of the window (perhaps toward the window you want to visit next) and press Command+W. I never use the X (nor Abandon) on any window any more because Command+w is much easier. Now, in Squeak we also added Command+\ to send the current window to the back so, now to clean up the desktop simply position the mouse anywhere on the desktop and repeatedly press Command+w and Command+\ for the windows to remove/save, respectively.

Jan. 2, 2013

Re: [Pharo-project] About morph layout

by Chris Muller

Craig's NAIAD stands for "Name And Identity Are Distinct". Just thinking aloud -- because Morphic is so entrenched.. Could NAIAD or Colin's Environments allow Juan's Morphic (or, Morphic3) to co-exist with original Morphic, so that it would allow working on the port without depending on it for the tools? Once the port was complete, a sane migration could more easily occur.. On Wed, Jan 2, 2013 at 7:00 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 2 January 2013 12:55, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Hello again Igor >> and Happy and Successful New "Pharo" Year 2013 >> > > Thanks Hannes :) > Wish best to you in New Year too :) > > >> --Hannes >> >> my notes are inserted below. >> >> >> On 12/24/12, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> On 24 December 2012 09:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>> Hello Igor >>>> >>>> Thank you for this interesting mail. An issue over 11 years old, see >>>> below. >>>> >>>> On 12/24/12, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>>> Hi, >>>>> >>>>> just wanna share some ideas about how we can cleanup morph a bit. >>>> >>>> A bit? >>>> It will be a lot of effort. >>>> >>> We can do it in small steps. >>> >>>> Squeak 4.4-12234 (current) >>>> >>>> Morph selectors size 1183 >>>> >>>> >>>> Pharo 2.0 (Beta) >>>> >>>> Morph selectors size 865 >>>> >>>> >>>> Cuis 4.1 (18th Dec 2012) >>>> >>>> Morph selectors size 343 >>>> >>>> >>>> This was an issue in 2001 >>>> >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2001-June.txt >>>> >>>> see >>>> >>> I am not first day here, of course i am aware of this :) >> >> Did you start working with Squeak already in 2001? >> > no. But i know this is a long standing issue :) > >>>>> Layout.. bizarre. >>>> >>>> Yes, see humorous contribution from June 2001 >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2001-June.txt >>>> >>>> search for >>>> >>>> the Morph class has 924 methods >>>> >>>> in that mails >>>> >>>> There was an effort >>>> Morphic Cleanup Project >>>> >>>> http://wiki.squeak.org/squeak/3005 >>>> >>>> lead by >>>> >>>> Diego Gomez Deck >>>> >>>> It produced some results. But they did not reach far enough. >>>> >>> yes yes.. i know. >>> >>>> However Juan Vuletic was successful in coming up with a simpler Morphic in >>>> Cuis. >>>> >>>> http://www.jvuletich.org/Cuis/Index.html >>>> >>> search this mailing list for Small Morphic. >>> It was an attempt to use Juan's work, which didn't fly. >> >> Of course I am aware of SmallMorphic. If a first attempt at >> integrating SimpleMorphic into Pharo was not successful it does not >> necessarily mean that a second one has to be a failure again. >> >> Time spent on an analysis why it didn't fly is surely not a waste. >> >> For example another approach could be instead of copying code from >> Cuis and implanting it into Pharo "blob style" you could follow Juan >> Vuletich's refactoring steps incrementally and copy smaller chunks of >> code. Cuis had many releases until it reached version 4.1. >> >> In terms of factoring out classes from the class Morph you seem to >> want to do that anyway. >> >> See for example >> >> http://www.jvuletich.org/Cuis/CuisReleaseNotes.html >> New in Cuis 2.7 (released September 3, 2010) >> >> * Morphic. New LayoutSpec mechanism. Simpler and nicer. >> * Morphic Simplification: Layout, Extensions, etc >> > > Well, one thing is that Juan doing quite radical changes to code. > He is not concerned about backwards compatibility (but unlike from Pharo, nobody > raising it as an issue over and over again ;) ). > Yes, i checked new Cuis code. > I see a lot of simplifications. But also i see reduced functionality. > For instance, i did not found things like 'fill style', and themes. > Also, i see some protocols is renamed, in preparation for something > bigger (morphic 3 i guess ;) > > So, i agree we should not copy/paste the code. Because it won't fly. > We should gradually analyze it and improve ours step by step. > > Layout code in Cuis is somewhat similar to what i proposing. > But my proposal is essentially about approach, which you can apply to > anything.. not just layouts in Morphics. > >>>>> There are so many methods dedicated to laying out morphs that it easy >>>>> to get lost. >>>> >>>> Cuis has a new layout system. >>>> >>>> Worth to check out. >>>> >>> Sure. >> >> Fine. >> >>> >>>>> For me the main mystery and source of confusion is that there actually >>>>> two different groups: >>>>> >>>>> - methods to control morph's own layout (in respect to its parent) >>>>> - methods to control morph's children layout (something called >>>>> layoutPolicy) >>>>> >>>>> the problem is that both APIs are found in single class, >>>> >>>> which one? >>>> >>> Morph >>> >>>> and most of >>>>> them contain 'layout' word in it, >>>>> so it is really hard to determine which one to use and when.. >>>>> >>>>> Over a years, i seen that people learned how to use existing >>>>> functionality, without delving deep into >>>>> implementation detail. >>>> >>>> Yes. >>>> >>>>> But if you try to extend/change behavior (in your subclass), you will >>>>> quite soon find out that it is really >>>>> hard to tell with 100% certainty that the methods you override is the >>>>> right place for your customization. >>>> >>>> Yes, this actually has made development very difficult. In such a way >>>> that most people have abandoned it. Very few GUIs are actually built >>>> with it. >>>> >>>> >>>>> Also, an important detail is extremely polluted protocol(s), making >>>>> Morph a GOD class, >> >> Morph is at the root of a large subclasses tree. The question is: what >> can be pushed down or factored out. An analysis in terms of number of >> method candidates to move out would surely be a good thing to know. >> > > > > -- > Best regards, > Igor Stasenko. >

Jan. 2, 2013

Re: [Pharo-project] Extracting a ZipArchive in 2.0

by Vanessa PeÃ±a Araya

Hi Camillo, Thank you for your reply. Yes, I understand, but I was wondering from the ZipArchive side. I mean, what I don't understand is if I'm using the wrong method (ZipArchive>>#extractAllTo:) or if ZipArchive is not updated to FileReference, or something else I'm not seeing :) Thanks, Vanessa. On 12/28/2012 07:38 PM, Camillo Bruni wrote: > try to have a look at the other ensure* methods on FileReference or AbstractFileReference. > I think you need #ensureFile or #ensureDirectory :) > > On 2012-12-27, at 17:28, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: > >> Hi, >> >> I want to extract a ZipArchive in Pharo 2.0, as the title says. I'm trying to do it with this: >> >> zipArchive >> extractAllTo: aDirectory >> informing: bar >> overwrite: false >> >> I'm trying the new file system but my problem is that ZipArchiveMember calls a method called "assureExistence", which does not exist... anywhere. >> >> Has anyone experience something like this? >> >> Thanks, >> Vanessa. >> > >

Jan. 2, 2013

Re: [Pharo-project] UITheme builder, change newList list onButtonClick

by Ben Coman

I only used Polymorph for the first time a couple of months ago. I don't really know what is available, but having a quick poke around what I found was: 1. If you follow the call-chain from UITheme>>newListFor:list:selected:changeSelected:help: you end up in UITheme>>newListIn:for: list: selected: changeSelected: getEnabled: help: which uses PluggableListMorph 2. There is also PluggableMultiColumnListMorph (read its comment) but if if you check "References" for it, it does not appear to be used by UITheme So the short answer seems to be - no, Polymorph doesn't out of the box support multi-column lists. The long answer - the components seem to be available for you to add multi-column-lists to Polymorph yourself - perhaps just replicating the call-chain from (1.) to end up using PluggableMultiColumnListMorph) cheers -ben J. P. L. MartÃn wrote: > I got everything working besides the list update when changed. Also, is > there anyway to properly display data in columns? This is what i have: > http://i.imgur.com/bwK2M.png > > > On Wed, Jan 2, 2013 at 11:47 AM, Ben Coman <btc(a)openinworld.com> wrote: > > >> J. P. L. MartÃn wrote: >> >> Hello, I'm having trouble to figure out how to do this, I have a simple >> >>> window with 3 buttons, each button should change the content listed on the >>> list below them but I'm really not sure about how to do it. >>> >>> This is the code for the window: >>> --- >>> open >>> "Abre la ventana principal del Sistema de Gestion Bibleotecaria" >>> >>> | builder contain | >>> builder := UITheme builder. >>> contain := builder newColumn: {builder newRow: { >>> builder newButtonFor: self action: #onPrestamosClick label: >>> 'Prestamos' help: ''. >>> builder newButtonFor: self action: #onMaterialesClick label: >>> 'Materiales' help: ''. >>> builder newButtonFor: self action: #onSociosClick label: >>> 'Socios' help: ''}. >>> builder newColumn: { >>> builder newListFor: self list: nil selected: nil >>> changeSelected: nil help: '' }.}. >>> >>> (contain openInWindowLabeled: 'Babel') extent: 600@600. >>> --- >>> >>> How should I define #onLabelClick to set the list to for example: Prestamo >>> database. >>> >>> Thanks in advance. >>> >>> >>> >>> >> J. P. L. MartÃn wrote: >> >> >>> Actually the code of the GUI is inspired on the Pharocast video on the >>> making of a Contact list. I wonder if the list is static since is defined >>> there as a newListFor and because that you can't send any message to it, >>> >>> >>> >> The #changed: method tells the list to get its contents again - see >> example below. >> >> >>> I'm sure there should be a way to do it so #onPrestamosClick look like: >>> --- >>> #onPrestamosClick >>> listMorph list: Prestamo database. >>> --- >>> or something like that. >>> >>> >>> >>> >>> >> You didn't explicitly state your references, I presume you a referring to >> http://www.pharocasts.com/**2011/02/pharo-gui-with-**polymorph.html<http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html> >> . >> Note that ContactManager-**LaurentLaffront.1.mcz referred to from this >> post uses... >> >> |builder newListFor: self list: >> #contacts >> selected: #contactSelectedIndex >> changeSelected: #contactSelectedIndex: >> help: ''.| >> >> whereas you have... >> >> builder newListFor: self list: nil >> selected: nil >> changeSelected: nil help: '' >> which is the key part you are missing, where the (list: #contacts) defines >> the method to return the list contents, for example... >> --- >> #contacts >> ^ Contact database collect: [:aContact| >> ', ' join: {aContact lastName. aContact firstName} >> ]. >> --- >> >> >> You have defined your list contents as (list: nil), whereas if it was >> (list: #selectedDatabase) the following might work... >> --- >> #onPrestamosClick >> >> selectedDatabase := Prestamo database. >> self changed: #selectedDatabase. >> --- >> #selectedDatabase >> ^selectedDatabase. >> >> --- >> >> good luck, >> cheers -ben >> >> >> >> > >

Jan. 2, 2013

Re: [Pharo-project] alert: not defined on non-interactive ui manager

by Igor Stasenko

On 2 January 2013 16:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all > > alert:, alert:title:... are defined on MorphicUIManager but not on NonInteractiveUIManager > so this means that we get DNU when loading packages that call it. > > http://code.google.com/p/pharo/issues/detail?id=7205 > > I thought that bringing a pop up or dun in non interactive mode was killing the system > but not. I'm confused but any how it would be good to have these two classes a bit more > polymorphic so tell me if I'm saying something stupid. > > Stef When i first added NonInteractiveUIManager , i made sure that all protocol in UIManager is supported. Then, people adding more stuff to MorphicUIManager without: a) declaring new protocol in abstract UIManager and describing intended behavior there b) making sure it works (or has default behavior) in rest of classes, not just MorphicUIManager UI manager has too many responsibilities. But it is hard to see how we can avoid that. -- Best regards, Igor Stasenko.

Jan. 2, 2013

[Pharo-project] FOSDEM 2013 Smalltalk devroom

by Rafael Luque

Hi Pharoers, I've noticed that FOSDEM 2013 will host an Smalltalk devroom like the previous year. Any idea about the scheduled sessions? I'd like to see tutorials related with Pharo, Seaside, Amber, Moose, etc. Thank you.

Jan. 2, 2013

Re: [Pharo-project] corrupt images on gforge

by Christophe Demarey

I tried to fix it. It seems we reach a disk quota on the forge :( lsebot@ff-scm-v4-prod:/home/groups/pharo/htdocs/ci/image/20$ cp -f 20459.zip latest.zip cp: closing `latest.zip': Disk quota exceeded lsebot@ff-scm-v4-prod:/home/groups/pharo/htdocs$ du -sh . 10G I will send an email to forge admins to ask more disk space. Christophe. Le 30 dÃ©c. 2012 Ã 16:50, Camillo Bruni a Ã©crit : > see http://code.google.com/p/pharo/issues/detail?id=7196 > > I suggest someone other than me fixes it ;) to > - add missing documentation > - see how complicated everything is >

Jan. 2, 2013

Re: [Pharo-project] Escape key to remove a debugger...

by StÃ©phane Ducasse

On Jan 2, 2013, at 12:59 PM, Alexandre Bergel wrote: > Hi! > > Pressing "Abandon" in a pre-debugger window is cumbersome. It would be cool to press esc to remove it. > What would be the easy way to do this? + 1 probably :)

Jan. 2, 2013