As Kilon say, this is a personal wishlist. Any direction you mentioned is worth and will have impact.
However, here's my personal top 5:
- **Git in the image**, that would be awesome to be able integrate the gitflow way of developing in team. Easy branching/merging is a must. - **Slots**. I still need to check the current implementation and see what's possible (Property slots?) but as I have understood you've planned even more for pharo4? - **Text Editor with sensible keybindings**. - **ARM support** - **Athens**
We are getting there.
On Wed, Jun 4, 2014 at 9:06 PM, jannik laval <jannik.laval@gmail.com <mailto:jannik.laval@gmail.com>> wrote:
Hi all,
>From my point of view, I like the progrss on the ARM VM. I hope to have an Android VM that works. Also I hope to see Pharo3.0 and Pharo4.0 working on iOS.
Another question is about two interesting plugins: Mpeg3Plugin and CameraPlugin. Is it possible to integrate them in the VM build ?
Thank you guys for all the work done. Jannik
2014-06-04 20:53 GMT+02:00 stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>:
Hi Esteban,
As you mentioned a lot of new tools and protocols were introduced, people (me included) does not well about those ones. As an example I am slowly discovering announcement and now AFAIK the image use three different protocols for this: change/update, observer and Announcement!
Yes we know that the situation is not ideal. We started to move more to announcement. The problem is that some of the widgets requires the change/update. For the observer I do not know what you mean.
Personally I beg for a great Pharo 4.x series of iterative cleaning+consolidations.
Thanks
Hilaire
Le 04/06/2014 17:36, Esteban Lorenzano a écrit :
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
--
~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/