- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Poll: missing libraries to support busines

by GermÃ¡n Arduino

Thanks Stef! It loads ok on the latest PharoCore 1.2. A quick try show me that the tests don't work mainly because the changes on UI. I can add this to my infinite to-do list and take a look if is worth to the community. Also we should add a repo on SqueakSource? I noticed several license notes on the source code, but not idea if can be released as mit or not..... Clues? German. 2010/8/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Aug 6, 2010, at 8:16 AM, Stephan Eggermont wrote: > >> I would like to have native, or at least better, libraries for manipulating PDFs >> and office files. >> >> Stephan >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 24, 2010

[Pharo-project] why are Bitmaps instanciated even in headless mode?

by Mariano Martinez Peck

I took a dev image, and run them in two ways: the normal and headless. For each I did a: "Smalltalk garbageCollect. SpaceTally new printSpaceAnalysis" Normal one: Class code space # instances inst space percent Bitmap 3753 133 11099904 37.4 ByteString 2515 85110 6106378 20.6 CompiledMethod 19130 59452 3703463 12.5 Array 2176 77579 2561928 8.6 ...... Headless: Class code space # instances inst space percent ByteString 2515 85110 6106378 24.7 Bitmap 3753 126 6049208 24.5 CompiledMethod 19130 59452 3703463 15.0 Array 2176 77577 2561844 10.4 ...... So....even in headless mode, I have 133 instances of Bitmap, representing 24.5% of the memory.... Ok, 24.5 is better than 37.5, but I don't understand why Bitmap instances are created. Why they are needed ? is there a way to garbageCollect them? thanks Mariano

Aug. 24, 2010

[Pharo-project] [Survey] Assess the cycles in your software

by Laval Jannik

Hi, A new reminder for our study. We need your help to finish the study. Thank you to all participants. Cheers, > >> >> On Jul 19, 2010, at 08:36 , Laval Jannik wrote: >> >>> Hi Pharoers, and Smalltalkers in general, >>> >>> Have you seen waited to assess the cycles in your software? Now you can :) >>> >>> We request some of you to perform an experiment using DSM to see your software package structure and to fix cycles between packages. Our tool shows dependencies between packages and highlight some bad dependencies generating structure cycles. It also helps to understand dependencies. >>> >>> Your goal is to fill a survey using our tool. >>> I prepared a mini-tutorial about DSM and eDSM. It can help you to understand the visualization tool. >>> >>> To ease the use of our tool, I loaded it in a PharoCore1.2. And there are two archives available: >>> - the first contains an image with our tool with a model of Pharo loaded in it, so you can play with our tool on pharo itself. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithPharo.zip. Pay attention, the image is slow. >>> - the second contains the same thing without the model of Pharo. Here, you have to load your code, then populate a moose model and use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip >>> The two archives contain the tutorial and the survey. If you are a pharo integrator, we suggest you to take the one with Pharo model loaded, else the other. >>> >>> To use our tool, load your tool in Pharo. Then do "MoosePanel open", and import your software in Moose by "import from Smalltalk image". When it is imported, select your project in the list on the left of MoosePanel, and select "all model packages" on the list on center. >>> >>> Then, you have two choices: >>> - you can scan all your project: right click on "all model packages" and do DSM. >>> - or select "all model packages" then select some packages in the next list and right click, do DSM. >>> >>> After that, you can perform the survey (with reading of the tutorial). We need your answers for the end of August. So, you have two months to do it. >>> >>> If you have any question, just let me know. >>> >>> Best regards, >>> Jannik. >>> >>> --- >>> Jannik Laval >>> PhD Student - Rmod Team - INRIA >>> Certified Project Management Associate (IPMA) >>> http://www.jannik-laval.eu >>> http://rmod.lille.inria.fr >>> --- >>> > --- Jannik Laval

Aug. 24, 2010

[Pharo-project] [Survey] Assess the cycles in your software

by Laval Jannik

Hi, A new reminder for our study. We need your help to finish the study. Thank you to all participants. Cheers, > > On Jul 19, 2010, at 08:36 , Laval Jannik wrote: > >> Hi Pharoers, and Smalltalkers in general, >> >> Have you seen waited to assess the cycles in your software? Now you can :) >> >> We request some of you to perform an experiment using DSM to see your software package structure and to fix cycles between packages. Our tool shows dependencies between packages and highlight some bad dependencies generating structure cycles. It also helps to understand dependencies. >> >> Your goal is to fill a survey using our tool. >> I prepared a mini-tutorial about DSM and eDSM. It can help you to understand the visualization tool. >> >> To ease the use of our tool, I loaded it in a PharoCore1.2. And there are two archives available: >> - the first contains an image with our tool with a model of Pharo loaded in it, so you can play with our tool on pharo itself. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithPharo.zip. Pay attention, the image is slow. >> - the second contains the same thing without the model of Pharo. Here, you have to load your code, then populate a moose model and use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip >> The two archives contain the tutorial and the survey. If you are a pharo integrator, we suggest you to take the one with Pharo model loaded, else the other. >> >> To use our tool, load your tool in Pharo. Then do "MoosePanel open", and import your software in Moose by "import from Smalltalk image". When it is imported, select your project in the list on the left of MoosePanel, and select "all model packages" on the list on center. >> >> Then, you have two choices: >> - you can scan all your project: right click on "all model packages" and do DSM. >> - or select "all model packages" then select some packages in the next list and right click, do DSM. >> >> After that, you can perform the survey (with reading of the tutorial). We need your answers for the end of August. So, you have two months to do it. >> >> If you have any question, just let me know. >> >> Best regards, >> Jannik. >> >> --- >> Jannik Laval >> PhD Student - Rmod Team - INRIA >> Certified Project Management Associate (IPMA) >> http://www.jannik-laval.eu >> http://rmod.lille.inria.fr >> --- >>

Aug. 24, 2010

Re: [Pharo-project] some important fixes we should focus on for 1.2

by Guillermo Polito

Issue 1981: Raising DuplicateError Exception in class builder http://code.google.com/p/pharo/issues/detail?id=1981 has status = FixedWaitingToBePharoed since august 01. Is it done? On Sat, Aug 21, 2010 at 6:07 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > I'll have a look at > http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: > Â MethodDictionary improvement > > On Sat, Aug 21, 2010 at 1:41 PM, stephane ducasse > <stephane.ducasse(a)free.fr> wrote: >> Hi guys >> >> here is a list of issue I would like to work and get some help. >> >> Stef >> >> http://code.google.com/p/pharo/issues/detail?id=2570 Issue 2570: >> Removed implicit conversion of DateAndTime equality-testing argument. >> >> http://code.google.com/p/pharo/issues/detail?id=2579 >> http://code.google.com/p/pharo/issues/detail?id=2698 >> Â Â Issue 2698: Â Â Â Â Smalltalk registration to SystemChangeNotifier should be handle in startup >> http://code.google.com/p/pharo/issues/detail?id=2177 Issue 2177: Â Â Â Â Generalize stream protocol #readInto:startingAt:count: >> Issue 1981: Â Â Raising DuplicateError Exception in class builder >> http://code.google.com/p/pharo/issues/detail?id=1981 >> http://code.google.com/p/pharo/issues/detail?id=2146 Issue 2146: Â Â Â Â Fix SystemChangeNotification for traits. >> >> http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: Â Â Â Â MethodDictionary improvement >> http://code.google.com/p/pharo/issues/detail?id=2315 Method Dictionary Compact protocol to investigate >> >> http://code.google.com/p/pharo/issues/list?cursor=2313 Â Issue 2313: Â Â HashedCollectionIntegrityTest >> >> http://code.google.com/p/pharo/issues/detail?id=2583 Issue 2583: Â Â Â Â COG - MessageTally >> Â Issue 2619: Â Â ignore vm parameters with nil value in MessageTally, so it can be used in Cog >> >> http://code.google.com/p/pharo/issues/detail?id=2584 COG- COG- LargeNegativeInteger to be compact at 5 >> >> http://code.google.com/p/pharo/issues/detail?id=2567 >> Â Issue 2567: Â Â evaluate the finalizers outside the protected block in WeakRegistry >> >> http://code.google.com/p/pharo/issues/detail?id=2564 >> Â Issue 2564: Â Â WeakKeyDictionary finalizeValue tests >> >> http://code.google.com/p/pharo/issues/detail?id=2769 >> Issue 2769: Â Â Fixes for broken SocketStream behavior. >> >> http://code.google.com/p/pharo/issues/list?cursor=2551 weakstructure >> >> http://code.google.com/p/pharo/issues/detail?can=2&q=2244 >> Issue 2244: Â Â Socket support for #next:putAll:startingAt: and #readInto:startingAt:count: >> >> http://code.google.com/p/pharo/issues/detail?id=2825 >> Issue 2825: Â Â [[true] whileTrue] fork cannot be interrupted >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Aug. 24, 2010

Re: [Pharo-project] 'foo' asTime

by Guillermo Polito

Thinking aloud. I usually don't have to write dates in my code, because they are picked by the user. I think that a well built kernel and nice well integrated UI widgets (maybe I'm going out of the scope :P ) are enough in most of the cases. Anyway, IMHO it's very important to review Time>>fromString: because it's useful for serialization stuff. Like webservices and that kind of things a lot of people have to use. I opened a ticket http://code.google.com/p/pharo/issues/detail?id=2854 On Tue, Aug 24, 2010 at 8:24 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ok here is my take on it: > Â Â Â Â - I would like to have a mini kernel where date time is just good enough for what the system needs > Â Â Â Â - then people load the framework they want and yes I love aconcagua and chalten but there is also chronos > Â Â Â Â so you see I would prefer that people pick the one they like. > Now people can have a different opinion and I would like to hear them :) > > Stef > > On Aug 23, 2010, at 11:45 PM, Mariano Abel Coca wrote: > >> As an off topic of 3 seconds... >> >> Have you considered to include HernÃ¡n Wilkinson and Maximiliano Taborda's packages Aconcagua and Chalten in Pharo Dev? >> >> Chalten is a great Â Time framework and much better than the ansi Smalltalk 80's Time class, even with the addition of Duration. And it represents the Minute and Second concepts along with Month, Day, DayOfMonth, MonthOfYear, etc. :) >> >> With Chalten you could simply write: December second, 2005. >> >> If you want to try them, just evaluate: >> >> Gofer new >> Â Â Â squeaksource: 'Chalten'; >> Â Â Â package: 'Chalten'; >> Â Â Â load. >> >> Cheers, >> >> Mariano. >> >> >> On Mon, Aug 23, 2010 at 5:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> 3 seconds is indeed better. >> Right now we are talking about string over extension. >> >> Stef >> >> On Aug 23, 2010, at 9:00 AM, Brent Pinkney wrote: >> >> >> I would really like to have the approach proposed by K. Beck on conversion >> >> methods. Conversion methods for API compatible objects. Of course it will >> >> lead to less compact program (URL readFrom: 'http://' instead of 'http://' >> >> url) but avoids a lot of code in String (of course class extensions limit >> >> the plague). >> > >> > Hi, please reconsider this. There is just no way (Duration seconds: 3) is >> > better than '3 seconds'. >> > >> > This smacks of working for the computer instead of the other way around. >> > >> > Brent >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 24, 2010

[Pharo-project] Float>>basicAt: primitive for Cog

by Guillermo Polito

Hi! taking a look at issue 2579 http://code.google.com/p/pharo/issues/detail?id=2579 I saw it's all done but: "The float access methods are an alternative to what is described in 2580 / 2581 , didn't see this when I posted. They are slightly slower in a CogVM when primitive fails, since you will have 2 primitive failures before handling, but do not need the Parser change which allows primitive pragmas with non-literal error parameter. Either way, if this approach is chosen, we might as well write: (same for basicAt:put:) Float >> basicAt: index <primitive: 38> ^super basicAt: index as ec is always nil in this case." That should replace Float >> basicAt: index "...." <primitive: 38> | ec | ec == nil ifTrue: "primitive not implemented; floats are in big-endian/PowerPC order." [^super basicAt: index]. index isInteger ifTrue: [self errorSubscriptBounds: index]. index isNumber ifTrue: [^self basicAt: index asInteger] ifFalse: [self errorNonIntegerIndex] -------------------------------------------------------------------------- I ran all the FloatTests and I got: -Cog VM: all green before and after the change. -non-Cog VM: 1 failure (on testNaNCompare) before and after the change I can't see tests for the primitive failure, maybe we should have... Anyway, I wonder if this change is ok for the non-cog vm also. Does anyone know? Cheers, Guile

Aug. 24, 2010

Re: [Pharo-project] Fwd: [Pharo-users] 3600 seconds seconds = 0 ???

by StÃ©phane Ducasse

we should check our ugly standard because apparently seconds comes from ANSI. Stef On Aug 24, 2010, at 12:45 PM, Guillermo Polito wrote: > On Tue, Aug 24, 2010 at 7:27 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> 3600 seconds seconds = 0 >> which means that this is a number of seconds in the hour:min:seconds decomposition >> >> Now it looks to me that the method comment is wrong > > yeap > >> >> seconds >> "Answer the number of seconds the receiver represents." >> >> ^ (seconds rem: SecondsInMinute) >> >> >> 3600 seconds asSeconds = 3600 is what is working >> >> may be (Duration seconds: 3600) would be better >> >> To me there is something conceptually bogus with such definition of minutes and seconds. >> (Duration seconds: 3600) minutes = 0 >> (Duration seconds: 3600) seconds = 0 >> > > that's the same you remarked, the decomposition of the duration :). > Maybe there are better names for the decomposition... Or better comments. > > I'm looking that Duration also lacks methods to get the total hours > and minutes the duration represents (Which is the behavior you > expected, didn't you?). Something like > > (Duration seconds: 3600) totalMinutes = 60 > (Duration seconds: 3600) totalSeconds = 3600 > > But, what about something like > > (Duration seconds: 3601) totalMinutes = (3601/60) ?? > > Guille > >> >> >> Stef >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 24, 2010

Re: [Pharo-project] Working on Pharo 1.2

by StÃ©phane Ducasse

excellent! I like that it takes good shape. >>> OK, I created: >>> >>> http://www.pharo-project.org/pharo-download/unstable-core >>> >>> Marcus, for updating: log into Cmsbox, select the page 'unstable-core' under 'download' and edit the code part on this page. >>> >> >> Thanks, that's nice! > > > I added links to the latest unstable to the download page. > I change the links to 1.1 to point to stable-core and stable, too. So they will be correct when we do a 1.0.1 > > http://www.pharo-project.org/pharo-download > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 24, 2010

Re: [Pharo-project] Poll: missing libraries to support busines

by StÃ©phane Ducasse

On Aug 6, 2010, at 8:16 AM, Stephan Eggermont wrote: > I would like to have native, or at least better, libraries for manipulating PDFs > and office files. > > Stephan > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 24, 2010