March 2017 - Pharo-users - lists.pharo.org

Installing Voyage ??
by Hilaire March 27, 2017

March 27, 2017

When I follow the procedure at https://github.com/pharo-nosql/voyage to install Voyage in a 4.0 image, it leads to an unfonctonnal Voyage (timeout on socket when doing a query) My configure baseline is just as simple as the one bellow. All is loaded fine but Voyage. Any suggestion? Hilaire baseline10: spec <version: '1.0-baseline'> "This is Work-In-Progress and should be renamed upon stabilization" spec for: #common do: [ spec blessing: #baseline. [..] "External PROJECTS dependencies" spec project: 'voyage' with: [ spec className: 'ConfigurationOfVoyageMongo'; repository: 'github://pharo-nosql/voyage:master/mc'; versionString: #stable. ]. spec project: 'osprocess' with: [ spec className: 'ConfigurationOfOSProcess'; repository: 'http://www.squeaksource.com/OSProcess'; versionString: #stable]. spec project: 'mustache' with: [ spec className: 'ConfigurationOfMustache'; repository: 'http://www.smalltalkhub.com/mc/NorbertHartl/Mustache/main'; versionString: #stable]. spec project: 'neocsv' with: [ spec className: 'ConfigurationOfNeoCSV'; repository: 'http://mc.stfx.eu/Neo'; versionString: #stable]. spec project: 'seaside' with: [ spec className: 'ConfigurationOfSeaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; versionString: #stable]. spec project: 'bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://www.smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main'; versionString: #stable]. spec package: 'mold' with: [ spec repository: 'http://www.smalltalkhub.com/mc/philippeback/Mold/main']. "Our PACKAGES dependencies" spec package: 'Cofigest' with: [ spec requires: #('neocsv' 'mustache' 'osprocess' 'voyage')]; package: 'Cofigest-Bank products' with: [ spec requires: 'Cofigest']; package: 'Cofigest-Seaside' with: [ spec requires: #('Cofigest' 'Cofigest-Bank products' 'seaside' 'bootstrap' 'mold')]; package: 'Cofigest-Tests' with: [ spec requires: #('Cofigest' 'Cofigest-Bank products')] ] -- Dr. Geo http://drgeo.eu

4 14

Smalltalk on Stack Overflow Developers Survey 2017
by Davorin Rusevljan March 26, 2017

March 26, 2017

sorry to abuse pharo list, but I guess it is related enough. Smalltalk made it to SO developer Survey. Unfortunately it did not appear in most used languages list, but it got great place as "Second most loved language"! So for those of you who participated in the survey, it payed off. davorin

10 12

Voyage Timeout
by Hilaire March 26, 2017

March 26, 2017

Hi, When I configure a production image with command st handler as following: pharo myImage st --save --quit configureMyImage.st I notice at image start up, a Socket timeout error. In the configureMyImage.st script, among other things, I open a singleton Voyage repository. I added a 5s delay at the end of this script, just wondering if image was shutdown before Voyage establishes connection with the Mongo DB, but no. Any incompatibility issues to be aware of between st command handler (particularly the --save part) and Voyage repository? Thanks, Hilaire -- Dr. Geo http://drgeo.eu

3 5

REfactoring - extract method.
by Mark Bestley March 25, 2017

March 25, 2017

In Pharo 6 I select some code and then from menu choose Suggestions ExtractMethod If the code is one line it sometimes works but after the first fail it then logs "Could not extract code from method' If it has multiple lines including onbe message over lines I get a debugger call back In SugsNatilusContent selectedStatements selectedNode isMessage ifTrue: [ ^{selectedNode} ]. ^(selectedNode statements select: [ :stat | stat containedBy: selectionPreviousHighligth ]) selectionPreviousHighligth is nil That nil is passed to RBMessageNode containedBy: sp its anInterval is nil and it crashes. Apart from the bad spelling what is wrong here? -- Mark

2 1

Voyage hang
by Hilaire March 24, 2017

March 24, 2017

>From a production image, built from script with the voyage configuration as: >"External PROJECTS dependencies" >spec project: 'voyage' with: [ > spec > className: 'ConfigurationOfVoyageMongo'; > repository: 'github://pharo-nosql/voyage:master/mc'; > versionString: #stable. > ]. The image is first configured and used to populate a MongoDB, but then when doing a simple #selectAll on a persisted class of objets the image hangs! It is really weird because the Mongo browser from the same image let me see my database objects. So the MongoDB connection should be fine. I can alt+. the image, so enclosed the debug log. Any idea or direction to look at? Thanks Hilaire -- Dr. Geo http://drgeo.eu

1 0

[Deploy Application] Where to host using Gemstone/s?
by sergio ruiz March 23, 2017

March 23, 2017

I am ready to deploy a live production application, and am exploring my options.. I currently host a bunch of other things over at Digital Ocean. I would like to use them for this project to, using a new droplet. Does anyone know if there is a quick and easy way to install Gemstone/s on the Digital Ocean server? I will also need to port Teapot to Gemstone/s. If I need to install Gemtone/s from scratch on the server, which distro would be the recommended for such a thing> Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com <http://www.village-buzz.com/> http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/> http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

2 2

Fwd: GSoC 2017: Tips on Reviewing Student Proposals
by Serge Stinckwich March 23, 2017

March 23, 2017

Dear all, this is a short update for the Google Summer of Code 2017. The students have to submit your proposals on the Google website before April 3rd. See details below. I dunno exactly who are the students/mentors who are submitting a proposal for Pharo. Can the mentors (or students) send me in private an email about the name of the students/mentors + a title of your project ? Thank you very much. Regards, ---------- Forwarded message ---------- From: Google Summer of Code <summerofcode-noreply(a)google.com> Date: Mon, Mar 20, 2017 at 7:26 PM Subject: GSoC 2017: Tips on Reviewing Student Proposals To: sergestinckwich(a)gmail.com [image: Google Summer of Code] Hi Serge Stinckwich, Thank you for registering to be a GSoC 2017 mentor or organization administrator! We have many new mentors and organizations this year so we wanted to go through some important details to help you understand the process for the next couple of months. Please take the time to reach out to your organization administrator about what is expected of you this year as a mentor. We also encourage you to read the entire Google Summer of Code mentor manual <http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/> and the Roles and Responsibilities doc if you haven't done so already. Both the manual and Roles and Responsibilities doc were written by GSoC veteran Org Admins, Mentors, former students and Google Program Admins. They have helpful information about the program and how to participate successfully at each step in GSoC. *New GSoC Orgs*: the section about participating in your first GSoC has some great tips. To see all emails sent to mentors and org admins visit this page <https://developers.google.com/open-source/gsoc/2017/mentor-oa-announcements> that will continue to be updated throughout the program. Student Proposals As of today, students are able to submit their proposals via the website. Each student may submit up to 5 proposals to the program. They can submit multiple proposals to the same organization for different projects if they wish. Historically, the students with the best proposals reach out to the orgs early to receive feedback before submitting their final proposal. To encourage more students to seek feedback on their proposals we made draft proposals part of the official proposal workflow. Be sure to refresh your dashboard periodically so that you can see when new drafts are ready to review. You will not receive an email. We are encouraging the use of Google Docs for proposals as this will allow you to comment directly on the proposal (if the student sets their sharing settings correctly). Over the next couple of weeks you will be interacting with dozens and in some cases hundreds of students interested in working with your project. We know many of you may become overwhelmed and some students can be impatient, so you may want to have an auto-responder or some sort of canned response to let students know you are looking at their proposals but it could take X days to receive a response. Students *must* submit their final proposal as a PDF through the website. It will be visible to you after the deadline for student applications (April 3 16:00 UTC). You should make your decisions on which students to accept based on the contents of the final PDF proposal and your interactions with the student. Students can delete their proposals and you will not receive an email of the deletion. If a proposal disappears from your list, it is likely because they deleted it. Working with Students All student projects must have at least 1 mentor assigned to the project. We strongly encourage assigning a second mentor as a backup mentor or co-mentor. A mentor should not be the primary mentor for more than one or two students. Mentoring can be a lot of work and we donât want anyone to burn out and become frustrated with the program. Important GSoC 2017 Dates and Deadlines *March 20 - April 3 16:00 UTC*: Mentors and Org Admins review student draft proposals and give students feedback on their proposals. *April 3 - 16:* Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request. *April 17, 16:00 UTC*: Deadline to submit slot requests (OAs enter requests) *April 19, 16:00 UTC*: Slot allocations are announced by Google *April 19 - 24 16:00 UTC* : Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections) *April 24 - May 4:* Google Program Admins will do another review of student eligibility *May 4*: Accepted GSoC students/projects are announced *May 4 - 29*: Community Bonding Period *May 30*: Coding begins *June 26-30*: First evaluation period - mentors evaluate students, students evaluate mentors *July 24 - 28*: Second evaluation period - mentors evaluate students, students evaluate mentors *August 21- 29*: Students wrap up their projects and submit final evaluation of their mentor *August 29 - September 5*: Mentors submit final evaluations of students *September 6*: Students passing GSoC 2017 are announced Mentors Mailing List If you want to be included on the GSoC mentors mailing list be sure to opt in on your User Profile page. We will add anyone who has opted in to the list every few days for the next month. And then every couple of weeks throughout the program. You can always opt out once you have been added by unsubscribing using the link on any of the emails. Contact Us Please use the gsoc-support(a)google.com email address for questions so that anyone on our team can answer your question for you. We look forward to working with all of you over these next 6 months! Thanks again for being a mentor for GSoC 2017! Google Open Source Programs Office This email was sent to serge.stinckwich(a)gmail.com. You are receiving this email because of your participation in Google Summer of Code 2017. https://summerofcode.withgoogle.com To leave the program and stop receiving all emails, you can go to your profile <https://summerofcode.withgoogle.com/dashboard/profile/> and request deletion of your program profile. For any questions, please contact gsoc-support(a)google.com. Replies to this message go to an unmonitored mailbox. Â© 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

Re: [Pharo-users] Magritte extension
by DiegoLont March 23, 2017

March 23, 2017

Hi all, It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web ... I am all in favour of forming a group of active people to do some improvements on Magritte. I wrote on my todo list that I should feed back some of the improvements made in QCMagritte back to Magritte, but feeling a lack of interest from the community it dropped of my list. Maybe now is a good time to find some room in my schedule for doing so. First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer). Secondly. I agree that the most easy customisation of Magritte is using custom components. The Magritte components provided are quite basic. That is why in QCMagritte there is a number of components included that support AJAX functionality. It also contains a component that allows inline editing in a report. The idea about Magritte is also that the descriptions do not require a certain set of components. I.e. there was also an attempt on creating a Morph set of components ... that is a bit incomplete. Third. Feeding the improvements I have made in QC Magritte back into Magritte should probably be discussed this on the Magritte mailinglist. So I will do this in a separate post, mailing to bost lists. Cheers, Diego -- View this message in context: http://forum.world.st/Magritte-extension-tp4939046p4939547.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

4 7

[ANN] MaterialDesignLite for Seaside v1.1.0
by Cyril Ferlicot D. March 22, 2017

March 22, 2017

Hello everyone, Today I released the version v1.1.0 of MaterialDesignLite for Seaside. (https://github.com/DuneSt/MaterialDesignLite) Since this is a minor version it shouldn't break anything existing, but nobody can avoid bugs. If you encounter a regression, feel free to open an issue and I'll try to commit a hotfix soon. Thanks to Philippe Back, Paul Debruicker, Sabine Mana, Tobias Pape, Guillaume Larcheveque and Yann Lesage for the contributions and the feedback. Also thanks to everyone using this project. You can now find an image with the project on pharo-contribution's Jenkins and on PharoLauncher. (https://ci.inria.fr/pharo-contribution/job/MaterialDesignLite) You can find more detail on the README.md to start with the project. One of the future goal would be to add Functional tests with Parasol. Here is the changelog. You can find a more readable version at: https://github.com/DuneSt/MaterialDesignLite/blob/v1.1.0/CHANGELOG.md # [v1.1.0](https://github.com/DuneSt/MaterialDesignLite/compare/v1.0.2...v1.1.… (2017-03-22) ## Bug Fixes * **SelectWidget: Do not upgrade the dom at all node insertion** ([59c2534](https://github.com/DuneSt/MaterialDesignLite/commit/59c2534)) * **MDLDialog>>openButtonId: missing .close eventListener** ([262e6f3](https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **Chips: Use #ensureId rather than overriding #id & #id:** ([40fcca5](https://github.com/DuneSt/MaterialDesignLite/commit/40fcca5)) * **SortableTable: Visible page might end up out of bounds** ([b1833e8](https://github.com/DuneSt/MaterialDesignLite/commit/b1833e8)) * **NestedList: Tooltips are unusable** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) ## Features * **Anchors as buttons** This add the possibility to have links with the style of buttons to not break semantic ([ba3f0f7](https://github.com/DuneSt/MaterialDesignLite/commit/ba3f0f7)) * **Sliders: New features** This add a label with MD style, possibility to add an icon, possibility to add an output, show the bounds and a demo ([b203a1f](https://github.com/DuneSt/MaterialDesignLite/commit/b203a1f)) * **Dialog: Multiple opening buttons for a dialog** ([209d49a](https://github.com/DuneSt/MaterialDesignLite/commit/209d49a)) * **SelectWidget: Allow to customize the field** ([ace3e31](https://github.com/DuneSt/MaterialDesignLite/commit/ace3e31)) * **SelectWidget: Add tooltips on entries** ([14466d2](https://github.com/DuneSt/MaterialDesignLite/commit/14466d2)) * **SortableTable: Allow to have no pagination** ([aaa6c19](https://github.com/DuneSt/MaterialDesignLite/commit/aaa6c19)) * **SortableTable: Allow to personalize the style** ([69284d7](https://github.com/DuneSt/MaterialDesignLite/commit/69284d7)) * **NestedList: Add way to customize style + add some default styles** ([5f5088c](https://github.com/DuneSt/MaterialDesignLite/commit/5f5088c)) * **NestedList: Ajax actions on clic** ([feaba43](https://github.com/DuneSt/MaterialDesignLite/commit/feaba43)) * **NestedList: possibility to customize an entry** ([9421917](https://github.com/DuneSt/MaterialDesignLite/commit/9421917)) * **NestedList: Possibility to have an icon to the right of the list** ([27fa1fa](https://github.com/DuneSt/MaterialDesignLite/commit/27fa1fa)) * **NestedList: Add a filter** ([9ecffad](https://github.com/DuneSt/MaterialDesignLite/commit/9ecffad)) * **NestedList: Dynamically load children** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **NestedList: Search and loading should add a spinner while executing** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **Tooltip: API should let choose the position of the tooltip** ([de33e68](https://github.com/DuneSt/MaterialDesignLite/commit/de33e68)) ## Cleaning * **Dialogs** Clean javascript ([262e6f3]https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **NestedList** Extract the javascript into a file and use dataset instead of ids ([21c0535](https://github.com/DuneSt/MaterialDesignLite/commit/21c0535)) * **Extract Material Colors in another project** New repositories to get only the MDLColors: [https://github.com/DuneSt/MaterialColors](https://github.com/DuneSt/Materia… ([2efac41](https://github.com/DuneSt/MaterialDesignLite/commit/2efac41)) * **Improve Chips loading scripts** ([b366ddd](https://github.com/DuneSt/MaterialDesignLite/commit/b366ddd)) ## Infrastructure * **Travis and Appveyor CI** ([1afa628](https://github.com/DuneSt/MaterialDesignLite/commit/1afa628)) ## Compatibility ### Squeak * **`MDColor` has a lowercase class variable** ([888fb39](https://github.com/DuneSt/MaterialDesignLite/commit/888fb39)) ### Gemstone * **Use string in baseline and remove #asString** ([868f71b](https://github.com/DuneSt/MaterialDesignLite/commit/868f71b)) -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

1 0

UI with Spec, how to get mouse events ?
by Daniel BLANC March 22, 2017

March 22, 2017

Hi all, I'm building a Spec UI with an ImageModel and a LabelModel. The image is a map, and the label should display the mouse coordinates when the mouse cursor is on the map. I'm a newcomer to Pharo and Smalltalk, I've searched in the pharo image, and looked into events, on:send:to: message, but I don't know how to properly use them with Spec. For testing purpose I've tried just to get a mouse click with this: MyStuff >> initializeWidgets map := self newImage. mousePos := self newLabel. map on: #click send: #mouseClicked to: self But that doesn't work. Any idea how I can do this ? Thanks, Daniel

2 2