- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] XMLParserHTML moved to GitHub

by Esteban Maringolo

Great! I just added a link to the README.md of the project and created a PR, because it is very likely that if you're parsing HTML you're doing some scrapping. :-) Esteban A. Maringolo On Fri, Nov 29, 2019 at 2:18 PM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > Stef and other wrote this book a while ago: > > http://books.pharo.org/booklet-Scraping/html/scrapingbook.html > > Basically XMLHtmlParser + XPath > > To me, far better than using Soup. > Google chrome pharo integration helps top to scrap complex full JS web site like google ;)

Nov. 29, 2019

Re: [Pharo-users] [ANN] XMLParserHTML moved to GitHub

by CÃ©drick BÃ©ler

Stef and other wrote this book a while ago: http://books.pharo.org/booklet-Scraping/html/scrapingbook.html Basically XMLHtmlParser + XPath To me, far better than using Soup. Google chrome pharo integration helps top to scrap complex full JS web site like google ;) Cheers, Cedrick > Le 29 nov. 2019 Ã 15:41, Esteban Maringolo <emaringolo(a)gmail.com> a Ã©crit : > > ï»¿Thank you Torsten, > > I wasn't aware of this tool, I'm already using it to scrap content > from a website and fed a Pharo driven system :) > > The XML integration in the Inspector is great too. > > Regards! > > Esteban A. Maringolo > >> On Tue, Nov 19, 2019 at 8:40 AM Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Hi, >> >> the STHub -> PharoExtras project "XMLParserHTML" >> >> was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParserHTML to >> https://github.com/pharo-contributions/XML-XMLParserHTML including the FULL HISTORY >> >> The old STHub repo was marked as obsolete - but is linking to the new one. I've also >> setup an CI job: https://travis-ci.org/pharo-contributions/XML-XMLParserHTML >> which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can >> see from commit history. >> >> The new version is tagged in git as version 1.6.0 (with a moveable tag 1.6.x in case further >> hotfixes are required). >> >> You can load using >> >> Metacello new >> baseline: 'XMLParserHTML'; >> repository: 'github://pharo-contributions/XML-XMLParserHTML/src'; >> load. >> >> or from catalog in Pharo 7 or 8. >> >> Attached is current dependency graph. >> >> More to come soon ... >> >> Bye >> T. >

Nov. 29, 2019

Re: [Pharo-users] [ANN] XMLParserHTML moved to GitHub

by Esteban Maringolo

Thank you Torsten, I wasn't aware of this tool, I'm already using it to scrap content from a website and fed a Pharo driven system :) The XML integration in the Inspector is great too. Regards! Esteban A. Maringolo On Tue, Nov 19, 2019 at 8:40 AM Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > the STHub -> PharoExtras project "XMLParserHTML" > > was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParserHTML to > https://github.com/pharo-contributions/XML-XMLParserHTML including the FULL HISTORY > > The old STHub repo was marked as obsolete - but is linking to the new one. I've also > setup an CI job: https://travis-ci.org/pharo-contributions/XML-XMLParserHTML > which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can > see from commit history. > > The new version is tagged in git as version 1.6.0 (with a moveable tag 1.6.x in case further > hotfixes are required). > > You can load using > > Metacello new > baseline: 'XMLParserHTML'; > repository: 'github://pharo-contributions/XML-XMLParserHTML/src'; > load. > > or from catalog in Pharo 7 or 8. > > Attached is current dependency graph. > > More to come soon ... > > Bye > T.

Nov. 29, 2019

[ANN] Next Pharo Sprint: Nov 29

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Nov 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

Nov. 25, 2019

Re: [Pharo-users] open spec window to handle exception and pause execution

by Paul DeBruicker

Thanks Richard. That helped me figure it out. I ended up doing: [ [self testCondition] whileTrue:[ self doSomeStuff] ] on: MyNotification do:[:ex | |presenter | presenter:=MyPresenter forException: ex . presenter openWithSpec. Smalltalk ui theme runModal: presenter window] Which does what I want Richard Sargent wrote > Paul, I'm going by memory and not Pharo specific. > > I believe the default handling of the end of the exception block is > implicitly equivalent to ex return: nil. > > So, to get further handling of the exception, you need to #pass it or > otherwise resignal it. Then the development environment will catch and > handle the unhandled exception. > > > On Wed, Nov 20, 2019, 20:53 PAUL DEBRUICKER < > pdebruic@ > > wrote: > >> Hi - >> >> I have a subclass of ComposablePresenter (lets call it MyPresenter) that >> seems to work how I want. When doing some processing I'd like to open >> MyPresenter when an exception occurs and pass it the exception e.g. >> >> >> [ [self testCondition] whileTrue:[ self doSomeStuff] ] >> on: MyNotification >> do:[:ex | self openMyPresenterWith: ex] >> >> But that just results in lots of MyPresenter windows opening while the >> execution of the #whileTrue: loop runs its course. >> >> >> How do I pause the loop so I can use the MyPresenter window to modify and >> fix the condition that raised the MyNotification? >> >> The MyPresenter window just edits the contents of a couple Dictionaries >> so >> isn't too tricky but it isn't really as easy to do in a debugger as it is >> clicking a radio button and a "do it" button. >> >> >> Thanks >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 23, 2019

Re: [Pharo-users] Glorp + P3 + SQLite

by Pavel Krivanek

Hi Todd, we want to do some more testing before merging it into the upstream repository. -- Pavel Ät 21. 11. 2019 v 14:34 odesÃlatel Todd Blanchard via Pharo-users < pharo-users(a)lists.pharo.org> napsal: > Hi Pavel, > > I've just gotten around to figuring out BaslineOf and packages. I see > this work is in a branch on your own repository. > > Do you plan to do a pull request back to the original repository? I feel > like we have database code all over the place and no clear "official" > versions. > > Stll trying to figure out what is current and what is obsolete (Garage?) > > On Oct 19, 2019, at 5:18 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > Btw. there exists an updated version of Glorp: > github://pavel-krivanek/glorp:8.3.1-23-baseline > But the compatibility of it with SQLite was never tested > > -- Pavel > > so 19. 10. 2019 v 10:27 odesÃlatel Todd Blanchard via Pharo-users < > pharo-users(a)lists.pharo.org> napsal: > >> I loaded GLORP+P3 without issue. >> >> Trying to load SQLite3 - it also wants to load GLORP which complains of >> conflict. >> >> For P3 I used: >> >> Metacello new >> baseline: 'P3'; >> repository: 'github://svenvc/P3'; >> load: 'glorp'. >> >> >> >> For SQLite: >> >> Metacello new >> repository: 'github://PierceNg/glorp-sqlite3:pharo7'; >> baseline: 'GlorpSQLite'; >> load. >> >> >> but this fails with a conflict. I suspect the conflict is it wants to >> load in glorp again. >> >> I would also like to have mysql driver at some point. >> >> Any tips for getting these to play nice together would be great. >> > >

Nov. 21, 2019

Re: [Pharo-users] Glorp + P3 + SQLite

by Todd Blanchard

Hi Pavel, I've just gotten around to figuring out BaslineOf and packages. I see this work is in a branch on your own repository. Do you plan to do a pull request back to the original repository? I feel like we have database code all over the place and no clear "official" versions. Stll trying to figure out what is current and what is obsolete (Garage?) > On Oct 19, 2019, at 5:18 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Btw. there exists an updated version of Glorp: > github://pavel-krivanek/glorp:8.3.1-23-baseline > But the compatibility of it with SQLite was never tested > > -- Pavel > > so 19. 10. 2019 v 10:27 odesÃlatel Todd Blanchard via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> napsal: > I loaded GLORP+P3 without issue. > > Trying to load SQLite3 - it also wants to load GLORP which complains of conflict. > > For P3 I used: > > Metacello new > baseline: 'P3'; > repository: 'github://svenvc/P3 <>'; > load: 'glorp'. > > > For SQLite: > > Metacello new > repository: 'github://PierceNg/glorp-sqlite3:pharo7 <>'; > baseline: 'GlorpSQLite'; > load. > > but this fails with a conflict. I suspect the conflict is it wants to load in glorp again. > > I would also like to have mysql driver at some point. > > Any tips for getting these to play nice together would be great.

Nov. 21, 2019

Re: [Pharo-users] open spec window to handle exception and pause execution

by Richard Sargent

Paul, I'm going by memory and not Pharo specific. I believe the default handling of the end of the exception block is implicitly equivalent to ex return: nil. So, to get further handling of the exception, you need to #pass it or otherwise resignal it. Then the development environment will catch and handle the unhandled exception. On Wed, Nov 20, 2019, 20:53 PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > Hi - > > I have a subclass of ComposablePresenter (lets call it MyPresenter) that > seems to work how I want. When doing some processing I'd like to open > MyPresenter when an exception occurs and pass it the exception e.g. > > > [ [self testCondition] whileTrue:[ self doSomeStuff] ] > on: MyNotification > do:[:ex | self openMyPresenterWith: ex] > > But that just results in lots of MyPresenter windows opening while the > execution of the #whileTrue: loop runs its course. > > > How do I pause the loop so I can use the MyPresenter window to modify and > fix the condition that raised the MyNotification? > > The MyPresenter window just edits the contents of a couple Dictionaries so > isn't too tricky but it isn't really as easy to do in a debugger as it is > clicking a radio button and a "do it" button. > > > Thanks >

Nov. 21, 2019

open spec window to handle exception and pause execution

by PAUL DEBRUICKER

Hi - I have a subclass of ComposablePresenter (lets call it MyPresenter) that seems to work how I want. When doing some processing I'd like to open MyPresenter when an exception occurs and pass it the exception e.g. [ [self testCondition] whileTrue:[ self doSomeStuff] ] on: MyNotification do:[:ex | self openMyPresenterWith: ex] But that just results in lots of MyPresenter windows opening while the execution of the #whileTrue: loop runs its course. How do I pause the loop so I can use the MyPresenter window to modify and fix the condition that raised the MyNotification? The MyPresenter window just edits the contents of a couple Dictionaries so isn't too tricky but it isn't really as easy to do in a debugger as it is clicking a radio button and a "do it" button. Thanks

Nov. 21, 2019

Pharo Techtalk Nov 21

by Marcus Denker

Hi, Next techtalk will be *this* week (Nov 21): Topic: Discussion around Contributing to Pharo8 The idea is to discuss on Discord and may do some examples liveâ¦ Calendar entry: https://association.pharo.org/event-3419546 (sorry for the late announceâ¦ )

Nov. 19, 2019