February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Stressing SmalltalkHub :)

by Nicolas Petton

Yep, only a couple 502 errors when stef tried to DDOS it ;) We'll move it to the Inria servers probably next week. There I will do load balancing. But overall SmalltalkHub is taking the (relative) load quite well, I was glad to see to the Moose guys moving everything there with Gofer scripts without any problem. 23000 packages uploaded there already. Even Camillo couldn't crash it (yes, I suspect him of having tried to kill it a at least a couple of times). Nico On Feb 26, 2013, at 11:23 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > nice nice! > > On 2013-02-26, at 23:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> I started to migrate Pharo 1.4 to SmalltalkHub to stress it a bit :) >> Nicolas was curious to see and he loves to see all the packages getting published there. >> So I could not resist (my upload bandwidth suffered :). >> >> It means also that SmalltalkHub will have to be load balanced in the future because I got some >> problems (reported to nico). >> >> Stef >> >> >> > >

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Frank Shearar

On 26 February 2013 22:15, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Frank > > if you want me to continue to interact with you on this topic (which I hope) :) > you will have to read the document :) Read it it takes 10 min on this point and you will see what we are starting to do. > I wrote it specifically to document this kind of discussion but I will not reproduce it in emails :) Sure, section 3.2. OK, so you're going to do what I'd just imagined. The SM-like thing just acts as a web UI to the various Distribution boxes. Cool! frank > We hope to have a first beta for June and it will be Cool and once it will be there nobody will not want to use it. > > I'm writing other chapters for the new book and this is an important task. Even if it is somehow boring too :). > > Syeg > >>> >> >> Yes. I should have said "What is it that you want for Pharo, _in this >> case_?" I understand (and support) the Pharo vision in general, but >> I'm not clear on what you mean by "I have been there and now I know >> what I want for Pharo." >> >> I mean, SqueakMap is abysmally ugly, hard to navigate, etc. etc. And >> yet, the core idea is sound: a place that lets you find cool packages. >> >>> A nice note: I browsed it 3 min and this is cool to see that some parts have already been done. The cool >>> aspects is that I'm quite confident that we will implement the vision and do a lot more. >>> >>> Now to reply to your question is a bad three line (the full answer is nicely explained in the vision doc): I want an automated validated tested distributions and core system. I want that users can click on a package and that it loads and all the tests are green and the smallLint rule ok. I think that this is a minimum. >>> And I do not want to rely on servers that can disappear. >> >> I tell what _would_ be cool: something that does what SM does - lists >> available packages, tells you what Smalltalks those packages claim to >> support... and also automatically tells you the dependencies (easily >> doable thanks to Metacello) and - most importantly - _periodically >> verifies_ the claims. So you go to the site and it says "PetitParser >> runs on Pharo 1.4, 2.0, Squeak 4.4, 4.5 and Cuis 4.1" Wouldn't it be >> really cool if SM-like thing actually verified these claims? (It would >> have to farm out the task elsewhere, of course.) >> >> Actually, GitHub almost does all of what we need: it's searchable, and >> you can easily hook things like Travis CI to show that your project >> works. (But of course Travis CI is inadequate for the kinds of >> cross-platform stuff we typically write.) >> >> frank >> >>> Stef >> > >

Feb. 26, 2013

[Pharo-project] iOS VM and external bluetooth keyboard

by phil＠highoctane.be

After a long hiatus, I've been back at hacking the iOS VM for supporting proper keystrokes from an external bluetooth keyboard. I guess I've nailed it down technically speaking (and learned a serious bunch about how the iOS VM is connecting Pharo with the world. Now, I have to get this right in the image. This will allow to have the full support for bindings on the iPad (which is what I am interested in). I would just love being able to program on the iPad like on a Dynabook! Stay tuned. Phil

Feb. 26, 2013

Re: [Pharo-project] Stressing SmalltalkHub :)

by Camillo Bruni

nice nice! On 2013-02-26, at 23:19, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I started to migrate Pharo 1.4 to SmalltalkHub to stress it a bit :) > Nicolas was curious to see and he loves to see all the packages getting published there. > So I could not resist (my upload bandwidth suffered :). > > It means also that SmalltalkHub will have to be load balanced in the future because I got some > problems (reported to nico). > > Stef > > >

Feb. 26, 2013

[Pharo-project] Stressing SmalltalkHub :)

by StÃ©phane Ducasse

Hi guys I started to migrate Pharo 1.4 to SmalltalkHub to stress it a bit :) Nicolas was curious to see and he loves to see all the packages getting published there. So I could not resist (my upload bandwidth suffered :). It means also that SmalltalkHub will have to be load balanced in the future because I got some problems (reported to nico). Stef

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by stephane ducasse

Frank if you want me to continue to interact with you on this topic (which I hope) :) you will have to read the document :) Read it it takes 10 min on this point and you will see what we are starting to do. I wrote it specifically to document this kind of discussion but I will not reproduce it in emails :) We hope to have a first beta for June and it will be Cool and once it will be there nobody will not want to use it. I'm writing other chapters for the new book and this is an important task. Even if it is somehow boring too :). Syeg >> > > Yes. I should have said "What is it that you want for Pharo, _in this > case_?" I understand (and support) the Pharo vision in general, but > I'm not clear on what you mean by "I have been there and now I know > what I want for Pharo." > > I mean, SqueakMap is abysmally ugly, hard to navigate, etc. etc. And > yet, the core idea is sound: a place that lets you find cool packages. > >> A nice note: I browsed it 3 min and this is cool to see that some parts have already been done. The cool >> aspects is that I'm quite confident that we will implement the vision and do a lot more. >> >> Now to reply to your question is a bad three line (the full answer is nicely explained in the vision doc): I want an automated validated tested distributions and core system. I want that users can click on a package and that it loads and all the tests are green and the smallLint rule ok. I think that this is a minimum. >> And I do not want to rely on servers that can disappear. > > I tell what _would_ be cool: something that does what SM does - lists > available packages, tells you what Smalltalks those packages claim to > support... and also automatically tells you the dependencies (easily > doable thanks to Metacello) and - most importantly - _periodically > verifies_ the claims. So you go to the site and it says "PetitParser > runs on Pharo 1.4, 2.0, Squeak 4.4, 4.5 and Cuis 4.1" Wouldn't it be > really cool if SM-like thing actually verified these claims? (It would > have to farm out the task elsewhere, of course.) > > Actually, GitHub almost does all of what we need: it's searchable, and > you can easily hook things like Travis CI to show that your project > works. (But of course Travis CI is inadequate for the kinds of > cross-platform stuff we typically write.) > > frank > >> Stef >

Feb. 26, 2013

Re: [Pharo-project] Happy to see progress

by Sven Van Caekenberghe

Yes, very impressive and so much more to comeâ¦ On 26 Feb 2013, at 22:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > have a look at the doc below I wrote it in november 2011, you will see that we are moving in the right direction :) > > For example > > 3.1 Towards a small kernel [we have it now we should think about all the core packages] > > 3.2 Towards a verified package catalog [On the way] > > 4.1 A Robust and Extensible System Events [Beta and should be in 3.0] > > 4.2 Rewrite of Filesystem/Streams [DONE for Files] > > 4.3 Announcements and Ephemerons [Annoucements is done :) - more cleans ready for 3.0 :) > > 4.4 UI Canvas for Zoomable Interfaces [Waiting for TextModel and 3.0] > > 4.5 Bootstrap of the Core [Done should be integrated in 3.0] > > 4.6 Fully parametrized compiler tool chain [Start with Opal in 3.0] > > 4.7 Packages as real objects [in 2.0 and will improve in 3.0] > > 4.8 Package Meta-Data [Done] > > 4.9 Less Model Clutter and Duplication [Started in 2.0 will be accentuated in 3.0] > > 4.10 Building and Reusing UI Logic [First cut in 2.0 UIPainter for 3.0] > > 4.11 New Network Layer [We will see] > > 4.12 Serializers [Done] > > 4.13 SystemChangeNotifier replacement [Done] > > 4.14 Cleaning Morphic [To be continued in 3.0] > > 5.2 VMs identification and regression testing [On the way] > > 5.3 One Unified FFI framework [ before June ] > <pharovision-1.pdf>

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by Frank Shearar

On 26 February 2013 21:26, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> >>> If you want to use SqueakMap go ahead. I have been there and now I know >>> what I want for Pharo. > > Hi frank > > >> I never know what you mean when you say things like this. What is it >> that you want for Pharo? > > I wrote a 40 page vision document just for that. It was not really fun but this is an important document so that people > that are not close to us can understand why we are doing certain things or saying others. So please have a look > and let us know if this is clear. > http://www.pharo-project.org/community/consortium Yes. I should have said "What is it that you want for Pharo, _in this case_?" I understand (and support) the Pharo vision in general, but I'm not clear on what you mean by "I have been there and now I know what I want for Pharo." I mean, SqueakMap is abysmally ugly, hard to navigate, etc. etc. And yet, the core idea is sound: a place that lets you find cool packages. > A nice note: I browsed it 3 min and this is cool to see that some parts have already been done. The cool > aspects is that I'm quite confident that we will implement the vision and do a lot more. > > Now to reply to your question is a bad three line (the full answer is nicely explained in the vision doc): I want an automated validated tested distributions and core system. I want that users can click on a package and that it loads and all the tests are green and the smallLint rule ok. I think that this is a minimum. > And I do not want to rely on servers that can disappear. I tell what _would_ be cool: something that does what SM does - lists available packages, tells you what Smalltalks those packages claim to support... and also automatically tells you the dependencies (easily doable thanks to Metacello) and - most importantly - _periodically verifies_ the claims. So you go to the site and it says "PetitParser runs on Pharo 1.4, 2.0, Squeak 4.4, 4.5 and Cuis 4.1" Wouldn't it be really cool if SM-like thing actually verified these claims? (It would have to farm out the task elsewhere, of course.) Actually, GitHub almost does all of what we need: it's searchable, and you can easily hook things like Travis CI to show that your project works. (But of course Travis CI is inadequate for the kinds of cross-platform stuff we typically write.) frank > Stef

Feb. 26, 2013

[Pharo-project] Happy to see progress

by StÃ©phane Ducasse

Hi guys have a look at the doc below I wrote it in november 2011, you will see that we are moving in the right direction :) For example 3.1 Towards a small kernel [we have it now we should think about all the core packages] 3.2 Towards a verified package catalog [On the way] 4.1 A Robust and Extensible System Events [Beta and should be in 3.0] 4.2 Rewrite of Filesystem/Streams [DONE for Files] 4.3 Announcements and Ephemerons [Annoucements is done :) - more cleans ready for 3.0 :) 4.4 UI Canvas for Zoomable Interfaces [Waiting for TextModel and 3.0] 4.5 Bootstrap of the Core [Done should be integrated in 3.0] 4.6 Fully parametrized compiler tool chain [Start with Opal in 3.0] 4.7 Packages as real objects [in 2.0 and will improve in 3.0] 4.8 Package Meta-Data [Done] 4.9 Less Model Clutter and Duplication [Started in 2.0 will be accentuated in 3.0] 4.10 Building and Reusing UI Logic [First cut in 2.0 UIPainter for 3.0] 4.11 New Network Layer [We will see] 4.12 Serializers [Done] 4.13 SystemChangeNotifier replacement [Done] 4.14 Cleaning Morphic [To be continued in 3.0] 5.2 VMs identification and regression testing [On the way] 5.3 One Unified FFI framework [ before June ]

Feb. 26, 2013

Re: [Pharo-project] [ANN] ZTimestamp[Precise]SNTPClient

by stephane ducasse

>>> >> If you want to use SqueakMap go ahead. I have been there and now I know >> what I want for Pharo. Hi frank > I never know what you mean when you say things like this. What is it > that you want for Pharo? I wrote a 40 page vision document just for that. It was not really fun but this is an important document so that people that are not close to us can understand why we are doing certain things or saying others. So please have a look and let us know if this is clear. http://www.pharo-project.org/community/consortium A nice note: I browsed it 3 min and this is cool to see that some parts have already been done. The cool aspects is that I'm quite confident that we will implement the vision and do a lot more. Now to reply to your question is a bad three line (the full answer is nicely explained in the vision doc): I want an automated validated tested distributions and core system. I want that users can click on a package and that it loads and all the tests are green and the smallLint rule ok. I think that this is a minimum. And I do not want to rely on servers that can disappear. Stef

Feb. 26, 2013