- Pharo-dev - lists.pharo.org

[Ann] PharmIDE is renamed to TelePharo and moved to github
by Denis Kudriashov Aug. 24, 2017

Aug. 24, 2017

Hi. In the team we finally agreed on the end name for project. It is now TelePharo. Prefix "tele" means some action on or by distance. And this is what the project is about: to work remotely with Pharo images. Not all people like this name. But there are no name which was good for everybody. So it was decision. And we now continue with it. With new name project was moved to github repository https://github.com/dionisiydk/TelePharo with all dependencies. Feel free to fork and report bugs. You can find more details in my blog http://dionisiydk.blogspot.fr/2017/08/pharmide-is-renamed-to-telepharo-and.… . Best regards, Denis

5 6

[Ann] Workflow
by Max Leske Aug. 23, 2017

Aug. 23, 2017

Hi everyone, Stef has asked me whether Netstyle would release our workflow engine to the public, so here goes: Workflow (originally called "Aare") was conceived as part of an application that Netstyle developed back in the day. We can't release all of that code but we can release the engine. I've published it on Github with an MIT license (loadable via baseline): https://github.com/Netstyle/Workflow. Please note: - Workflow used to depend on OmniBase for storing objects (one of the main superclasses inherited from an OmniBase class for that). I've removed that dependency. - As this only includes the engine, there's no UI and the things shown in the whitepaper (see repository) are technically correct but are missing the appropriate model (the UI was written with Magritte and Morphic). - The code is from 2005 and we haven't touched it since then, so there might be a couple of hiccups. - We can't provide full support for the code but I'll be happy to talk to anyone interested in maintaining or improving it. We at Netstyle hope that Workflow may be useful to some of you. Cheers, Max

5 5

Latest Debian, Ubuntu and CentOS packages of the pharo-vm
by Holger Freyther Aug. 23, 2017

Aug. 23, 2017

Hi, when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well. Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a "latest" package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The "stable" VM is not built from pharo-vm.git (yet?) so it doesn't show on OBS yet. Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are: - pharo6-32 (32bit version) - pharo6-64 (64bit version) - pharo6-32-ui (32bit version with X11 dependencies) - pharo6-64-ui (64bit version with X11 dependencies) CentOS 6.8: # Add the repo $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… # Install 32bit packages (with X11 dependency for *-ui or not) $ yum install pharo6-32-ui.i686 or pharo6-32.i386 # Install 64bit packages $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 CentOS 7 (only 64bit): $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 Debian 8: # Add signing key $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… | apt-key add - # Update and install $ apt update $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) Ubuntu 14.04 LTS # Add signing key $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - # Update and install $ apt update $ apt install pharo6-32-ui pharo6-64-ui Ubuntu 16.04 # Add signing key $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - # Update and install $ apt update $ apt install pharo6-32-ui pharo6-64-ui

6 8

Launcher Opening Tiny Windows
by Sean P. DeNigris Aug. 23, 2017

Aug. 23, 2017

Check out this screenshot. <http://forum.world.st/file/n4962615/Screenshot_2017-08-19_19.png> The red arrow points to an open "window" of a newly created Pharo 6.0 based image, minimized to the point of barely being visible. Clicking on it makes a title bar somewhat more visible, the edges of which can then be dragged as any other window. Anyone else seeing this? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-Opening-Tiny-Windows-tp4962615.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 4

Catalog statistics (Who know this projects?)
by Esteban Lorenzano Aug. 22, 2017

Aug. 22, 2017

Soâ¦ I took a couple of minutes to do a small list of project description status: >From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. Which means 264 are mysterious projects nobody can guess what are they about. I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) Even very important projects like Seaside or Garage and Glorp are not documented. So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. Here the list of non-documented projects: http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main --- 'A4BP' 'Aconcagua' 'BootstrapMagritte' 'Chalten' 'CommandShell' 'Cormas' 'DependencyAnalyser' 'FamixJS' 'FontAwesome' 'Garage' 'GarageConnectionPool' 'GarageGlorp' 'Glorp' 'Grease' 'IniModules' 'Kendrick' 'Magritte3' 'MagritteMagic' 'MetaBoardBoard' 'MyFirstWebApp' 'NBOpenGL' 'NeoJSON' 'OSProcess' 'PetitParser' 'Phexample' 'Pier3' 'Pier3AddOns' 'ProcessWrapper' 'RewriteTool' 'Seaside3' 'SimplePersistence' 'Ston' 'Telescope' 'Woden' âXtreams' http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo40/main --- 'AconcaguaDeluxe' 'AthensSVG' 'Autotest' 'CPanel' 'CreativeCommonsLive' 'DevFlow' 'EventRecorder' 'ExtendedNumberParser' 'ExternalWebBrowser2' 'FixedDecimal' 'Ghost' 'GraphViz' 'Gravatar' 'Hubcap' 'Infinity' 'Mandrill' 'Mathex' 'MemoryMonitor' 'MinimalConnectors' 'Mocketry' 'MongoTalk' 'NBSQLite3' 'NumericalMethods' 'ODBC' 'OSOSX' 'OSWindows' 'PackageDependenciesAnalysis' 'PharoLauncher' 'PlagueDoctor' 'Pomodoro' 'RemoteAnnouncement' 'SandstoneDb' 'Scheduler' 'ScriptManager' 'Shapes' 'SmallUML' 'Spreadsheet' 'Spy' 'StateSpecs' 'SuffixConditionals' 'Teachable' 'TestMock' 'Trees' 'Twilio' 'Vidi' 'VistaCursors' 'Viva' 'WiringPi' 'WorkingSet' 'XBase' 'sQuick' âsQuick_new' http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main --- 'Actalk' 'Arduino' 'BabyMock2' 'CTranslator' 'DBPedia' 'DigitalOcean' 'Forum' 'Fuel' 'GTDebugger' 'GTInspector' 'GTInspectorCore' 'GTPlayground' 'GTPlaygroundCore' 'GTSpotter' 'GToolkit' 'GlamourCore' 'GlorpDBX' 'GraphET' 'InstanceEncoder' 'Marina' 'Mechanize' 'Memcached' 'Moose' 'Pastell' 'PharoOnlineHelp' 'ProfStef' 'PythonParser' 'RFB' 'Roassal3d' 'SQLite3' 'Smallapack' 'SmalltalkHub' 'Snapshotcello' 'SortFunctions' 'Spotlight' 'Stamp' 'Tide' 'VersionBrowser' âVersionner' http://www.squeaksource.com/MetacelloRepository --- 'AXAnnouncements' 'Adore' 'Aida' 'Ajp' 'Algernon' 'Alien' 'Amers' 'Announcements' 'AutomaticMethodCategorizer' 'BetaNineIPAddress' 'CAnalyzer' 'CairoGraphics' 'CampSmalltalkLondon' 'Cecinestpasunepomme' 'CharacterMap' 'Chronos' 'CloudforkAWS' 'Cog' 'Connectors' 'ContextS' 'Control' 'Country' 'Countryside' 'DBXBrowser' 'DBXTools' 'DependencyBrowser' 'DependencyView' 'EnhancedOmniBrowser' 'ExternalIconFamily' 'ExternalWebBrowser' 'FileMan' 'FileTree' 'Filesystem' 'GemTools' 'Gitocello' 'Glamour' 'Gofer' 'GoferProjectLoader' 'GoogleAnalytics' 'HPDF' 'HealthReportProducer' 'HelpSystem' 'ICal' 'InstancesBrowser' 'JQueryWidgetBox' 'JavaScriptAnalyzer' 'Jejak' 'Keymapping' 'Kozen' 'KyotoTycoonClient' 'MaBase' 'MaClientServer' 'Magma' 'Magmafy' 'Magritte' 'Magritte2' 'Magritte3AddOns' 'MagritteAddOns2' 'Metacello' 'MetacelloBrowser' 'MetacelloPreview' 'MockGemStone' 'Mondrian' 'Money' 'MonticelloRedirect' 'Murmansk' 'Nagare' 'NativeBoost' 'Neo4reSt' 'NewECompletion' 'NewInspector' 'NewOCompletion' 'Nile' 'NotificationsArea' 'O2' 'OCompletion' 'OPAX' 'ObjectMetaTools' 'OmniBrowser' 'OmniBrowserLukas' 'Orca' 'PagedReader' 'Pharo' 'PharoMorphicExtras' 'PharoNonCore' 'Phriak' 'Pier' 'Pier2' 'PierAddOns' 'PierAddOns2' 'PostMark' 'ProcessModel' 'Quaternion' 'REPL' 'Raphael' 'RatPack' 'RefactoringBrowser' 'RefactoringTools' 'RoelTyper' 'SIXX' 'SPort2' 'SandcastleThemes' 'Scamper' 'Scribo' 'Seafox' 'Seaside' 'Seaside28' 'Seaside28Examples' 'Seaside30' 'SeasideJSON' 'SeasideRest' 'SeasideTesting' 'SharedWorkspace' 'Shout' 'SimpleApplescript' 'SoapOpera' 'SpellingServices' 'SpyForO2' 'Sqnappy' 'SqueakCheck' 'SqueakDBX' 'SqueakFS' 'SqueakSource' 'StOMP' 'Stripe' 'SunnysidePlanning2' 'SwaLint' 'Swazoo2' 'TODO' 'TimerDaemon' 'Tuio' 'VMMaker' 'Waterfall' 'WebClient' 'WebTester' 'XMLRPC' 'XMLSupport' 'Zodiac'

15 22

SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail
by Alistair Grant Aug. 22, 2017

Aug. 22, 2017

Hi Everyone, I'm attempting to update to the latest Pharo7 image (918efe2, 32 bit), but am getting an error while loading OSsubprocess. The error occurs in FFISharedPool class>>initialize: initialize self flag: #removeIt. "This IF will be eliminated soon...only here temporary" (SystemVersion current highestUpdate >= 50558) ifTrue: [ SessionManager default registerToolClassNamed: self name ] ifFalse: [ Smalltalk addToStartUpList: self. ] because #highestUpdate is nil. The top of the stack is: UndefinedObject(Object)>>doesNotUnderstand: #'>=' FFISharedPool class>>initialize MCMethodDefinition>>postloadOver: [ :each | each postloadOver: (self obsoletionFor: each) ] in MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each postloadOver: (self obsoletionFor: ...etc... Based on the method above, it looks like highestUpdate used to be set based on the image number, and has presumably broken during the move to Pharo 7 and git. Earlier Pharo 7 images had it set to 0, which doesn't sound right. Since a build number was recently introduced (fogbugz 20321), should the highestUpdate be set to 70000+buildNumber? E.g. this image has an identifier of: Pharo 7.0 Build information: alpha.build.56.sha.918efe28fa3e6ad485b059dbf4ce675fd4086cf6 So highestUpdate would be 70056. Thanks! Alistair

3 6

[ANN] Pharo 6.1 (summer) released!
by Esteban Lorenzano Aug. 22, 2017

Aug. 22, 2017

Hi, We are releasing Pharo 6.1. Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: - running on macOS 64bits - adds cherry pick - adds major improvements on performance for big repositories - adds pull request review plugin - repositories browser: group branches by remote - adds bitbucket and gitlab to recognised providers on metacello integration - uses libgit v0.25.1 as backend - several bugfixes Other important change: - linux vm by default is now vm threaded heartbeat. We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. To download 6.1 version, you can go to http://pharo.org/download <http://pharo.org/download> page, or with zeroconf: wget -O- get.pharo.org | bash Enjoy! Esteban

16 36

19609 FileReference>>base should be before last separator
by Alistair Grant Aug. 22, 2017

Aug. 22, 2017

Hi All, I've just taken a look at issue 19609 FileReference>>base should be before last separator and wonder whether it is a correct interpretation of the original intentions. The original author of the issue, Michael, seems to feel that FileReferene>>base and FileReference>>basenameWithoutExtension are the same. My reading of the comments is that they perform a different function, i.e.: '/a/b/c.d.e' asFileReference base. "c" '/a/b/c.d.e' asFileReference basenameWithoutExtension. "c.d" are both the expected values, i.e.: - #base answers the name up to the first extensionDelimiter. - #basenameWithoutExtension answers the name without what is typically considered the file extension (the bit after the last extensionDelimiter). Not shown above, but: - #basename answers the entire filename, i.e. "c.d.e". Does anyone know the history of these methods? Cheers, Alistair

5 6

[ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes
by Marcus Denker Aug. 22, 2017

Aug. 22, 2017

[ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes https://pharo.fogbugz.com/f/cases/20306/Make-SUnit-loadable-by-Hermes https://github.com/pharo-project/pharo/pull/195

1 0

[Wanted] Newsletter topics and "takeovers"
by Marcus Denker Aug. 22, 2017

Aug. 22, 2017

Hi, As you for sure know, we have now a good monthly rhythm with the newsletter. http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486… <http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486…> And the number of subscribers is growing! If you have ideas for the next newsletters (August is done and will be posted soon, but we need content for September and laterâ¦) We need both small and larger items. Example for smaller news: - announcements of new libraries - new releasese - links to videos - links to blog posts And larger items. These have not just the title and link, but a short description and if possible a picture. (If you look at the older newsletters it should be clear what is needed). Another idea I had: we could even have âcomplete takeoverâ of a newsletter by someone who wants to edit a newsletter for one specific topic. This can be about one project, or just a âthemeâ (e.g. âcloud deployment with Pharoâ) if you are interested â> send a mail to board(a)pharo.org <mailto:board@pharo.org> Marcus

1 0