October 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] ring deprecation in pharo 7

by Stephan Eggermont

Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > the Ring 2 is not integrated because we do not want to have two version in > the system at once and we are not ready for the old Ring removal. However, > it is marked as deprecated to warn people that they probably should not > base their new code on it. That is not how I understand we deprecate code. How is this migration supposed to work? Stephan

Oct. 26, 2018

MetaLink>>level: failing?

by Vitor Medina Cruz

Hello, I am playing with MetaLink, really cool!, but I am having issues that I am unsure if it's some erro or if I am doing something wrong (I am using Pharo 6.1 32 bits in windows.). Consider: TestMetaLink>>execute UIManager default alert: 'Actual Version'. And in Playground: | link | link := MetaLink new metaObject: [ :object | UIManager default alert: 'Linked Version' ]; selector: #value:; arguments: #(#object); control: #instead. (TestMetaLink >> #execute) ast link: link. TestMetaLink new execute. link uninstall. This works as expected, an alert with 'Linked Version' is promped. But then suppose I want to execute the actual node alongside with the linked one considering some condition: | link choice | choice := true. link := MetaLink new metaObject: [ :object :selector :arguments | UIManager default alert: 'Linked Version'. choice ifTrue: [ object perform: selector withArguments: arguments]. ]; selector: #value:value:value:; arguments: #(#object #selector #arguments); control: #instead; * level: 0*. (TestMetaLink >> #execute) ast link: link. TestMetaLink new execute. link uninstall. As I understand, level:0 is necessary in order to avoid an infinite loop, but then I get an error: KeyNotFound: key #RFArgumentsReificationVar not found in Dictionary Am I doing something wrong? Is that an error? Best Regards, Vitor

Oct. 24, 2018

Re: [Pharo-users] Pharo for PWAs and Web Push Notifications

by Rafael Luque

Hi Phil, I have a general knowledge about these kind of cloud-powered PaaS and serverless solutions, though I have much more experience with the AWS portfolio: AWS Lambdas, Cloudformation, AWS Amplify, etc. I suppose they are more or less comparable with GCP's options. For sure, I will go in depth in the study of Firebase, and I don't dismiss it as an option for critical projects. However, in order to learn PWA and Pharo, I prefer to implement an agnostic solution without any vendor dependencies. In other words, when I think in Pharo not always think in terms of effort/results, or at least not the most immediate and pragmatic results. An acceptable tradeoff for me could be effort/learning that can be transformed to effort/results in the mid-term. Thank you! El mar., 23 oct. 2018 a las 15:41, phil(a)highoctane.be (<phil(a)highoctane.be>) escribiÃ³: > > > On Tue, Oct 23, 2018 at 11:32 AM Rafael Luque < > rafael.luque.leiva(a)gmail.com> wrote: > >> Hi all, >> >> I'm interested in developing progressive web applications (PWA) [1] in >> Pharo, so I'd like to know if anyone has been involved in such kind of task >> before and could share his experiences. >> > > The best thing I used for such stuff in terms of effort/results is using > Firebase. > > https://firebase.google.com > > Why? Because it provides a ton of the mechanisms for what you ask below, > works well, handles a ton of periphrenalia that I really do not want to > deal with directly. > > The good bit is that the frontend piece (the actual PWA) can be written in > any way you want provided that at the end there is some JS code handling > the UI. > > Services can be provided as cloud functions of Google Cloud and nothing > prevents them from being in Pharo. > > In the Firebase SDK, there is a command line tool that provides for local > execution of the generated JS and one can then push that code to the server > side. > Integration with Google general push notification system is easy to > implement as well. > > Costs of operation are quite low, even for pushing to large user bases. > > There is of course the "database" component (the actual "Firebase") that > is key/value pair system, along with read/write policies (which can be > quite complexand support quite a number of situations very well, provided > the schema is well done) and if what one needs is a relational DB, this is > not really the same thing. > > So, that's how I would do PWAs, they work nicely using that very stack. > > Phil > > >> At first sight, I was thinking in trying PharoJS [2] to build >> abstractions in Pharo for each PWA's client-side concept like Service >> Workers, Cache API, IndexedDB API, appshell architecture, etc. >> >> By the other hand, one of the more appealing features of PWAs is the web >> push notifications capability. To be able to send push notifications from a >> Pharo server I will also need an implementation of the Web Push Protocol >> [3] and the VAPID spec [4]. Do you know any previous related work in Pharo >> or should I think in my own implementation? >> >> Thank you! >> >> [1] https://developers.google.com/web/progressive-web-apps/ >> [2] https://pharojs.github.io/ >> [3] https://tools.ietf.org/html/draft-ietf-webpush-protocol-12 >> [4] https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 >> >

Oct. 24, 2018

Re: [Pharo-users] Pharo for PWAs and Web Push Notifications

by Rafael Luque

Hi Sven! As I understand, the HTTP/2 protocol is only required by the following 3 operations: - Receiving Push Messages for a Subscription. - Receiving Push Messages for a Subscription Set. - Receiving Push Message Receipts. The first two use cases are communications between the user agent (browser) and the Push Service (provided by the different browser companies). The operations I need to implement will be those which involve the application server, in our case implemented in Pharo. As far as I read these operations are sent over HTTP/1.1. Thank you! El mar., 23 oct. 2018 a las 14:30, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > Rafael, > > > On 23 Oct 2018, at 11:32, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > > > > By the other hand, one of the more appealing features of PWAs is the web push notifications capability. To be able to send push notifications from a Pharo server I will also need an implementation of the Web Push Protocol [3] and the VAPID spec [4]. Do you know any previous related work in Pharo or should I think in my own implementation? > > The two protocols you mention are based on HTTP/2, which we do not (yet) have. > We do have WebSockets in Zinc, which might help in understanding the issues at hand. > > Sven

Oct. 24, 2018

Re: [Pharo-users] Pharo for PWAs and Web Push Notifications

by Rafael Luque

Hi Tim! I will also check Willow following your suggestion. Thank you! El mar., 23 oct. 2018 a las 14:18, Tim Mackinnon (<tim(a)testit.works>) escribiÃ³: > Have you also looked at Willow - https://link.medium.com/Iyj4qo2BfR? > > It has spa âs in mind - although Iâm not sure of the proâs/cons vs Pharo > js which also looks good too. > > Would be interested in what you decide. > > Tim > > Sent from my iPhone > > On 23 Oct 2018, at 19:02, Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > > Hi all, > > I'm interested in developing progressive web applications (PWA) [1] in > Pharo, so I'd like to know if anyone has been involved in such kind of task > before and could share his experiences. > > At first sight, I was thinking in trying PharoJS [2] to build abstractions > in Pharo for each PWA's client-side concept like Service Workers, Cache > API, IndexedDB API, appshell architecture, etc. > > By the other hand, one of the more appealing features of PWAs is the web > push notifications capability. To be able to send push notifications from a > Pharo server I will also need an implementation of the Web Push Protocol > [3] and the VAPID spec [4]. Do you know any previous related work in Pharo > or should I think in my own implementation? > > Thank you! > > [1] https://developers.google.com/web/progressive-web-apps/ > [2] https://pharojs.github.io/ > [3] https://tools.ietf.org/html/draft-ietf-webpush-protocol-12 > [4] https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 > >

Oct. 24, 2018

[ANN] PEG Grammar, Compiler and Parser for PetitParser2

by Steffen MÃ¤rcker

Hi, I've just published a small tool that helped me prototyping grammars. PP2PEGGrammar - the original PEG ASCII syntax PP2PEGParserParser - parse a PEG and build a parser object PP2PEGParserCompiler - compile a PEG to methods and variables in a given parser class It is available as PetitParser2-PEG in the PublicStore (VW) and on GitHub (https://github.com/merkste/petitparser2/tree/PEG) Best, Steffen Am .10.2018, 22:46 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > I gave Xtreams-Parsing and PetitParser a shot and like to share my > findings.[*] > > The task was to parse the modelling language of the probabilistic model > checker PRISM. I've written a grammer of about 130 definitions in the > Xtreams DSL, which is close to Bryan Fords syntax. To avoid doing it all > again with PetitParser, I wrote a PetitParserGenerator that takes the > DSL and builds a PetitParser. > > The numbers below are just parsing times, no further actions involved. > For reference I show the times from PRISM (which uses JavaCC), too -- > although they involve additional verification and normalization steps on > the AST. > > input Prism XP PP > 230kB 14s 9s 2s > 544kB 121s 20s 5s > 1.1MB 421s 34s 8s > 1.4MB 1091s 47s 12s > 2.2MB 63s 16s > 2.9MB 81s 20s > 3.8MB 107s 25s > 4.4MB 123s 30s > > Please note that these times are not representative at all. It's just a > single example and I put zero effort in optimization. However, I am > quite satisfied with the results. > > [*] I was already familiar with the DSL of Xtreams-Parsing, which I like > very much. I did not consider SmaCC, as I find PEGs easier to use. > > Best, Steffen > > > > Am .10.2018, 20:14 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > >> Dear all, >> >> I have two questions regarding parsing frameworks. >> >> 1) Do you have any insights on the performance of SmaCC VS Xtreams >> Parsing VS PetitParser? >> 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it >> worth the effort? >> >> Sorry for cross-posting, I thought this might interest both communities. >> >> Cheers, Steffen

Oct. 24, 2018

Re: [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

by Alexandre Bergel

> I really like the tool as it makes cross-platform-life a lot easier. Thanks :-) > I really wish there was a similar tool for the reverse direction, too! That is interesting. Anyone else interested in such a tool? Cheers, Alexandre > > Cheers! Steffen > > Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users <pharo-users(a)lists.pharo.org>: > >> Thanks Steffen for your contribution to Pharo2VW. >> We reviewed and accepted your PullRequests. >> >> Alexandre >> >>> On Oct 19, 2018, at 6:29 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >>> >>> Nevermind, I figured it out easily. Must been blind before. >>> >>> Many thanks to the Iceberg team, the tool works like a charm in 6.1! >>> >>> >>> Am .10.2018, 10:58 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >>> > <---Schnitt---> >>> >> >> > > >

Oct. 24, 2018

Issue decoding source file

by Andrew Black

Iâm getting a walkback while attempting to look at the prior versions of certain methods. It happens on some methods, but not all. I think the the issue may be related to having characters in the method body that are represented as multi-byte sequences in UTF-8. The error is 'Illegal leading byte for utf-8 encodingâ from ZnUTF8Encoder Here are the top few stack frames: ZnUTF8Encoder>>error: ZnUTF8Encoder>>errorIllegalLeadingByte ZnUTF8Encoder>>nextCodePointFromStream: ZnUTF8Encoder(ZnCharacterEncoder)>>nextFromStream: ZnCharacterReadStream>>nextElement ZnCharacterReadStream(ZnEncodedReadStream)>>peek SourceFile>>peek ChunkReadStream(DecoratorStream)>>peek ChunkReadStream>>skipSeparators ChunkReadStream>>basicNextChunk ChunkReadStream>>next SourceFileArray>>readOnlyDo: BlockClosure>>ensure: SourceFileArray>>readOnlyDo: SourceFileArray>>changeRecordsFrom:className:isMeta:do: SourceFileArray>>changeRecordsFrom:className:isMeta: VersionBrowser>>buildChangeList VersionBrowser>>buildBrowser VersionBrowser>>browseVersionsOf: Everything looks reasonable. The underlying ZnBufferedReadStream is at position 2, and the first few bytes are 159 166 34 39 46 or, in hex: 9F A6 22 27 2E That first byte, 9F or 10011111, is not valid as the first byte in a UTF-8 sequence (itâs a valid continuing byte) â which presumably is why ZnUTF8Encoder is complaining. So, why is the VersionBrowser starting to look at that particular place in the source file? VersionBrowser >> buildChangeList looks like this: buildChangeList rgMethod sourcePointer ifNil:[ ^ #() ]. ^ (SourceFiles changeRecordsFrom: rgMethod sourcePointer className: rgMethod instanceSideParentName isMeta: rgMethod isMetaSide) collectWithIndex: [ :c :i | | rg | rg := c asRingDefinition. rg annotationNamed: #versionIndex put: i ] and rgMethod sourcePointer is the value of the sourcePointer attribute in the attributes dictionary in rgMehod. What can be done to fix this? Andrew

Oct. 23, 2018

Re: [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

by Steffen MÃ¤rcker

You're welcome. =) I really like the tool as it makes cross-platform-life a lot easier. I really wish there was a similar tool for the reverse direction, too! Cheers! Steffen Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users <pharo-users(a)lists.pharo.org>: > Thanks Steffen for your contribution to Pharo2VW. > We reviewed and accepted your PullRequests. > > Alexandre > >> On Oct 19, 2018, at 6:29 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >> Nevermind, I figured it out easily. Must been blind before. >> >> Many thanks to the Iceberg team, the tool works like a charm in 6.1! >> >> >> Am .10.2018, 10:58 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >> <---Schnitt---> >> > >

Oct. 23, 2018

Re: [Pharo-users] Pharo for PWAs and Web Push Notifications

by phil＠highoctane.be

Last spam bit: https://www.youtube.com/watch?v=iHqqUoqvYx4 On Tue, Oct 23, 2018 at 11:32 AM Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi all, > > I'm interested in developing progressive web applications (PWA) [1] in > Pharo, so I'd like to know if anyone has been involved in such kind of task > before and could share his experiences. > > At first sight, I was thinking in trying PharoJS [2] to build abstractions > in Pharo for each PWA's client-side concept like Service Workers, Cache > API, IndexedDB API, appshell architecture, etc. > > By the other hand, one of the more appealing features of PWAs is the web > push notifications capability. To be able to send push notifications from a > Pharo server I will also need an implementation of the Web Push Protocol > [3] and the VAPID spec [4]. Do you know any previous related work in Pharo > or should I think in my own implementation? > > Thank you! > > [1] https://developers.google.com/web/progressive-web-apps/ > [2] https://pharojs.github.io/ > [3] https://tools.ietf.org/html/draft-ietf-webpush-protocol-12 > [4] https://tools.ietf.org/html/draft-thomson-webpush-vapid-02 >

Oct. 23, 2018