- Pharo-dev - lists.pharo.org

Brainstorming Pharo4

by Esteban Lorenzano

Hi, A couple of weeks ago we started to plan Pharo4. This work became stagnated for many reasons, but mainly because I needed to travel to Argentina. Now I'm slowly resuming the work and I wanted to share with you what we have been talking/dreaming. In esence, we have two important drivers for this release: 1) Improving tools Turns out that we have introduced a lot of kernel improvements (opal compiler, layouts, slots, etc.) and tools are still not aware of them. Even worst: we have traits since a lot of time and our tools are still now aware enough to provide good interoperability. But not just that: we have introduced things that are not well used yet: keybindings (who do not want a better keybindings structure... coherent and editable?), spec should allow us to continue enhancing existing tools and to replace old ones. 2) Modularisation One of the fundamental ideas behind Pharo is to provide a modular environment. But well... since Pharo start to the moment, we prepared things to allow it, but still few direct effort has been made. In our dreams, Pharo should be built starting for a small kernel image and adding different modules to get a complete version. In this idea Pharo=Kernel+GUI(Morphic)+Tools. This has huge advantages (I do not think is necesary to explain them, isn't ;)?) We brainstomed around this and we get this list of issues (not all of them directly related to the objectives, but well... good stuff also :) ) Web site: - add catalog - add videos - enhance it in general Infrastructure: - support more vm platforms VM: - spur - 64bits - make vm embedable and UI independent (with SDL2 and OSWindow) Image: - Modularisation - Removing old compiler - Repackage Morphic (to allow better modularisation) - Athens (replace old bitblt) Tools - Replace changes with Ombu/Epicea - Replace sources with a better abstraction - Git support inside image (with libgit2 + tools) - Pass on Spec - Include Glamour? - Make Ring unloadable - Fonts with FreeType And lots of bugfixes :) We would like to exchange ideas with you. So, what do you think? Esteban

June 4, 2014

TextMorph on Athens

by Hilaire Fernandes

Hi, DrGeo needs to know what is the status of TextMorph on Athens. I have been through most of the broken parts of DrGeo@Pharo3 (really a lot!), and this one is the last one AFAIK. Depending on, I may write a temporary hack to bypass textmorph, but may be it is not necessary and DrGeo can wait a bit, but I need to know. Thanks Hilaire -- Dr. Geo http://drgeo.eu

June 4, 2014

Re: [Pharo-dev] Some PharoVM work news

by Hilaire Fernandes

Thanks Esteban! Hilaire Le 04/06/2014 15:38, Esteban Lorenzano a Ã©crit : > Hi, > > Iâve been working on re-aligning our sources to latest Eliot sources. > This is a step previous to compile a spur vm for Pharo. > So farâ¦ it was a lot of work but I have a working version (in mac, not yet tested in others)â¦ but I forget to port Igorâs finalization improvements (I forgot it was there and I passed over it when merging), now I have to put it back inâ¦ > Overallâ¦ I have the impression latest Eliot versions are 5-10% faster than our current ones, but Iâm not sure (it could be just a good day for my machine), so we will need to wait until release. > > This is a necessary step: our codebase is diverging more and more from Eliotâs without any good reason, just a direct application of entropy laws, and we need to realign if we want to continue working together (and we certainly want :D). > > With luck, this work will be finished for the end of the week. > > cheers, > Esteban > > > -- Dr. Geo http://drgeo.eu

June 4, 2014

[pharo-project/pharo-core]

by GitHub

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

June 4, 2014

[pharo-project/pharo-core] 75ace5: 40014

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 75ace54738aa1db4187fc9cfecfd32dcb132f96e https://github.com/pharo-project/pharo-core/commit/75ace54738aa1db4187fc9cf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-04 (Wed, 04 Jun 2014) Changed paths: R FreeType.package/extension/BalloonMorph/class/chooseBalloonFont.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/findAChangeSorter_.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/findAWindowSatisfying_orMakeOneUsing_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script14.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40014.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/extension/PasteUpMorph/instance/defaultDesktopCommandKeyTriplets.st Log Message: ----------- 40014 13299 findAChangeSorter: should be removed https://pharo.fogbugz.com/f/cases/13299 http://files.pharo.org/image/40/40014.zip

June 4, 2014

[pharo-project/pharo-core]

by GitHub

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

June 4, 2014

[pharo-project/pharo-core] 6524e5: 40013

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6524e5bf7c1213a807065c466b0b3e1946f6cf81 https://github.com/pharo-project/pharo-core/commit/6524e5bf7c1213a807065c46… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-04 (Wed, 04 Jun 2014) Changed paths: M Morphic-Base.package/HaloMorph.class/class/halo theme/initialize.st A Polymorph-Widgets.package/UITheme.class/instance/accessing colors/menuKeyboardFocusColor.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script13.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40013.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40013 13302 error on menus after theme refactor https://pharo.fogbugz.com/f/cases/13302 13300 HaloMorph class should not invoke super initialize https://pharo.fogbugz.com/f/cases/13300 http://files.pharo.org/image/40/40013.zip

June 4, 2014

Re: [Pharo-dev] Some PharoVM work news

by Stephan Eggermont

Great! I assume you'd want to deal with the outstanding pull requests after synchronization is finished? Stephan

June 4, 2014

Re: [Pharo-dev] Some PharoVM work news

by Max Leske

Go Esteban!! > On 04.06.2014, at 15:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Iâve been working on re-aligning our sources to latest Eliot sources. > This is a step previous to compile a spur vm for Pharo. > So farâ¦ it was a lot of work but I have a working version (in mac, not yet tested in others)â¦ but I forget to port Igorâs finalization improvements (I forgot it was there and I passed over it when merging), now I have to put it back inâ¦ > Overallâ¦ I have the impression latest Eliot versions are 5-10% faster than our current ones, but Iâm not sure (it could be just a good day for my machine), so we will need to wait until release. > > This is a necessary step: our codebase is diverging more and more from Eliotâs without any good reason, just a direct application of entropy laws, and we need to realign if we want to continue working together (and we certainly want :D). > > With luck, this work will be finished for the end of the week. > > cheers, > Esteban > >

June 4, 2014

Some PharoVM work news

by Esteban Lorenzano

Hi, Iâve been working on re-aligning our sources to latest Eliot sources. This is a step previous to compile a spur vm for Pharo. So farâ¦ it was a lot of work but I have a working version (in mac, not yet tested in others)â¦ but I forget to port Igorâs finalization improvements (I forgot it was there and I passed over it when merging), now I have to put it back inâ¦ Overallâ¦ I have the impression latest Eliot versions are 5-10% faster than our current ones, but Iâm not sure (it could be just a good day for my machine), so we will need to wait until release. This is a necessary step: our codebase is diverging more and more from Eliotâs without any good reason, just a direct application of entropy laws, and we need to realign if we want to continue working together (and we certainly want :D). With luck, this work will be finished for the end of the week. cheers, Esteban

June 4, 2014