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

Re: [Pharo-dev] [ANN]: ValidationRevisited (alpha)

by Sean P. DeNigris

stephane ducasse wrote > show us how you specify that? It's a simple Spec UI, receiving announcements from the domain object. Whenever the model changes, the UI receives: modelChanged: anAnnouncement failureList items: model validate failures. #validate is the main entry point for the framework. You can call this on any domain object and the validation rules will be run. Under the hood are specialized SUnit classes. Here (on Nabble) is a screenshot of the validator class, a specialized TestCase which holds the rules for the object in the screencast: <http://forum.world.st/file/n4690694/Screen_Shot_2013-05-29_at_5.37.12_PM.png> The really cool thing which is not shown in the video is that the failures are real objects which hold the domain object, the property that failed (called an 'aspect'), and the description shown in the UI. So you could do a lot more than show the description... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-ValidationRevisited-alpha-tp4690680p4690694.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 29, 2013

Re: [Pharo-dev] #"asdada"B is a valid symbol?

by Nicolas Cellier

Ha ha, a long time weirdness http://lists.squeakfoundation.org/pipermail/squeak-dev/2006-May/104250.html http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-May/116956.html 2013/5/29 Camille Teruel <camille.teruel(a)gmail.com> > > > Yes the same... 1"sdads"2 is interpreted as 12 and all estrange > combinations... > > > If #"whatever"symbol evaluates to #symbol, 123"blabla"456 doesn't parse in > my image. > Anyway, the first seems quite useless to me just like this other cases > (also covered by test) like: > ## # ## # # ## # asd > that evaluates to #asd and: > #123.456 > that evaluates to 123.456 > > Camille > >

May 29, 2013

Trait exclusions

by Frank Shearar

I have a Trait TGroup that requires #*, #identity and #inverse. I want to construct a TField by composing TGroup with itself. One TGroup will form the operations #*, #one, and #reciprocal while the other will form #+, #zero and #negated. I don't want #identity or #inverse, because these apply to one operation, and it makes TField's API ambiguous. That's what TraitExclusion is for. I had thought I could say (TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} + TGroup @ {#identity->#one. #inverse->#reciprocal}) - {#identity. #inverse} but TraitComposition >> #- says that exclusion binds tighter than +. So in effect the above composition is the same as TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} + (TGroup @ {#identity->#one. #inverse->#reciprocal} - {#identity. #inverse}) In short, to remove the undesirable #identity and #inverse I have to exclude from both sides of the composition: TGroup @ {#identity->#zero. #* -> #+. #inverse->#negated} - {#identity. #inverse} + TGroup @ {#identity->#one. #inverse->#reciprocal} - {#identity. #inverse} My question is this: what is the reason for - binding more tightly than +? Why is it _not_ desirable to have - distribute over +? frank

May 29, 2013

Re: [Pharo-dev] Pharo & Redis?

by stephane ducasse

On May 29, 2013, at 8:00 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > doesn't seem to. > > Anyone has any objection on comiting a copy of that in smalltalkhub so it stays available?? sure go for it. Stef > > sebastian > > o/ > > > > > > On May 28, 2013, at 3:52 PM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > >> Hey guys, >> >> I've seen here a reference in http://redis.io/clients to this Smalltalk client: >> >> http://www.squeaksource.com/@kv_Jds-P7FbzciwZ/xU6A7ylR >> >> The last commit is kind of old (2011) >> >> 1. Are you using it? >> >> 2. Is anybody interested in maintaining a Redis Pharo client here? >> >> Why Redis you might ask? >> >> Well, it's fast and has a very interesting feature: Notifications >> >> With notifications you can subscribe observers and publish object events (I'll leave the rest to your smalltalker imagination) on persisted objects. >> >> This opens many possibilities in real-time smalltalk based apps that scales nice. >> >> sebastian >> >> o/ >> >

May 29, 2013

Re: [Pharo-dev] [ANN]: ValidationRevisited (alpha)

by stephane ducasse

;) show us how you specify that? Stef On May 29, 2013, at 11:12 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > I got really inspired reading the extreme validation section of "A Mentoring > Course on Smalltalk", Andres Valloud's OOP bible (see > seandenigris.com/blog/?p=573) and enhanced a bit my port of > ValidationRevisited. > > I made a short screencast of a little UI monitoring the health of a domain > object in real-time. > > https://vimeo.com/67244280 > > If you want to play with the code (works on Pharo 2.0), doIt: > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'aMentoringCourseOnSmalltalk'; > package: 'ValidationRevisited'; > load. > See ValidationDashboard class>>#openExample > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-ValidationRevisited-alpha-tp4690680.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 29, 2013

Re: [Pharo-dev] RPackage and overrides

by stephane ducasse

On May 29, 2013, at 9:08 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 28/05/2013 22:23, stephane ducasse a Ã©crit : >> >> >>> I have a question about RPackage and overrides. >>> >>> RPackage consider that an override method is an extension, right? >> >> for RPackage a package is a list of method definitions and class definition. >> There is no specific tagging for overriding methods that would magically reappear when >> their overriding method would be unloaded. > > Ok. But in MC, a MethodDefinition has a way of telling if it is an override or not. We do not support this "feature" since it is bogus since years. > RPackage does not (and list -overrides as extensions, as for example in Keymapping). > >> I do not know if this answer your question. > > Not sure :) I wondered if I should bother with overrides or let them as extensions, as RPackage seems to be considering them the same. > > What do you think? Is it important to classify overrides as such, or just let them be extensions ? just extensions. Stef > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

May 29, 2013

Re: [Pharo-dev] No Internationalization (nor Multilingual) Project in bug tracker

by stephane ducasse

On May 29, 2013, at 10:45 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Like in Squeak/Trunk I want to push UTF8 encoding in .mcz/snapshot/source.st and want to first create an InvalidUTF8 exception (Error) - so as to fallback to legacy encoding in error handling. Thanks > What project do you suggest for classifying the fogbugz entry? Kernel? We will handle it. > Nicolas

May 29, 2013

[ANN]: ValidationRevisited (alpha)

by Sean P. DeNigris

I got really inspired reading the extreme validation section of "A Mentoring Course on Smalltalk", Andres Valloud's OOP bible (see seandenigris.com/blog/?p=573) and enhanced a bit my port of ValidationRevisited. I made a short screencast of a little UI monitoring the health of a domain object in real-time. https://vimeo.com/67244280 If you want to play with the code (works on Pharo 2.0), doIt: Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'aMentoringCourseOnSmalltalk'; package: 'ValidationRevisited'; load. See ValidationDashboard class>>#openExample ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-ValidationRevisited-alpha-tp4690680.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 29, 2013

Livecoding - Fluxus - Athens?

by phil＠highoctane.be

http://www.pawfal.org/dave/index.cgi?Projects/Fluxus Guess we need something like that :-) Phil

May 29, 2013

No Internationalization (nor Multilingual) Project in bug tracker

by Nicolas Cellier

Like in Squeak/Trunk I want to push UTF8 encoding in .mcz/snapshot/source.stand want to first create an InvalidUTF8 exception (Error) - so as to fallback to legacy encoding in error handling. What project do you suggest for classifying the fogbugz entry? Nicolas

May 29, 2013