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

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

[Pharo-project] About ~= and ~~
by Clara Allende Nov. 26, 2016

Nov. 26, 2016

Hi guys, I'm wondering, why? ProtoObject>> ~~ anObject "Answer whether the receiver and the argument are not the same object (do not have the same object pointer)." self == anObject ifTrue: [^ false] ifFalse: [^ true] Instead of: ProtoObject>> ~~ anObject "Answer whether the receiver and the argument are not the same object (do not have the same object pointer)." ^(self == anObject) not And why? Object >> ~= anObject "Answer whether the receiver and the argument do not represent the same object." ^self = anObject == false Instead of Object>> ~= anObject "Answer whether the receiver and the argument do not represent the same object." ^(self = anObject) not. Is there any particular reason for this that I'm missing? Thanks in advance! -- "*Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.*" Linus Torvalds

12 26

[Pharo-project] Status of SmallPOS
by Stephan Eggermont Aug. 9, 2016

Aug. 9, 2016

I noticed the SmallPOS on ss3 is under MIT license. AFAIK, it was GPLv3. When did this relicensing happen? Stephan

4 8

[Pharo-project] [ANN] Pomodoro for Pharo 2.0
by Torsten Bergmann Feb. 5, 2016

Feb. 5, 2016

Hi, I followed the recent discussion and initial code about "Pomodoro" and since (until now) I used a timer written in Java I thought it would be a good idea to replace it with a Smalltalk one ;) I grabbed the HOPomodoro code from Phil and since it was marked as "experiment" I thought it would be good to write a new clean implementation with tests for Pharo 2.0. Thanks Phil - hope you are not angry that I hijacked the idea ... Attached is a screenshot of the tool. Install ======= Go to the Config browser in Pharo 2.0 ("Tools" -> "Config Browser") and load "Pomodoro" from the "Verified" tab. A new timer should appear and you can just click on "Start" to run the timer. When it finished it turns red, beeps and informs the user. How to use ========== You can open a new pomodoro (defaults 25 minutes) from the world menu ("Tools" -> "Pomodoro"). Customize ========= You can customize the pomodoro using Smalltalk. Here are a few examples: "open a new 25 minute one" Pomodoro new open "Opens a new timer with one minute total time" Pomodoro timerFor: 1 minute "Provide an action when pomodoro is finished" Pomodoro timerFor: 5 seconds whenFinishedDo: [ self inform: 'Pomodoro finished'] Code ==== The project comes with 15 tests. Code lives on project "Pomodoro" on SmalltalkHub. So far I added Phil and Sean as contributors since they discussed this topic already and may provide new ideas. If one wants to contribute feel free to do so. Thanks T.

5 6

[Pharo-project] Do we have the new primitive?? [WAS] Re: IdentitySet but using #hash rather than #identityHash ?
by Mariano Martinez Peck Dec. 16, 2015

Dec. 16, 2015

> All I can say is that I am impressed by the numbers it is really much >> faster. >> I still don't understand why I send this email with a subject say >> IdentitySet because what I really need is a fast/large IdentityDictionary >> :( Anyway, there's a place where we can use this LargeIdentitySet in Fuel >> I think). >> >> So Levente, you say this is not possible to adapt this for dictionary? >> can >> we contact Eliot to provide such a primitive? >> > > As promised, I uploaded my LargeIdentityDictionary implementation to > http://leves.web.elte.hu/**squeak/**LargeIdentityDictionary.st<http://leves.web.elte.hu/squeak/LargeIdentityDictionary.st>. > The numbers will be a bit worse compared to LargeIdentitySet, because of > the lack of the primitive, but it's still 2-3x faster than other solutions > (IdentityDictionary, PluggableIdentityDictionary, subclassing, etc). I'm > about to propose this primitive with other improvements on the vm-dev list. > > Hi Eliot/Levente. What is the status of this? Do we have already the new primitive? If true, how can we adapt LargeIdentitySet to use such new primitive? Thanks! > > Levente > > >> thanks >> >> On Fri, Dec 16, 2011 at 3:28 PM, Levente Uzonyi <leves(a)elte.hu> wrote: >> >> On Fri, 16 Dec 2011, Henrik Sperre Johansen wrote: >>> >>> On 16.12.2011 03:26, Levente Uzonyi wrote: >>> >>>> >>>> >>>>> How about my numbers? :) >>>>> >>>>> "Preallocate objects, so we won't count gc time." >>>>> n := 1000000. >>>>> objects := Array new: n streamContents: [ :stream | >>>>> n timesRepeat: [ stream nextPut: Object new ] ]. >>>>> >>>>> set := IdentitySet new: n. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "4949" >>>>> >>>>> set := LargeIdentitySet new. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "331" >>>>> >>>>> set := (PluggableSet new: n) >>>>> hashBlock: [ :object | object identityHash * 4096 + object class >>>>> identityHash * 64 ]; "Change this to #basicIdentityHash in Pharo" >>>>> equalBlock: [ :a :b | a == b ]; >>>>> yourself. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "5511" >>>>> >>>>> >>>>> I also have a LargeIdentityDictionary, which is relatively fast, but >>>>> not >>>>> as fast as LargeIdentitySet, because (for some unknown reason) we don't >>>>> have a primitive that could support it. If we had a primitive like >>>>> primitive 132 which would return the index of the element if found or >>>>> 0 if >>>>> not, then we could have a really fast LargeIdentityDictionary. >>>>> >>>>> >>>>> Levente >>>>> >>>>> Hehe yes, if writing a version fully exploiting the limited range, >>>> that's >>>> probably the approach I would go for as well. >>>> (IAssuming it's the version at http://leves.web.elte.hu/** >>>> squeak/LargeIdentitySet.st<htt**p://leves.web.elte.hu/squeak/** >>>> LargeIdentitySet.st<http://leves.web.elte.hu/squeak/LargeIdentitySet.st> >>>> > >>>> ) >>>> >>>> Mariano commented in the version at http://www.squeaksource.com/** >>>> FuelExperiments <http://www.squeaksource.com/**FuelExperiments<http://www.squeaksource.com/FuelExperiments>> >>>> that it's >>>> >>>> slow for them, which I guess is due to not adopting #identityHash calls >>>> to >>>> #basicIdentityHash calls for Pharo: >>>> ((0 to: 4095) collect: [:each | each << 22 \\ 4096 ]) asSet size -> 1 >>>> So it basically uses 1 bucket instead of 4096... Whoops. :) >>>> >>>> Uploaded a new version to the MC repository which is adapted for Pharo, >>>> on the same machine my numbers were taken from, it does the same test >>>> as I >>>> used above in 871 ms. (181 with preallocation). >>>> >>>> >>> Cool. One more thing: in Squeak the method using primitive 132 directly >>> was renamed to #instVarsInclude:, so now #pointsTo: works as expected. If >>> this was also added to Pharo, then the #pointsTo: sends should be changed >>> to #instVarsInclude:, otherwise Array can be reported as included even if >>> it wasn't added. >>> I'll upload my LargeIdentityDictionary implementation to the same place >>> this evening, since it's still 2-3 factor faster than other solutionts >>> and >>> there seem to be demand for it. >>> >>> >>> Levente >>> >>> >>> Cheers, >>>> Henry >>>> >>>> >>>> >>>> >>> >> >> -- >> Mariano >> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >> >> > -- Mariano http://marianopeck.wordpress.com

3 5

[Pharo-project] StandardFileStream size limit?
by GÃ¶ran Krampe Nov. 13, 2015

Nov. 13, 2015

Hey all! I have just added large file (chunkwise upload and download) support to Kom/Networking/Iliad in Pharo 1.4 and while testing it I tried uploading a 2.9Gb file. I haven't looked at the exact error message, and I haven't tried writing a trivial test - but the "half written" file on disk is almost EXACTLY 2Gb (2147483647) so I am wondering - do we still have a 2Gb file size limit? This is "one click 1.4" on Ubuntu 64 with ext4. regards, GÃ¶ran

7 10

[Pharo-project] RTF reader/writer
by StÃ©phane Ducasse April 8, 2015

April 8, 2015

Hi guys Do you know if there is a library somewhere in Smalltalk to deal with RTF writing/saving? Stef

7 10

[Pharo-project] A solution to manage units like inches and centimeters in Pharo?
by Guillaume Larcheveque April 29, 2014

April 29, 2014

Does something exists because I looked and don't find anything. -- *Guillaume Larcheveque*

10 15

[Pharo-project] PluggableListMorph error, how to debug ?
by laurent laffont Jan. 13, 2014

Jan. 13, 2014

Hi, sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? [image: Inline image 1] Cheers, Laurent

7 10

[Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration
by Denis Kudriashov Nov. 30, 2013

Nov. 30, 2013

Hello I think you read about Mocketry and know that It provides same "should syntax" DSL like project Phexample. There is problem between two projects. We both implement #should message in Object class. So when somebody want Phexample Mocketry become broken and vice versa. In the past I actually only read about Phexample tests reusage idea with #given message. And I didn't know that It provides "should syntax" too. Now I read about it and look at code (thank's Yuriy Tymchuk) and I have some suggestions about it. First few words about state of Mocketry project. Mocketry is not based on SSpec (I was google such wrong opinion). It is just implement SSpec idea about executable specifications and "should syntax". And specifications part with DSL was extracted from Mocketry to StateSpecs project. So Mocketry is only about mocks and behaviour specs. Idea of executable specifications is not about replacement "assert syntax" with "should syntax". It is about building reusable first class objects which can validate domain objects. For example there are EqualitySpec, ElementsCountSpec, ClassSpec. All this specs present "valid state" of objects. They know how to validate objects. State specs can be used in tests, UI and any other domain where you want put descriptions about what it mean "valid object". I start use StateSpecs in Presenty to build object editor. With specs I put requirements on model aspects. I am sure Magritte provides something similar in description objects. So StateSpecs solve very general problem: how to describe validation rules for objects and how to make such descriptions reusable. To make it convenient and readable StateSpecs provides two kind of DSL: - should syntax to immediately check object state - first class words to create spec instances with more readable way: Instance of: SomeClass, Equal to: #some, Containing item: arrayItem and others First option can be used in tests instead #assert: expressions. Last can be used in mock message arguments. StateSpecs provide very simple way to extend it DSL based on pragmas: Instance of: aClass <syntax: #(be an instance of:)> ^ClassSpec for: aClass Equal to: anObject <syntax: #(equal:)> <syntax: #(be equal:)> ^self return: (EqualitySpec pattern: anObject) Containing item: anObject <syntax: #(include:)> ^ElementContainmentSpec requiredElement: anObject And with this you can write: object should be an instance of: SomeClass object should equal: #some object should be equal: #some array should include: item. So with such approach both kind of DSL extended at one place. Ok. Now my main suggestion. Let's Phexample use StateSpecs for "should syntax". I can provide all "should protocol" of Phexample in StateSpecs. So it will be transparent for current users. It just few extra pragmas and classes in StateSpecs-DSL package. Maybe it is already done by Yuriy Tymchuk. With such integration both projects will just improved. What do you think? Best regards, Denis

6 19