- Pharo-users - lists.pharo.org

Breaking News

by horrido

Smalltalk to get a second crack at the whip <https://medium.com/@richardeng/smalltalk-to-get-a-second-crack-at-the-whip-…> . By frickin' time! -- View this message in context: http://forum.world.st/Breaking-News-tp4940893.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 1, 2017

Re: [Pharo-users] Morphic component to display images/pictures

by Stephane Ducasse

Cool (for the interpreter refactoring). Let us know when you have something. I thought that you wanted to display an image. On Sat, Apr 1, 2017 at 11:44 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > The mooc challenge (no #4) doesn't really address any of the things I am > interested in (the result is the same as what inspector can currently do). > > Spec has ImageModel, but that doesn't even have scrollbars... > > anyway... I am currently refactoring Spec interpreter and after that I > would like to improve some things... so maybe I could improve the > ImageModel, since we don't have what I want... > > Peter > > > On Sat, Apr 01, 2017 at 09:58:26AM +0200, Hilaire wrote: > > Just by curiosity: can it be done with Spec ? > > > > Hilaire > > > > Le 31/03/2017 Ã 08:16, Stephane Ducasse a Ã©crit : > > > have a look at the solution of the challenge 2 or 3 in the mooc :) > > > > > > > -- > > Dr. Geo > > http://drgeo.eu > > > > > >

April 1, 2017

Smalltalk/Java job in france

by Stephane Ducasse

*From: *Babel <contact(a)babel.coop> *Subject: **Offre d'emploi profil double compÃ©tence Smalltalk/Java* *Date: *21 February 2017 at 21:31:26 GMT+1 *To: *smalltalk-fr(a)googlegroups.com *Reply-To: *smalltalk-fr(a)googlegroups.com Nous proposons Ã un profil concepteur-dÃ©veloppeur Smalltalk/Java de rejoindre une Ã©quipe dÃ©diÃ©e "socle technique", dans le cadre de travaux de maintenance corrective et Ã©volutive, pour une mission longue. CompÃ©tences attendues : - expÃ©rience significative en Smalltalk - expÃ©rience significative en Java - autonomie - sens de l'Ã©quipe Lieu : Poitou-Charentes DisponibilitÃ© : immÃ©diate L'offre est ouverte Ã tous, freelance ou non : la personne aura la possibilitÃ© de rejoindre si elle le souhaite une coopÃ©rative d'entrepreneurs. Pour plus d'informations, contactez-nous rapidement : contact arob babel.coop -- View this message in context: http://forum.world.st/Offre-d-emploi-profil-double-competence-Smalltalk-Jav… Sent from the FranÃ§ais (French) mailing list archive at Nabble.com <http://nabble.com/>.

April 1, 2017

Re: [Pharo-users] How childrenBlock: in TreeModel works

by Peter Uhnak

Hi, I wanted to point you to the new Spec book ( http://files.pharo.org/books-pdfs/spec/2017-01-23-SpecBooklet.pdf ), but apprently it's not there. Many Spec widgets have examples accompanying them, so always check class side (not for all though). For TreeModel you can see couple there - good for playing around; e.g. exampleWithNoSpecifiedNodes "self exampleWithNoSpecifiedNodes" TreeModel new roots: (1 to: 5); childrenBlock: [ :item | 1+item to: 5+item ]; openWithSpec You specify the initial data (root nodes) via the `roots:` message. The `childrenBlock:` then specifies how one would retrieve data given a particular node; note that this applies to _any node_, not just the root ones; so you can have potentially infinitely deep trees. A more complex example could be this (this is awful code for demonstration only ;): TreeModel new roots: {#parent. #childless. 20. #root -> #(a b c)}; childrenBlock: [ :item | item isSymbol ifTrue: [ item = #parent ifTrue: [ #(child1 child2) ] ifFalse: [ #() ] ] ifFalse: [ item isNumber ifTrue: [ {item + 2. item ** 2} ] ifFalse: [ "association" item value ] ] ]; openWithSpec Peter On Sat, Apr 01, 2017 at 06:49:41AM -0700, chrismihaylyk wrote: > Hi! > > Could anyone explain me how works childrenBlock: method from TreeModel? > step-by-step. > What data it operates? How makes a result? > > Thanks a lot? Khrystyna. > > > > > > -- > View this message in context: http://forum.world.st/How-childrenBlock-in-TreeModel-works-tp4940884.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 1, 2017

How childrenBlock: in TreeModel works

by chrismihaylyk

Hi! Could anyone explain me how works childrenBlock: method from TreeModel? step-by-step. What data it operates? How makes a result? Thanks a lot? Khrystyna. -- View this message in context: http://forum.world.st/How-childrenBlock-in-TreeModel-works-tp4940884.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 1, 2017

Re: [Pharo-users] Morphic component to display images/pictures

by Peter Uhnak

The mooc challenge (no #4) doesn't really address any of the things I am interested in (the result is the same as what inspector can currently do). Spec has ImageModel, but that doesn't even have scrollbars... anyway... I am currently refactoring Spec interpreter and after that I would like to improve some things... so maybe I could improve the ImageModel, since we don't have what I want... Peter On Sat, Apr 01, 2017 at 09:58:26AM +0200, Hilaire wrote: > Just by curiosity: can it be done with Spec ? > > Hilaire > > Le 31/03/2017 Ã 08:16, Stephane Ducasse a Ã©crit : > > have a look at the solution of the challenge 2 or 3 in the mooc :) > > > > -- > Dr. Geo > http://drgeo.eu > >

April 1, 2017

Re: [Pharo-users] Morphic component to display images/pictures

by Hilaire

Just by curiosity: can it be done with Spec ? Hilaire Le 31/03/2017 Ã 08:16, Stephane Ducasse a Ã©crit : > have a look at the solution of the challenge 2 or 3 in the mooc :) > -- Dr. Geo http://drgeo.eu

April 1, 2017

Re: [Pharo-users] Voyage, DateAndTime and UTC

by Hilaire

Based on the Paul suggestion, one can write a description to get DateAndTime right. Hopefully this could be fixed in Voyage Hilarie mongoAccesstime <mongoDescription> ^ VOToOneDescription new attributeName: 'accessTime'; accessor: (MAPluggableAccessor read: [:userClient| userClient accessTime printString] write: [:userClient :string | userClient accessTime: (DateAndTime fromString: string)]); yourself Le 31/03/2017 Ã 21:06, Hilaire a Ã©crit : > Thanks for the idea. > For me it is a bug[2], like the other one related to Date persistency, > saved as DateAndTime, then shifting you one day[1]. -- Dr. Geo http://drgeo.eu

April 1, 2017

Re: [Pharo-users] type checking in Smalltalk

by Ben Coman

On Sat, Apr 1, 2017 at 2:34 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 31 Mar 2017, at 19:38, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > > > On Fri, 31 Mar 2017 at 19:13, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > if you copy/paste something you should give a reference > > > > > > I did not copy paste anything, 100 % mine. What part you think it's copy > ? > > Ah, sorry then, the formatting seemed to suggest it came from somewhere > else. > > BTW, I don't think the hybrid part is a real thing. > > Although I understand that static typed languages like C, C++, Java and so > many others have their place and use, people in those languages spend an > awful amount of time and code dealing with the types they love so much. The > modern static languages with all their magic are even worse. And even in a > nice static typed program that compiles with no warnings, there are still > dynamic errors lurking everywhere. The world cannot be defined in a static > way. > > The dynamic type errors that you get in Pharo during development are 95% > plain logic errors, once you fix those and write some unit tests, a Pharo > program is just as stable and reliable as anything else that is well > written, tested and debugged. > > And I love Igor's "Don't ask, tell" idea - right on target. > This would make a good name for a book on OO. cheers -ben > > Anyway, that is my personal opinion, I don't want to convince you. > > Sven >

April 1, 2017

Re: [Pharo-users] PetitParser question parsing HTML meta tags

by monty

You could use XMLHTMLParser from STHub PharoExtras/XMLParserHTML (supported on Pharo, Squak, and GS): descriptions := OrderedCollection new. (XMLHTMLParser parseURL: aURL) allElementsNamed: 'meta' do: [:each | ((each attributeAt: 'name') asLowercase = 'description' or: [(each attributeAt: 'http-equiv') asLowercase = 'description']) ifTrue: [descriptions addLast: (each attributeAt: 'content')]]. it accepts messy HTML and produces an XML DOM tree from it. > Sent: Thursday, March 30, 2017 at 1:58 PM > From: "PAUL DEBRUICKER" <pdebruic(a)gmail.com> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] PetitParser question parsing HTML meta tags > > This is kind of a "I'm tired of thinking about this and not making much progress for the amount of time I'm putting in question" but here it is: > > > > I'm trying to parse descriptions from HTML meta elements. I can't use Soup because there isn't a working GemStone port. > > I've got it to work with the structure: > > <meta name="description" content="my description"> > > and > > <meta name="Description" content="my description"> > > > but I'm running into instances of: > > <meta http-equiv="description" content="my description"> > > and > > <meta http-equiv="Description" content="my description"> > > > and am having trouble adapting my parsing code (such as it is). > > > The parsing code that addresses the first two cases is: > > > > parseHtmlPageForDescription: htmlString > | startParser endParser ppStream descParser result text lower str doubleQuoteIndex | > lower := 'escription' asParser. > startParser := '<meta name=' asParser , #'any' asParser , #'any' asParser. > endParser := '>' asParser. > ppStream := htmlString readStream asPetitStream. > descParser := ((#'any' asParser starLazy: startParser , lower) > , (#'any' asParser starLazy: endParser)) ==> #'second'. > result := descParser parse: ppStream. > text := (result > inject: (WriteStream on: String new) > into: [ :stream :char | > stream nextPut: char. > stream ]) > contents trimBoth. > str := text copyFrom: (text findString: 'content=') + 9 to: text size. > doubleQuoteIndex := 8 - ((str last: 7) indexOf: $"). > ^ str copyFrom: 1 to: str size - doubleQuoteIndex > > > I can't figure out how to change the startParser parser to accept the second idiom. And maybe there's a better approach altogether. Anyway. If anyone has any ideas on different approaches I'd appreciate learning them. > > > Thanks for giving it some thought > > Paul >

March 31, 2017