- Pharo-dev - lists.pharo.org

Re: [Pharo-project] FFI in 1.1

by laurent laffont

On Tue, Apr 20, 2010 at 9:14 AM, Lawson English <lenglish5(a)cox.net> wrote: > John M McIntosh wrote: > >> Well I asked for it... >> (a) you can get graphic cut/copy/paste of complex data on the macintosh >> and windows. >> >> (b) I'd rather have people learn FFI & Alien so they can build their own >> api to Rome, Pango, & Curl instead of waiting on about 4 people in the world >> to get around to building and distributing *official* plugins . >> >> (c) When your curl, rome, etc FFI call freaks and toasts your image why >> you can do debugging, versus relying on a handful of people in the world to >> grind thru some compiler, gnu debug session to figure out why that register >> move results in a fatal Virtual memory page fault. >> > > Forget curl, I want to recreate the Cocoa class libs in squeak/pharo for > WebKit... > Cocoa ? So it will run only on Mac OS X ? Cheers, Laurent Laffont > And then create etoy extensions that can handle them. > > ;-). > > > Lawson > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2010

Re: [Pharo-project] FEATURE: User chooses preferred location for MC directory repositories

by StÃ©phane Ducasse

for example or just choosing it using settings. Stef PS: one of these dasy we will need to be able to use environment variables On Apr 20, 2010, at 9:25 AM, Michael Roberts wrote: > Regarding sharing a package cache, I made a change a while ago that > searches up the directory tree to see if there is one higher up. You > then don't have to change the fresh image. What do you think? > > Cheers > mike > > On Tuesday, April 20, 2010, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Apr 20, 2010, at 1:00 AM, Sean P. DeNigris wrote: >> >>> >>> http://code.google.com/p/pharo/issues/detail?id=2329 >>> >>> Pharo image: Pharo 1.0 >>> >>> In Monticello Browser, when I click "+Repository" and select "directory," >>> I'd love to be taken right to the directory where I keep my local >>> repositories, instead of having to click to the same place over and over. >>> >>> I changed the following method: >>> MCDirectoryRepository class>>morphicConfigure >>> ^ (UIManager default chooseDirectoryFrom: (FileDirectory on: >>> '/path/to/my/Repositories')) ifNotNil: >>> [:directory | >>> self new directory: directory] >>> >>> How should I store the default repository directory? Would anyone else find >>> this helpful? >> >> it would be good to be able to >> either choose to have one local cache on the side of the image >> or one shared among image - this implies a way to store and set it up >> => probably a class variable + a setting in 1.1 >>> >>> Sean DeNigris >>> -- >>> View this message in context: http://n4.nabble.com/FEATURE-User-chooses-preferred-location-for-MC-directo… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by StÃ©phane Ducasse

But ok we need time for that.... and I do not have any right now. Stef On Apr 20, 2010, at 9:21 AM, Peter Hugosson-Miller wrote: > On 20 apr 2010, at 09.13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> >> On Apr 20, 2010, at 9:06 AM, Peter Hugosson-Miller wrote: >> >>> Stef, I like how you're thinking, but your list raises one question in my mind: how do you propose to load anything into "Mini" without a Compiler? Sorry if that's a stupid question, but I need to know :-p >>> >> In my coolest dream: socket + object serializer like in some versions of S# of dan simmons. > > Aha! TrÃ¨s trÃ¨s cool! :-D > >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Cheers, > Peter > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010

Re: [Pharo-project] FEATURE: User chooses preferred location for MC directory repositories

by Michael Roberts

Regarding sharing a package cache, I made a change a while ago that searches up the directory tree to see if there is one higher up. You then don't have to change the fresh image. What do you think? Cheers mike On Tuesday, April 20, 2010, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Apr 20, 2010, at 1:00 AM, Sean P. DeNigris wrote: > >> >> http://code.google.com/p/pharo/issues/detail?id=2329 >> >> Pharo image: Pharo 1.0 >> >> In Monticello Browser, when I click "+Repository" and select "directory," >> I'd love to be taken right to the directory where I keep my local >> repositories, instead of having to click to the same place over and over. >> >> I changed the following method: >> MCDirectoryRepository class>>morphicConfigure >> Â Â Â ^ (UIManager default chooseDirectoryFrom: (FileDirectory on: >> '/path/to/my/Repositories')) ifNotNil: >> Â Â Â Â Â Â Â [:directory | >> Â Â Â Â Â Â Â self new directory: directory] >> >> How should I store the default repository directory? Â Would anyone else find >> this helpful? > > it would be good to be able to > Â Â Â Â either choose to have one local cache on the side of the image > Â Â Â Â or one shared among image - this implies a way to store and set it up > Â Â Â Â Â Â Â Â => probably a class variable + a setting in 1.1 >> >> Sean DeNigris >> -- >> View this message in context: http://n4.nabble.com/FEATURE-User-chooses-preferred-location-for-MC-directo… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by Peter Hugosson-Miller

On 20 apr 2010, at 09.13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Apr 20, 2010, at 9:06 AM, Peter Hugosson-Miller wrote: > >> Stef, I like how you're thinking, but your list raises one question >> in my mind: how do you propose to load anything into "Mini" without >> a Compiler? Sorry if that's a stupid question, but I need to know :-p >> > In my coolest dream: socket + object serializer like in some > versions of S# of dan simmons. Aha! TrÃ¨s trÃ¨s cool! :-D > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Cheers, Peter

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by Lawson English

John M McIntosh wrote: > Well I asked for it... > > (a) you can get graphic cut/copy/paste of complex data on the macintosh and windows. > > (b) I'd rather have people learn FFI & Alien so they can build their own api to Rome, Pango, & Curl instead of waiting on about 4 people in the world to get around to building and distributing *official* plugins . > > (c) When your curl, rome, etc FFI call freaks and toasts your image why you can do debugging, versus relying on a handful of people in the world to grind thru some compiler, gnu debug session to figure out why that register move results in a fatal Virtual memory page fault. > Forget curl, I want to recreate the Cocoa class libs in squeak/pharo for WebKit... And then create etoy extensions that can handle them. ;-). Lawson

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by StÃ©phane Ducasse

On Apr 20, 2010, at 9:06 AM, Peter Hugosson-Miller wrote: > Stef, I like how you're thinking, but your list raises one question in my mind: how do you propose to load anything into "Mini" without a Compiler? Sorry if that's a stupid question, but I need to know :-p > In my coolest dream: socket + object serializer like in some versions of S# of dan simmons. Stef

April 20, 2010

Re: [Pharo-project] Minor GUI glitch with Pharo 1.0 on Mac

by StÃ©phane Ducasse

but this is fixed in 1.1 :) > http://code.google.com/p/pharo/issues/detail?id=1882 > > On Tue, Apr 20, 2010 at 4:53 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > It is already reported...sorry no time to search it in the bug tracker > > > On Thu, Apr 15, 2010 at 9:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > this is not a problem but reporting is the first step. > Now I imagine that we should get a resize window event and react to it. > On Apr 15, 2010, at 9:19 PM, Lawson English wrote:

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by John M McIntosh

Well I asked for it... (a) you can get graphic cut/copy/paste of complex data on the macintosh and windows. (b) I'd rather have people learn FFI & Alien so they can build their own api to Rome, Pango, & Curl instead of waiting on about 4 people in the world to get around to building and distributing *official* plugins . (c) When your curl, rome, etc FFI call freaks and toasts your image why you can do debugging, versus relying on a handful of people in the world to grind thru some compiler, gnu debug session to figure out why that register move results in a fatal Virtual memory page fault. On 2010-04-19, at 11:41 PM, Torsten Bergmann wrote: >> I wouldn't include neither FFI or Alien FFI in neither PharoCore or PharoDev >> image. > > +1 > >> That's only my opinion. > > Maybe Stef should tell us more about why he thinks it should be included. > > Bye > T. > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by Peter Hugosson-Miller

Stef, I like how you're thinking, but your list raises one question in my mind: how do you propose to load anything into "Mini" without a Compiler? Sorry if that's a stupid question, but I need to know :-p -- Cheers, Peter. On 20 apr 2010, at 08.59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > The question is what we call core. > I think that core should contain less and less but pharo should > contain infrastructure and FFI or Alien > are infrastructure. > > > If you look at my answer to German on "Re: [Pharo-project] Really > Important message (tm)" > April 16 > You can see that with a fast loading package mechanism then we could > really introduce in "Pharo-Core" (= what we have now) > infrastructure package to produce Pharo and works on making a real > core. FFI does not belong to this core=mini but > to Pharo from my point of view > > Mini > Mini + FFI + Tools + IDE + Compiler ....= PharoCore > Pharo + Sounds + Morphic examples + archiview.... = Pharo > > Note that the belonging of one package to group is not automatically > clear. > This is why metacello is key and a metacelloRepository. > > Steg > >>> I wouldn't include neither FFI or Alien FFI in neither PharoCore >>> or PharoDev >>> image. >> >> +1 >> >>> That's only my opinion. >> >> Maybe Stef should tell us more about why he thinks it should be >> included. >> >> Bye >> T. >> >> -- >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010