April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Ehh??? cannot fileout with Nautilus and RPackage?

by StÃ©phane Ducasse

On Apr 19, 2012, at 5:40 PM, Mariano Martinez Peck wrote: > fileOut > > self error: 'I should be implemented somehow' > > mmmmmmm Yes a good soul should sit and add the magic invocation. > > > -- > Mariano > http://marianopeck.wordpress.com >

April 19, 2012

Re: [Pharo-project] Long click on pluggeable button

by phil＠highoctane.be

Interacting with tablets and touch is indeed a different experience (just inputting numbers properly is big - gestures would be great for example). Longpress or double touch is also to be discussed. For editing a point, you'd be better off with two fingers or a double touch. I am experimenting with this with my iPad app (not in Smalltalk but for the end user it is the same). Also, swiping gestures require some recording and effects over time. Best is to have a low level thing that picks up the touch events and a set of event handlers that do get the notification when all the low level messy thinking is done. Otherwise the app code gets cluttered as hell. Well, that's my 0.02 EUR. I am *very* interested in prototyping such things, beta testing and so on. Phil 2012/4/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hilaire > > we should just continue and slowly but steadily fix and simplify. > We have been doing it and we will continue. Now if you have concrete with > examples suggestions > please let us know. > > Stef > > > Responding to myself as it may be useful to other: > > > > > > btn showSelectionFeedback: false. > > btn changed. > > > > but well. > > > > Hilaire > > > > Le 18/04/2012 11:32, Hilaire Fernandes a Ã©crit : > >> Hello, > >> > >> Don't know if any of you tried to use long click event with pluggable > >> button. > >> > >> At first it looks pretty easy, as: > >> > >> btn on: #mouseStillDown send: #hello to: self. > >> > >> does the job. > >> > >> The hell is comming because btn aspect is changed but it states is not > >> changed. This is what I want but the aspect changed, but not the state, > >> so it get unsynchronized. > >> > >> I cannot find how to get the btn back to its aspect reflected by its > >> sate (#getModelState). I look at #update: but did not find. > >> > >> Of course it will be even better if its aspect is not changed when > >> #mouseStillDown event is triggered, but only at mouseUp. > >> > >> > >> Thanks > >> > >> Hilaire > >> > >> > >> PS: > >> - I found state to be misleading, should not it be selected? > >> - Also the use of symbol to describe the morph is a hell > >> - the morph extension add a layer of obscurity > >> - update/change is catastrophic in term of readability to maintain large > >> application > >> > >> Yes, I fell Morph does not scale when you get large application. At > >> least I got lost in my own code only when dealing with this specific > part. > >> > >> > > > > > > -- > > Dr. Geo -- http://www.drgeo.eu > > > > > > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 19, 2012

Re: [Pharo-project] Problem with Traits, Ring, RPcakage and Obsoletes

by StÃ©phane Ducasse

Please please please pay attention! RPackageOrganizer needs another pass because - not because of RPackageOrganizer but because of the state of the system Then notice that RPackageOrganizer has been designed in a way that the tests are ***NOT*** run against the default RPackageOrganizer to make sure that if you write a bad tests you do not break the system. Have a look at RPackageOrganize API and how we use it in RPackageOrganizer tests Now if may happen that you keep a debugger open when you debug a test of RPackageOrganizer and it may confuse you because you will see propagation of events handled in the RPackageOrganizer instance and not the default one. So pay attention to close the debugger so that notification are passed to the default organizer. Now I need somebody good and with time to have a look at the integration of RPackage into the system. But right now I do not have 3 hours to me to get concentrated. Stef

April 19, 2012

Re: [Pharo-project] OB, Refactoring, and OCompletion in 1.4

by Esteban Lorenzano

...and btw, you shouldn't install newocompletion. It is integrated with pharocore now. nd the versions in repository are not updated (my fault, completely forget about that :P). If you want to re-load it, you can install packages in pharo repository (NECompletion and NOCompletion, in that order) best, Esteban On Apr 19, 2012, at 7:58 PM, StÃ©phane Ducasse wrote: > Yes people should fix the configurations. > We will start to work on the process described in the PharoVision so that all the Configurations get tested. > > Stef > > > On Apr 18, 2012, at 6:35 PM, Sean P. DeNigris wrote: > >> The Welcome window points to the config browser, which loads basic OB (no >> refactoring). I was expecting to have refactoring installed, which is done >> via (per >> http://forum.world.st/ANN-new-stable-version-of-omnibrowser-td4525968.html#…) >> (ConfigurationOfOmniBrowser >> project version: #stable) load: #( 'Dev' 'Dev Tests'). >> >> This scripts installs OmniBrowser + OCompletion + Refactoring Browser >> >> The above works, but maybe this is a problem because it's using the old >> OCompletion? >> >> Then I tried to load NewOCompletion to see if it played nicely with OB, and >> got: "Error: Could not resolve: ConfigurationOfNewECompletion >> [ConfigurationOfNewECompletion] in /.../Pharo-1.4/package-cache". >> >> So I loaded ConfigurationOfNewECompletion manually in the MC browser, and >> then ran into "MessageNotUnderstood: NOCCompletionTable >> class>>methodChanged:" >> >> So there are some problems with the configs for the new completion work... >> and if these new tools work with OB, maybe the config for OB should be >> updated to use them, and then maybe the default group of the OB config >> should load 'Dev'... >> >> Sean >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/OB-Refactoring-and-OCompletion-in-1-4-tp4568254p45682… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

April 19, 2012

Re: [Pharo-project] Final 1.4 images...

by StÃ©phane Ducasse

Gary yes send the fixes they will get directly in 2.0alpha Stef > >> Too late for Polymorph etc. changes for 1.4 I guess... > > life does not stop with 1.4.... :-) > >> Going to make time for a changeset tomorrow, should be back-portable. >> >> I'll use the current 1.4 build as a difference baseline. >> > Ok, then we can integrate that in 2.0 directly at the start. > > > -- > Marcus Denker -- http://marcusdenker.de > >

April 19, 2012

Re: [Pharo-project] The video about Athens

by phil＠highoctane.be

Supercool! 2012/4/19 Denis Kudriashov <dionisiydk(a)gmail.com> > It's so great stuff!!! :)) > > Is cairo used as athens backend for this demo? > Is it should work with Bitblt backend? > > In demo I see many usage of angel parameter for transformations. Do you > think about "angel unit objects" like "90 degrees" or "2 radians" instead > of raw numbers ? > > How #scaledBy: works with Point argument (self extend) and Float like > (frame / 100 sin abs) at the same time? What' logic? > > Best regards, > Denis > > 2012/4/19 Igor Stasenko <siguctua(a)gmail.com> > >> Hello, all >> >> I recorded a small introductory video about Athens. >> Here it is: >> >> http://vimeo.com/40653315 >> >> (about 21 minutes). >> >> I explain some basic stuff like drawing things using Athens canvas, >> building paths, use of transformation matrices etc. >> >> Please note, this is a first video i ever recorded in such context in >> my life, so don't be too harsh :) >> Also, note that the animations are jagged because of video recording >> frame rate, not because it is that slow in reality. >> >> There are still a blog post pending about it.. which i plan to finish >> when i will finish ;) >> >> -- >> Best regards, >> Igor Stasenko. >> >> > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 19, 2012

Re: [Pharo-project] Long click on pluggeable button

by StÃ©phane Ducasse

Hilaire we should just continue and slowly but steadily fix and simplify. We have been doing it and we will continue. Now if you have concrete with examples suggestions please let us know. Stef > Responding to myself as it may be useful to other: > > > btn showSelectionFeedback: false. > btn changed. > > but well. > > Hilaire > > Le 18/04/2012 11:32, Hilaire Fernandes a Ã©crit : >> Hello, >> >> Don't know if any of you tried to use long click event with pluggable >> button. >> >> At first it looks pretty easy, as: >> >> btn on: #mouseStillDown send: #hello to: self. >> >> does the job. >> >> The hell is comming because btn aspect is changed but it states is not >> changed. This is what I want but the aspect changed, but not the state, >> so it get unsynchronized. >> >> I cannot find how to get the btn back to its aspect reflected by its >> sate (#getModelState). I look at #update: but did not find. >> >> Of course it will be even better if its aspect is not changed when >> #mouseStillDown event is triggered, but only at mouseUp. >> >> >> Thanks >> >> Hilaire >> >> >> PS: >> - I found state to be misleading, should not it be selected? >> - Also the use of symbol to describe the morph is a hell >> - the morph extension add a layer of obscurity >> - update/change is catastrophic in term of readability to maintain large >> application >> >> Yes, I fell Morph does not scale when you get large application. At >> least I got lost in my own code only when dealing with this specific part. >> >> > > > -- > Dr. Geo -- http://www.drgeo.eu > >

April 19, 2012

Re: [Pharo-project] OB, Refactoring, and OCompletion in 1.4

by StÃ©phane Ducasse

Yes people should fix the configurations. We will start to work on the process described in the PharoVision so that all the Configurations get tested. Stef On Apr 18, 2012, at 6:35 PM, Sean P. DeNigris wrote: > The Welcome window points to the config browser, which loads basic OB (no > refactoring). I was expecting to have refactoring installed, which is done > via (per > http://forum.world.st/ANN-new-stable-version-of-omnibrowser-td4525968.html#…) > (ConfigurationOfOmniBrowser > project version: #stable) load: #( 'Dev' 'Dev Tests'). > > This scripts installs OmniBrowser + OCompletion + Refactoring Browser > > The above works, but maybe this is a problem because it's using the old > OCompletion? > > Then I tried to load NewOCompletion to see if it played nicely with OB, and > got: "Error: Could not resolve: ConfigurationOfNewECompletion > [ConfigurationOfNewECompletion] in /.../Pharo-1.4/package-cache". > > So I loaded ConfigurationOfNewECompletion manually in the MC browser, and > then ran into "MessageNotUnderstood: NOCCompletionTable > class>>methodChanged:" > > So there are some problems with the configs for the new completion work... > and if these new tools work with OB, maybe the config for OB should be > updated to use them, and then maybe the default group of the OB config > should load 'Dev'... > > Sean > > Sean > > -- > View this message in context: http://forum.world.st/OB-Refactoring-and-OCompletion-in-1-4-tp4568254p45682… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 19, 2012

[Pharo-project] 1.4, seaside, comet, how to get it working

by jb

i just downloaded 1.4, installed seaside using the configuration browser and everything went great. i added a Zinc server adapator in the Seaside control panel and its all working fine. but then i went to set up the comet/streaming server and im kind of stumped. there is only one kind of Zinc server adapter and when i try to use it for the comet examples they all complain about needing a server that supports streaming. what do i need to do to get a streaming server for the comet applications? thanks in advance! jb

April 19, 2012

Re: [Pharo-project] Problem with Traits, Ring, RPcakage and Obsoletes

by Eliot Miranda

On Wed, Apr 18, 2012 at 11:27 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 18, 2012, at 11:49 PM, Mariano Martinez Peck wrote: > > > Hi guys. I am running some tests with Fuel. In such test I create > classes and traits. The problem is that I get a: "MessageNotUnderstood: > receiver of "isProvided" is nil" > > Everything starts (it seems) when I do #addToComposition: and I > receive a MethodRecategorized event and RPackage calls > #systemMethodRecategorizedActionFrom: > > There, the problem is with -> method isProvidedByATrait > > the class of the method is 'AnObsoleteClassForTestToBeDeleted1' > > And the error finally arrives to #providedLocatedMethod where it does > "each method isProvided" the problem is that "each" is a > RGMethodDefinition with everything in nil except 'name' and 'annotations'. > > I attach PharoDebug.log. > > Any help is really appreaciated. > > we should fix this bug: > > http://code.google.com/p/pharo/issues/detail?id=4750 > > it used to be that methods did not know their name, thus MethodReference > had to be used for many things. > This combined with not sharing compiledMethods means that traits can use > methods > directly. > I'm very worried by this. This misses the fact that a MethodReference and a CompiledMethod are two different things *because* methods can be redefined. So if one holds onto a method that gets redefined one can have more than one method with the same name. However, a MethodReference always refers to the method that is currently installed. In this way a MethodReference is a pointer, a coordinate, but a method is a referent. Personally I think the distinction is important; browser tools should use references, not referents. > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- best, Eliot

April 19, 2012