- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo on Apple App Store

by Alexandre Bergel

What does it mean? I think we should have a clear roadmap on how to get a pharo application in the appstore. The train is passing by and we are not taking it. Cheers, Alexandre On 4 Mar 2011, at 10:04, Esteban Lorenzano wrote: > Hi, > yes you can! > ...but the application must be code signed :) > > best, > Esteban > > El 04/03/2011, a las 5:53a.m., laurent laffont escribiÃ³: > >> Hi, >> >> is it possible today to distribute Pharo apps through Apple App Store (OSX) ? If no, why ? Can I hope it will be possible or should I learn objective-C ? >> >> >> Laurent > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2011

Re: [Pharo-project] Kernel

by Alexandre Bergel

> For now, there is no interaction because the VM should have new primitives to provides textual interactivity. > But if you want to play, you can change the method HazelTracer2>>#freshProcess This is cool! One could imagine to have a read eval loop here. Alexandre > > > > Thanks for your feedback, > > Ben > > On Mar 4, 2011, at 1:57 PM, Alexandre Bergel wrote: > >> Hi Ben, >> >> I tried, and it works. But what can I do then? >> When I run your image (by just double clicking on it), I have a sound without nothing appearing. >> Do you have some more information about Hazel? What can I do with the image? How can I use it? >> >> Cheers, >> Alexandre >> >> On 4 Mar 2011, at 09:51, Benjamin wrote: >> >>> Hello guys, >>> >>> >>> I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) >>> >>> You can try it here: >>> >>> Gofer new >>> squeaksource: 'PharoTaskForces'; >>> package: 'SystemTracing'; >>> load. >>> >>> Gofer new >>> squeaksource: 'Seed'; >>> package: 'Seed-HazelBuilder'; >>> load. >>> >>> HazelTracer2 writeImage: 'hazel.image'. >>> >>> >>> If you have an error in Point>>#printOn: , you can use this fix >>> <FixPointPrintOn.1.cs> >>> >>> >>> >>> I want to thank Igor again, because he helps me a lot :) >>> >>> >>> >>> Ben >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2011

Re: [Pharo-project] Kernel

by Benjamin

For now, it just beeping to prove that the image is living :) For now, there is no interaction because the VM should have new primitives to provides textual interactivity. But if you want to play, you can change the method HazelTracer2>>#freshProcess Thanks for your feedback, Ben On Mar 4, 2011, at 1:57 PM, Alexandre Bergel wrote: > Hi Ben, > > I tried, and it works. But what can I do then? > When I run your image (by just double clicking on it), I have a sound without nothing appearing. > Do you have some more information about Hazel? What can I do with the image? How can I use it? > > Cheers, > Alexandre > > On 4 Mar 2011, at 09:51, Benjamin wrote: > >> Hello guys, >> >> >> I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) >> >> You can try it here: >> >> Gofer new >> squeaksource: 'PharoTaskForces'; >> package: 'SystemTracing'; >> load. >> >> Gofer new >> squeaksource: 'Seed'; >> package: 'Seed-HazelBuilder'; >> load. >> >> HazelTracer2 writeImage: 'hazel.image'. >> >> >> If you have an error in Point>>#printOn: , you can use this fix >> <FixPointPrintOn.1.cs> >> >> >> >> I want to thank Igor again, because he helps me a lot :) >> >> >> >> Ben > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

March 4, 2011

Re: [Pharo-project] Pharo on Apple App Store

by Esteban Lorenzano

Hi, yes you can! ...but the application must be code signed :) best, Esteban El 04/03/2011, a las 5:53a.m., laurent laffont escribiÃ³: > Hi, > > is it possible today to distribute Pharo apps through Apple App Store (OSX) ? If no, why ? Can I hope it will be possible or should I learn objective-C ? > > > Laurent

March 4, 2011

Re: [Pharo-project] Kernel

by Alexandre Bergel

Hi Ben, I tried, and it works. But what can I do then? When I run your image (by just double clicking on it), I have a sound without nothing appearing. Do you have some more information about Hazel? What can I do with the image? How can I use it? Cheers, Alexandre On 4 Mar 2011, at 09:51, Benjamin wrote: > Hello guys, > > > I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) > > You can try it here: > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'SystemTracing'; > load. > > Gofer new > squeaksource: 'Seed'; > package: 'Seed-HazelBuilder'; > load. > > HazelTracer2 writeImage: 'hazel.image'. > > > If you have an error in Point>>#printOn: , you can use this fix > <FixPointPrintOn.1.cs> > > > > I want to thank Igor again, because he helps me a lot :) > > > > Ben -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2011

[Pharo-project] Kernel

by Benjamin

Hello guys, I finally success (with the help of Igor) to trace and create a new Smalltalk kernel based on Pharo. The new born weight 2.2Mb and includes 230 classes ;) You can try it here: Gofer new squeaksource: 'PharoTaskForces'; package: 'SystemTracing'; load. Gofer new squeaksource: 'Seed'; package: 'Seed-HazelBuilder'; load. HazelTracer2 writeImage: 'hazel.image'. If you have an error in Point>>#printOn: , you can use this fix I want to thank Igor again, because he helps me a lot :) Ben

March 4, 2011

[Pharo-project] Issue 3783 in pharo: Point>>#printOn:

by pharo＠googlecode.com

Status: Fixed Owner: Benjamin...(a)gmail.com Labels: Type-Seed New issue 3783 by Benjamin...(a)gmail.com: Point>>#printOn: http://code.google.com/p/pharo/issues/detail?id=3783 Error if you do: Point new printString ... Attachments: FixPointPrintOn.1.cs 414 bytes

March 4, 2011

Re: [Pharo-project] Issue 3781 in pharo: Finder version 30 does not report all selectors - 2 problems

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3781 by Benjamin...(a)gmail.com: Finder version 30 does not report all selectors - 2 problems http://code.google.com/p/pharo/issues/detail?id=3781 Thank you for your feedbacks ;) Fixed in 31

March 4, 2011

Re: [Pharo-project] [squeak-dev] [ANN] ESUG supports once again SqueakDBX

by Mariano Martinez Peck

On Fri, Mar 4, 2011 at 11:50 AM, GermÃ¡n Arduino <garduino(a)gmail.com> wrote: > Certainly all the Smalltalk community should thank ESUG by the > continous support to lot of initiatives. > > And to ESUG sponsors :) and ESUG conference attendees...and...and..lots of people :) > Thanks ESUG. > > > 2011/3/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > We are really happy to announce that ESUG will sponsor us once again > through > > the ESUG Summer Talk project. This means that we have reached the ESUG > > expectations and that they still think that relational database access is > an > > important matter in Smalltalk. > > > > One important thing is that we are going to rename the project (we are > still > > working on it) since SqueakDBX runs not only in Squeak but also in Pharo, > > and there have been even ports to Dolphin. What's the reason for this > > decision? Because we do not want to couple ourselves to a smalltalk > dialect > > nor to OpenDBX, because our project is much more than that (later I will > > tell you about our plans). So, these are some of the possible names: > > ObjectPark, SmallParking, Parktalk, SmallValet, Valetalk, ValetST, > > NorayTalk, Ballard, Noray and Cruise. Please let us know which one is > your > > favourite or help us find a new one. > > > > Another important subject is the team. There will be three "mentors", > > Esteban Lorenzano, Diogenes Moreira and myself, Mariano Martinez Peck; > and > > three students: Guillermo Polito, Nicolas Scarcella and Santiago > Bragagnolo. > > > > We are open to suggestions and ideas. In addition, we have defined a > > possible list of actions that I copy at the end of the email. > > > > For the moment, the url remains www.squeakdbx.org and the mailing > > list squeakdbx(a)lists.squeakfoundation.org > > > > Once again, we want to thank ESUG for their support and trust. > > > > Thank you very much, > > > > SqueakDBX team > > > > > > > > > > > > Possible list of actions: > > > > 1) Change SqueakDBXâs name. > > > > 2) Update GLORP version since the actual one is 3 years old. > > > > Port it again from VisualWorks, create a VW porting tool (may be). > > Complete support to Glorp. Today it works with PostgreSQL, Oracle and > > MySQL. Make it work with most databases OpenDBX supports. > > > > 3) Create a lightweight solution, alternatively to GLORP. There are some > > options: > > > > Make SqueakSave work with SqueakDBX. SqueakSave developers already > > contacted us because they wanted to do it. SqueakSave seems to be 20% > slower > > than Glorp but you don't need to write the mappings :) > > Adapt Ramon Leon's active record to use an abstract database driver, and > > create a driver for SqueakDBX. > > Port the new Glorpâs kind of active record to Pharo. (included in 2). > > > > 4) Write a Pharo By Example 2 chapter based on the card game Stef built > ;). > > > > 5) Cog compatibility. > > > > 6) Use Alien instead of FFI. > > Eliot is working on a threaded CogVM. One of the projects of the GSoC of > > this year was to make something similar to a threaded FFI. What the > student > > did is a modification in Alien (I think) that can be run in a > multithreaded > > envirorment. He worked with Eliot. The idea is when Eliot releases the > > threaded CogVM, this FFI would work our of the box, and would avoid > locking > > the WHOLE vm while a C function is being invoked (as it happens today > with > > FFI).....So....when that VM is released, we MUST migrate to that). > > > > 7) Explore performance issues (maybe with our approach of "In thread > > execution plugin"). > > > > 8) Complete integration with OpenDBX. For example, Oracle, for large > objects > > (Clob, Blob, etc) use specific functions. There are specific functions in > > OpenDBX that have to be used if the database uses specific functions > (oracle > > is the only one for the moment.). We don't manage those functions yet. > > > > 9) In this link http://www.squeakdbx.org/Targets%20and%20Features > > You can see a list of future possible features like Connection pooling > (now > > it is done!), Prepared statement interface, Store procedures, Escape and > > avoid of SQL insertion, Authentication support: extends to other methods, > > not only user/password, Full text support, etc. > > > > > > >

March 4, 2011

Re: [Pharo-project] [squeak-dev] [ANN] ESUG supports once again SqueakDBX

by GermÃ¡n Arduino

Certainly all the Smalltalk community should thank ESUG by the continous support to lot of initiatives. Thanks ESUG. 2011/3/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > We are really happy to announce that ESUG will sponsor us once again through > the ESUG Summer Talk project. This means that we have reached the ESUG > expectations and that they still think that relational database access is an > important matter in Smalltalk. > > One important thing is that we are going to rename the project (we are still > working on it) since SqueakDBX runs not only in Squeak but also in Pharo, > and there have been even ports to Dolphin. What's the reason for this > decision? Because we do not want to couple ourselves to a smalltalk dialect > nor to OpenDBX, because our project is much more than that (later I will > tell you about our plans). So, these are some of the possible names: > ObjectPark, SmallParking, Parktalk, SmallValet, Valetalk, ValetST, > NorayTalk, Ballard, Noray and Cruise. Please let us know which one is your > favourite or help us find a new one. > > Another important subject is the team. There will be three "mentors", > Esteban Lorenzano, Diogenes Moreira and myself, Mariano Martinez Peck; and > three students: Guillermo Polito, Nicolas Scarcella and Santiago Bragagnolo. > > We are open to suggestions and ideas. In addition, we have defined a > possible list of actions that I copy at the end of the email. > > For the moment, the url remainsÂ www.squeakdbx.orgÂ and the mailing > listÂ squeakdbx(a)lists.squeakfoundation.org > > Once again, we want to thank ESUG for their support and trust. > > Thank you very much, > > SqueakDBX team > > > > > > Possible list of actions: > > 1) Change SqueakDBXâs name. > > 2) Update GLORP version since the actual one is 3 years old. > > Port it again from VisualWorks, create a VW porting tool (may be). > Complete support to Glorp. Â Today it works with PostgreSQL, Oracle and > MySQL. Â Make it work with most databases OpenDBX supports. > > 3) Create a lightweight solution, alternatively to GLORP. Â There are some > options: > > Make SqueakSave work with SqueakDBX. Â SqueakSave developers already > contacted us because they wanted to do it. SqueakSave seems to be 20% slower > than Glorp but you don't need to write the mappings :) > Adapt Ramon Leon's active record to use an abstract database driver, and > create a driver for SqueakDBX. > Port the new Glorpâs kind of active record to Pharo. (included in 2). > > 4) Write a Pharo By Example 2 chapter based on the card game Stef built ;). > > 5) Cog compatibility. > > 6) Use Alien instead of FFI. > Eliot is working on a threaded CogVM. One of the projects of the GSoC of > this year was to make something similar to a threaded FFI. What the student > did is a modification in Alien (I think) that can be run in a multithreaded > envirorment. He worked with Eliot. The idea is when Eliot releases the > threaded CogVM, this FFI would work our of the box, and would avoid locking > the WHOLE vm while a C function is being invoked (as it happens today with > FFI).....So....when that VM is released, we MUST migrate to that). > > 7) Explore performance issues (maybe with our approach of "In thread > execution plugin"). > > 8) Complete integration with OpenDBX. For example, Oracle, for large objects > (Clob, Blob, etc) use specific functions. There are specific functions in > OpenDBX that have to be used if the database uses specific functions (oracle > is the only one for the moment.). We don't manage those functions yet. > > 9) In this linkÂ http://www.squeakdbx.org/Targets%20and%20Features > You can see a list of future possible features like Connection pooling (now > it is done!), Prepared statement interface, Store procedures, Escape and > avoid of SQL insertion, Authentication support: extends to other methods, > not only user/password, Full text support, etc. > > >

March 4, 2011