- Once again... I would LOVE to have a really working-out-of-the-box multithreaded FFI with callbacks. This is a MUST if Pharo wants to be business friendly.
- Unify the VMs. Have only ONE place where a single pharo user can go and pickup a VM. Have ANOTHER place for those bleeding edge or experiment VMs. This means merging gforge, jenkins, pharo website, pharo one click, etc. In addition, we need a way to IDENTIFY a VM. So that when someone reports a bug, we can exactly know which VM to reproduce it. - Integrate Nautilus with RB. Nobody (ok, most of us) cannot work without RB integration. Ok, integrations could live without that, but they INTEGRATE. If you are DEVELOPING you cannot develop without RB. If nobody will make OB to work in 1.4, then someone needs to integrate Nautilus with RB, otherwise people will stick with 1.3 and never change. - Make development really tools work in Pharo 1.4: OCompletion, Shout - Continue pushing Coral, Zinc, Ocean, DBXTalk, Fuel, Nautilus, etc. - Maintain issue tracker: let's give Marcus a rest. This means tagging issues, close them, validate, etc etc etc. Cheers On Mon, Oct 31, 2011 at 8:25 PM, Schwab,Wilhelm K <bsch...@anest.ufl.edu>wrote: > I can't take credit for thinking of the bridge, I was simply acknowledging > it and the breadth of its audience as part of my shameless attempt to > direct effort toward another feature that would get a lot of use :) > > Bill > > > > ________________________________________ > From: pharo-project-boun...@lists.gforge.inria.fr [ > pharo-project-boun...@lists.gforge.inria.fr] on behalf of Sean P. > DeNigris [s...@clipperadams.com] > Sent: Monday, October 31, 2011 3:22 PM > To: pharo-project@lists.gforge.inria.fr > Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo > Consortium Engineer :) > > Schwab,Wilhelm K wrote: > > > > The object-c bridge is probably a big deal to the Mac users among us, > > right? > > Yes! Thank you for the reminder, I'd temporarily given up and forgotten > about this. A stable, well-documented ObjC bridge would be /huge/. My > inability to effectively use it was one of the key drivers in my delving > into debugging the VM. Like FFI, I think documentation will be extremely > important here. > > Sean > > -- > View this message in context: > http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consortium-Engineer-tp3955399p3959945.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > -- Mariano http://marianopeck.wordpress.com
