August 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Seaside 3.1 on Pharo 2.0

by Sven Van Caekenberghe

I am happy to report that, thanks to some extra work done by Philippe Marschall - Thx, Philippe ! -, there is now a way to get Seaside 3.1 working on the current version of Pharo 2.0. The trick is to use the following script: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st Here is the code to execute in a Workspace: "Basic" Gofer new squeaksource: 'Seaside31'; package: 'Grease-Core'; package: 'Grease-Pharo20-Core'; package: 'Grease-Tests-Core'; package: 'Grease-Tests-Pharo20-Core'; package: 'Seaside-Core'; package: 'Seaside-Pharo20-Core'; package: 'Seaside-Tests-Core'; package: 'Seaside-Tests-UTF8'; package: 'Seaside-Tests-Pharo20-Core'; package: 'Seaside-Canvas'; package: 'Seaside-Pharo-Canvas'; package: 'Seaside-Tests-Canvas'; package: 'Seaside-Session'; package: 'Seaside-Tests-Session'; package: 'Seaside-Component'; package: 'Seaside-Tests-Component'; package: 'Seaside-RenderLoop'; package: 'Seaside-Tests-RenderLoop'; package: 'Seaside-Tools-Core'; package: 'Seaside-Widgets'; package: 'Seaside-Environment'; package: 'Seaside-Pharo-Environment'; package: 'Seaside-Tests-Environment'; load. ! "Traditional" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Tests-Functional'; package: 'Seaside-Tests-Pharo-Functional'; package: 'Seaside-Pharo-Continuation'; package: 'Seaside-Tests-Pharo-Continuation'; package: 'Seaside-Flow'; package: 'Seaside-Pharo-Flow'; package: 'Seaside-Tests-Flow'; package: 'Seaside-Tools-Web'; package: 'Seaside-Pharo20-Tools-Web'; package: 'Seaside-Tests-Tools-Web'; package: 'Seaside-Development'; package: 'Seaside-Pharo-Development'; package: 'Seaside-Tests-Development'; package: 'Seaside-Tests-Pharo-Development'; package: 'Seaside-Examples'; package: 'Seaside-Tests-Examples'; load. ! "RSS" Gofer new squeaksource: 'Seaside31'; package: 'RSS-Core'; package: 'RSS-Tests-Core'; package: 'RSS-Examples'; load. ! "Javascript" Gofer new squeaksource: 'Seaside31'; package: 'Javascript-Core'; package: 'Seaside-JSON-Core'; package: 'Seaside-Pharo-JSON-Core'; package: 'Javascript-Pharo20-Core'; package: 'Javascript-Tests-Core'; package: 'Javascript-Tests-Pharo-Core'; package: 'Seaside-Tests-JSON'; package: 'JQuery-Core'; package: 'JQuery-Tests-Core'; package: 'JQuery-JSON'; package: 'JQuery-Tests-JSON'; package: 'JQuery-UI'; package: 'JQuery-Tests-UI'; package: 'Prototype-Core'; package: 'Prototype-Tests-Core'; package: 'Scriptaculous-Core'; package: 'Scriptaculous-Tests-Core'; package: 'Scriptaculous-Components'; package: 'Scriptaculous-Tests-Components'; package: 'Comet-Core'; package: 'Comet-Examples'; package: 'Comet-Pharo-Core'; package: 'Comet-Tests-Core'; load. ! "Other Packages" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Welcome'; package: 'Seaside-Pharo-Welcome'; package: 'Seaside-Tests-Welcome'; package: 'Seaside-HTML5'; package: 'Seaside-Tests-HTML5'; package: 'Seaside-InternetExplorer'; package: 'Seaside-Tests-InternetExplorer'; package: 'Seaside-Email'; package: 'Seaside-Tests-Email'; package: 'Seaside-Pharo-Email'; package: 'Seaside-Tests-Pharo-Email'; load. ! "REST" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-REST-Core'; package: 'Seaside-Pharo-REST-Core'; package: 'Seaside-Tests-REST-Core'; load. This does not yet load an adaptor. You can go find ZnZincServerAdaptor in the Zinc repository, like this (updating all Zn): Gofer new url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'Zinc-HTTP'; package: 'Zinc-Tests; package: 'Zinc-FileSystem'; package: 'Zinc-Seaside'; load. And finally, ZnZincStaticServerAdaptor startOn: 8080. ZnZincStaticServerAdaptor stop. (The Seaside control panel is not there). All but one, less relevant test, pass. Thanks again, Philippe. Sven PS: The ConfigurationOfSeaside is in the process to be updated as well. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Aug. 29, 2012

Re: [Pharo-project] Pharo/Seaside as back-end for a social media app

by Esteban Lorenzano

Hi, On Aug 29, 2012, at 6:39 AM, Francois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Hi Oscar, > >> + Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?) > > You probably don't want to serve medias with Pharo but use Apache/nginx/whatever. They serve static files really well and you don't want to put load on your Smalltalk for such a task. yeah... but thats an usual configuration. I don't think anyone in the world renders video by themselves. > >> + Database communication (I can use GlorpDBX) > > Never used it but it seems to work fine for many people. you can use it (dbxtalk.org) but... why do you need a relational database? Why care about that now? > >> + Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server) > > I would be interested if you find a solution/package. no idea :) > >> + Scalability, where I can easily grow from hundreds to thousands of clients. > > If you go stateless (you probably will if you go full REST) you can distribute load on as many images as you want. as in all solutions, it depends much in your application design. A regular Seaside application can handle more or less 30-50 simultaneous requests per image, which is not much but with some design you can improve a lot... and of course, you can scale by adding pharo boxes, and since a pharo box will consume around 100m (again if your design is ok...), with 1G RAM available you can run 10 pharo boxes which gives you 300-500 simultaneous requests... which most than good for most applications :) > >> Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails. > > Ruby/Rails has probably a bigger ecosystem and conventions around it but Pharo is definitely cooler ;) > as a summary, I think you are going to be ok :) Esteban

Aug. 29, 2012

Re: [Pharo-project] The MC diff tool highligting is broken

by Mariano Martinez Peck

yes this is terrible broken since a long time. For me this is a really stop-the-world. I cannot commit because I cannot be sure what I am committing (since I cannot see the changes), you cannot merge safely. cheers, On Wed, Aug 29, 2012 at 7:35 AM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > add a bug report :) > > On 2012-08-28, at 22:21, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > in 2.0 it highlights random portions of text, completely out of sync > > with real difference. > > > > and if you resize the window, it doesn't changes, it doesn't follows > > the text.. (i think this can be a good hint to look for a place to > > fix) > > > > -- > > Best regards, > > Igor Stasenko. > > > > > -- Mariano http://marianopeck.wordpress.com

Aug. 29, 2012

Re: [Pharo-project] Why FileSystemHandle has writable flag, but not readable?

by Camillo Bruni

'foo' asFileReference isReadable 'foo' asFileReference isWriteable 'foo' asFileReference permissions On 2012-08-29, at 01:14, Igor Stasenko <siguctua(a)gmail.com> wrote: > you know, it can happen that you can open a file for write but not for read. > > i do not see how i can say "this reference is for write only"

Aug. 29, 2012

Re: [Pharo-project] The MC diff tool highligting is broken

by Camillo Bruni

add a bug report :) On 2012-08-28, at 22:21, Igor Stasenko <siguctua(a)gmail.com> wrote: > in 2.0 it highlights random portions of text, completely out of sync > with real difference. > > and if you resize the window, it doesn't changes, it doesn't follows > the text.. (i think this can be a good hint to look for a place to > fix) > > -- > Best regards, > Igor Stasenko. >

Aug. 29, 2012

Re: [Pharo-project] Pharo/Seaside as back-end for a social media app

by Francois Stephany

Hi Oscar, > + Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?) You probably don't want to serve medias with Pharo but use Apache/nginx/whatever. They serve static files really well and you don't want to put load on your Smalltalk for such a task. > + Database communication (I can use GlorpDBX) Never used it but it seems to work fine for many people. > + Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server) I would be interested if you find a solution/package. > + Scalability, where I can easily grow from hundreds to thousands of clients. If you go stateless (you probably will if you go full REST) you can distribute load on as many images as you want. > Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails. Ruby/Rails has probably a bigger ecosystem and conventions around it but Pharo is definitely cooler ;)

Aug. 29, 2012

[Pharo-project] Pharo/Seaside as back-end for a social media app

by Oscar E A CallaÃº

Hi all, I plan to build a social media app, initially targeted to iOS clients. I was wondering if pharo 1.4 and seaside 3.07/3.1 are enough for a back-end where at least these requirements are expected: + Rest communication (I can use Seaside-REST) + Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?) + Database communication (I can use GlorpDBX) + Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server) + Scalability, where I can easily grow from hundreds to thousands of clients. Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails. Thanks in advance. I'll really appreciate your comments. Cheers

Aug. 29, 2012

[Pharo-project] Why FileSystemHandle has writable flag, but not readable?

by Igor Stasenko

you know, it can happen that you can open a file for write but not for read. i do not see how i can say "this reference is for write only" -- Best regards, Igor Stasenko.

Aug. 28, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.3

by Igor Stasenko

On 28 August 2012 23:41, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > On Tue, Aug 28, 2012 at 2:20 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 28 August 2012 16:31, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: >>>> >>> Cannot parse. You want to integrate it till it fails? :) >>> >>> >>> Yes.. keep it in from now on in the main base till it shows up as unusable. >>> I do not mind occasional instability.. or something I can workaround... :). >>> >> >> i think you meant 'i will use it till i find a better alternative'. That's fine. >> I do not pretend to have best of the best, which will answer all of >> your needs :) >> > Hmm. I read S Krish as saying that he wants to use it until it proves > itself so broken, he can't use it. > and how is that possible? That's why i asked for clarification. Because it doesn't makes sense to me. The project is open source. So, if there a people interested in keeping it in a good shape, that simply cannot happen, even if i will disappear. And part of my today's work is actually to eliminate the 'bus factor'. > I suspect as long as you are interested in it, he won't find that to > actually happen... > and how is that possible as well? Of course, there is a probability that one day i will wake up and say "that is enough" and lose interest not only in NativeBoost , but in programming as a whole. But that probability is not too high, something like meeting a dinosaur on the street. :) -- Best regards, Igor Stasenko.

Aug. 28, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.3

by Chris Cunningham

On Tue, Aug 28, 2012 at 2:20 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 28 August 2012 16:31, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: >>> >> Cannot parse. You want to integrate it till it fails? :) >> >> >> Yes.. keep it in from now on in the main base till it shows up as unusable. >> I do not mind occasional instability.. or something I can workaround... :). >> > > i think you meant 'i will use it till i find a better alternative'. That's fine. > I do not pretend to have best of the best, which will answer all of > your needs :) > Hmm. I read S Krish as saying that he wants to use it until it proves itself so broken, he can't use it. I suspect as long as you are interested in it, he won't find that to actually happen...

Aug. 28, 2012