January 2014 - Pharo-dev - lists.pharo.org

Voyage backends
by Torsten Bergmann Jan. 16, 2014

Jan. 16, 2014

Hi Esteban, if I understood correctly Voyage is primarily an abstraction layer to access NoSQL databases. Currently MongoDB or the image can be used as a backend. Are there any other backends available or planned (for instance to UnQLite using PUnqlite [1]). As UnQLite is an embeddable database of really small size I guess it will be as sucessful for the NoSQL world as SQlite3 was for the relation DBMS world and supporting it as one possible backend for Voyage might be a real plus. At least I see that MongoDB is 102MB to install before one can use it and unqlite library [2] is only a few KB ;) So it is easier to package, deploy, ... - I havent checked the other features of Mongo vs. PunQlite so far. Any comments about backends in general or UnQlite in particular? Thx T. [1] http://forum.world.st/ANN-PunQLite-a-new-NoSQL-wrapper-for-Pharo-td4732162.… [2] https://github.com/mumez/PunQLite/tree/master/binary

2 1

[ANN] Pillar release 0.6
by Damien Cassou Jan. 16, 2014

Jan. 16, 2014

Dear lists, I'm proud to announce the 0.6 release of Pillar, a syntax and associated tools to write and generate documentation and books. Pillar is currently used to write the Enterprise Pharo book (https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/) and other projects. The attached screenshot shows a part of the Voyage documentation generated by Pillar (from https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english/bl…) Pillar has many features: - simple markup-based syntax with references, tables, pictures, captions... (this is the syntax of Pier) - export to HTML, LaTeX and markdown (more to come) - customization of the export through a dedicated STON configuration file - support of templates using the Mustache templating engine - syntax-highlighting of generated code blocks (not yet in LaTeX) - configurable numbering of section titles and figures - ... Pillar has also: - a 5-minutes tutorial (https://github.com/DamienCassou/pillar-documentation/blob/master/README.md#…) - a documentation (https://github.com/DamienCassou/pillar-documentation) (in progress) - a good test coverage (91% with more than a 1000 executed tests) - a continuous integration job (https://ci.inria.fr/pharo-contribution/job/Pillar/) - a command-line interface (https://github.com/DamienCassou/pillar-documentation#5--command-line-interf…) - several existing use cases: https://github.com/DamienCassou/pillar-documentation#6--example-pillar-usage -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

7 9

how to debug NB?
by paolo.bernardi.67＠gmail.com Jan. 16, 2014

Jan. 16, 2014

Hi all, I'm trying to write a binding of wxWidgets 3.0 into Pharo 3.0. I wrote some glue-code to implement a C interface to wxWidgets (that is C++). I can open windows on the screen of my Winxp-box, I place buttons into them, I change position and size of the windows and I can attach BlockClosures on MOVE and CLICK events. Wow: if a cow-boy like me is able to do that, it means NativeBoost is really magic! Here the question. Sometime Pharo crashes. it happens when an event occurs (and a st callback was attached on). In some sessions Pharo stay alive, in some other it dies. What should I do? Re-compile a vm and run Pharo in debug mode? I'm not sure I could understand the reason of the crash... Thanks paolo --- Questa e-mail Ã¨ priva di virus e malware perchÃ© Ã¨ attiva la protezione avast! Antivirus. http://www.avast.com

4 9

Pharo3: Update 700
by Marcus Denker Jan. 16, 2014

Jan. 16, 2014

Hi, Pharo3 just got it's 700th update. This is a record for any Pharo release yet (Pharo2 was released with just below 600 updates). Every update contains the code of 1-5 issues from the issue tracker. Fixes, improvements, but even completely new subsystems. So the number does not work at all as a metric ;-) On the issue tracker, we have 1930 closed issues tagged for Pharo3, but many more where evaluated and closed without that tag (e.g. concerning infrastructure). 68 cases where resolved the last 7 days alone (!!). In the issue tracker, we have still 51 issues for Pharo3 that are rated "must fix" or higher, but with the speed of bug fixing we see, we are very much on the road to have a very stable release in March. The issue tracker is at https://pharo.fogbugz.com

1 0

[pharo-project/pharo-core] dfdd25: 30700
by GitHub Jan. 16, 2014

Jan. 16, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: dfdd255891e92f21f81e1fcc63a2cd439a44e042 https://github.com/pharo-project/pharo-core/commit/dfdd255891e92f21f81e1fcc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-16 (Thu, 16 Jan 2014) Changed paths: M SUnit-UI.package/TestRunner.class/instance/actions/addDeclaredPackagesUnderTestTo_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script353.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30700.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30700 12656 Code coverage does not work anymore with specified #packageNamesUnderTest https://pharo.fogbugz.com/f/cases/12656 http://files.pharo.org/image/30/30700.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 16, 2014

Jan. 16, 2014

Branch: refs/tags/30700 Home: https://github.com/pharo-project/pharo-core

1 0

Pharo 3 bugs on Linux with openWorldWithSpec?
by kmo Jan. 16, 2014

Jan. 16, 2014

I've come across two weird bugs (or at least strange effects) when using OpenWorldWithSpec. I'm not sure whether they are genuine bugs or it's just the way I've coded. I'm using the latest Pharo 3 on Ubuntu 13.10. I have a simple ComposableModel consisting of a TreeModel and a LabelModel which acts as a status line. The composableMorph is made up like this: spec <spec: #default> ^ SpecLayout composed add: #concordanceTreeModel origin: 0 @ 0 corner: 1 @ 1.0 offsetOrigin: 0 @ 0 offsetCorner: 0 @ self statusLineHeight negated; add: #statusLine origin: 0 @ 1.0 corner: 1.0 @ 1.0 offsetOrigin: 0 @ 0 offsetCorner: 0 @ self statusLineHeight negated; yourself When I run openInWorld I get the expected behaviour as below. <http://forum.world.st/file/n4735903/PharoScreenshot.2.png> Note how the background to the labelmodel status line is silver. But when I open the same ui with openWorldWithSpec I get this: <http://forum.world.st/file/n4735903/DarkGrayStatus.png> Note how the colour of the labelmodel background has changed. It's darker - in fact it has picked up the colour of my pharo desktop as though its background were transparent. Any ideas on this strange behaviour? Note also that the title of my ComposableModel is not copied to the pharo window either - this is bug 12231 which I reported a few weeks ago. The other strange effect is when I place the following code in a script |ui| ui := ConcordanceSpecUI new. ui openWorldWithSpec. and run it from the command line. This is what happens. <http://forum.world.st/file/n4735903/UsingStartupScript.png> (This is with an initialExtent specified - if there's no initial extent it's worse - I get a tiny area in the top left of the main window). But if I now click on the desktop, or resize the window, the interface suddenly corrects itself, like this: <http://forum.world.st/file/n4735903/good.png> I have tried this on Windows 7 and I do not get this behaviour - the ComposableModel fills the pharo window immediately and correctly. Any thoughts - should I be raising these as bugs? - Ken -- View this message in context: http://forum.world.st/Pharo-3-bugs-on-Linux-with-openWorldWithSpec-tp473590… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 1

after an software update the current changeset is unnamed - literally
by Nicolai Hess Jan. 16, 2014

Jan. 16, 2014

This is what happens duing an update (30697 - 30698) save old cs Unnamed new changes 30698-Pha-Update new changes ScriptLoader30-MarcusDenker.853 new changes 30698-Pha-Update new changes Metacello-MC-MarcusDenker.696 new changes 30698-Pha-Update ChangeSet cleanup new changes Unnamed restore old cs <no name -- garbage?> new changes <no name -- garbage?> the old changeset is saved update stream starts-> every package update creates a new changeset scriptloader calls cleanup update stream ends old (cleanuped) cs is restored now every change goes to this unnamed changeset. If you open the changesorter it calls "ChangeSet current" which creates a new unnamed ("Unnamed") changeset and of course the prior changes are lost. Is this inevitable?

2 2

[pharo-project/pharo-core] d7228c: 30699
by GitHub Jan. 15, 2014

Jan. 15, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d7228caeefd837d1bb66a541ed7e8171fdbe3561 https://github.com/pharo-project/pharo-core/commit/d7228caeefd837d1bb66a541… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-15 (Wed, 15 Jan 2014) Changed paths: M Morphic-Core.package/KeyboardEvent.class/instance/printing/storeOn_.st M Morphic-Core.package/WorldState.class/class/world menu items/windowsOn_.st M RPackage-Core.package/RPackageSet.class/instance/initialization/initialize_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script352.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30699.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30699 12661 KeyboardEvent>>#storeOn: broken https://pharo.fogbugz.com/f/cases/12661 12660 MCPackage reviving RPackage when it shouldn't https://pharo.fogbugz.com/f/cases/12660 12659 Add Toggle full screen mode to World Windows menu https://pharo.fogbugz.com/f/cases/12659 http://files.pharo.org/image/30/30699.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 15, 2014

Jan. 15, 2014

Branch: refs/tags/30699 Home: https://github.com/pharo-project/pharo-core

1 0