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

Understanding WeakValueDictionary

by Norbert Hartl

While looking at the code in voyage I got to WeakValueDictionary as voyage uses it as object cache. If I looked correctly the WeakValueDictionary is based on equality and not identity. Is that correct? Feels wrong! Norbert

April 17, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by Norbert Hartl

Am 17.04.2014 um 10:08 schrieb phil(a)highoctane.be: > Not magically. > > I have my own guide/visitor thing to do the save. > But as I do have a "complicated" domain, the fact that I do not have to maintain all attributes in the image but directly through mapless helps me save a ton of time. Can you elaborate on the point ânot to have to maintain all attributes in the imageâ? I donât get what it means. And if you know voyage can share with us what are the differences? thanks, Norbert > > Phil > > On Thu, Apr 17, 2014 at 10:03 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > But how does a key/value store magically store a network of objects ? > How is each object serialised ? > > On 17 Apr 2014, at 08:57, phil(a)highoctane.be wrote: > > > On Thu, Apr 17, 2014 at 1:46 AM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > Phil, can you describe your use case ?! > > > > > > Network of objects persistence. > > > > > > > > On Wed, Apr 16, 2014 at 11:20 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > > > > I worked with Sebastian on using Mapless for my application. > > > > Just one word: Wow. This has potential!!!! > > > > Phil > > > > On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > > Mapless > > Mapless is a small framework for storing objects in a key->data fashion (i.e.: noSQL databases) without requiring any kind of object-data map. So far only MongoDB is supported. It can use Redis for reactivity (pub/sub) and cache. > > > > Motivation > > > > I wanted to persist objects with extremely low friction and extremely low maintenanceand great scaling and availability capabilities so Mapless is totally biased towards that. This framework is what I came up with after incorporating my experience withAggregate. > > > > There is no spoonâ¦ > > > > There is no object-relational impedanceâ¦ > > > > There is no instVarsâ¦ > > > > only persistence :D > > > > Code and instructions here: > > > > https://github.com/sebastianconcept/Mapless > > > > All MIT, enjoy > > > > sebastian > > > > o/ > > > > > > > > > > > > > > > > > > >

April 17, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by phil＠highoctane.be

Not magically. I have my own guide/visitor thing to do the save. But as I do have a "complicated" domain, the fact that I do not have to maintain all attributes in the image but directly through mapless helps me save a ton of time. Phil On Thu, Apr 17, 2014 at 10:03 AM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > But how does a key/value store magically store a network of objects ? > How is each object serialised ? > > On 17 Apr 2014, at 08:57, phil(a)highoctane.be wrote: > > > On Thu, Apr 17, 2014 at 1:46 AM, FranÃ§ois Stephany < > tulipe.moutarde(a)gmail.com> wrote: > > Phil, can you describe your use case ?! > > > > > > Network of objects persistence. > > > > > > > > On Wed, Apr 16, 2014 at 11:20 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > > > I worked with Sebastian on using Mapless for my application. > > > > Just one word: Wow. This has potential!!!! > > > > Phil > > > > On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > > Mapless > > Mapless is a small framework for storing objects in a key->data fashion > (i.e.: noSQL databases) without requiring any kind of object-data map. So > far only MongoDB is supported. It can use Redis for reactivity (pub/sub) > and cache. > > > > Motivation > > > > I wanted to persist objects with extremely low friction and extremely > low maintenanceand great scaling and availability capabilities so Mapless > is totally biased towards that. This framework is what I came up with after > incorporating my experience withAggregate. > > > > There is no spoonâ¦ > > > > There is no object-relational impedanceâ¦ > > > > There is no instVarsâ¦ > > > > only persistence :D > > > > Code and instructions here: > > > > https://github.com/sebastianconcept/Mapless > > > > All MIT, enjoy > > > > sebastian > > > > o/ > > > > > > > > > > > > > > > > > > >

April 17, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by Sven Van Caekenberghe

But how does a key/value store magically store a network of objects ? How is each object serialised ? On 17 Apr 2014, at 08:57, phil(a)highoctane.be wrote: > On Thu, Apr 17, 2014 at 1:46 AM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Phil, can you describe your use case ?! > > > Network of objects persistence. > > > > On Wed, Apr 16, 2014 at 11:20 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > > I worked with Sebastian on using Mapless for my application. > > Just one word: Wow. This has potential!!!! > > Phil > > On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Mapless > Mapless is a small framework for storing objects in a key->data fashion (i.e.: noSQL databases) without requiring any kind of object-data map. So far only MongoDB is supported. It can use Redis for reactivity (pub/sub) and cache. > > Motivation > > I wanted to persist objects with extremely low friction and extremely low maintenanceand great scaling and availability capabilities so Mapless is totally biased towards that. This framework is what I came up with after incorporating my experience withAggregate. > > There is no spoonâ¦ > > There is no object-relational impedanceâ¦ > > There is no instVarsâ¦ > > only persistence :D > > Code and instructions here: > > https://github.com/sebastianconcept/Mapless > > All MIT, enjoy > > sebastian > > o/ > > > > > > > >

April 17, 2014

Re: [Pharo-dev] IMPORTANT: Looking for names of contributors for Pharo 3

by Esteban Lorenzano

cool :) but still not accurate enough :( so, keep the names going! Esteban On 16 Apr 2014, at 18:54, Stephan Eggermont <stephan(a)stack.nl> wrote: > These are the names in the 30inbox > > (((MCHttpRepository allInstances second allFileNames collect: [ :each | > |minpos dotpos| > minpos := 0. > dotpos := 0. > each doWithIndex: [ :char :index | > char = $. ifTrue: [ > minpos =0 ifFalse: [ > dotpos =0 ifTrue: [dotpos :=index ] ] ]. > char = $- ifTrue: [ minpos := index ]]. > dotpos > minpos ifTrue: [ each copyFrom: minpos+1 to: dotpos-1 ] > ifFalse: [ '' ] ]) asSet )asSortedCollection ) > > a SortedCollection('' 'AlainPlantec' 'AlejandroInfante' 'AlexandreBergel' 'AliakseiSyrel' 'AndreiChis' 'AttilaMagyar' 'BenComan' 'BenjaminVanRyseghem' 'BernardoContreras' 'CAMILLETERUEL' 'CT' 'CamilleTeruel' 'CamilloBruni' 'ChristopheDemarey' 'ClementBer' 'ClementBera' 'DamienCassou' 'DamienPollet' 'DenisKudryashov' 'ErwanD' 'ErwanDouaille' 'EstebanLorenzano' 'FernandoOlivero' 'GabrielOmarCotelli' 'GiselaDecuzzi' 'GuidoChari' 'GuillermoPolito' 'HenrikSperreJohansen' 'HernanMoralesDurand' 'HernanWilkinson' 'HilaireFernandes' 'IgorStasenko' 'JochenRick' 'JurajKubelka' 'LaurentLaffont' 'LeoGassman' 'LucFabresse' 'LucasGiudice' 'MarcusDenjer' 'MarcusDenker' 'MarianoMartinezPeck' 'MartinDias' 'MartinWalk' 'MaxLeske' 'NickPapoulias' 'NicolaiHess' 'NicolasPapagnaMaldonado' 'NicolasPasserini' 'NicolasPetton' 'NorbertHartl' 'PabloHerrero' 'Part' 'Part2' 'PartOne' 'PavelKrivanek' 'PavelKrivnaek' 'PhilippeBack' 'RobertoMinelli' 'RonieSalgado' 'S' 'ST' 'SamirSaleh' 'SeanDeNigris' 'SebastianTleue' 'SebastianTleye' 'SimomAllier' 'SimonAllier' 'SqR' 'StephanEggermont' 'StephaneDucass' 'StephaneDucasse' 'SvenVanCaekenberghe' 'ThierryGoubier' 'TommasoDalSasso' 'TorstenBergmann' 'TudorGirba' 'USETHISVERSION' 'VincentBlondeau' 'YuriyTymchuk' 'abc' 'cami' 'cb' 'clementBera' 'janniklaval' 'jb' 'jeanbaptistearnaud' 'johanfabry' 'jordidelgado' 'kilonalios' 'md' 'nice' 'nicolascellier' 'onierstrasz' 'st' 'stleye' 'tbn' 'usmanbhatti')

April 17, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by phil＠highoctane.be

On Thu, Apr 17, 2014 at 1:46 AM, FranÃ§ois Stephany < tulipe.moutarde(a)gmail.com> wrote: > Phil, can you describe your use case ?! > > Network of objects persistence. > > On Wed, Apr 16, 2014 at 11:20 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > >> >> I worked with Sebastian on using Mapless for my application. >> >> Just one word: Wow. This has potential!!!! >> >> Phil >> >> On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre < >> sebastian(a)flowingconcept.com> wrote: >> >>> Mapless >>> >>> Mapless is a small framework for storing objects in a key->data fashion >>> (i.e.: noSQL databases) without requiring any kind of object-data map. So >>> far only MongoDB is supported. It can use Redis for reactivity (pub/sub) >>> and cache. >>> Motivation >>> >>> I wanted to persist objects with extremely *low friction* and extremely *low >>> maintenance*and great *scaling* and *availability* capabilities so >>> Mapless is totally biased towards that. This framework is what I came up >>> with after incorporating my experience withAggregate<https://github.com/sebastianconcept/Aggregate> >>> . >>> >>> *There is no spoonâ¦* >>> >>> *There is no object-relational impedanceâ¦* >>> >>> *There is no instVarsâ¦* >>> only persistence :D >>> >>> Code and instructions here: >>> >>> https://github.com/sebastianconcept/Mapless >>> >>> All MIT, enjoy >>> >>> sebastian <https://about.me/sebastianconcept> >>> >>> o/ >>> >>> >>> >>> >>> >>> >> >

April 17, 2014

Re: [Pharo-dev] InfiniteForm

by Igor Stasenko

On 15 April 2014 23:15, pharo4Stef(a)free.fr <pharo4Stef(a)free.fr> wrote: > There a plenty of isKindOf: InfiniteForm in the system and I was trying to > understand how we could get rid of them. > How other systems handle pattern based color filling shape? > > why bother? Just use The God's Hammer Dispatch (AKA Non-intuitive way of programming for those who don't think in objects ;) : fillRectangle: aRectangle basicFillStyle: aFillStyle "Fill the given rectangle with the given, non-composite, fill style." | pattern | (aFillStyle isKindOf: InfiniteForm) ifTrue: [ ^self infiniteFillRectangle: aRectangle fillStyle: aFillStyle ]. => fillRectangle: aRectangle basicFillStyle: aFillStyle "Fill the given rectangle with the given, non-composite, fill style." ^ aFillStyle fillRectangle: aRectangle onCanvas: self ..and then after refactoring it will look exactly how Athens doing it, because if you rename fill style with "paint" and rectangle with "shape" you will see it :) > Stef > > -- Best regards, Igor Stasenko.

April 17, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by FranÃ§ois Stephany

Phil, can you describe your use case ?! On Wed, Apr 16, 2014 at 11:20 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > > I worked with Sebastian on using Mapless for my application. > > Just one word: Wow. This has potential!!!! > > Phil > > On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > >> Mapless >> >> Mapless is a small framework for storing objects in a key->data fashion >> (i.e.: noSQL databases) without requiring any kind of object-data map. So >> far only MongoDB is supported. It can use Redis for reactivity (pub/sub) >> and cache. >> Motivation >> >> I wanted to persist objects with extremely *low friction* and extremely *low >> maintenance*and great *scaling* and *availability* capabilities so >> Mapless is totally biased towards that. This framework is what I came up >> with after incorporating my experience withAggregate<https://github.com/sebastianconcept/Aggregate> >> . >> >> *There is no spoonâ¦* >> >> *There is no object-relational impedanceâ¦* >> >> *There is no instVarsâ¦* >> only persistence :D >> >> Code and instructions here: >> >> https://github.com/sebastianconcept/Mapless >> >> All MIT, enjoy >> >> sebastian <https://about.me/sebastianconcept> >> >> o/ >> >> >> >> >> >> >

April 16, 2014

Re: [Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

by phil＠highoctane.be

I worked with Sebastian on using Mapless for my application. Just one word: Wow. This has potential!!!! Phil On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Mapless > > Mapless is a small framework for storing objects in a key->data fashion > (i.e.: noSQL databases) without requiring any kind of object-data map. So > far only MongoDB is supported. It can use Redis for reactivity (pub/sub) > and cache. > Motivation > > I wanted to persist objects with extremely *low friction* and extremely *low > maintenance*and great *scaling* and *availability* capabilities so > Mapless is totally biased towards that. This framework is what I came up > with after incorporating my experience withAggregate<https://github.com/sebastianconcept/Aggregate> > . > > *There is no spoonâ¦* > > *There is no object-relational impedanceâ¦* > > *There is no instVarsâ¦* > only persistence :D > > Code and instructions here: > > https://github.com/sebastianconcept/Mapless > > All MIT, enjoy > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > >

April 16, 2014

Re: [Pharo-dev] IMPORTANT: Looking for names of contributors for Pharo 3

by Sean P. DeNigris

Stephan Eggermont wrote > These are the names in the 30inbox > (((MCHttpRepository allInstances second allFileNames collect: [ :each | I <3 Smalltalk ----- Cheers, Sean -- View this message in context: http://forum.world.st/IMPORTANT-Looking-for-names-of-contributors-for-Pharo… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2014