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

Re: [Pharo-users] Personal wiki / information manager
by Evan Donahue Sept. 25, 2023

Sept. 25, 2023

Seems that Pharo is a magnet for this kind of project. I've been writing one as well and using it to organize my research notes. Does anyone working on personal info mgmt tools want to talk offline? I expect we're running into some of the same issues, both conceptual and technical. Evan

18 33

Pharo 6.0 and 6.1 64 bit freeze on MacMini
by Ted F.A.van Gaalen Jan. 27, 2020

Jan. 27, 2020

Hi, I reverted to 5.0 because Pharo 6.0 and 6.1 64 bit hangs on my Mac Mini with UDH 4K screen (may that has to do with?) with its maiden image (at first start after download when: I resize or go to full screen. Maybe VM problem? my mac Mini metrics: Hardware Overview: Model Name: Mac mini Model Identifier: Macmini6,2 Processor Name: Intel Core i7 Processor Speed: 2,6 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 4 GB Boot ROM Version: MM61.0106.B1F SMC Version (system): 2.8f0 maybe this problem was already reported, but could find it. Kind Regards TedvG

14 77

Namespaces (was Re: Behold Pharo: The Modern Smalltalk)
by Ben Coman Dec. 24, 2019

Dec. 24, 2019

On Thu, Oct 12, 2017 at 8:52 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > horrido wrote > > Having separate namespaces would be really good. > > VisualWorks has them. Why not Pharo? > > I can't remember ever hearing disagreement on this subject. It seems the > only questions have been: 1) how to do them *right*, The default position would be leveraging someone else's experience, so this begs the question, what is wrong in namespace implementations in VW, Gemstone, Squeak (as our immediate neighbours, then plus Dolphin, SmalltalkX, other languages) Are there been any research papers around comparing these? I found the "Pharo on Gemstone VM" talk impressive. The "develop on Pharo deploy on Gemstone" philosophy seems like a nice synergy for Pharo's commercial future. So a naive approach would be to do namespaces just like Gemstone. Maybe its not the best, but would it be "good enough" -- perfection being the enemy of done and all that jazz. cheers -ben > and 2) where they fall on the endless prioritized todo list >

13 24

Microsoft COM
by Ben Coman Sept. 27, 2019

Sept. 27, 2019

Hi Pablo, At work I managed to remote control Internet Explorer with Excel VBA like this... [1] http://www.automateexcel.com/vba/automate-internet-explorer and went looking for how similar might be achieved from Pharo. IIUC I discovered this would be done via Microsoft's Component Object Model, and then I bumped into your repo... [2] https://github.com/tesonep/pharo-com Could you advise the status and your plans for this? Since I see its only a few months old I've probably stumbled onto it prematurely, but I see no documentation or tests to discover how to use it. So I'll curious whether it makes something like [1] possible? And could you show how that would be done? cheers -ben P.S. For context, at work I automated IE since the intranet document management system (OpenText) does authentication via a javascript function in the browser, which doesn't compute with Microsoft's MSXML.DOMDocument component. So I use IE to do the authentication and grab the raw XML from IE to then stuff it into MSXML.DOMDocument from which I pull the data I need. But I'd love to do it with Pharo instead (if I can get IT to white list it) cheers -ben

7 10

ZnUrls with Non-ASCII characters
by Sean P. DeNigris March 23, 2019

March 23, 2019

'https://en.wiktionary.org/wiki/prÃªt#French' asUrl ==> ZnCharacterEncodingError: ASCII character expected. Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

3 7

Calypso question: adding a context menu item
by Juraj Kubelka March 16, 2019

March 16, 2019

Hi, To implement a context menu item. I have implemented a new class: -=-=-=- CmdCommand subclass: #ClyHelloCommand instanceVariableNames: '' classVariableNames: '' package: 'Calypso-Extensionsâ -=-=-=- with methods: -=-=-=-=- ClyHelloCommand class >> #systemBrowserMenuActivator <commandActivator> ^CmdContextMenuCommandActivator byRootGroupItemFor: ClyVariableSystemBrowserContext ClyHelloCommand >> # defaultMenuItemName ^'Say Helloâ ClyHelloCommand >> # execute self inform: 'Hello' -=-=-=-=- But it does not display in the context menu. I expect it next to âGenerate accessorsâ as I took this command as an example. What do I miss? Thanks, Juraj

3 3

Aggregation framework in MongoTalk?
by phil＠highoctane.be Feb. 18, 2019

Feb. 18, 2019

Is there anyone using the aggregation framework of MongDb through MongoTalk? It uses the aggregate() command, so I was wondering if this could be supported out of the box or if there is a need for an additional Operation. TIA Phil

2 1

Pharo 6 snap package
by Alistair Grant Sept. 20, 2018

Sept. 20, 2018

Hi Everyone, I've updated the Pharo 6 snap package for Ubuntu. The major advantages of using the snap package are: - No need to install all the 32 bit dependencies on a 64 bit system, they're all contained and isolated within the snap package. - Automagically distinguish between 32 bit and 64 bit images and run the appropriate VM (as with the ZeroConf package, the 64 bit VM still needs more testing). To get Pharo up and running on Ubuntu 16.04 or later: # Install Pharo $ sudo snap install --candidate pharo --classic # If your system isn't configured for threaded heartbeat: $ sudo pharo.config # Download the latest Pharo 6 image $ pharo.getimage # Go... $ pharo.ui Pharo.image # or: $ pharo Pharo.image eval 4+3 To get a list of available commands: $ snap info pharo If you're on Debian or Ubuntu 14.04 you'll need to install snapd, see https://snapcraft.io/docs/core/install The VM is the threaded heartbeat, dated 201705310241. The installation flags are: --candidate - The edge and beta channels are for development versions. It progresses to candidate and then stable. --classic - Snap packages are normally sandboxed for security reasons. Since Pharo is a development environment in which we want to be able to run any executable, or load any library, it is installed with access to the entire system (as the running user). Why use snap packages? - They include all dependencies. In particular, for the 32 bit versions, this means that it isn't necessary to install all the 32 bit architecture and associated dependencies. - Including dependencies means that there shouldn't be any problems with incompatible library versions when upgrading. Why not use snap packages? - It's a relatively new technology, with a number of rough edges. - There may still be issues with its sandboxing that I haven't discovered yet. - Because the package uses classic confinement, it isn't cross-distribution in practice (unfortunately). Please let me know of any other advantages or disadvantages you think should be listed here. If you don't trust me to configure your system correctly (which requires sudo): - All the scripts that make up the sub-commands are visible, e.g. pharo.config can be viewed at /snap/pharo/current/usr/bin/CONFIG The packaging code is at: https://github.com/akgrant43/pharo-snap Cheers, Alistair

7 12

Retina support in Pharo
by markm Sept. 20, 2018

Sept. 20, 2018

Hi Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I have tried searching for some answers, but alas could only find a handful of posts from a few years back. Any help much appreciated! Mark -- View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

10 14

Yet another Pharo in docker
by Herby VojÄÃk Sept. 18, 2018

Sept. 18, 2018

https://hub.docker.com/r/herbysk/pharo/

8 16

Howto BaselineOf
by Hilaire July 23, 2018

July 23, 2018

Hi, I have this enclosed BaselineOfDrGeo which I think contains mostly all I need. How should I load it? This code bellow does not work: (BaselineOfDrGeo project version: #development) load. By the way the PharoDebug log file is not recorded along the image, but at the user root directory. Is itÂ wished? ... -- Dr. Geo http://drgeo.eu

7 25

Macros?
by Debiller 777 June 12, 2018

June 12, 2018

Well, I've already asked about adding new literals to pharo or Smalltalk in general, however this time I have a better idea: macros. Can they be added? Because if I understand correctly they may be the only way to do that.

9 12

Problem with PharoLauncher on Ubuntu 18.04 (64 bit)
by Francisco Lizarralde May 31, 2018

May 31, 2018

Hi all, I was using the PharoLauncher (32 bits) version on Ubuntu 14.04 (32 bits) without problem. But two days ago I installed Ubuntu 18.04 (64 bits) and tried to run PharoLauncher-linux-1.1-x64 and when I tried to run a 6.1 image I got this message. Try this on a terminal: cd "/home/francisco/Pharo/vms/private/6521" && export SQUEAK_PLUGINS="" && "/home/francisco/Pharo/vms/private/6521/pharo" --nodisplay "/home/francisco/Pharo/images/Pharo 6.1 (stable)_1/Pharo 6.1 (stable)_1.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor|major := SystemVersion current major.minor := SystemVersion current minor.(major = 6 and: [ SystemVersion current highestUpdate >= 60509 ])ifTrue: [ minor := 1 ].stream << major asString;<< minor asString ]" And got this: Error. Could not determine platform's libc path for VM. Try forcing $PLATFORMLIBDIR in /home/francisco/Pharo/vms/private/6521/pharo, based on LIBC_SO. Please report what works to pharo [vm-dev] mail list. LIBC_SO= DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic UNAME=Linux Dynabook 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System seems to be 64 bit. You may need to (re)install the 32-bit libraries. Do I really need to install 32-bit libraries ? Any advice will be apreciated !!! Thanks in advance, Francisco -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 3

Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?
by Julien May 31, 2018

May 31, 2018

Hello, In Pharo 7, Specâs *Model classes were renamed following the pattern *Presenter, which is better. The original classes names (*Model) are still usable but their usage is deprecated in Pharo 7. I wonder if someone did a package for Pharo 6.1 that does the opposite: provide *Presenter classes in Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* allowing to keep them compatible with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The implementation would be quite easy : create an empty subclass using the pattern *Presenter for the name for each *Model class of spec. Thanks in advance, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

3 3

[ANN] Iceberg v1.0.0
by Guillermo Polito May 31, 2018

May 31, 2018

Hi all, Time for a new Iceberg update, that will be available in the next Pharo build. This time, there are lots of cleanups and enhancements. On the big highlights: - Tonel migration plugin is available in the "Other menu item" - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 bits). Thanks to everybody that participated in reviewing, opening/closing issues or even fixing a typo! # Documentation Just as a reminder, here you have a link to iceberg's wiki, convering some info like terminology, how to help us, and so on... https://github.com/pharo-vcs/iceberg/wiki # And some videos ;) - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI - Loading a Baseline https://youtu.be/brUHEOr-p_E - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M # Changes Log https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 Enjoy, Guille PS, detailed changes log below: # Cleanups #819 Fix tooltip typo in settings #800 Iceberg should be removed from the catalogue #801 Remove not referenced packages #803 Correct some lints in tests #806 Bad repair options when local repository is missing #725 Remove and clean old UI #794 Some classes should use category "utilities" instead of "utility" #791 Begin to remove old UI #734 Begin to remove old UI #576 Add link to github/gitlab ssh instructions # Enhancements #776 Upgrade to Commander 0.6.2 dependencies #765 Add command to copy SHA from history window #793 Add the commit message to history window #785 Metacello conflicts are not handled Metacello Integration # Bug fixes #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not implemented #748 Code subdirectory in empty repository #767 Error while pulling with renamed packages #814 Moving extension from a package removes extended class #807 When we do not have the right to push on a report we get an Error instead of the pop up! #768 Inverse merge preview shows wrong diff #784 Pulling from a non existing remote branch fails#810 #removePackage: should recursively delete files # Documentation #702 Create screencast - How to contribute to iceberg #774 Copy Wiki contribution page to pharo-project/pharo wiki # Infrastructure #761 Make tests run in 64 bits Pharo 7

6 11

Pharo 10th Anniversary
by Sven Van Caekenberghe May 30, 2018

May 30, 2018

Hi, This short post by StÃ©phane Ducasse is worth sharing: https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/ Congratulation ! Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

8 7

ESUG 2018
by Norbert Hartl May 30, 2018

May 30, 2018

https://esug.github.io/2018-Conference/conf2018.html <https://esug.github.io/2018-Conference/conf2018.html> says the registration is open. Did I miss an announcement. It is quite important, no? Norbert

2 1

Lazy vs eager initialization
by sergio ruiz May 30, 2018

May 30, 2018

If a model has a list of things.. such as a user that can/may have lots of pets, are there any real benefits to initializing the list of pets lazily? like: self pets := OrderedCollection new. vs. pets Â pets ifNil: [self pets: OrderedCollection new] Â ^ pets thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

4 5

Second Call for Papers: 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018)
by Andrei Chis May 29, 2018

May 29, 2018

------------------------------------------------------------------------ Call for Papers: 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018) co-located with SPLASH 2018 November 5-6, 2018 Boston, Massachusetts, United States https://conf.researchr.org/track/sle-2018/papers ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018), held in conjunction with SPLASH 2018 at Boston, Massachusetts on November 5-6, 2018. --------------------------- Scope --------------------------- With the ubiquity of computers, software has become the dominating intellectual asset of our time. In turn, this software depends on software languages, namely the languages it is written in, the languages used to describe its environment, and the languages driving its development process. Given that everything depends on software and that software depends on software languages, it seems fair to say that for many years to come, everything will depend on software languages. Software language engineering (SLE) is the discipline of engineering languages and their tools required for the creation of software. It abstracts from the differences between programming languages, modelling languages, and other software languages, and emphasizes the engineering facet of the creation of such languages, that is, the establishment of the scientific methods and practices that enable the best results. While SLE is certainly driven by its metacircular character (software languages are engineered using software languages), SLE is not self-satisfying: its scope extends to the engineering of languages for all and everything. Like its predecessors, the 11th edition of the SLE conference, SLE 2018, will bring together researchers from different areas united by their common interest in the creation, capture, and tooling of software languages. It overlaps with traditional conferences on the design and implementation of programming languages, model-driven engineering, and compiler construction, and emphasizes the fusion of their communities. To foster the latter, SLE traditionally fills a two-day program with a single track, with the only temporal overlap occurring between co-located events. --------------------------- Topics of Interest --------------------------- SLE 2018 solicits high-quality contributions in areas ranging from theoretical and conceptual contributions, to tools, techniques, and frameworks in the domain of software language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in contributions from the following areas: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral / executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth. * Fri 29 June 2018 - Abstract Submission * Fri 6 July 2018 - Paper Submission * Fri 24 August 2018 - Author Notification * Fri 31 August 2018 - Artifact Submission * Fri 14 September 2018 - Artifact Kick-the-Tires Evaluation Author Response * Fri 5 October 2018 - Camera Ready Deadline * Wed 10 October 2018 - Artifact Notification * Fri 12 October 2018 - Deadline for Artifact-Related Paper Updates * Sun 4 Nov 2018 - SLE Workshops * Mon 5 Nov - Tue 6 Nov 2018 - SLE Conference --------------------------- Types of Submissions --------------------------- * Research papers These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography. * Tool papers Because of SLEâs interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages excluding bibliography, and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords âTool Demoâ or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. * New ideas / vision papers New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages excluding bibliography. --------------------------- Artifact Evaluation --------------------------- For the third year SLE will use an evaluation process for assessing the quality of the artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted papers are invited to submit artifacts. More information is provided on the conference Website. --------------------------- Submission --------------------------- Submissions have to use the ACM SIGPLAN Conference Format "acmart" ( http://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template ( https://www.acm.org/binaries/content/assets/publications/consolidated-tex-t…) and that the document class definition is \documentclass[sigplan,screen]{acmart}. Do not make any changes to this format! Using the Word template is strongly discouraged. 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 in figures and tables are legible. SLE follows a single-blind review process. Thus, you do not have to blind your submission. All submissions must be in PDF format. Concurrent Submissions: Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy ( http://www.sigplan.org/Resources/Policies/Republication) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( http://www.acm.org/publications/policies/plagiarism_policy) Submissions that violate these policies will be desk-rejected. Submission Site: Submissions will be accepted at https://sle18.hotcrp.com/. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning novelty, correctness, significance, readability, and alignment with the conference call. New ideas / vision papers will be evaluated primarily concerning novelty, significance, readability, and alignment with the conference call. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review, at the discretion of the PC chairs. --------------------------- Awards --------------------------- * Distinguished paper: Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme committee. * Distinguished reviewer: Award for distinguished reviewer, as determined by the PC chairs. * Distinguished artifact: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. 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 the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Keynote --------------------------- We are very proud to announce that this yearâs SLE keynote will be given by Martin Rinard from the Massachusetts Institute of Technology. Martin Rinard is professor in the Department of Electrical Engineering and Computer Science at the Massachusetts Institute of Technology, and a member of the Computer Science and Artificial Intelligence Laboratory. His research focuses on software systems and related topics. The broad goal of his research is to obtain better software - making software more robust, resilient, and secure, improving the performance, verifying that the software satisfies important correctness, acceptability, reliability, or accuracy properties, or making systems (both software and hardware) easier to specify, build, maintain, or improve. More information on his research can be found at http://people.csail.mit.edu/rinard/. Details about his keynote at SLE will be announced soon on the conference Website. --------------------------- Program Committee --------------------------- Andrew Black, Portland State University, USA Anya Helene Bagge, University of Bergen, Norway Erwan Bousse, TU Wien, Austria Marco Brambilla, Politecnico di Milano, Italy Ruth Breu, University of Innsbruck, Austria Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Aston University, UK Juan de Lara, Universidad Autonoma de Madrid, Spain Thomas Degueule, CWI Amsterdam, Netherlands Juergen Dingel, Queen's University, Canada Tom Dinkelaker, Ericsson, Germany Sebastian Erdweg, Delft University of Technology, Netherlands Bernd Fischer, Stellenbosch University, South Africa Esther Guerra, Autonomous University of Madrid, Spain Daco Harkes, Delft University of Technology, Netherlands Robert Hirschfeld, University of Potsdam, Germany Michael Homer, Victoria University of Wellington, New Zealand Dimitris Kolovos, University of York, UK Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Marjan Mernik, University of Maribor, Slovenia Gunter Mussbacher, McGill University, Canada James Noble, Victoria University of Wellington, New Zealand Bruno Oliveira, University of Hong Kong, China Christoph Reichenbach, Lund University, Sweden Jan Oliver Ringert, University of Leicester, UK Bernhard Rumpe, RWTH Aachen University, Germany Markus Schordan, Lawrence Livermore National Laboratory, USA Anthony Sloane, Macquarie University, Australia Emma SÃ¶derberg, Google, Denmark Mark van den Brand, TU Eindhoven, Netherlands Tijs van der Storm, CWI Amsterdam, Netherlands Eelco Visser, Delft University of Technology, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Vadim Zaytsev, Rain Code, Belgium --------------------------- Artifact Evaluation Committee (tentative) --------------------------- Arvid Butting, RWTH Aachen University, Germany LuÃs Eduardo de Souza Amorim, Delft University of Technology, Netherlands Anna Maria Eilertsen, University of Bergen, Norway Abel GÃ³mez, Open University Catalonia, Spain Marcel Heinz, University of Koblenz-Landau, Germany Ludovico Iovino, GSSI, Italy Jesper Ãqvist, Lund University, Sweden --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please contact the organizers by email: sle2018(a)googlegroups.com.

1 0

Set Rounding mode for IEEE floating point operations
by Steffen MÃ¤rcker May 29, 2018

May 29, 2018

Hi, is there any way to set the rounding mode for IEEE floating point operations? Maybe something like > Double roundToMinusInfWhile: [... code goes here ...]Double > roundToZeroWhile: [... more code here ...] If not, is it possible to add this behavior, e.g., via a custom primitive? Best, Steffen

3 15

Code completion in Pharo?
by andreo May 26, 2018

May 26, 2018

Dear Pharoers, I'm just starting out with Pharo 6.1, and I'm trying to use code completion to interactively explore various objects and their messages. However, I'm having difficulties doing this efficiently - I think I must be missing something obvious, and I hope you can point me in the right direction. For instance, let's say I have the below in Playground: 'some text' asMorph and I would like to display the morph object as a window, but I don't know the exact message name, or whether such a message exists at all. If I type "Window", then the completion popup will show a long list of matching messages, but won't show their documentation or argument names, so it will be difficult to know exactly what these messages do. I can see that one can do "Do it and go" on an expression and then browse the available messages in Meta, but maybe there is simpler/faster way? How would an experienced Pharo user typically go about discovering the right messages in such situations? Best regards, Andrzej -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

5 5

Serving files with ZnServer
by Hilaire May 26, 2018

May 26, 2018

Hi, On P7, I try to server files with ZnServer, but got trouble: server := ZnServer startDefaultOn: 9595. server delegate: ( ZnStaticFileServerDelegate new Â Â Â directory: '/home/hilaire' asFileReference ; Â Â Â prefixFromString: 'files'; Â Â Â yourself). server logToTranscript. server start. The browser pointed at http://localhost:9595/files/ only print: Not Found /files/ The log reflects the not found: 2018-05-26 10:21:06 378 128292 Started ZnManagingMultiThreadedServer HTTP port 9595 2018-05-26 10:21:10 379 552905 Connection Accepted 127.0.0.1 2018-05-26 10:21:10 380 552905 Connection Accepted 127.0.0.1 2018-05-26 10:21:10 381 990536 Request Read a ZnRequest(GET /files/) 25ms 2018-05-26 10:21:10 382 990536 Request Handled a ZnRequest(GET /files/) 4ms 2018-05-26 10:21:10 383 990536 Response Written a ZnResponse(404 Not Found text/plain;charset=utf-8 19B) 2ms 2018-05-26 10:21:10 384 990536 GET /files/ 404 19B 6ms Any idea? Hilaire -- Dr. Geo http://drgeo.eu

3 3

feenk log
by Tudor Girba May 25, 2018

May 25, 2018

Hi, We were a bit silent the last couple of months. Quite a bit happened in the meantime, so here is a summary (for more fine grained announcements, you can follow us on Twitter): ---- Bloc ---- - Scrolling. We finally have a good scrolling support: https://twitter.com/feenkcom/status/991690465224331264 This might sound like a trivial feature, but it turns out it is not. We had a bug that forced us to rethink the support quite deeply in order to be able to debug it. To do this, we now can simulate time in Bloc, which is really cool: https://twitter.com/feenkcom/status/989797367523233797 https://twitter.com/feenkcom/status/988753142299938817 (as a side note, the bug we fought with was the last - Pannable element is a combination of a scrollable element with a scalable element, and it offers the possibility either to zoom in/out + scroll, or to fit screen and resize when the parent resizes. - PDF, SVG, PNG, JPG export (based on the underlying Moz2D support): https://twitter.com/feenkcom/status/976580153802358786 https://twitter.com/feenkcom/status/976578060429484032 - Better curve support: https://twitter.com/feenkcom/status/990967109193781249 https://twitter.com/feenkcom/status/990971530615107584 - Better debugging support for understanding bounds: https://twitter.com/feenkcom/status/989138457288167424 ---- Brick ---- - We now have simple list and columned list widgets. The list is both fast and scalable and supports rows of variable heights: https://twitter.com/feenkcom/status/984744251920658432 https://twitter.com/feenkcom/status/984143821192744961 - Basic tab widget: https://twitter.com/feenkcom/status/974420432240685062 - Looks: a mechanism for specifying element-specific composition and interaction. ---- GT ---- - Documenter saw some major improvements. Just a reminder, Documenter is the tool that enables live programming and previews directly within Pillar documents. We now have a capability similar to notebooks like Jupyter: https://twitter.com/feenkcom/status/996310432225820672 We use it extensively to document our code. For example, here is a tutorial about playing with looks in Bloc: https://twitter.com/feenkcom/status/973899862482866176 And we can also express whole tutorials based on Epicea: https://twitter.com/feenkcom/status/999975333972541440 - Diagrammer. We now have better editing support for detailed things such as arrow head: https://twitter.com/feenkcom/status/976341449267531776 While Diagrammer is apparently a tool for diagrams, it has a rather generic design that can be utilized for all sorts of use cases. For example, one side effect is that now all elements can be visually edited: https://twitter.com/feenkcom/status/982656456968241152 - Mondrian: Using the new pannable element, we can now zoom in/out and scroll, and we can also set element to fit screen. We can also drag elements around. - Inspector: we now have an initial support for multiple views associated with an object. The support is similar to the one from the current inspector. Have fun, The feenk team -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

3 2

BlueInk Pretty Printer Array Formatting
by Evan Donahue May 25, 2018

May 25, 2018

Hi, I've just discovered that I can change the auto-formatter settings and I'm trying to figure out how I can make array syntax behave nicely. If I write: a := {1. 2. 3. }. The formatter keeps it all on the same line. This is what I want. However, if one of those constants is a variable, as in: a := { 1. 2. b }. It breaks the whole array up across multiple lines, as shown, which quickly becomes unreadable for nested arrays. Is there some setting I can tweak to make it keep the array all on one line? Thanks, Evan

2 1

pharo location include korean charactor then look is not good.
by peter yoo May 25, 2018

May 25, 2018

so.. application location include korean charactor then broken title string in pharo window. (of course ubuntu 18.04 with gnome env) broken title is "ë°ííë©´". it's ok? or where to report? look a attached file please. -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

4 5