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

Re: [Pharo-users] [Seaside] [ANN] TelescopeCytoscape for Seaside v1.0.0
by Cyril Ferlicot D. May 3, 2018

May 3, 2018

Le 04/05/2018 Ã 00:13, Tim Mackinnon a Ã©critÂ : > +100 and also for helping advance iceberg - weâre all desperate for a stable version with a reliable UI, and it sounds like this latest incarnation is really getting there? > As a quick answer I think that the new UI is much more user friendly and stable than the old one. I still miss some features but we are getting there step by step. With the old UI I would say I did 50% of the work with Iceberg and 50% with external git tools. Now I think it's more 80%-20%. And there is less blocking bugs (and I use the dev version ;) ) If the subject continue on Iceberg, it's better to open a new thread to keep this one around the Cytoscape connector for Telescope. Thanks. > Tim > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Cyril Ferlicot https://ferlicot.fr

1 0

[Voyage] How to declare an instance variable as transient?
by sergio ruiz May 3, 2018

May 3, 2018

Hi, all.. I have an instance variable that I donât want to save as part of the full project. I was wondering how to set this up. The documentation says: Lastly, attributes can be excluded from storage (and hence retrieval) by re- turning a VOMongoTransientDescription instance as the attribute descrip- tor. But I am not sure how to set this up in my class. 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

2 2

[ANN] TelescopeCytoscape for Seaside v1.0.0
by Cyril Ferlicot D. May 3, 2018

May 3, 2018

Hi, Telescope is an engine for efficiently creating meaningful visualizations. It allow users to create models of visualizations and to render them via connectors to visualization frameworks. Until now, it was hosted on SmalltalkHub and we just migrated it to Github. https://github.com/TelescopeSt/Telescope We also finished the v1.0.0 of the CytoscapeJs (http://js.cytoscape.org/) Telescope connector. It is build on top of Seaside to use visualizations as components. You can find the project at: https://github.com/TelescopeSt/TelescopeCytoscape And a demo at: https://demos.ferlicot.fr/TelescopeDemo -- Cyril Ferlicot https://ferlicot.fr

2 2

[Ann] Iceberg 0.7.5
by Guillermo Polito May 3, 2018

May 3, 2018

Time for the weekly Iceberg update. Iceberg 0.7.5. will be in the next Pharo build. Thanks to all brave users, issue reporters and contributors :). Key improvements: - Several improvements in metacello integration. (see #625, #664, #688 + more tests) - For those using CI, we think this release will also fix https://github.com/pharo-vcs/iceberg/issues/643 Infrastructure improvements: - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 - In the next release we plan to do a pass on 64 bits ** Pharo 6.1 backport ** - We plan to backport this version to Pharo 6.1 - Cyril has been using the development version of Iceberg on Pharo 6.1 for a couple of weeks now. - This plus the green CI encourages us to backport to Pharo 6.1 Detailed ChangesLog: #625 Non explicit error while loading a project #758 [Regression] Repair action clone is not setting pharo repository #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of IceTipURLLabelMorph did not understand #addEmphasis:) #749 Adding repair actions to the code subdirectory missing problem #655 Rename extension method buildToolbarItem of CommandActivator #755 Extracting the URL label behavior as a component that we can reuse #468 Commiting via Iceberg does not commit package removal #750 Add possibility to see current commit in Repositories/Package view #754 Showing and coping the Commit ID #753 Create branch dialog layout is broken #664 Package wrongly shown with "uncommited changes" status #752 Add "invalid ssh" #747 Cloning a Git repository should change the path with the project name. #738 Remove "pharo" Repository with "also remove from filesystem" gives error #746 Make tests run on pharo 6 #735 Issue while registering a new project on Pharo 6.1 #733 Add license file #740 Fogbugz panel: Improve label, focus order and layout #549 IceRestoreRepositoryModel should have a class comment #688 Duplicated project error when loading in a fresh image Enjoy, Guille in behalf of all people that contributed :)

2 2

[ANN] Heimdall logging manager for Seaside v1.0.0
by Cyril Ferlicot D. May 3, 2018

May 3, 2018

Hi! Guillaume Larcheveque begun a simple login manager for Seaside. I just finished to port it to github and we released the v1.0.0. It is still experimental and help is welcomed. Project can be found at: https://github.com/DuneSt/Heimdall -- Cyril Ferlicot https://ferlicot.fr

1 0

[ANN] PrismCodeDisplayer for Seaside v1.0.0
by Cyril Ferlicot D. May 3, 2018

May 3, 2018

Hi! We just finished the release v1.0.0 of PrismCodeDisplayer for Seaside. Prism (https://github.com/PrismJS/prism/) is a lightweight, robust, elegant syntax highlighting library. The Seaside binding allows to: Display code See line numbers Select code and act on the selection Customize the style of some text intervals Add links to text intervals Add a search feature Have a dynamic loading of the text content Copy the text content Have a minimap Project can be found at: https://github.com/DuneSt/PrismCodeDisplayer Demo at: https://demos.ferlicot.fr/PrismDemo -- Cyril Ferlicot https://ferlicot.fr

1 0

[Ann] Iceberg 0.7.3
by Guillermo Polito May 3, 2018

May 3, 2018

Hi all, We just introduced Iceberg 0.7.3 into Pharo. This new version solves several issues people had when contributing to Pharo in general and others. I've made a screencast on how to contribute to Pharo, and added some tutorial and glossary in Iceberg's wiki. Below the links and the changes log. Thanks for making your issue reports ^^. We will schedule a backporting to Pharo6.1 in a couple of weeks, once we have another iteration. Cheers, Guille # Contribute to Pharo with Iceberg 0.7.3 - wiki page: https://github.com/pharo-vcs/iceberg/wiki/Contribute-to-Pharo-with-Iceberg-… - Screencast: https://www.youtube.com/watch?v=PK2yCu2rWCc&feature=youtu.because This screencast shows how to use Iceberg 0.7.3 to contribute to latest Pharo 7, by cloning from scratch your own (potentially outdated) clone. This video will guide you through: - solve the "Missing local repository" by cloning - solve the "Fetch required" that appears because the fork is out of date - solve the "Detached working copy" by creating a new branch - use the pharo plugin to create an issue branch - make some changes, commit them and push them to your fork - make a pull request If you already have a clone, you can just import an existing repository from your disk. The rest of the instructions should be the same. If you don't have a fork, create one before doing anything else. New videos to come with more explanations. # Iceberg Glossary https://github.com/pharo-vcs/iceberg/wiki/Iceberg-glossary # 0.7.3 ChangesLog - #693 <https://github.com/pharo-vcs/iceberg/pull/693>: fixing problem when the announcement of changes in a package is nil. (bug, important) - #682 <https://github.com/pharo-vcs/iceberg/issues/682>: update update script (Pharo6-backport) - #681 <https://github.com/pharo-vcs/iceberg/issues/681>: Author name is not correctly decoded (UI, enhancement) - #680 <https://github.com/pharo-vcs/iceberg/issues/680>: Repair actions dialog should explain the situation (UI, enhancement, important) - #679 <https://github.com/pharo-vcs/iceberg/issues/679>: Create branch repair action should show create branch from issue if available (Pharo plugin, UI) - #678 <https://github.com/pharo-vcs/iceberg/issues/678>: Iceberg does not correctly recognize packages (bug, important) - #677 <https://github.com/pharo-vcs/iceberg/issues/677>: Unknown commit can only be solved with repair action (Model, bug, important) - #676 <https://github.com/pharo-vcs/iceberg/issues/676>: Unknown commit state is not properly shown (UI, bug, important) - #667 <https://github.com/pharo-vcs/iceberg/issues/667>: Merging branches with file deletion doesn't seem possible (bug, important, merge) - #666 <https://github.com/pharo-vcs/iceberg/issues/666>: Iceberg sometimes add a $ to commit message (Model, bug) - #662 <https://github.com/pharo-vcs/iceberg/issues/662>: The Pharo plugin has to do the fetch only if required. (Pharo plugin, enhancement) - #660 <https://github.com/pharo-vcs/iceberg/pull/660>: Add a star badge in the push button in case of a new branch () - #658 <https://github.com/pharo-vcs/iceberg/issues/658>: Progress Bar during checkout of Repository. (UI, enhancement) - #657 <https://github.com/pharo-vcs/iceberg/issues/657>: Confusing UI: Ghost Test maybe should be default? (UI, enhancement) - #656 <https://github.com/pharo-vcs/iceberg/issues/656>: Typo in Progress Bar (UI, bug) - #651 <https://github.com/pharo-vcs/iceberg/issues/651>: When pushing a new branch the list of commit is empty (UI, bug) - #650 <https://github.com/pharo-vcs/iceberg/issues/650>: "Create new branch from issue" is leaving image in detached working copy state () - #649 <https://github.com/pharo-vcs/iceberg/issues/649>: The VM is crashing when trying to use Iceberg from a saved image (bug) - #645 <https://github.com/pharo-vcs/iceberg/issues/645>: IceLibgitRepository should use "utilities" protocol instead of "utils" (clean up) - #644 <https://github.com/pharo-vcs/iceberg/issues/644>: Unnecessary temp in IceTipGitHubRepositoryPanel>>#getGitHubRepository" (clean up) - #643 <https://github.com/pharo-vcs/iceberg/issues/643>: LGit_GIT_ERROR: error authenticating: no auth sock variable loading a Tonel based baseline dependency in smalltalkCI (bug, important) - #639 <https://github.com/pharo-vcs/iceberg/issues/639>: Create pull request fails if branch has not been pushed (Github plugin, bug) - #636 <https://github.com/pharo-vcs/iceberg/issues/636>: The pull button should have a star badge when it has no upstream (UI, enhancement, important) - #634 <https://github.com/pharo-vcs/iceberg/issues/634>: Travis is not building Pull Requests (CI, bug, important) - #624 <https://github.com/pharo-vcs/iceberg/issues/624>: add "add remote" to remote picking on pull/push browsers (enhancement) - #610 <https://github.com/pharo-vcs/iceberg/pull/610>: Fix for issue #608 <https://github.com/pharo-vcs/iceberg/issues/608> and #607 <https://github.com/pharo-vcs/iceberg/issues/607>. (clean up) - #609 <https://github.com/pharo-vcs/iceberg/issues/609>: New branch repair action does not refresh dirty packages (UI, bug) - #583 <https://github.com/pharo-vcs/iceberg/issues/583>: Creating a tonel project does not commit the properties file (Model, bug) - #542 <https://github.com/pharo-vcs/iceberg/issues/542>: Bug during commit of a new package (Model, bug) -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

2 1

Iceberg Pharo6.1 on Microsoft Windows 7
by Federico.Balaguer May 2, 2018

May 2, 2018

Hello, I am trying to help some newbies to Smalltalk to use Iceberg on Pharo6.1 on Windows 7. I have a VirtualBox with Windows 7, I have the PharoLauncher installed from where I launch the Pharo 6.1 image. I cannot clone github repositories, I get a debugger: "LGit_GIT_ERROR: failed to get server certificate: The handle is in the wrong state for the requested operation" Do I have to compile libgit or libgit2 on the MSWindows virtual machine? thanks. federico -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

3 2

Pharo 7 image, some more size reducation
by Hilaire May 2, 2018

May 2, 2018

Hi, Pharo7 has proven to be a reliable host for Dr. Geo, and thank you for your advices and helps. In the past weeks several screenshotsÂ were posted on DrGeo twitter, all based on P7 built. Many notable tools or frameworks like Tonel, Glamour tool kit, Calypso, Metacello, VM builts have proven to be reliable. IÂ am now at the point where I am thinking about a new public release. Before that I want to squeeze a bit more the image. It is now about 36MB, and I am looking at some advices to shrink it a bit more. What is done is described there[1]. For example is it possible to remove Nautilus? A temporary built can be fetched from there[2], tests and feedbacks are also greatly appreciated. Thanks Hilaire [1] https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/… [2] https://www.dropbox.com/s/a4wb7c6od4fdl9k/DrGeo.app-18.06a.zip?dl=0 -- Dr. Geo http://drgeo.eu

5 11

Pharo Laucher > Copy and subfolders
by phil＠highoctane.be May 2, 2018

May 2, 2018

In the Pharo Launcher (Windows 19 here), I do a copy of an existing "image" (actually an entry in the right pane). The copy copies everything which is at the root and the subfolders but the subfolders end up being empty (apparently pharo-local and github-cache included). That's pretty annoying and makes the copy feature a lot less interesting. Is this the expected behavior? Recorded in https://github.com/pharo-project/pharo-launcher/issues/98 Phil

1 0

[ANN] ba-st Web Stack family gets a new member: Willow-Mixpanel and new releases
by Gabriel Cotelli May 2, 2018

May 2, 2018

Hi, We're happy to announce a new member in the Web Stack family hosted at https://github.com/ba-st/ : Willow-Mixpanel <https://github.com/ba-st/Willow-Mixpanel>. This is also a multi-release announcement of the following project versions: - Willow-Mixpanel <https://github.com/ba-st/Willow-Mixpanel> v1.0.0 - Provides Integration between Willow <https://github.com/ba-st/Willow/> and the Mixpanel Javascript API making easy to send events directly from the browser - HighchartsSt <https://github.com/ba-st/HighchartsSt> v7.0.0 - Updated Highcharts and Highstock JS libraries to version 6.0.7 - Improved Importing Tools - Migrated sources to Tonel - Willow <https://github.com/ba-st/Willow> v8.0.2. Changes since latest announcement: - Migrate sources to Tonel format - Improve ScrollIntoViewCommand - Updated JQuery to 3.3.1 - Improve libraries test cases to verify the file contents - Fixed Bug #108 <https://github.com/ba-st/Willow/issues/108>: Senders of #identifier must ensure the component has assigned an id - Added FAQs to documentation - Added an easy way to add additional libraries to a WillowApplication - Added table footer support - Added to interaction interpreters: - show:whileCallingServerToRender: This will replace anIdentifiedWebView contents with aRenderable in the DOM before doing the server call, and replace it again with the rendering obtained from the server call response - transform:into: This will replace anIdentifiedWebView content with aRenderable on the browser side - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v8.0.2 - Improve file deployment tests - Update datepicker plugin to v1.8.0 - Migrated sources to Tonel format - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v7.1.0 - Added JQuery UI dialog builder to component supplier - Improve file deployment tests - Migrated sources to Tonel format - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v5.0.2 - Improve file deployment tests - Migrated sources to Tonel format - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v5.0.0 - Improve package tagging and rename some classes to make the code more uniform - Use the new interaction facilities - RenoirSt <https://github.com/ba-st/RenoirSt> v5.0.0 - Migrated sources to Tonel format - Updated dependencies Find a more detailed changelog and migration instructions on the release pages of each repository. Special thanks to Tim Mackinnon <https://github.com/macta> for the constructive feedback driving some of the improvements in Willow and Francisco Ortiz <https://github.com/fortizpenaloza> for the Mixpanel support. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed. Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

2 1

Re: [Pharo-users] Why no collect:ifNone: ?
by Tim Mackinnon May 2, 2018

May 2, 2018

Yep - as I was reading the replies from you and Esteban - I was thinking there was something odd, and its correct, Iâve been careless - the problematic code had a trailing #sum to it, which is actually where the problem wasâ¦. total := schedule ifEmpty: [ 0 ] ifNotEmpty: [ :c | (c collect: [ :r | ((DateAndTime fromString: r end) - (DateAndTime fromString: r start)) asHours ]) sum ]. So you are both correct - it should have used inject. total := schedule inject: 0 into: [ :result :item | result + ((DateAndTime fromString: item end) - (DateAndTime fromString: item start)) asHours ]. Oops - thanks for being my sound board. Tim > On 30 Apr 2018, at 22:02, Francisco Garau <francisco.garau(a)gmail.com> wrote: > > > Have you tried #inject:into: ? Looks like what are needing here > > - Francisco > > >> On 30 Apr 2018, at 19:37, Tim Mackinnon <tim(a)testit.works> wrote: >> >> >> Hi - I hit a small bug in my lunch experiments with Willow where I wanted to sum up a collection of support hours. >> >> I was collect: in the hours worked and hadnât accounted for an empty collection. >> >> When I went to do it I was surprised there isnât a concept of #collect:ifNone: that mirrors something like at:ifAbsent: or the nicely readable collect:thenXxx: methods. >> >> Why is this? >> >> Iâm curious about style - and the elegance of my workaround : >> >> result ifEmpty: [ 0 ] ifNotEmpty:[ :r | r collect: [:I | i hours ]] >> >> which is ok, but seems a mouthful? >> >> Am I missing a trick? >> >> Tim >> >> Sent from my iPhone >>

1 1

Linux 64 bits and Pharo Launcher
by Rene Paul Mages (ramix) May 1, 2018

May 1, 2018

Hello and thanks for your help, No difficulties to launch Pharo 6.1 when I use the following package : https://files.pharo.org/platform/Pharo6.1-64-linux.zip but when I try to use Pharo Laucher : http://files.pharo.org/pharo-launcher/1.1/PharoLauncher-linux-1.1-x64.zip on my laptop (Linux 64 bits) the following error message occurs : http://ramix.org/roassal/error-message.png Details concerning my Linux distribution : DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" VERSION="18.04 LTS (Bionic Beaver)" -- All the best. Rene Paul Mages ( GnuPG_key 0x9840A6F7 ) http://renemages.wordpress.com/smalltalk/pharo/ http://blog.pharo.fr

1 0