March 2017 - Pharo-users - lists.pharo.org

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

Re: [Pharo-users] diff'ing with metacello

by Siemen Baader

> One of the thing that can be done is to temporarily copy all the versions concerned into a Git-based repository with Iceberg or GitFileTree, and then sees if git can provides a better diff, or even a git blame ability Great tip, thanks, Thierry! -- Siemen > . I've done that multiple times... copy multiple versions in a repo, study the diff, and then just throw it away. > > Thierry > >> >> Thanks for enlightening me! >> >> Siemen >> >> On Thu, Mar 30, 2017 at 4:57 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> >>> 2017-03-30 16:42 GMT+02:00 Ben Coman <btc(a)openinworld.com>: >>>> On Thu, Mar 30, 2017 at 2:58 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: >>>> > Below is a fileout of 'ConfigurationOfPharoJS'. I download new releases of >>>> > PharoJS as they become available. Recently I found a regression - a method >>>> > 'PjApplication class >> playgroundWithoutLaunch' did not work any more. What >>>> > I wanted to do was to revert the whole project to an earlier version until >>>> > the method worked again - then look for the code that has been changed >>>> > between releases and find the bug. >>>> > >>>> > In practice, even the earliest version (version 1.0 - method #version10) did >>>> > have the bug and I could not roll back the project to earlier release states >>>> > because there is no metadate for them. But I'd still like to learn how to do >>>> > it, so let's just say I want to compare version 1.2 and 1.3: >>>> > >>>> > version12: spec >>>> > <version: '1.2' imports: #('0.1-baseline' )> >>>> > >>>> > version13: spec >>>> > <version: '1.3' imports: #('0.2-baseline' )> >>>> > >>>> > >>>> > I hope this makes sense. Thanks for helping me understand! >>>> >>>> You can only directly diff the Configurations themselves. >>>> I fairly sure you can't auto-diff the packages loaded by each configuration. >>>> This is a missing feature. It would be nice to have something like >>>> the merge-diff, >>>> but there are probably other priorities. Maybe the new git workflow >>>> will open some possibilities?? >>> >>> If you have a project-oriented way of committing to git (you commit both the configuration and all the packages in one commit), then diffing via git would work. >>> >>> Current status on that feature is: >>> >>> - BaselineOf and all related packages save in one commit can be done with GitFileTree. I added an API for that and made a few experiments by organising and saving projects via the Metacello registry (with GUI support). I rolled back that extension in AltBrowser and I will reimplement it soon in a different, better way. >>> >>> - Iceberg ? >>> >>> - ConfigurationOf ? The approach of storing a configurationOf inside a meta repository makes implementing that harder. >>> >>> Now, I think the tools would probably be able to get that to work over Monticello with few changes, but they are a tad complex to implement, as in loading two different configurationsOf and resolving related packages (without loading them), and then changing the diff viewer to project all differences between all classes of the two groups of packages. One thing to remember is that complete packages, in multiple versions, can be loaded simultaneously as Monticello models without disrupting the code currently loaded and active in the image, as when you "browse" a Monticello package on disk. >>> >>> Thierry >>> >>>> >>>> cheers -ben >

March 31, 2017

Re: [Pharo-users] Smacc debugger

by Stephane Ducasse

Hi thierry Where can I find a documentation of +, * ? in the grammar (and especially how to manage the production)? And indeed they do not work in the Moose version. I think that if +, *, ?, ( ) are working in the grammar it is an important addition to Smacc. Because I found it right now verbose compare to ANTLR Stef On Wed, Mar 29, 2017 at 7:19 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2017-03-29 18:21 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> So I browsed the mailing-list and I foind the mail of thierry saying that >> there is no difference. >> I will try to tools in moose then. >> > > Probably: the +, *, ?, ( ) in the grammar don't work anymore. As I told > you: very few differences. > > >> On Wed, Mar 29, 2017 at 6:07 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Ok I should say that I do not understand the differences and why there >>> are two versions of Smacc. >>> So I will stop maintaining the tutorial because now may be I should >>> revert what I wrote. >>> I was too stupid to do it in fact I should focus on my stuff and nothing >>> else. >>> This saddens me a lot. >>> We are a small community and we split ourselves into little chunks. >>> I do not get why there is no notion of economy and sharing in our >>> culture. >>> >> > Thierry > > >> >>> Stef >>> >>> >>> >>> On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> >>> wrote: >>> >>>> Hi, >>>> >>>> > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse < >>>> stepharo.self(a)gmail.com> wrote: >>>> > >>>> > OK >>>> > I loaded Smacc from github as mentioned by thierry. >>>> > >>>> > Metacello new >>>> > baseline: 'SmaCC'; >>>> > repository: 'github://ThierryGoubier/SmaCC'; >>>> > load >>>> > >>>> > Are there two configurationOfSmacc? >>>> > May be we should only have one no? >>>> > >>>> > I have the impression that even thierry and jason working heavily >>>> with Smacc do not know that. >>>> > And we should not force them to use Moose. At least we do not have to >>>> win >>>> > anything with it. >>>> >>>> I did not mean to force anyone to use Moose. I just said it is already >>>> loaded there, in case you use it. >>>> >>>> Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry >>>> has another repository that he created before John moved his work to Pharo. >>>> But, now that he does work with Pharo Moose relies on his version. >>>> >>>> Cheers, >>>> Doru >>>> >>>> > >>>> > Stef >>>> > >>>> > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> >>>> wrote: >>>> > They come with the ConfigurationOfSmaCC which is already in the Moose >>>> image. >>>> > >>>> > Doru >>>> > >>>> > >>>> > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse < >>>> stepharo.self(a)gmail.com> wrote: >>>> > > >>>> > > Hi >>>> > > >>>> > > where can I load the Smacc gt extension and debugger extensions? >>>> > > >>>> > > Stef >>>> > >>>> > -- >>>> > www.tudorgirba.com >>>> > www.feenk.com >>>> > >>>> > "Speaking louder won't make the point worthier." >>>> > >>>> > >>>> > >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "There are no old things, there are only old ways of looking at them." >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >

March 31, 2017

Re: [Pharo-users] type checking in Smalltalk

by Dimitris Chloupis

Hehe yeah I love nice formatting :) You don't need to convince me , I prefer coding dynamically Ironically enough is the static that is not a real thing anymore. I am coding C++ and Unreal uses templates for pretty much everything. Templates the equivalent of dynamic types, kinda. However when performance is concerned anything dynamic must go, which in C++ means templates and smart pointers. One for dynamic types and the other for dynamic memory management. Generally however templates and generics are super popular and coders are frowned upon if they do not use them because falling back to pure static coding is considered bad coding practice. C++ is on route of becoming even more hybrid, the new hot potato being modules a replacement to header files , similar to Python modules. It was to be included in the next iteration of C++ but was postponed. Probably will get included in the one after the next. In Python a module is a source code file that is treated as an object. So a global variable is equivalent to class variable, the source file being the class. If the module is a package (file folder) then it's class variables are the sub modules. Nowadays people use static languages not because they want to but because the have to for legacy code and performance reasons. Still modern projects usually mix dynamic with static languages. The static plays the role of the kernel providing high performance the dynamic the role of easy to use , beginner friendly, scripting interface. Java and C# support out of the box any dynamic language out there. So the lines nowadays are extremely blurry. It's 2017 , great time to live in when you can choose among so many choices. On Fri, 31 Mar 2017 at 21:35, 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. > > Anyway, that is my personal opinion, I don't want to convince you. > > Sven >

March 31, 2017

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

by Hilaire

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]. Hilaire [1] https://github.com/pharo-nosql/voyage/issues/88 [2] https://github.com/pharo-nosql/voyage/issues/89 Le 31/03/2017 Ã 18:54, Paul DeBruicker a Ã©crit : > Or just store as ISO8601 string. > -- Dr. Geo http://drgeo.eu

March 31, 2017

Re: [Pharo-users] type checking in Smalltalk

by Sven Van Caekenberghe

> 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. Anyway, that is my personal opinion, I don't want to convince you. Sven

March 31, 2017

Re: [Pharo-users] New chapter for new book

by Marc Hanisch

Thanks Stephane, I'm digging into Pharo and I'm reading the books like a sponge ;-) Great work and thanks for the link! Marc Am 31.03.2017 19:18 schrieb "Stephane Ducasse" <stepharo.self(a)gmail.com>: > Marc the full book is available at: > > https://ci.inria.fr/pharo-contribution/view/Books/job/ > LearningObjectOrientedProgramming/lastSuccessfulBuild/ > artifact/build/book.pdf > > On Fri, Mar 31, 2017 at 4:05 PM, Marc Hanisch via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> >> >> ---------- Forwarded message ---------- >> From: Marc Hanisch <marc.hanisch(a)googlemail.com> >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Cc: >> Bcc: >> Date: Fri, 31 Mar 2017 16:05:11 +0200 >> Subject: Re: [Pharo-users] New chapter for new book >> Wow, thats amazing! >> >> Thank you Stephane! >> >> 2017-03-31 15:51 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>> Hi >>> >>> I attached a new chapter for my forthcoming book. >>> >>> Stef >>> >>> >> >> >

March 31, 2017

Re: [Pharo-users] New chapter for new book

by Dimitris Chloupis

PBE was stuck in version 1.4 until we got to version 4 when I started updating it. So PBE 2 and 3 and most of 4 do not exist. Even PBE 5 is partial. On Fri, 31 Mar 2017 at 18:21, Hilaire <hilaire(a)drgeo.eu> wrote: > This is not exactly true. Pharo By Example was already there, and > preceeded by Squeak By Exemple, which the former is an adaptation. > > Le 31/03/2017 Ã 16:47, Dimitris Chloupis a Ã©crit : > > when I joined back in 2011 there was not even basic documentation > > -- > Dr. Geo > http://drgeo.eu > > >

March 31, 2017

Re: [Pharo-users] type checking in Smalltalk

by Dimitris Chloupis

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 ?

March 31, 2017

Re: [Pharo-users] New chapter for new book

by Stephane Ducasse

Marc the full book is available at: https://ci.inria.fr/pharo-contribution/view/Books/job/LearningObjectOriente… On Fri, Mar 31, 2017 at 4:05 PM, Marc Hanisch via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Marc Hanisch <marc.hanisch(a)googlemail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Fri, 31 Mar 2017 16:05:11 +0200 > Subject: Re: [Pharo-users] New chapter for new book > Wow, thats amazing! > > Thank you Stephane! > > 2017-03-31 15:51 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Hi >> >> I attached a new chapter for my forthcoming book. >> >> Stef >> >> > >

March 31, 2017