On Mon, Oct 31, 2011 at 10:40 PM, Stéphane Ducasse <
[email protected]> wrote:

> esteban
>
> would mars be the perfect case to validate the FFI we all need?
>
>
DBXTalk is a perfect candidate for the multithreaded part (not the callback
since we do not use callbacks)



> Stef
>
> On Oct 31, 2011, at 10:33 PM, Esteban Lorenzano wrote:
>
> > Hi,
> >
> > ObjectiveCBridge2 (John's one) should be working with latest builds...
> at least I *think* it should be (the older bug was fixed... so if it does
> not works now is probably because other reasons. I didn't check it since
> last six months, so I don't know. Reason why I didn't check it? well... two
> reasons: nobody ask for, so I assumed I was the only user (sorry if that's
> not true), and also, in my work of mars/deimos I found several performace
> issues (most people will not have it, but mars/deimos is very callback
> dependent) and objective-c callback architecture was not enough, so I
> started to create (well... to finish, because machinery was already there)
> a new objective-c bridge, based on Alien... it was working (and the
> response times were incredible fast), but then came the new FFI (not
> threaded) and I started migrating the alien objective-c bridge to the new
> plugin... and well... that's not finished because time is never enough :)
> > I think in the long way the new plugin is the way to go, but for now we
> have the bridge and it should work :)
> >
> > So, as a summary: ObjectiveCBridge2 *should* be working, if anyone want
> to take a look, I will be happy to help if there are any problems.
> >
> > Cheers,
> > Esteban
> >
> > El 31/10/2011, a las 5:58p.m., Stéphane Ducasse escribió:
> >
> >> When igor release athens, we will really ask him to get a 100% fully
> working FFI will be the most important task
> >>
> >> Stef
> >>
> >> On Oct 31, 2011, at 8:04 PM, Schwab,Wilhelm K wrote:
> >>
> >>> 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: [email protected] [
> [email protected]] on behalf of Noury Bouraqadi
> [[email protected]]
> >>> Sent: Monday, October 31, 2011 11:17 AM
> >>> To: [email protected]
> >>> 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
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com

Reply via email to