November 2019 - Pharo-users

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

by PBKResearch

Sean I used Soup a few times, but found it difficult to interpret the output, because the parse did not seem to reflect the hierarchy of the nodes in the original; in particular, sibling nodes were not necessarily at the same level in the Soup. XMLHTMLParser always gets the structure right, in my experience. I think this is essential if you want to use Xpath to process the parse. The worked examples in the scraping booklet show how the parser and Xpath can work together. HTH Peter Kenny -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sean P. DeNigris Sent: 30 November 2019 16:43 To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] [ANN] XMLParserHTML moved to GitHub cedreek wrote > To me, far better than using Soup. Ah, interesting! I use Soup almost exclusively. What did you find superior about XMLParserHTML? I may give it a try... cedreek wrote > Google chrome pharo integration helps top to scrap complex full JS web > site like google ;) Also interesting! Any publicly available examples? How does one load "Google chrome pharo integration"? Also, there is often the "poor man's" way (albeit requiring manual intervention) by inspecting the Ajax http requests in a developer console and then recreating directly in Pharo. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 30, 2019

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

by CÃ©drick BÃ©ler

I couldnât get it from Zn as (I think) there are some js lib that defer the full rendering. I have the same problem with a site in France (leboncoin). They use https://datadome.co <https://datadome.co/> to complicate webscrapping. So an headless browser is the only solution I know. Cheers, CÃ©drick > Le 1 dÃ©c. 2019 Ã 00:23, Esteban Maringolo <emaringolo(a)gmail.com> a Ã©crit : > > Why use Chrome instead of ZnClient? To get a "real" render of the > content? (including JS and whatnot). > > Regards! > > > Esteban A. Maringolo > > On Sat, Nov 30, 2019 at 8:11 PM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> >> >>> >>> Also interesting! Any publicly available examples? How does one load "Google >>> chrome pharo integration Â»? >> >> "https://github.com/astares/Pharo-Chrome" >> "https://github.com/akgrant43/Pharo-Chrome Â» >> >> Cheers, >> >> CÃ©drick >> >> >

Nov. 30, 2019

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

by Esteban Maringolo

Why use Chrome instead of ZnClient? To get a "real" render of the content? (including JS and whatnot). Regards! Esteban A. Maringolo On Sat, Nov 30, 2019 at 8:11 PM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > > > > > Also interesting! Any publicly available examples? How does one load "Google > > chrome pharo integration Â»? > > "https://github.com/astares/Pharo-Chrome" > "https://github.com/akgrant43/Pharo-Chrome Â» > > Cheers, > > CÃ©drick > >

Nov. 30, 2019

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

by CÃ©drick BÃ©ler

> > Also interesting! Any publicly available examples? How does one load "Google > chrome pharo integration Â»? "https://github.com/astares/Pharo-Chrome" "https://github.com/akgrant43/Pharo-Chrome Â» Cheers, CÃ©drick

Nov. 30, 2019

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

by CÃ©drick BÃ©ler

Just a quick try to scrap a query from google search (using Chrome plugin + XMLHTMLParser + Path) : Really coolâ¦ and in few lines you get your own Â« google Â» powered search engine ;-). Nevertheless this is a bit slow (5 seconds for one page, around 20s for the 5 from the script (I think this might be doable to speed things a bit). HTH, CÃ©drick PS: code below in text searches := OrderedCollection new. query := 'black friday' urlEncoded. "chrome plugin" browser := GoogleChrome new. browser headless: true. browser open. page := browser firstTab. 0 to: 50 by: 10 do: [:paging | page get: 'https://www.google.com/search?q=',query,'&start=', paging asString. result := page html. dom := result parseHTML. "uses XMLHTMLParser" searches addAll: (dom xpath: '//div[@class="g"]/div/div/div/a/@href'). ]. searches size "64". searches first. "href=""https://www.fnac.com/black-friday""" "xpath cheat sheet: https://gist.github.com/LeCoupa/8c305ec8c713aad07b14"

Nov. 30, 2019

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

by CÃ©drick BÃ©ler

> ï»¿cedreek wrote >> To me, far better than using Soup. > > Ah, interesting! I use Soup almost exclusively. What did you find superior > about XMLParserHTML? I may give it a try... > Itâs mainly xpath which I find easier than navigating the html tree with soup or even The xmlHtmlparser. I usually copy the xpath form a web inspector. I have to tweak it a bit though. > > cedreek wrote >> Google chrome pharo integration helps top to scrap complex full JS web >> site like google ;) > > Also interesting! Any publicly available examples? How does one load "Google > chrome pharo integration"? Also, there is often the "poor man's" way (albeit > requiring manual intervention) by inspecting the Ajax http requests in a > developer console and then recreating directly in Pharo. > I just tried it once. There is a google chrome plugin that allows to use chrome headless to get the fully loaded html page. I need to try it again. A simple example Iâd like to do is to scrap google and remove advertised content ^^ This is btw Torsten package: https://github.com/astares/Pharo-Chrome Happy scrapping ;-) And thx Torsten for all ^^ Cedrick > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 30, 2019

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

by Sean P. DeNigris

cedreek wrote > To me, far better than using Soup. Ah, interesting! I use Soup almost exclusively. What did you find superior about XMLParserHTML? I may give it a try... cedreek wrote > Google chrome pharo integration helps top to scrap complex full JS web > site like google ;) Also interesting! Any publicly available examples? How does one load "Google chrome pharo integration"? Also, there is often the "poor man's" way (albeit requiring manual intervention) by inspecting the Ajax http requests in a developer console and then recreating directly in Pharo. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 30, 2019

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

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

by Sven Van Caekenberghe

> On 19 Nov 2019, at 15:15, Torsten Bergmann <astares(a)gmx.de> wrote: > > Nonetheless do not thank me - we should thank all the contributors who have added code > over the past years. Especially monty who did a lot of implementation work - the XML support stuff is > really well written code which is covered by over 6800 unit tests. Yes indeed, it is a great package tackling a complex subject.

Nov. 19, 2019

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

by Torsten Bergmann

Hi Sven, yes - took a while. And thanks for helping / giving me the right advice on Discord to fiddle with the encoding issues I found in some old mcz files. For now I focused on Pharo loading only - leaving aside the #gemstone part as I do not have an installation here. So I defer the work for checking the "gemstone compatibility" packages to people who actually need this. Should not be too hard as they are also included in the GH project as well - but might require adopting the baslines and further loading tests. Nonetheless do not thank me - we should thank all the contributors who have added code over the past years. Especially monty who did a lot of implementation work - the XML support stuff is really well written code which is covered by over 6800 unit tests. I hope that GitHub allows us to manage it even better in the future. At least we are not bound to STHub anymore. Step by step it goes ... BTW: There is now also a channel #xml on Discord so people can discuss related issues and "pharo-contributors" can align on moving on with the packages. Thanks T. > Gesendet: Dienstag, 19. November 2019 um 12:53 Uhr > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Betreff: Re: [Pharo-users] [ANN] XMLParser moved to GitHub > > Great! > > Thank you for this effort, it was probably much harder than it looks. >

Nov. 19, 2019

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

by Cyril Ferlicot

On Tue, Nov 19, 2019 at 12:33 PM Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > the STHub -> PharoExtras project "XMLParser" > > was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParser to > https://github.com/pharo-contributions/XML-XMLParser 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-XMLParser > 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 3.5.0 (with a moveable tag 3.5.x in case further > hotfixes are required). > > If you want to load use > > Metacello new > baseline: 'XMLParser'; > repository: 'github://pharo-contributions/XML-XMLParser/src'; > load. > > or try to load from catalog in Pharo 7 and 8. > > For referencing in own baselines I would suggest to use the 3.5.x tag line: > > ---------------------------------------------------------------------------------------------------- > xmlParserOn: spec > spec > baseline: 'XMLParser' > with: [ > spec > loads: #('Core'); > repository: 'github://pharo-contributions/XML-XMLParser:3.5.x/src' ]. > spec > project: 'XMLParser Tests' copyFrom: 'XMLParser' with: [ spec loads: #('Tests') ]; > project: 'XMLParser Tools' copyFrom: 'XMLParser' with: [ spec loads: #('Tools') ] > ---------------------------------------------------------------------------------------------------- > > Currently there is a dependency on OrderPreservingDictionary project which will be thrown out in > a later iteration (see attached graph and [1] for more details). > > More to come soon ... > > Have fun > T. > > [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November… Thank you very much for this effort! I'll migrate my projects depending on it this week probably! -- Cyril Ferlicot https://ferlicot.fr

Nov. 19, 2019

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

by Esteban Maringolo

+1 Thanks for the effort. Not only migrated the code, but also polished it, documented, and setup a CI for it. Regards! Esteban A. Maringolo On Tue, Nov 19, 2019 at 8:53 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Great! > > Thank you for this effort, it was probably much harder than it looks. > > > On 19 Nov 2019, at 12:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > the STHub -> PharoExtras project "XMLParser" > > > > was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParser to > > https://github.com/pharo-contributions/XML-XMLParser 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-XMLParser > > 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 3.5.0 (with a moveable tag 3.5.x in case further > > hotfixes are required). > > > > If you want to load use > > > > Metacello new > > baseline: 'XMLParser'; > > repository: 'github://pharo-contributions/XML-XMLParser/src'; > > load. > > > > or try to load from catalog in Pharo 7 and 8. > > > > For referencing in own baselines I would suggest to use the 3.5.x tag line: > > > > ---------------------------------------------------------------------------------------------------- > > xmlParserOn: spec > > spec > > baseline: 'XMLParser' > > with: [ > > spec > > loads: #('Core'); > > repository: 'github://pharo-contributions/XML-XMLParser:3.5.x/src' ]. > > spec > > project: 'XMLParser Tests' copyFrom: 'XMLParser' with: [ spec loads: #('Tests') ]; > > project: 'XMLParser Tools' copyFrom: 'XMLParser' with: [ spec loads: #('Tools') ] > > ---------------------------------------------------------------------------------------------------- > > > > Currently there is a dependency on OrderPreservingDictionary project which will be thrown out in > > a later iteration (see attached graph and [1] for more details). > > > > More to come soon ... > > > > Have fun > > T. > > > > [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November… > > <xmlparser.png> > >

Nov. 19, 2019

[ANN] Pastell moved to GitHub

by Torsten Bergmann

Hi, the STHub -> PharoExtras project "Pastell" (XPath-like DSL that makes navigation in XML DOM trees easier) was now moved from http://smalltalkhub.com/#!/~PharoExtras/Pastell to https://github.com/pharo-contributions/XML-Pastell 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-Pastell 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: 'Pastell'; repository: 'github://pharo-contributions/XML-Pastell/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. SIDE NOTE: ========== If you want to load Pastell and XPath [1] into the same image you will see in Iceberg they have colliding methods. Currently one can not share them since either XPath or Pastell tests are green depending on which one are used. This already was the case in the STHub project versions. I would suggest to only use Pastell or XPath until this could possibly be sorted out in the future. Bye T. [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November…

Nov. 19, 2019

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

by Sven Van Caekenberghe

Great! Thank you for this effort, it was probably much harder than it looks. > On 19 Nov 2019, at 12:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > the STHub -> PharoExtras project "XMLParser" > > was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParser to > https://github.com/pharo-contributions/XML-XMLParser 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-XMLParser > 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 3.5.0 (with a moveable tag 3.5.x in case further > hotfixes are required). > > If you want to load use > > Metacello new > baseline: 'XMLParser'; > repository: 'github://pharo-contributions/XML-XMLParser/src'; > load. > > or try to load from catalog in Pharo 7 and 8. > > For referencing in own baselines I would suggest to use the 3.5.x tag line: > > ---------------------------------------------------------------------------------------------------- > xmlParserOn: spec > spec > baseline: 'XMLParser' > with: [ > spec > loads: #('Core'); > repository: 'github://pharo-contributions/XML-XMLParser:3.5.x/src' ]. > spec > project: 'XMLParser Tests' copyFrom: 'XMLParser' with: [ spec loads: #('Tests') ]; > project: 'XMLParser Tools' copyFrom: 'XMLParser' with: [ spec loads: #('Tools') ] > ---------------------------------------------------------------------------------------------------- > > Currently there is a dependency on OrderPreservingDictionary project which will be thrown out in > a later iteration (see attached graph and [1] for more details). > > More to come soon ... > > Have fun > T. > > [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November… > <xmlparser.png>

Nov. 19, 2019

[ANN] XPath moved to GitHub

by Torsten Bergmann

Hi, the STHub -> PharoExtras project "XPath" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XPath to https://github.com/pharo-contributions/XML-XPath 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-XPath 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 2.2.0 (with a moveable tag 2.2.x in case further hotfixes are required). You can load using Metacello new baseline: 'XPath'; repository: 'github://pharo-contributions/XML-XPath/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. More to come soon ... Bye T.

Nov. 19, 2019

XMLParserStAX moved to GitHub

by Torsten Bergmann

Hi, the STHub -> PharoExtras project "XMLParserStAX" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParserStAX to https://github.com/pharo-contributions/XML-XMLParserStAX 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-XMLParserStAX 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.4.0 (with a moveable tag 1.4.x in case further hotfixes are required). You can load using Metacello new baseline: 'XMLParserStAX'; repository: 'github://pharo-contributions/XML-XMLParserStAX/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. More to come soon ... Bye T.

Nov. 19, 2019