- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3537 in pharo: Addinf inst average size to SpaceTally

by pharo＠googlecode.com

Status: Accepted Owner: marianopeck Labels: Milestone-1.2 New issue 3537 by marianopeck: Addinf inst average size to SpaceTally http://code.google.com/p/pharo/issues/detail?id=3537 Hi. I did a little change to SpaceTally to add one more column which represents the instance average size per class So. before if you evaluated: SpaceTally new printSpaceAnalysis you get a file something like this: Class code space # instances inst space percent Bitmap 3525 227 3373140 14.4 Array 2152 82896 2804472 12.0 ByteSymbol 1062 40714 1037516 4.4 .... Now, you get something like this: Class code space # instances inst space percent inst average size ByteString 1984 96048 6598440 24.40 68.70 Bitmap 3525 328 5908048 21.80 18012.34 CompiledMethod 19125 65347 4061396 15.00 62.15 Array 2152 88541 3024132 11.20 34.16 ..... Pharo core version: 12300

Jan. 13, 2011

[Pharo-project] html parser

by Tudor Girba

Hi, Is there a robust html parser in Pharo? As I understand, there would be one in VW called TwoFlowers, but I do not know the license. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

Jan. 13, 2011

Re: [Pharo-project] Xtreams up to date

by StÃ©phane Ducasse

thansk martin Stef On Jan 12, 2011, at 1:08 AM, mkobetic(a)gmail.com wrote: > Hope it's OK to cross-post this, I figured there might be interested people on both sides. I finished the updates of the Xtreams port to match the VW version, so everything (that is available) should work as advertised in the documentation (http://code.google.com/p/xtreams/) > > Besides the implementation updates this last round of changes includes: > > * repackaging to match the docs and VW better, the dialect specific parts are now (mostly) gathered in Xtreams-Support > > * there is now a Gofer expression on the project page (http://www.squeaksource.com/Xtreams.html) to help people loading it, it shouldn't be hard to keep it up to date it shouldn't change very much > > * the source code is now identical between the dialects as much as possible, to help keeping it up to date. > > * one significant API change is that we renamed XTIncomplete to Incomplete to make code that uses Xtreams more portable. This is the only class that is very prominent in the API and hard to avoid in any sufficiently complex application, hopefully this is acceptable. > > I don't anticipate any significant changes in the port for next little while. I'd like to play with Squeak FFI next to see if I can bring the cryptographic streams from Xtreams-Xtras over and then see what it would take to get Xtreams-SSH2 running on Squeak and how it would perform. If you're curious how it went on VW side, I wrote about that in a blog post here: http://www.cincomsmalltalk.com/userblogs/cst/blogView. > > If you find bugs or issues, feel free to file an issue on the google project page (http://code.google.com/p/xtreams/issues/list) I'm monitoring both of these lists now as well and will try to answer any questions promptly. > > Cheers! > > Martin >

Jan. 13, 2011

Re: [Pharo-project] XML packages, CDATA and encoding

by StÃ©phane Ducasse

I was using soup to scrap some url and soup worked well with information I got from a stream over the url but it barked when I saved the file on the disc. I have to write a good metacello conf for soup and for my code to identify if this is a bug or not. stef On Jan 10, 2011, at 1:38 PM, Torsten Bergmann wrote: > Create a file "test.xml" with the following > contents (german umlaut): > > > <?xml version="1.0" encoding="iso-8859-1"?> > <test><![CDATA[ZaunkÃ¶nig]]></test> > > After loading ConfigurationOfXML try to parse it: > > |fs| > fs := FileStream fileNamed: 'test.xml'. > XMLDOMParser parseDocumentFrom: fs. > > > => gives an error: 'Invalid utf8 input detected' > => it works if you remove the CDATA section > > Looks like UTF8TextConverter is used independent > from the encoding of the XML... > > Bye > T. > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone >

Jan. 13, 2011

Re: [Pharo-project] BitmapFillStyle does not support translucent form

by StÃ©phane Ducasse

Hi denis On Jan 11, 2011, at 10:34 PM, Denis Kudriashov wrote: > Hello, > > I try BitmapFillStyle with translucent form for my morph object. And It's does not work. Did you try in latest squeak because I saw passing a fix for translucency but I do not know if this > There is AlphaInfiniteForm in polymorph package that work good as translucent fill styles. > > BitmapFillStyle used by Morph>>useBitmapFill. This method try set default bitmap form fill: > > fill := BitmapFillStyle fromForm: self defaultBitmapFillForm. > "Note: Must fix the origin due to global coordinates" > fill origin: self bounds origin. > self fillStyle: fill. > > For my application I change #useBitmapFill to open file choose dialog and using user selection for fill style (by AlphaInfiniteForm). > > I want to share this little code. But I don't know how to package this? > AlphaInfiniteForm is from Polymorph-... package. But useBitmapFill is from Morphic-.. package. > > Maybe AlphaInfiniteForm can be moved to Graphics-Display Objects package? as a first step Yes! Now I'm not sure that popping up a dialog is what should be done by default. > > What you think? Thanks for sharing that and we will > >

Jan. 13, 2011

Re: [Pharo-project] DuplicatedVariableError: styler is already defined in PluggableTextMorph

by Sven Van Caekenberghe

On 13 Jan 2011, at 09:26, StÃ©phane Ducasse wrote: > Here is the current draft of documentation around metacello. People often complain that there is no doc > but writing doc is also a full time jobwe are trying to address. > > Feedback is welcomed and source is on github. > <Metacello.pdf> > > Symbolic versions are really draft version. > Stef Yeah, I found that too, it looks quite nice. I was justing printing it out this morning to read this evening. And yes, I really appreciate such documentation work, it is very hard work. Thank you, Mariano ! Sven

Jan. 13, 2011

Re: [Pharo-project] Issue 3535 in pharo: I broke SpaceTally in Pharo 1.2

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3535 by stephane.ducasse: I broke SpaceTally in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3535 in 12300

Jan. 13, 2011

Re: [Pharo-project] [update 1.2] #12297

by Sven Van Caekenberghe

On 13 Jan 2011, at 01:26, Igor Stasenko wrote: > Kewl.. Orange is much much better. > > I modified it a little. Check it out The 'underline' for selected buttons is very nice. I don't see much (or any) difference in the orange. Although I don't really like the blue (it is a bit soft), it matches better with the Pharo logo (and we won't be changing that I think). Sven

Jan. 13, 2011

Re: [Pharo-project] Dirty MC Packages in Pharo-1.1.1-OneClickCogVM

by StÃ©phane Ducasse

why do you need method wrapper in dev? Again this goes with my mail about pushing metacello dsitributions versus pharo-dev+++ Stef On Jan 12, 2011, at 10:15 PM, Mariano Martinez Peck wrote: > yes, that was a hack I had to do becuase at that moment Cog didn't support well objects as methods, used by MethodWrappers, and when running its tests, it crashed. > we wanted to create a quick image so that people could start using cog and help testing it. > > this is not the case anymore in Pharo 1,2 > > so, if someone wants, the real solution is to create a new one click of 1.1.1 (without touching by hand method wrappers) and put new CogVMs. > > cheers > > mariano > > On Wed, Jan 12, 2011 at 8:10 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Yesterday I downloaded Pharo-1.1.1-OneClickCogVM from > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > and I noticed it has two dirty MC packages (MethodWrappers and Tests). > > This is probably a glitch, but not nice and confusion for beginners. > > Sven > > >

Jan. 13, 2011

Re: [Pharo-project] DuplicatedVariableError: styler is already defined in PluggableTextMorph

by StÃ©phane Ducasse

> There is a fix already submitted to PharoTaskForces. Where what bug entry? > If you download the last version from the metacello config, it should load well :). > > Cheers! > > On Wed, Jan 12, 2011 at 4:05 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > When trying to do: > > Gofer new renggli: 'omnibrowser'; > package: 'OmniBrowser'; > package: 'OB-Standard'; > package: 'OB-Morphic'; > package: 'OB-Shout'; > package: 'OB-Refactory'; > package: 'OB-Regex'; > package: 'OB-SUnitIntegration'; > load > > (Part of the build scripts of LR's builder scripting package) > > I get the following error: > > DuplicatedVariableError: styler is already defined in PluggableTextMorph > > while loading the definitiion of OBPluggableTextMorphWithShout in PharoCore 1.2 #12294. > > I have seen some things flying around on the mailinglist related indirectly to this issue. > > Is there a solution ? > > Thx, > > Sven > > >

Jan. 13, 2011