- Pharo-users - lists.pharo.org

[ANN] XMLParser moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

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…

4 5

[ANN] Pastell moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

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…

1 0

[ANN] XPath moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

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.

1 0

XMLParserStAX moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

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.

1 0

[ANN] OrderPreservingDictionary version 1.5.0
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

After - BitmapCharacterSet [1] - XMLWriter [2] were moved to "pharo-contributions" GitHub I also did a pass on OrderPreservingDictionary: https://github.com/pharo-contributions/OrderPreservingDictionary which is now available as 1.5.0 version (and also as moving tag 1.5.x in case we provide further hotfixes). Basically cleanups were applied: - add missing comments - cleanup packaging - fixing typos - adding tools group for GT extensions - align CI definitions with projects like Seaside - CI green again (throwing out non-working Gemstone, volunteers welcomed) - fix catalog entry - deprecating http://smalltalkhub.com/#!/~PharoExtras/OrderPreservingDictionary and http://smalltalkhub.com/#!/~Pharo/OrderPreservingDictionary You can load it using Metacello new baseline: 'OrderPreservingDictionary'; repository: 'github://pharo-contributions/OrderPreservingDictionary/src'; load or via catalog in Pharo 7 and 8. SIDE NOTE: ========== As of today XMLWriter still requires the "OrderPreservingDictionary" project as a dependency. OrderPreservingDictionary could be replaced by OrderedDictionary (same code, in the standard image) - I will do a pass on that later on. For now I focus on moving the XML stuff to GitHub first. [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-October/… [2] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-October/…

1 0

transactional saving of images
by Siemen Baader Nov. 18, 2019

Nov. 18, 2019

Hi, I have had a few occasions where I broke an image because I either ran out of disk space or had an endless loop that grew my image endlessly (I think). But why does Pharo not save the image & .changes file in hidden files named eg ~Pharo.image while it saves? Then it can rename them when saving was successful. Many unix programs do this. (I'm using pharo 6.1 so don't know if newer versions do this) -- Siemen

3 2

Tech talk & demo of Pharo in SoCal this Wednesday
by tbrunz Nov. 18, 2019

Nov. 18, 2019

For those who will be in Southern California this week, I will be giving a talk & demo of Pharo this Wednesday night in Pasadena. Details here: https://www.meetup.com/SGVTech/events/266517925/ -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: [Pharo-users] Where did all the Comments Go?
by Andrew Black Nov. 15, 2019

Nov. 15, 2019

To try and make some progress, I copied a working image from another machine. On startup (on MacOS 10.14.6) I get this walkback: File class(ProtoObject)>>primitiveFailed: File class(ProtoObject)>>primitiveFailed File class>>fileDescriptorType: File class>>fileDescriptorIsAvailable: Stdio class>>standardIOStreamNamed:forWrite: Stdio class>>stdout VTermOutputDriver class>>stdout BasicCommandLineHandler(CommandLineHandler)>>initializeStdout BasicCommandLineHandler(CommandLineHandler)>>initialize BasicCommandLineHandler>>initialize BasicCommandLineHandler class(Behavior)>>new [ self new activate ] in BasicCommandLineHandler class>>startUp: in Block: [ self new activate ] BlockClosure>>cull: WorkingSession>>executeDeferredStartupActions: WorkingSession>>runStartup: WorkingSession>>start: SessionManager>>launchSnapshot:andQuit: [ isImageStarting := self launchSnapshot: save andQuit: quit. wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... > On 19 Sep 2019, at 17:43 , Andrew Black <apblack(a)pdx.edu> wrote: > > Iâm coming back to Pharo after not having used it for several months. Iâm pleased to see that Pharo 7 is now stable and that work has started on Pharo 8. > > I downloaded a new Pharo Launcher (the old one could no longer figure out which version of the VM to use), used the Launcher to create a Pharo 7.0 stable image, and started loading my packages into it from github. > > My attempt to install the baseline of my code failed when some initialization code could not get the definitionComment for my parser (which is written using SmaCC). Normally, SmaCC stores oneâs whole grammar _as a method comment_ in a method called definitionComment. Oddly, this method was empty, even though the version on disk (in the file Grace-Parser.package/GraceParser.class/class/definitionComment.st) contained the comment, as I expected. > > Hoping to at least complete the installation of my code, I manually copied the comment from this file into Calypso and saved the method. It looked fine, but as soon as I moved Calypso to another method, and then back again, the comment had disappeared. I experimented with adding comments to other methods: they looked fine, and I could save the method, but if I moved to another method and then back, the comment had disappeared. > > Class comments have also disappeared. > > I donât think that this is a Calypso problem, because the loading of code from git would not involve Calypso. Rather it is a code storage problem. I saw a File System primitive failure when I launched my new image, but ignored it; Iâm guessing that the comments disappear because they are only in the file system, whereas the code is in memory. And for some reason I canât access the sources file? The changes file ahs been created as expected. > > I just tried downloading the VM manually, and running the âstableâ image that I created, and this time got a different file system primitive failure on startup: #createDirectory in MacStore. > > Whatâs going on? Whatâs the right way to get a working Pharo in the New World Order? > > Andrew > ____________________________ Prof. Andrew P. Black Department of Computer Science Portland State University Oregon, USA http://www.cs.pdx.edu/~black Telephone: +1 503 725 2411

4 4

Zinc & IdentityServer4
by Siemen Baader Nov. 15, 2019

Nov. 15, 2019

Hi, Iâm trying to log a registered user into a webshop (https://mad.coop.dk) using Zinc, but it uses IdentityServer4 ( https://github.com/IdentityServer/IdentityServer4) for authentication (at https://accounts.cl.coop.dk/) So there are more steps involved than just submitting credentials. Usually I just inspect how things work in the Firefox console, then replicate the interactions in Pharo, but this system is a bit too complex, with many unrelated requests happening. Can anyone guide me towards the correct steps to sign in? thanks Siemen

4 5

[Ann] TF-Login for Seaside 3.3 for Pharo 7
by Pierce Ng Nov. 15, 2019

Nov. 15, 2019

Hi all, Apologies for the x-posting. As per subject, I've ported TF-Login to Seaside 3.3 for Pharo 7. To load, start with fresh Pharo 7 image: Metacello new baseline: 'Seaside3'; repository: 'github://SeasideSt/Seaside:v3.3.3/repository'; load. Metacello new baseline: 'TFLogin'; repository: 'github://PierceNg/TF-Login:pharo7/src'; load. The baseline doesn't load Seaside, in case you want to load it into an image that already has Seaside. Start Test Runner and run the TF-Login tests. All 62 tests should pass. Pierce

1 0