The object-c bridge is probably a big deal to the Mac users among us, right? My understand is that there are quite a few of you?? I've thought about it myself, but that's another story.
For external interfacing, I would very much like to see callbacks widely supported; I'm thinking of solvers/minimizers etc., where one needs to tell the library how to evaluate a function. FFI has been pretty good to me, and Andreas described something that might be turned into a reusable callback mechanism for it. Alien and NativeBoost are also options. It would be nice if we had one external interface system that does it all. ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] on behalf of Noury Bouraqadi [bouraq...@gmail.com] Sent: Monday, October 31, 2011 11:17 AM To: Pharo-project@lists.gforge.inria.fr Cc: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :) What about adding to this todo list: -Fixing/finishing the Objective-C bridge :-) During ESUG 2010 Esteban told me that there was a pb with the Mac VM that causes the crash. I believe this wasn't fixed and this is the biggest issue with the MARS project. Noury On 31 oct. 2011, at 11:54, Stéphane Ducasse wrote: > 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 > > > > Noury -- http://twitter.com/#!/NouryBouraqadi
