May 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by Sean Allen

> 11) We currently require infrastructure support for https eg stunnel or > reverse proxy through a webserver eg > http://www.monkeysnatchbanana.com/posts/2010/06/23/reverse-proxying-to-seas… > actually that link is... http://www.monkeysnatchbanana.com/posts/2010/06/22/faking-a-https-client-fo… just for posterity.

May 18, 2011

Re: [Pharo-project] Error loading update with AnObsoleteTranscript

by StÃ©phane Ducasse

Yes this is why we also removed from Transcript show: from deep down in the system. >From that perspective having a self log: would be better since we could control it. Right now there are plenty of places which holds a reference to the Transcript. What is strange is that the migration code was recompiling all the methods that had a reference to transcript so that they point to the new one. Stef > ahahahahhaha > > HAHAHAHAHAHAHAHAHHAHAHH > > SmalltalkImage >> fixObsoleteReferences > "SmalltalkImage current fixObsoleteReferences. > SystemNavigation default obsoleteBehaviors size > 0 > ifTrue: [ SystemNavigation default obsoleteBehaviors inspect. > self error:'Still have obsolete behaviors. See inspector']" > > | informee obsoleteBindings obsName realName realClass | > Smalltalk > garbageCollect; > garbageCollect. > CompiledMethod allInstances > do: [ :method | > obsoleteBindings := method literals > select: [ :literal | literal isVariableBinding > and: [ literal value isBehavior and: [ literal value isObsolete ]]]. > obsoleteBindings > do: [ :binding | > obsName := binding value name. > Transcript > show: 'Binding: '; > show: obsName; > cr. > realName := obsName copyReplaceAll: 'AnObsolete' with: ''. > realClass := Smalltalk globals at: realName asSymbol ifAbsent: [ UndefinedObject ]. > binding key: binding key value: realClass ] ]. > Behavior flushObsoleteSubclasses. > Smalltalk > garbageCollect; > garbageCollect > > > > remove that lines in yellow and try again :) > > > On Wed, May 18, 2011 at 12:30 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > When I do Smalltalk fixObsoleteReferences I have > AnObsoleteTranscript class DNU show: > :( > "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: BANLkTin_Q9ArEvU6qHZRcT2x9r3VLFp39w(a)mail.gmail.com... > > > On Wed, May 18, 2011 at 12:06 AM, Alain_Rastoul <alr.dev(a)free.fr> wrote: > Hi, > > Trying to upgrade my 1.3 image with Menu/System/Software Update, > I had a MNU during update 13191 at > AnObsoleteTranscript class >> cr > which comes from: > UndeclaredVariableWarning>>defaultAction > selector ifNotNil: [Transcript cr; nextPutAll: class name, '>>', selector, > ' '] > ifNil: [Transcript cr ]. > Transcript show: '(' , name , ' is Undeclared) '. > ^true > > Something is missing or I did something wrong? > > > Probably not. But probably Smalltalk fixObsoleteReferences also fixes it. > > > TIA > Regards, > Alain > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 18, 2011

Re: [Pharo-project] suppressing the ob ast navigation

by Tudor Girba

Hi again, Furthermore, ctrl+(left/right)arrow does not navigate through text words anymore. Instead, it seems to do the AST navigation :(. Cheers, Doru On 18 May 2011, at 12:40, Tudor Girba wrote: > Hi, > > In the latest OB, pressing ctrl+shift+(left/right)arrow gets you to navigate through the AST. This is certainly cool, but I could not find a usage for it yet :). > > But, the problem is that it overloads the ctrl+shift which in any text editor selects the previous/next word. > > If this feature is indeed wanted, could we find another keybinding solution for it? If not, how can I disable it in my image? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Presenting is storytelling." > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

May 18, 2011

Re: [Pharo-project] Basic tricks for improving a serializer?

by Henrik Sperre Johansen

On 18.05.2011 09:21, Martin Dias wrote: > > > On Tue, May 17, 2011 at 7:16 PM, Igor Stasenko <siguctua(a)gmail.com > <mailto:siguctua@gmail.com>> wrote: > > On 17 May 2011 22:58, Mariano Martinez Peck <marianopeck(a)gmail.com > <mailto:marianopeck@gmail.com>> wrote: > > > > > > On Tue, May 17, 2011 at 10:31 PM, Sven Van Caekenberghe > <sven(a)beta9.be <mailto:sven@beta9.be>> > > wrote: > >> > >> On 17 May 2011, at 21:57, Mariano Martinez Peck wrote: > >> > >> > Sven, I want to make it work :) > >> > > >> > so....the missing methods I told you that I need are: > >> > > >> > #nextStringPut: > >> > #nextNumber:put: > >> > #nextInt32Put: > >> > #nextWordPut: > >> > >> I guess these are pretty easy. But I think they clutter the > interface of > >> ZnBufferedWriteStream, so maybe you should make a subclass. > >> > > > > Yeah, don't worry. I can even duplicate the class hehehe > > > >> > >> > #contents > >> > > >> > Implement #contents I guess it is something like: > >> > > >> > ZnBufferedWriteStream >> contents > >> > ^ stream contents > >> > >> Why to you need #contents ? > > > > becasue I am an idiot. No, I don't need it. You are correct. > Thanks for > > asking. > > > >> > >> I would say that it goes a bit against the concept of a stream > as a sink > >> of data. > >> I haven't looked, but I would guess that saying #contents to a > FileStream > >> is not efficient. > >> > >> > Those missing methods I need are implemented > PositionableStream. I took > >> > the implementation from there and put it in > ZnBufferedWriteStream. > >> > I just added to them a first line " self flushBufferIfFull." > >> > >> That is probably OK, except when your string becomes larger > than the > >> buffer. Have a look at #nextPutAll: > >> > > > > I am not sure if I understood. The following are correct for > sure then: > > #nextNumber:put: > > #nextInt32Put: > > #nextWordPut: > > > > > > And #nextStringPut: is like this: > > > > nextStringPut: s > > "Append the string, s, to the receiver. Only used by > DataStream. Max > > size of 64*256*256*256." > > > > | length | > > self flushBufferIfFull. > > (length := s size) < 192 > > ifTrue: [self nextPut: length] > > ifFalse: > > [self nextPut: (length digitAt: 4)+192. > > self nextPut: (length digitAt: 3). > > self nextPut: (length digitAt: 2). > > self nextPut: (length digitAt: 1)]. > > self nextPutAll: s asByteArray. > > ^s > > > > Sorry, but i can't resist commenting on that. > Why, if you demand from stream to implement #nextInt32Put: > a the same time, you writing code like this > > self nextPut: (length digitAt: 4)+192. > self nextPut: (length digitAt: 3). > self nextPut: (length digitAt: 2). > self nextPut: (length digitAt: 1) > > ? > Then just extend your serializer with a notion of 'length' field, > which you can use for anything where you need to encode > length/size value, > but not just for Strings. > So, then the above method could be as short as: > > nextStringPut: s > self putLength: s size. > self nexPutAll: s asByteArray. > > and here you have a potential caveat because your string could be > WideString .. muhahaha. > > So, i suggest you to reconsider the way how you serializing strings. > Instead what you could do is to extend ByteString and WideString (and > perhaps similarily do for ByteSymbol and WideSymbol), > the methods which is responsible to turning a receiver in a sequence > of bytes, and then simply put it into output stream, > whatever it might be. > > Then you don't need #nextStringPut: because its > a) not polymorphic, because apparently serializing ByteString should > be different from serializing WideString > b) instead you implementing this in > Byte/WideString>>serializeToFuelStream: aStream and you done. > > > Yes, I am not sure if #nextStringPut: is not polymorphic, but I think > that with #serializeToFuelStream: we can avoid converting the > WideString to ByteArray just to write the ByteArray to the stream, and > instead just write the WideString to the stream. Right? You don't ever need the asByteArray call to store ByteStrings if you use nextPutAll: on a default stream in binary mode, the primitive handles that just fine for variableByte subclasses. If you are doing the same as DataStream, only ByteStrings are written using nextStringPut: , WideStrings are stored with the default writeWordLike: facilities. Is there a document describing the binary format of Fuel somewhere? Cheers, Henry

May 18, 2011

Re: [Pharo-project] [Seaside-dev] Re: [Esug-list] [ANN] SmallHarbour project

by Nick Ager

Hi, We are in the process of adding support for deploying GLASS applications > into the Cloud Foundry, but I wouldn't mind helping folks who are interested > in adding support for other Smalltalks into the Cloud Foundry ... The Cloud > Foundry is written largely in ruby, so you'll need to be wearing your ruby > dancing shoes:) > There certainly a lot of (justified) buzz around CloudFoundry at the moment. Building CloudFoundry infrastructure for Smalltalk deployment would appear to be a great approach - married with a hosting service that provides that infrastructure as a service. Nick

May 18, 2011

[Pharo-project] suppressing the ob ast navigation

by Tudor Girba

Hi, In the latest OB, pressing ctrl+shift+(left/right)arrow gets you to navigate through the AST. This is certainly cool, but I could not find a usage for it yet :). But, the problem is that it overloads the ctrl+shift which in any text editor selects the previous/next word. If this feature is indeed wanted, could we find another keybinding solution for it? If not, how can I disable it in my image? Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

May 18, 2011

[Pharo-project] Decompiler problem (leading to infinite loop of opening debuggers)

by Johan Brichau

Hi, In Pharo1.2.x, I get an infinite recursion of a debugger windows opening when I load a metacello config that has a problem in it. The relevant problem can be reconstructed (without the infinite loop :-) by evaluation the following: (MetacelloMCVersionSpec compiledMethodAt: #resolveToLoadableSpecs:map:) decompileWithTemps I'm absolutely no compiler guy, so I'm totally unaware of what is happening. But it's serious because I cannot debug the actual problem of the metacello config because of this. It was tried with Pharo1.2.1 and Pharo1.2.2-12353 and latest Cog VM (27 April 2011). I entered issue 4241 in the bug tracker for this. Johan

May 18, 2011

Re: [Pharo-project] [TODO] 1.3

by Norbert Hartl

That all makes completely sense. As I'm working with zinc now I'm going to switch to 1.3 immediately. Norbert Am 18.05.2011 um 09:18 schrieb Marcus Denker: > Current status: > > ==> all 1.3 builds are green > ==> Open Issues Core: 20 > ==> Open Issues Full: 3 > > So we are now in the state of "we could release next Friday". Thus the idea is now to steadily integrate what will happen, > while keeping the status green. > > Thus we can focus on other things as the Next Most Important Issue. e.g. > > Get VM build system in a state so we can ship 1.3 with VMs build by or Hudson (soon Jenkins): > > The idea here is to > > a) simplify the VM story. There are too many VMs, each with each own version-number. Very confusing. > b) not have to wait with deployment for a "maintainer" to release a VM every 2 years, but instead use the latest code base > within hours of a bugfix. > c) be able to actually improve the VM while in unstable. > > Thus we will > - provide a "Pharo Cog $VersionNumber" vm. This will make it easy to anwer the question of "which VM should I use" > - generate the archives one-click as well as the VMs listed on the website from the self-build VMs > > The good news is that we now have a window build slave, so we will soon have all 3 major architectures covered. > > On May 16, 2011, at 9:15 AM, Marcus Denker wrote: > >> Core >> ==== >> >> Open Issues: 20 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 >> Failing Tests: 1 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >> >> Full >> === >> Open Issues: 8 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage >> Failing Tests: 3 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… >> >> >> => Most important next Issue to tackle: Get all tests green. >> >> It would be nice to get both Core and Full green. Than the idea is that in the spirit of Continuous >> Delivery, we just keep it green. No degeneration of trivial problems (undeclards), fast roll-back of >> problematic changes... >> >> The idea is to keep it in a state that we could, at a minumum, always say "We could release next Friday". >> And the best would be: "We could release today". >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 18, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by laurent laffont

On Wed, May 18, 2011 at 10:50 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > You should check out: > > http://vagrantup.com > > It could help you automate the build of virtual environments > (virtual box). > OK, thank you Torsten. Laurent. > > Bye > T. > > > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone > >

May 18, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by laurent laffont

Thanks a lot Nick for your feedback, it is helpful. Laurent. On Wed, May 18, 2011 at 9:46 AM, Nick Ager <nick.ager(a)gmail.com> wrote: > Hi Romain, Laurent, > > >> Having Amazon ec2 image is also a very good idea, and some >>>> Smalltalkers have already made first important steps like: >>>> >>>> >>>> http://www.nickager.com/blog/Create-a-free-Gemstone-server-in-the-cloud-in-… >>>> >>> > After having shared the above Amazon AMI (Amazon machine image), and > experimented with EC2 hosting, I realised there are some undesirable > properties of AMIs: > > 1) It's an image; with all the benefits and problems that entails; namely > either you like the whole thing or not. It's not composable; it's difficult > to know precisely what has been configured and how, and difficult to choose > the bits you like and replace the bits you don't like. > 2) You can't (currently for Linux), create an AMI locally and upload it, > meaning everything has to be performed remotely and operating remotely in > the IDE over X11 forwarding can be slow. > 3) It's difficult to share across regions. Amazon's data centres operate > autonomously. I created the image in EU-WEST and copying it to US-WEST or > US-EAST is non-trivial. > 4) It's another configuration that I need to keep up to date and I don't. > 5) Not everyone wants to use EC2; other cloud services are available eg > slicehost, linode, cloud-foudry etc > 6) I configured the AMI using Amazon Linux, people might prefer Ubuntu, > RHEL, Suse, Windows!#*? etc > 7) I configured the AMI using Nginx as a front-end server with added > modules (http://nickager.com/blog/compiling-nginx-to-add-extra-modules/) > others might require other modules or other different server eg Apache, > Cherokee etc. Even with the same server the configuration required can vary > (url redirection, static file serving etc). > 8) Everyone has a different way of performing backups, monitoring the > health of the server. > 9) I configured the AMI using Gemstone, others might prefer image based > persistence or MySQL, Postgres etc. > 10) Ideally the configuration would allow you to specify the number of > images (or Gems for Gemstone) you'd like to respond to request, behind a > load balancer. > 11) We currently require infrastructure support for https eg stunnel or > reverse proxy through a webserver eg > http://www.monkeysnatchbanana.com/posts/2010/06/23/reverse-proxying-to-seas… > > Quite a list... The main issue is that I'd like to be able to build server > infrastructure from composable pieces and share configuration knowledge with > others. This led me to Chef (http://opscode.com/chef/) where people create > configuration "recipes" and a specific configuration is composed from these > recipes. The benefit of using something like Chef is that there are > already recipes for the standard parts of the server configuration eg > installing and configuring Apache, Nginx, MySql, Postgres etc have already > been taken care of. Chef abstracts the OS, and the cloud (eg EC2, slicehost > etc). > > The task is then to create recipes for Seaside specific parts. There are a > couple of Gemstone recipes already ( > https://github.com/timfel/gemstone-cookbooks, > https://github.com/johnnyt/gemstone-cookbooks) A few of us (myself > Norbert Hartl, Stephen Eggermont) plan to investigate coding our > configurations is Chef - though it's still early days and it may prove that > it's more complex than we need. > > Our basic requirements are to be able to rapidly deploy production, > staging, backup, Jenkins continuous integration and development VMs. > > Do others have experience with Chef or something similar? > > Ideally ESUG or someone else would provide http://www.heroku.com/ for > Seaside - but it would require formalising more of our stack and providing a > flexible solution to https. > > Hope this helps, > > Nick >

May 18, 2011