November 2013 - Pharo-users

Re: [Pharo-users] Updating Pharo 2 - Unable to resolve ConfigurationOfFuel

by Marcus Denker

On 04 Nov 2013, at 08:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 04 Nov 2013, at 00:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> But marcus we are doing update all the time because this is the way we push new updates daily. >> So I do not understand why this would be different? >> > > It happens due to strange things: updates that access the web and URLs change, for example. > Or in the past one problem was that it could overload squeak-source to load for hours and hours packagesâ¦ > > And it takes quite some care to keep it going: when *really* bad things happen, we now (once or twice in a year) > upload a fixed image that is than taken as the base. If you want to support âtake pharo2 and update it to pharo3â, > (or even, take Pharo3 half a year agoâ¦), then we need to put *a huge* (very huge) effort into making sure that > we never ever upload a hand-fixed image. > This is a lot of work. > > And in addition, even that does not guarantee anything: you would need to actually test itâ¦ > So in the end, when we get the the bootstrap into Pharo4, this would even mean that keeping an incremental updater would be completely additional work. Like they do with Chromeâ¦ I am sure one could generate the diff automatically and detect the cases when it does not work (and tell the user). Would be an interesting research project. Marcus

Nov. 4, 2013

Re: [Pharo-users] Updating Pharo 2 - Unable to resolve ConfigurationOfFuel

by Marcus Denker

On 04 Nov 2013, at 00:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > But marcus we are doing update all the time because this is the way we push new updates daily. > So I do not understand why this would be different? > It happens due to strange things: updates that access the web and URLs change, for example. Or in the past one problem was that it could overload squeak-source to load for hours and hours packagesâ¦ And it takes quite some care to keep it going: when *really* bad things happen, we now (once or twice in a year) upload a fixed image that is than taken as the base. If you want to support âtake pharo2 and update it to pharo3â, (or even, take Pharo3 half a year agoâ¦), then we need to put *a huge* (very huge) effort into making sure that we never ever upload a hand-fixed image. This is a lot of work. And in addition, even that does not guarantee anything: you would need to actually test itâ¦ >> >>> no you dont do anything wrong, unfortunately from what I have been told the update process is broken. Right now the best choices is to download directly from pharo website >>> >> The problem is that how images are used is shifting: People used to use an image for a long time, updating the base from time to time while their code >> was in the image. >> >> These days, what people do is to have an automatic (and well defined) process that build a fresh image on >> -> base system is updated >> -> Own code commit >> >> So e.g. I never retain images after I finish something. I commit, wait for the build system to tell me everything is green, and I throw the image >> away. Images are transient things. >> >> This in turn means nobody uses updating, and this means that it is not tested. and everything not tested brakes after a whileâ¦. >> (In turn, everything we want to be sure works needs to be tested after every commit, but testing âupdating every old version to the newestâ >> is not really testable, anaywayâ¦) >> >> When we move to an image-bootstrap for the development of Pharo itself (I guess in Pharo4), we should really check what and how (and if) we >> support updating existing images, or if we declare the image to be something that *always* be the result of a deterministic build processâ¦ >> >> Marcus >> >> > >

Nov. 4, 2013

Re: [Pharo-users] Yet another "building a GUI" question

by StÃ©phane Ducasse

On Nov 4, 2013, at 2:37 AM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > 2013/11/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > tx and archived! > And your enh is in the new integration :) > > > Yay! Scratching an itch and contributing something feels great :) :) Yes pay attention when you start to like that you learn and lot and you start to be addict :) Stef

Nov. 4, 2013

Re: [Pharo-users] Yet another "building a GUI" question

by Sergi Reyner

2013/11/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > tx and archived! > And your enh is in the new integration :) > > Yay! Scratching an itch and contributing something feels great :)

Nov. 4, 2013

Re: [Pharo-users] Yet another "building a GUI" question

by StÃ©phane Ducasse

tx and archived! And your enh is in the new integration :) On Nov 4, 2013, at 12:56 AM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > Sent to your mail, Stef! > > > 2013/11/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Sergi > > could you sign the Pharo license agreement and send it to us (scanned for example)? > > Stef > > On Nov 3, 2013, at 11:10 PM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > >> >> El 03/11/2013 21:45, "Benjamin" <Benjamin.VanRyseghem.Pharo(a)gmail.com> escribiÃ³: >> > >> > I think I missed the beginning of this thread :) >> > So my question is what do you want to do ? :) >> >> I want to have a way to get an AlphaImageMorph linked to a ValueHolder(?) holding a Form(?), and having it update automatically, for example in response to selecting an item from a list. >> >> Cheers, >> Sergi >> > >

Nov. 4, 2013

Re: [Pharo-users] Updating Pharo 2 - Unable to resolve ConfigurationOfFuel

by Mariano Martinez Peck

Bahman, Hi, Fuel was moved some time ago from SS3 to SmalltalkHub. Could it be that it was searching ConfigurationOfFuel in SS3? On Sun, Nov 3, 2013 at 3:10 AM, Bahman Movaqar <Bahman(a)bahmanm.com> wrote: > Hi all, > > I just downloaded Pharo 2.0 on a Windows machine, unpacked it, ran it > and from the world menu selected System -> Software Update but bumped > into an exception: > > <stacktrace> > > Error: Unable to resolve ConfigurationOfFuel > > GoferConfigurationReference(Object)>>error: > GoferConfigurationReference(GoferReference)>>resolveWith: > Gofer>>resolved in Block: [:each | each resolveWith: self] > Array(SequenceableCollection)>>collect: > Gofer>>resolved > GoferLoad>>initializeOn: > GoferLoad class(GoferOperation class)>>on: > Gofer>>execute:do: > Gofer>>execute: > Gofer>>load > ScriptLoader>>update20608 > UndefinedObject>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > Compiler class>>evaluate:for:notifying:logged: > Compiler class>>evaluate:for:logged: > Compiler class>>evaluate:logged: > DoItDeclaration>>import > CodeImporter>>evaluateDeclarations in Block: [:decl | value := decl > import] > OrderedCollection>>do: > CodeImporter>>evaluateDeclarations > CodeImporter class>>evaluateReadStream: > ChangeSet class>>newChangesFromStream:named: in Block: [| newStream > |... > BlockClosure>>ensure: > ChangeSet class>>newChangesFromStream:named: > UpdateStreamer>>elementaryReadServerUpdates: in Block: [| docQueue > docQueueSema |... > BlockClosure>>ensure: > CursorWithMask(Cursor)>>showWhile: > UpdateStreamer>>elementaryReadServerUpdates: > UpdateStreamer>>elementaryReadServerUpdates > UpdateStreamer>>updateFromServer in Block: [self > elementaryReadServerUpdates] > > </stacktrace> > > This is an ablsolutely fresh Pharo instance. Am I doing anything > wrong? How can I resolve this? > > TIA, > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > > -- Mariano http://marianopeck.wordpress.com

Nov. 4, 2013

Re: [Pharo-users] Yet another "building a GUI" question

by Sergi Reyner

Sent to your mail, Stef! 2013/11/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Sergi > > could you sign the Pharo license agreement and send it to us (scanned for > example)? > > Stef > > On Nov 3, 2013, at 11:10 PM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > > > El 03/11/2013 21:45, "Benjamin" <Benjamin.VanRyseghem.Pharo(a)gmail.com> > escribiÃ³: > > > > I think I missed the beginning of this thread :) > > So my question is what do you want to do ? :) > > I want to have a way to get an AlphaImageMorph linked to a ValueHolder(?) > holding a Form(?), and having it update automatically, for example in > response to selecting an item from a list. > > Cheers, > Sergi > > >

Nov. 3, 2013

Re: [Pharo-users] Yet another "building a GUI" question

by StÃ©phane Ducasse

Sergi could you sign the Pharo license agreement and send it to us (scanned for example)? Stef On Nov 3, 2013, at 11:10 PM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > > El 03/11/2013 21:45, "Benjamin" <Benjamin.VanRyseghem.Pharo(a)gmail.com> escribiÃ³: > > > > I think I missed the beginning of this thread :) > > So my question is what do you want to do ? :) > > I want to have a way to get an AlphaImageMorph linked to a ValueHolder(?) holding a Form(?), and having it update automatically, for example in response to selecting an item from a list. > > Cheers, > Sergi >

Nov. 3, 2013

Re: [Pharo-users] I would rather pay for Smalltalkhub than use Github for free.

by StÃ©phane Ducasse

+1 Pharo should be Pharo :) And we should all push in that direction - minimal core - sweet integration with the rest of the world - objects - cool libraries > I think that we should be passionate about what we are doing. Look at Scala for example. Itâs becoming quite popular, and it was developed for 10 years. Pharo still has a lot of time to attract people, but we need to push something new. Itâs not java like smalltalk, or something smalltalk-inspired that looks like C. For me Pharo is what had to happen to Smalltalk: evolution. Usually Smalltalk is mentioned with â80â suffix. Pharo is Smalltalk2013. And we can make it really cool, but we should stick to smalltalk philosophy. Having tools, working with objects, etc...

Nov. 3, 2013

Re: [Pharo-users] Building a simple UI with Spec. Problem with menus.

by StÃ©phane Ducasse

Hi I will integrate some fixes now. Stef > Hello and welcome :) > > > On 03 Nov 2013, at 18:36, nacho <0800nacho(a)gmail.com> wrote: > >> Hi, this is my first post in the Pharo group. >> I'm developing a simple Text Editor with some nice features as a way to >> understand how Spec works. It seems that Spec will be the default UI >> framework from Pharo 3 onwards, I know it's changing and evolving but I'll >> take the risk. > > Good to hear :) It is quite changing now, but should not change a lot starting from now (plus a couple of days > waiting for the last changes to be integrated). > >> The problem I'm facing is that I'm lost at trying to add a "Save as..." >> option in the menu. > > As far as I know, there is a bug in TextModel where the menu is hardcoded, and therefor can not be changed. > In addition, as you have said, it is currently using directly Morphic menus that is bad. > > The issue 12051 [1] introduces Spec models for menus. The fix has yet to be integrated. > So there are two solutions :) > 1) You wait a bit tip this issue is integrated, and the TextModel problem solved (which should be done tonight) > 2) You load locally the patches so you can try :) > If you wanna do so you need to take the latest image and to merge the slices: > - 11920 (this one will give you merge conflicts, you can safely take all the incoming versions) > - 12051. > - 11819 as soon as it is fixed > >> It seems that Spec is still using the Morphic MenuMorph>>ToggleMenuItemMorph >> but it's not clear to me hoy to add this item. >> On the other hand, inspecting the ComposableModel class, it seem that in the >> future this will be done directly in Spec as suggested by the >> ComposableModel>>addMenuItemsToWindowMenu: > > This method is to add custom menu entries to the window menu :) > > Ben > >> But so far that method simply says "do nothing". >> Any help? >> Thanks in advance >> Cheers >> Nacho >> >> >> >> -- >> View this message in context: http://forum.world.st/Building-a-simple-UI-with-Spec-Problem-with-menus-tp4… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > [1] https://pharo.fogbugz.com/default.asp?12051

Nov. 3, 2013