Brainstorming on the roadmap for first Pharo Consortium Engineer :)
Hi guys we have a roadmap for Esteban and we would like to share it with you. We have extra items that we would like to see fixed and we are welcoming your feedback/suggestions. Note this is typically the way we want to work with the consortium in the future: Build an initial roadmap and refine it based on the input of the community. - A website for the consortium registration (esteban is expert on that). - This is important for INRIA and for the visibility of the consortium. We should get new members :) - Integration with SmalltalkHub - Working on fixing bugs! - Debugger fixes - Continuous bug fixing. - Improving release process: faster, more people involved, simpler. - Working on metacello repositories for each distributions (everything is there but missing last bits) - Metacello tools - Automatic release validations - Automatic validation of fixes Now the free items with probably igor involvement - Multiwindowing support - Fully working multithreaded FFI with ***Documentation*** - Filesystem fix and integration - Integration of OPAL - RPackage integration Igor related - Ephemerons - Object format - VM branding - Use of new canvas - Event cleaning So we are waiting for your suggestions. Stef
We have a very exciting future! Stéphane Ducasse wrote:
Multiwindowing support
Meaning native windows? -- View this message in context: http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortiu... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
On Mon, Oct 31, 2011 at 5:33 PM, Sean P. DeNigris <sean@clipperadams.com>wrote:
We have a very exciting future!
Stéphane Ducasse wrote:
Multiwindowing support
Meaning native windows?
Now, that's not the same ;) I guess a first step is to be able to have multiple native windows, even if each of them are rendered with morphic. But then you can use the Windows-95-like-theme and you have a "similar" desktop app for a windows user ;)
-- View this message in context: http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortiu... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
-- Mariano http://marianopeck.wordpress.com
On Oct 31, 2011, at 5:33 PM, Sean P. DeNigris wrote:
We have a very exciting future!
Stéphane Ducasse wrote:
Multiwindowing support
Meaning native windows?
At least having multiple ones but not native because with MS, Apple, linux look and feel we will all die before we get something working :)
-- View this message in context: http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortiu... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Stéphane Ducasse wrote:
At least having multiple ones but not native because with MS, Apple, linux look and feel we will all die before we get something working :)
Ah, I didn't realize the nuance! Multiple windows are what I've wanted all along, and I've been calling them "native" (which could be useful, but not nearly as important to me). Sean -- View this message in context: http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortiu... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Am 31.10.2011 um 11:54 schrieb Stéphane Ducasse:
Now the free items with probably igor involvement - Multiwindowing support - Fully working multithreaded FFI with ***Documentation*** - Filesystem fix and integration - Integration of OPAL - RPackage integration
I like to add environments so we can have multiple versions in the same image and get rid of default global state. I think you have that already on your mind even with separate object memories. Norbert
Yes this is a long overdue. We will start another pass on it with nick in a week. So we will see: we want to have all the compilation chain to work in an environment. Stef
Now the free items with probably igor involvement - Multiwindowing support - Fully working multithreaded FFI with ***Documentation*** - Filesystem fix and integration - Integration of OPAL - RPackage integration
I like to add environments so we can have multiple versions in the same image and get rid of default global state. I think you have that already on your mind even with separate object memories.
Norbert
participants (4)
-
Mariano Martinez Peck -
Norbert Hartl -
Sean P. DeNigris -
Stéphane Ducasse