April 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Paul DeBruicker

Don't know about 4k. Have you tried a smaller monitor on your mini just to see? When pharo locks up from the command line you can get a stack dump in the terminal window you started pharo in. first find the pharo process you're interested in with ps -a | grep pharo then do a kill -SIGUSR1 <pharoProcessId> where you replace the <pharoProcessId> bit with the actual process number of your frozen pharo image TedVanGaalen wrote > Is pharo tested on 4K macs and/or mac mini with 4K screens? > so on anything with this resolution? > > Does Pharo or the VM emit a post-mortem log/dump file? cannot find any. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 17, 2019

Re: [Pharo-users] NewWave - WorkflowEngine

by BrunoBB

Hi Sebastijan, Excellent work !!! I have something similar (a BPM engine) but developed with GemStone Smalltalk: Code: https://github.com/brunobuzzi/BpmFlow Documentation: https://bpmflow.gitbook.io/project/introduction It can be ported to Pharo, from the top of my head i see a couple of issues with the port: - GemStone/S special indexes collection must be changed for regular Pharo collections. - GsQuery should be implemented in Pharo (maybe already is i do not know) or remove GsQuery references and so regular collection queries (select:, collect: anySatisfy and so on) The project is totally open source. Regards, Bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 17, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by TedVanGaalen

Sure. Which one? and with what image? However, don't know if that would make a difference, because I've been trying this repeatedly since Pharo 6.0 Squeak 5.2 (just downloaded and launched just to try) works ok, but for what I do, and previous work/classes made with Pharo 5.0, Pharo/Seaside would be preferable. Squeak uses another VM or so it seems (thought for a moment VMs were the same, that's why I tried Squeak,) regards from Souillac. (F) TedvG >From Squeak About ============================================================ /Applications/Squeak5.2-18229-64bit.app/Contents/Resources/Squeak5.2-18229-64bit.image Squeak5.2 latest update: #18229 Current Change Set: Unnamed1 Image format 68021 (64 bit) Virtual Machine --------------- /Applications/Squeak5.2-18229-64bit.app/Contents/MacOS/Squeak Croquet Closure Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-eem.2461] 64 bit Mac OS X built on Oct 20 2018 08:16:09 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) platform sources revision VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b5 Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2461 uuid: b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid: 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018 ============================================================ -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 17, 2019

Re: [Pharo-users] NewWave - WorkflowEngine

by TomaÅ¾ Turk

This is excellent, thanks! For busness applications, getting the tools for process-driven development is essential. Some emails ago there was an announcement on Netstyle's engine available here https://github.com/Netstyle/Workflow. Best wishes, Tomaz ------ Original Message ------ From: "Sebastijan Kaplar" <s.kaplar1(a)outlook.com> To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> Sent: 17. 04. 2019 15:03:23 Subject: [Pharo-users] NewWave - WorkflowEngine >Hello everyone, > >we've been working on a workflow engine written in Pharo. You can check >it out at: https://github.com/skaplar/NewWave >It is still in the early development and we discussed about making it >public so everyone interested can join, take a look or provide any kind >of feedback. I'm also at discord so you can contact me @skaplar. > >Best regards, >Sebastijan Kaplar

April 17, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Stephan Eggermont

TedVanGaalen <tedvga(a)gmail.com> wrote: > The freeze problem still exist. (since 2017, starting with Pharo 6) Hi Ted. It would be interesting to see if this is related to the fullscreen bug I described in an opensmalltalkvm issue. I was able to triangulate it to a set of commits, so could you try with a vm from just before? Stephan

April 17, 2019

Re: [Pharo-users] Migration from VW to Pharo

by Christian Haider

There is the bundle {Gemstone Fileout Project} in the public store (MIT license). Some information about it is at [1] and in the slides of the âPDF for Gemstoneâ talk at ESUG 2017 [2]. It is a generic code transformation machinery controlled by a declarative specification of changes to be applied to the source code (VW) to create target code (Gemstone). The tool is almost complete (class renamings, needed for namespace translations, are missing and overrides are not tested) and provably useful, since it was sufficient to port the PDFtalk project with it. To make it work for VW -> Pharo, class renamings need to get implemented, if you use namespaces in your source system. Also, the backend needs to get extended to create Tonel or FileOut format source files. Both features are not too difficult to add. If your project is large, this might be a way to do it. Especially, if you donât want only a one-shot migration, but to maintain an evolving project for different dialects, this approach is very attractive, I find. Happy hacking, Christian [1] https://wiki.pdftalk.de/doku.php?id=gemstonefileout [2] https://www.slideshare.net/esug/pdftalk-for-gemstone Von: Pharo-users <pharo-users-bounces(a)lists.pharo.org> Im Auftrag von Sreenath G K Gesendet: Mittwoch, 17. April 2019 13:52 An: pharo-users(a)lists.pharo.org Betreff: [Pharo-users] Migration from VW to Pharo Hello All, I just wanted to know if we have any tools for which we can make use of to migrate VW code base into Pharo. If something is there please let me know or your suggestion d to port it. Thanks in advance. Best Regards, Sree

April 17, 2019

Re: [Pharo-users] Migration from VW to Pharo

by Esteban Maringolo

You can migrate from Store to a git repository using a virtual machine with Linux and then continue working on Windows. It is certainly going to be simpler than having to export packages/bundles manually from VisualWorks. Esteban A. Maringolo On Wed, Apr 17, 2019 at 9:51 AM Sreenath G K <gk.sreenath(a)gmail.com> wrote: > > Hey, > > Unfortunately I have Windows though. I will have a look at it. Thanks for letting me know > > Best Regards, > Sree > > On Wed, Apr 17, 2019, 5:27 PM Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> There is this tool: https://github.com/GemTalk/SETT >> >> I used it with a few packages with no special Namespace and it worked just fine. >> >> It provides, however, several settings to map namespaces, packages, >> etc, so it should work. >> >> It only works in Linux though, because of the dependency to external >> process calls. >> >> Regards, >> >> Esteban A. Maringolo >> >> On Wed, Apr 17, 2019 at 8:53 AM Sreenath G K <gk.sreenath(a)gmail.com> wrote: >> > >> > Hello All, >> > >> > I just wanted to know if we have any tools for which we can make use of to migrate VW code base into Pharo. If something is there please let me know or your suggestion d to port it. >> > >> > Thanks in advance. >> > >> > Best Regards, >> > Sree >>

April 17, 2019

NewWave - WorkflowEngine

by Sebastijan Kaplar

Hello everyone, we've been working on a workflow engine written in Pharo. You can check it out at: https://github.com/skaplar/NewWave It is still in the early development and we discussed about making it public so everyone interested can join, take a look or provide any kind of feedback. I'm also at discord so you can contact me @skaplar. Best regards, Sebastijan Kaplar

April 17, 2019

Re: [Pharo-users] Migration from VW to Pharo

by Sreenath G K

Hey, Unfortunately I have Windows though. I will have a look at it. Thanks for letting me know Best Regards, Sree On Wed, Apr 17, 2019, 5:27 PM Esteban Maringolo <emaringolo(a)gmail.com> wrote: > There is this tool: https://github.com/GemTalk/SETT > > I used it with a few packages with no special Namespace and it worked just > fine. > > It provides, however, several settings to map namespaces, packages, > etc, so it should work. > > It only works in Linux though, because of the dependency to external > process calls. > > Regards, > > Esteban A. Maringolo > > On Wed, Apr 17, 2019 at 8:53 AM Sreenath G K <gk.sreenath(a)gmail.com> > wrote: > > > > Hello All, > > > > I just wanted to know if we have any tools for which we can make use of > to migrate VW code base into Pharo. If something is there please let me > know or your suggestion d to port it. > > > > Thanks in advance. > > > > Best Regards, > > Sree > >

April 17, 2019

Re: [Pharo-users] How to prevent Mustache from replacing & with & etc.?

by Norbert Hartl

> Am 17.04.2019 um 11:19 schrieb jtuchel(a)objektfabrik.de: > > Hi Norbert, > > thanks for commenting. I had a bad feeling about creating new class editions while I implemented them, so I appreciate your comments and I'll revisit my implementation, because I agree with all of your input here. > Especially extending the Visitor felt "wrong" or bad. DD can be helpful, but does not lend itself well to extensions, especially "personal" ones ;-) > > I didn't expect you to accept my extensions to Mustache anyways, becaus Mustache should be Mustache. > > But given that we now have multiple "standard" mechanisms for mixing text into templates in Smalltalk, and none fits very well for a lot of cases, I thought it could probably be a good starting point to look into Mustache as a powerful and nicely crafted starting point for more extendable implementations for inserting text. An extension point that builds on top of your > > parser := MustacheParser new. > parser delimiterExtensions at: $Â§ put: [ parser readLaTeXEscapedToken ] > > suggestion would be nice, but is not needed. > > I am just playing with ideas here. > > > Again: thanks a lot for your help and comments. Even if nobody else never needs or wants what I will implement here, this still helps me a lot in achieving what I need. > If you want to try you can checkout https://github.com/noha/mustache/tree/api-enhancements <https://github.com/noha/mustache/tree/api-enhancements> branch. I enhanced the API so you can set a custom visitor. Now you can do: aTemplate value: aDictionary visitor: MyCustomVisitor new Hope it helps! Norbert > > > Joachim > > > > > > > Am 17.04.19 um 10:52 schrieb Norbert Hartl: >> Joachim, >> >> I put the comments inline. >> >>> Am 17.04.2019 um 10:34 schrieb jtuchel(a)objektfabrik.de: >>> >>> So I think I found a solution for my problem which seems to work. Thanks for listening and your input of ideas. >>> >>> >>> What I did was to follow this idea: >>> >>> >>>> I am thinking of introducing a modifier, say Â§ to switch the html entity encoding for another one which I of course have to implement on my own. The end result would be: >>>> >>>> {{ myObject }} to encoe with HTML entities for all things (X)HTML >>>> {{& myObject }} to not encode at all (e.g. when I need & as & in the resulting String) >>>> {{Â§ myObject }} for an individually added encoding (tbd - for my LaTeX needs) >>>> >>> It turns out is was easy to implement a prototype of this (20 minutes?) >>> >>> There is only one tiny hole in this implementation: If I want to fill in a table body with Text that includes an &. I need to think about it later. Maybe I'll have to come back to the catcode thingie and choose some unlikely character for column separation and use my newly implemented {{Â§ encoding... >>> >>> >>> All that's needed to implement the above idea were these changes (VA Smalltalk Fileout Format): >>> >>> >>> !Character publicMethods ! >>> >>> asLaTeXString >>> "substitute characters like & into LaTex compliant elements" >>> "For protoytpe just encode &" >>> >>> (Dictionary with: $& -> '\&') >>> keysAndValuesDo: [:k :v | self = k ifTrue: [^v]]. >>> ^String with: self! ! >>> >>> !String publicMethods ! >>> >>> asLaTeXString >>> "substitute the < & > into LaTeX compliant elements" >>> "'<&>' asLaTeXString" >>> ^ self class new: self size streamContents: [ :s| >>> self do: [:c | s nextPutAll: c asLaTeXString ]]! ! >>> >>> >>> MustacheToken subclass: #MustacheLaTeXEscapedToken >>> instanceVariableNames: '' >>> classVariableNames: '' >>> poolDictionaries: ''! >>> >>> !MustacheLaTeXEscapedToken publicMethods ! >>> >>> accept: aVisitor >>> >>> aVisitor visitLaTeXEscapedToken: self! >>> >>> valueInContext: anObject >>> >>> ^(super valueInContext: anObject)asLaTeXString ! ! >>> >> This is the way it is designed so you can use your own token/visitor pair to extend it. >>> !MustacheParser publicMethods ! >>> >>> buildDelimiterExtensions >>> >>> ^Dictionary new >>> at: $# put: [self startSection: #MustacheSection abrAsClass]; >>> at: $/ put: [self endSection]; >>> at: ${ put: [self readDefaultUnescapedToken]; >>> at: $& put: [self readUnescapedToken]; >>> at: $!! put: [self readComment]; >>> at: $^ put: [self startSection: #MustacheInvertedSection abrAsClass]; >>> at: $= put: [self readChangeDelimiter]; >>> at: $> put: [self readPartial]; >>> at: $Â§ put: [self readLaTeXEscapedToken]; >>> yourself! >>> >> I donât think you need to change the parser to do that. >> >> parser := MustacheParser new. >> parser delimiterExtensions at: $Â§ put: [ parser readLaTeXEscapedToken ]. >> >> should do as well. If you have more specific needs I would subclass the parser >> >>> !MustacheVisitor publicMethods ! >>> >>> visitLaTeXEscapedToken: aToken ! ! >>> >>> >>> !MustacheWriteVisitor publicMethods ! >>> >>> visitLaTeXEscapedToken: aToken >>> >>> self addString: (aToken valueInContext: context)! ! >>> >>> >> I would make a visitor subclass for that. The problem is that the write visitor class name is hardcoded. We need to make that a setting. Then you could provide your own visitor. >> >> This way you can make it a real extension to mustache. >> >>> >>> So what do people think about this? Is this a worthwhile extension? Do you see problems on the horizon that I cannot see? >>> >>> >> I donât think it is a good extension. Mustache is implemented along the documentation and putting every use case in the code is not good. Changing the code so you can apply your changes or provide an extension package is needed of course. >> >> Norbert >> >>> Joachim >>> >>> >>> >>> >>> >>> >>> -- >>> >>> ----------------------------------------------------------------------- >>> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de >>> Fliederweg 1 http://www.objektfabrik.de >>> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >>> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >>> >>> >>> >> >> > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

April 17, 2019