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

Re: [Pharo-dev] what happened with ZipWriteStream class>>#crcTable ?

by Stefan Marr

Hi Esteban: On 26 May 2014, at 20:52, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I wonder what happen with that methodâ¦ why it was removed? no need of it? This question sounds very familiar. You are looking into VM stuff? Check the change in primitiveUpdateGZipCrc32 here: https://github.com/pharo-project/pharo-vm/pull/18/files Normally at least there, the change was integrated. Hope that helps Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

May 26, 2014

Re: [Pharo-dev] Immutable collections and encapsulation

by Aaron Rosenzweig

For objects - knowing if they have been modified or not could have big benefits in performance when you want to âcommitâ anything in your object graph to an object database. For collections - In NeXT / Apple WebObjects weâve always made a distinction: NSArray / NSMutableArray NSSet / NSMutableSet NSDictionary / NSMutableDictionary Each one of these has a âmutableCloneâ and âimmutableCloneâ method. It was this way when it was Objective-C and it remained this way when we went to Java. We never use the standard Java collections. The mutable classes always inherit from the immutable ones as you can see here: http://wocommunity.org/documents/javadoc/WebObjects/5.4.2/ that makes OO sense in that the mutable versions do everything the immutable canâ¦ plus you can âaddâ or âremoveâ as well. Here we are only talking about the reference to objectsâ¦ the objects themselves are still mutable. In general it seems nice to make this distinction in collections. For exampleâ¦ suppose a âCompanyâ has âEmployees.â But somebody later is playing with the array of âemployeesâ and wants to add one. Do they know that later someone looking at the Company will see a new employee? maybe they wouldnât. AARON ROSENZWEIG / Chat 'n Bike e: aaron(a)chatnbike.com t: (301) 956-2319 On May 14, 2014, at 7:45 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 14 May 2014, at 13:27, Carlo <snoobabk(a)gmail.com> wrote: > >> Hi >> >> Obviously this all depends on context and what is trying to be achieved ;) >> In certain cases all we want to do is ensure the container is not modifiable but donât mind access to the held objects within. if the internal data is immutable (e.g. a representation of an error) then we donât care if they have access to this data but we may care that they modify the collection that holds these objects. You then need to weigh in with a pro/con of using unmodifiable collections versus a copy; most of the time a copy is all you need as the collections will be small. >> >> If the context requires for some (odd) reason complete immutability and youâre happy to pay the price in terms of space/time or additional complexity then there are other solutions from deepCopy, to something like Worlds (http://www.vpri.org/pdf/tr2011001_final_worlds.pdf , http://www.vpri.org/pdf/m2013002_experiments.pdf ) or maybe some weird use of software transactional memory. >> > We did an experiment with read-only references some time ago: > > http://rmod.inria.fr/web/publications/bib?query=Arna10a&display=abstract > > The idea is that we hacked the VM to have references-as-objects that can override behaviour transparently. > > Marcus

May 26, 2014

Re: [Pharo-dev] GLORPDBX with sqlite3

by Torsten Bergmann

May 26, 2014

is ClassOrganization>>#categories right?

by Esteban Lorenzano

Hi, I wonder is current implementation of that method is good: right now, it answers all categories, including virtual ones (âallâ). A lot of things are made in that assumption, but I wonder if is not better to answer just real categories and to create a new method called #allCategories to answer the reals and the virtuals. Also, I wonder if wouldnât be better to just deprecate #categories and use the correct abstraction: #protocols. any opinions? Esteban

May 26, 2014

what happened with ZipWriteStream class>>#crcTable ?

by Esteban Lorenzano

Hi, I wonder what happen with that methodâ¦ why it was removed? no need of it? Esteban

May 26, 2014

Re: [Pharo-dev] GLORPDBX with sqlite3

by Pablo R. Digonzelli

Thanks Guille, It is working now. Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Guillermo Polito" <guillermopolito(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: Lunes, 26 de Mayo 2014 11:00:40 Asunto: Re: [Pharo-dev] GLORPDBX with sqlite3 Hi! do you have everything else already installed? Which Postgresql driver are you using, which platform? You need to install sqlite3 the opendbx driver on the Pharo side and the opendbx library for sqlite3. Once there, it should be enough to create your login like this (I just copypasted from the tests): ^(Login new) database: SQLite3Platform new; host: SmalltalkImage current imagePath asFileReference parent fullName, '/'; port: ''; username: ''; password: ''; databaseName: 'sodbxtest.db'. Saludos! Guille On Sun, May 25, 2014 at 4:45 AM, Pablo R. Digonzelli < pdigonzelli(a)gmail.com > wrote: Hi, can someone help me about how to configure GlorpDbx with Sqlite3?. Now , i have Glorp working with Postgresql and all is OK. Tia, Pablo Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714

May 26, 2014

Re: [Pharo-dev] Clarifications with small lint rules

by Yuriy Tymchuk

Iâd gladly submit improvements, but I need some background knowledge. Whatâs the plan? It looks like SmalllintManifestChecker is just overriding/fixing stuff that is wrong in RBSmalllintChecker. For example RBSmalllintChecker>>checkClass: does: â(environment includesClass: aClass) ifTrue:â while SmalllintManifestChecker>>runRules:onPackage:withoutTestCase: does: â(environment definesClass: class) ifTrue:â. SmalllintManifestChecker>>runRules:onPackage: doesnât do this check despite that fact that it should work similarly to SmalllintManifestChecker>>runRules:onPackage:withoutTestCase:. Do we need to flatten SmalllintManifestChecker into RBSmalllintChecker? What is the status, is anyone working on it with some purpose or not? Also SmallLint is tied with RB. Is RB going to change or not? Uko On 22 May 2014, at 18:54, stepharo <stepharo(a)free.fr> wrote: > If you improve the system send us fixes. > Just make sure that > - the tests run > - you add tests. > > Stef >

May 26, 2014

Re: [Pharo-dev] GLORPDBX with sqlite3

by Guillermo Polito

Hi! do you have everything else already installed? Which Postgresql driver are you using, which platform? You need to install sqlite3 the opendbx driver on the Pharo side and the opendbx library for sqlite3. Once there, it should be enough to create your login like this (I just copypasted from the tests): ^(Login new) database: SQLite3Platform new; host: SmalltalkImage current imagePath asFileReference parent fullName, '/'; port: ''; username: ''; password: ''; databaseName: 'sodbxtest.db'. Saludos! Guille On Sun, May 25, 2014 at 4:45 AM, Pablo R. Digonzelli <pdigonzelli(a)gmail.com>wrote: > Hi, can someone help me about how to configure GlorpDbx with Sqlite3?. > Now , i have Glorp working with Postgresql and all is OK. > > > Tia, > > Pablo > > ------------------------------ > *Ing. Pablo Digonzelli* > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > Email: pdigonzelli(a)softsargentina.com > pdigonzelli(a)gmail.com > Cel: 5493815982714 > >

May 26, 2014

Re: [Pharo-dev] Bad naming: users

by Stephan Eggermont

Hmm, how do I make sure the changes are applied in the right order? Do I need to split the change in multiple slices, or is there an easier way? Stephan

May 26, 2014

Re: [Pharo-dev] [website] small changes

by Esteban A. Maringolo

2014-05-26 4:56 GMT-03:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 25 May 2014, at 16:58, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Marcus: >> >> Could the images be hosted in a CDN? (AWS S3 or similar) >> It is bearable to open one picture, but if you want to do a fast >> browse through the gallery it takes forever. Around 5 secs per >> picture, which is a lot for some new visitor, and will probably cause >> a very high bounce rate. > I think the reason is that the small images are actually full size > â¦ 299kb*4 is a lot. It certainly affects, but if you need to display a big image you have no choice. If you look at the timing view it spends half second connecting and waiting. This is irrelevant of the file size. Regards, Esteban A. Maringolo

May 26, 2014