May 2020 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

by Tim Mackinnon

ï»¿ Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was ok but over time frustrating to use and difficult to make the pipeline understandable ... I looked at Hugo and a few others but ended up going with Metalsmith (a JS static generator). I liked the plugable pipeline model of it, but cursed the state of Js tools (a few years ago) . Iâve been meaning for ages to reimplement it in Smalltalk with a nice oo composite pipeline model and an easy way to debug and visualise what is going when getting your template right. Combine this with the new headless image and it should easily plug into netlify . Tim >> On 23 May 2020, at 21:41, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > ï»¿ > Hi Esteban, > >> This comes really on time for me, I decided to rewrite to small sites I have using Jekyll, and as read all their tutorials I thought even of having a Jekyllst variation, that uses the Jekyll directories and other conventions, but uses Smalltalk as its engine. Of course this is far reached given my real availability these days, that's lower than usual. > > Cool anyway if thatâs something that interest you too. What do you think of https://gohugo.io ? > > Themes are pretty cool https://themes.gohugo.io > >> >> However I'd like to be part of conversations around this, and eventually contribute to it, because I already started playing with Jekyll (and Gatsby as well). > > Perfect :) > > This is not urgent but I need to put 2 websites online for September (simple ones). For now, Iâm trying around. Summer will be perfect for me to work on such project. > > Cheers, > > CÃ©drick > >> >> Regards, >> >> >> Esteban A. Maringolo >> >> >>> On Sat, May 23, 2020 at 10:15 AM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >>> Hi there, >>> >>> This post is just to talk about one side project Iâm exploring and interested in from a long time. I think it may interest other people here. >>> >>> Iâd like to have powerful (static based) web site so hosting is really cheap (even free) and hassle free. Iâve my own server for years, it is cheap and simple but, of course, it needs some maintenance (linux update, nginx scripts, â¦) even if tools are the simplest Iâve found. >>> >>> Recently thanks to student projects ;-), I found some time to learn what I find is a wonderful solution. This solution is to use GitHub DSCM, GitHub Pages and Jekyll (a ruby static site generator that is natively integrated) all together. >>> https://jekyllrb.com >>> >>> The beauty is that you can edit the site straight on GitHub. We get the power of version system and hosting for freeâ¦ >>> It literally is a CMS and the cheapest and reliable that I know of (grav might be another option). >>> >>> Of course, there are some Â« dynamic Â» content possibilities too (otherwise GitHub Pages is enough) >>> - blog posts are natively generated through new files according to a name convention. >>> - there are plugins too (but you have to watch for compatibility in GitHub). >>> >>> Dealing with forms and comments is possible >>> - solutions that are hosted on a third-party. Solution like Discus or formspree, â¦ (thatâs a NO GO to me) >>> - web service integration that you can host (note that form spree is on GitHub too https://github.com/formspree/formspree) >>> >>> This last point is where Iâd like Pharo (Zinc, Iceberg) to be integrated. Again we could imagine a web service system based on Zinc. I could manage form submissions that way and everything Iâd like but it may end up complex. Do I need a database ? Do I need to store information and therefore manage the underlying architecture. If it crash, I want only the endpoint to be not available but the whole site still working. >>> >>> An in between elegant solution os to use git for what itâs good at (versioning collaboratively through PR, and also reliable hosting in classic platforms). >>> >>> The idea is to use the PR mechanisms to submit stuff like blog comments (note that you have a free moderation system). >>> This is actually not limited to comments but all kinds of possible interactionâ¦ >>> >>> This way is (to me) better in terms of infrastructure management. Such a service also needs to be available (and maintained) but this is a very minimalist machinery (hanling POST request service only - no real content management as deferred to github). And again, a fail safe version (for the last version of the generated pages). >>> >>> Staticman (https://staticman.net) is a nice node application that allows to do this. Itâs possible to host the service too. >>> <GraphiqueCollÃ©-1.png> >>> >>> I can use this node app of course, but I believe we could have quite easily such an application in Pharo with Zinc. >>> I also wonder if we could use Iceberg to deal with this information straight in a pharo image (thatâd be cherry on the cake). >>> The super cherry of the cake would be pharo core and lib documentation, demos (you can have one gihub page by organization and/or users - in paid plans, you can have more for private stuff)â¦ One place, one process to contribute, either for code or documentation. >>> >>> Anyway, I have no real question except than asking for feedback and also to know if some people are interested in such project. >>> >>> Cheers, >>> >>> CÃ©drick >>> >>> nb: my hidden goal is to provide web site for people, unipersonal and small organizations. So you know, they pay for the service of creation, but then they own it and can do whatever they like. Of course we can also offer paid services like managing dynamic information content. More than comments, Iâd like to be able to deal with stuff like orders, facturation, even meeting planning through ics versioned files, etc. >>> This really is something Iâd like to be able to provide soon (less than 1 yr time - simplest web site with contact form and comments at least). It might become something more serious the future...

May 26, 2020

[Pharo 9.0] Build #311: 6392-Turn-deprecated-into-deprecatedtransformWith

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #311 was: FAILURE. The Pull Request #6393 was integrated: "6392-Turn-deprecated-into-deprecatedtransformWith" Pull request url: https://github.com/pharo-project/pharo/pull/6393 Issue Url: https://github.com/pharo-project/pharo/issues/6392 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 26, 2020

about deprecation

by StÃ©phane Ducasse

Hi do you think that nbCall: fnSpec "You can override this method if you need to" <ffiCalloutTranslator> self deprecated: 'use ffiCall: instead'. ^ (self ffiCalloutIn: thisContext sender) convention: self ffiCallingConvention; function: fnSpec library: self ffiLibraryName can take advantage of the transformWith: nbCall: fnSpec "You can override this method if you need to" <ffiCalloutTranslator> self deprecated: 'use ffiCall: insteadâ transformWith: â`@rec nbCall: `@argâ -> â`@rec ffiCall: `@argâ ^ (self ffiCalloutIn: thisContext sender) convention: self ffiCallingConvention; function: fnSpec library: self ffiLibraryName Thanks Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 25, 2020

Recent speed improvements in Pharo 9 debugger; remaining key/mouse event latencies

by Shaping

Hi all. Within the last hour or so, the folks on Pharo Discord#Spec (notably @Stepharo, @Esteban Lorenzano, @Steven Costiou, @stephan and anyone else I left out) fixed most of the speed problem in the NewTools debugger in Pharo 9. Its stepping action when stepping into and returning from a method (when rendering a new code pane before selecting the next evaluable) is nearly as fast as stepping within one method. The remaining latency is tiny and much more tolerable compared to what it was. The latency is longest on larger methods that need more rendering time. The cause seems to be speed of rendering with the FreeType2 library or possibly a Morphic bug (but that may have been what was fixed to create the current speed up). The P9 debugger is workable for me. Iâm closer to a port. The only serious remaining latency problems are the already described ones following key events (insert, delete, cursor moves) and mouse clicks. The #Spec folks say that this will be fixed when the event-machinery remaining in the VM is moved to the image. Can someone estimate when this will happen? I would like to beta-test and contribute. Shaping

May 25, 2020

Refactorings/code rewriting

by stephan

When creating Spec2 presenters, I noticed the automated refactorings (create accessors) don't all work. Do we need changes to the slots, or to the rewrite rules there? Stephan

May 25, 2020

[ANN] Next Pharo Sprint: May 29

by Marcus Denker

We will organize a Pharo sprint / Moose dojoMay 29 (this Friday) Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

May 25, 2020

[Pharo 9.0] Build #310: asDoitShouldStoreFormattedSource

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #310 was: FAILURE. The Pull Request #6359 was integrated: "asDoitShouldStoreFormattedSource" Pull request url: https://github.com/pharo-project/pharo/pull/6359 Issue Url: https://github.com/pharo-project/pharo/issues/asDoitShouldStoreFormattedSou… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2020

[Mm10s] 2020-05-25

by Esteban Lorenzano

### Last week: * PR to remove enlumineur UI and tests from Pharo because it is not working and is causing problems with the Spec2 0.6 merge. * [Spec2] new merge with P9 * [newtools] profile inspector to see why StHeaderBar rendering is so slow in morphic (and it was because of the use of some font not standard). * [spec2] optimise a bit the application os styles by keeping the defined font instead look for it each time. This speeds up StDebugger a lot :) * [vm] compiling the vm on fedora 32. Some problems around, but I got it building (more or less, I needed to use clang). Now, I have problems with the load of modules (like libgit2). * [spec2] fix a bug on gtk in which labels and images where not responding to events defined in #eventHandler. * [spec2] fix a bug that was preventing some commands on GtkMillerAdapter to be executed correctly * [spec2] fix a bug on toolbar buttons (gtk side) that was causing the vm to crash because sometimes I keep invalid references (this may cause problems later?). * [spec2] code: I made a HUGE refactor on how interactionModel works (now they are real objects, and users need to use one of the existent or implement their own) ### This week (starting 2020-05-25): - work with the new inspector. - fixes on Gtk backend - finish (If possible) the Fedora 32 build

May 25, 2020

[Pharo 9.0] Build #309: CleanupOCKeyedSet2

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #309 was: FAILURE. The Pull Request #6371 was integrated: "CleanupOCKeyedSet2" Pull request url: https://github.com/pharo-project/pharo/pull/6371 Issue Url: https://github.com/pharo-project/pharo/issues/CleanupOCKeyedSet2 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2020

[CfP] MPLR 2020 - 17th International Conference on Managed Programming Languages & Runtimes

by Stefan Marr

======================================================================== Call for Papers MPLR 2020 - 17th International Conference on Managed Programming Languages & Runtimes November 4-6, 2020 in Manchester, United Kingdom https://mplr2020.cs.manchester.ac.uk/ Follow us @MPLR_Conf ======================================================================== The 17th International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang) is a premier forum for presenting and discussing novel results in all aspects of managed programming languages and runtime systems, which serve as building blocks for some of the most important computing systems in use, ranging from small-scale (embedded and real-time systems) to large-scale (cloud-computing and big-data platforms) and anything in between (desktop, mobile, IoT, and wearable applications). This year, MPLR will be held in Manchester, UK, as permitted considering Health and safety concerns. For up-to-date details, check out the conference website: https://mplr2020.cs.manchester.ac.uk/ and follow us on Twitter @MPLR_Conf. The areas of interest include but are not limited to: * Languages and Compilers - Managed languages (e.g., Java, Scala, JavaScript, Python, Ruby, C#, F#, Clojure, Groovy, Kotlin, R, Smalltalk, Racket, Rust, Go, etc.) - Domain-specific languages - Language design - Compilers and interpreters - Type systems and program logics - Language interoperability - Parallelism, distribution, and concurrency * Virtual Machines - Managed runtime systems (e.g., JVM, Android Runtime (ART), V8, LLVM, .NET CLR, RPython, GraalVM, etc.) - VM design and optimization - VMs for mobile and embedded devices - VMs for real-time applications - Memory management and garbage collection - Hardware/software co-design * Techniques, Tools, and Applications - Static and dynamic program analysis - Testing and debugging - Refactoring - Program understanding - Program synthesis - Security and privacy - Performance analysis and monitoring - Compiler and program verification Submission Categories --------------------- MPLR accepts four types of submissions: 1. Regular research papers describing novel contributions involving managed language platforms. Research papers will be evaluated based on their relevance, novelty, technical rigor, and contribution to the state-of-the-art. Format: up to 12 pages, excluding bibliography and appendix 2. Work-in-progress research papers describing promising new ideas, with perhaps less maturity than full Papers. Work-in-progress papers will be evaluated with an emphasis on novelty and the potential of the new ideas instead of technical rigor and experimental results. Format: up to 6 pages, excluding bibliography and appendix 3. Industry and tool papers presenting technical challenges and solutions for managed language platforms in the context of deployed applications and systems. Industry and tool papers will be evaluated on their relevance, usefulness, and results. Suitability for demonstration and availability will also be considered for tool papers. Format: up to 6 pages, excluding bibliography and appendix 4. Posters They will be evaluated similarly to work-in-progress papers. Posters can accompany any submission as a way to provide additional demonstration and discussion opportunities. Format: poster and 1-page abstract MPLR 2020 submissions must conform to the ACM Policy on Prior Publication and Simultaneous Submissions and to the SIGPLAN Republication Policy. See http://www.sigplan.org/Resources/Policies/Republication/ Author Instructions ------------------- Submissions need to use the ACM `acmart` format with the `sigconf` style: https://www.acm.org/publications/proceedings-template If you are using LaTeX, submissions need to use the 'acmart' document class with the 'sigconf' option. For reviewing, please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. The standard settings of a 9 point font size and the Libertine/Biolinum font family are to be kept. All submissions need to be in PDF format. MPLR uses single-blind reviewing, i.e., author names are generally included in submissions. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://mplr2020.cs.manchester.ac.uk/submissions/ Important Dates --------------- Submission Deadline: 12 August 2020 Author Notification: 14 September 2020 Camera Ready: 05 October 2020 Conference Dates: 04-06 November 2020 All deadlines are 23:59 AoE (UTC-12h). AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. COVID-19 -------- Given the uncertainties of the current situation, we want to assure you that MPRL is going to happen. To increase the likelihood of having a physical conference, we are planning it for November. If this wonât be possible, we are preparing a virtual MPLR, learning from the conferences taking place right now and over the summer. In either case, the submission and reviewing process will happen as outlined to ensure timely feedback and continuity for our research work. Organization ------------ Program Committee: Jeronimo Castrillon, TU Dresden, Germany Shigeru Chiba, University of Tokyo, Japan Irene Finocchi, LUISS Guido Carli University, Italy Juliana Franco, Microsoft Research, UK Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Robert Hirschfeld, Hasso Plattner Institute, Germany Roberto Ierusalimschy, PUC-Rio, Brazil Georgia Kouveli, ARM, UK Burcu KÃ¼lahÃ§Ä±oÄlu Ãzkan, MPI-SWS, Germany Doug Lea, SUNY Oswego, USA Daryl Maier, IBM, Canada Mark Marron, Microsoft Research, USA Hidehiko Masuhara, Tokyo Institute of Technology, Japan Hanspeter MÃ¶ssenbÃ¶ck, JKU Linz, Austria Hannes Payer, Google, Germany Julien Ponge, Red Hat, France Aleksandar Prokopec, Oracle Labs, Switzerland Manuel Rigger, ETH Zurich, Switzerland Andrea Rosa, USI, Switzerland Jeremy Singer, University of Glasgow, UK Eli Tilevich, Virginia Tech, USA Sam Tobin-Hochstadt, Indiana University, USA Tobias Wrigstad, Uppsala University, Sweden General Chair: Christos Kotselidis, University of Manchester, UK Program Chair: Stefan Marr, University of Kent, UK If you are unsure whether a particular topic falls within the scope of MPRLâ20 or if you have any other questions, please do not hesitate to contact the Program Chair (s.marr(a)kent.ac.uk) -- Stefan Marr School of Computing, University of Kent https://stefan-marr.de/research/

May 25, 2020