December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] big ui decisions

by Janko MivÅ¡ek

Hi Chip, For really cool web browser based apps watch also Iliad [1] and Aida/Web [2], we both have a big plans on richer client-side web apps, also standalone and offline, that is, they can work without a connection to the web server. And there are tools which package such an app actually completely standalone, for installation on mobile devices, for now. See for instance a PhoneGap [3] which wrap web applications inside a native application, as described in O'Reilly book [4]. This approach could be extended to any desktop too. To conclude, with our web technology we can actually "generate" standalone desktop apps, by using just HTML5, CSS and JavaScript, all generated from Smalltalk only! Best regards Janko [1] Iliad http://www.iliadproject.org [2] Aida/Web http://www.aidaweb.si [3] PhoneGap http://www.nitobi.com/products/phonegap [4] Building Android Apps HTML, CSS and JavaScript, O'Reilly 2010 On 22. 12. 2010 10:46, Chip Nowacek wrote: > > Thanks for your help so far. > > Now that I've had a chance to get my feet wet, start an eval of VW, watch > Peter Fisk's progress, etc. I've hit a scary point. To go the distance, my > app needs the maturity and capacity of Squeak/Pharo/VW(?). And, near- and > long-term, it needs an elegant, cogent, captivating, intelligent, engaging, > interactive front end. I've considered doing it in Flash or Silverlight or > AIR (fat client) or straight JavaScript - though splitting the tiers and > forgetting the backend seems like a lot of deferred pain. I know I have to > worry about deployment. I am. I'd rather do it through the browser. And, > even though DabbleDB and others are some of the coolest apps ever, I don't > see Seaside cutting the front-end mustard (at least the way I understand > things at this point). I sure wish there was a lightening-fast, > browser-based, morphic-3-supporting VM so I could run ST on both tiers. A > sexy, Smalltalk Lively-Kernel. I'm still trying to get Clamato to work. > > So, in your professional, experienced opinions, can I get a front end on > Pharo (either in-image via Rome/Athens or some cooler-than-I've-seen, > through-the-browser front end)? With all due respect to the Founding > Fathers, I can't do eToys. Should I just do the whole client tier in in JS > for the prototype and then hook to Seaside later? > > Any thoughts would be deeply appreciated. > > Thanks, > > Chip -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

Dec. 22, 2010

[Pharo-project] about copy in the bug tracker

by StÃ©phane Ducasse

Hi guys am i the only one having problem with copy (control-C when on the bug tracker)? I hate when it create a new entry. Stef

Dec. 22, 2010

Re: [Pharo-project] big ui decisions

by StÃ©phane Ducasse

On Dec 22, 2010, at 10:46 AM, Chip Nowacek wrote: > > Thanks for your help so far. > > Now that I've had a chance to get my feet wet, start an eval of VW, watch > Peter Fisk's progress, etc. I've hit a scary point. To go the distance, my > app needs the maturity and capacity of Squeak/Pharo/VW(?). And, near- and > long-term, it needs an elegant, cogent, captivating, intelligent, engaging, > interactive front end. I've considered doing it in Flash or Silverlight or > AIR (fat client) or straight JavaScript - though splitting the tiers and > forgetting the backend seems like a lot of deferred pain. I know I have to > worry about deployment. I am. I'd rather do it through the browser. And, > even though DabbleDB and others are some of the coolest apps ever, I don't > see Seaside cutting the front-end mustard (at least the way I understand > things at this point). what is specific about your app? > I sure wish there was a lightening-fast, > browser-based, morphic-3-supporting VM so I could run ST on both tiers. A > sexy, Smalltalk Lively-Kernel. I'm still trying to get Clamato to work. > > So, in your professional, experienced opinions, can I get a front end on > Pharo (either in-image via Rome/Athens or some cooler-than-I've-seen, > through-the-browser front end)? it depends what you need. Our plans with igor are to produce a nice API to access Cairo and openVG but this will not happen before 3-4 months. > With all due respect to the Founding > Fathers, I can't do eToys. Should I just do the whole client tier in in JS > for the prototype and then hook to Seaside later? did you see nextPlan? Because they generate svg too? > > Any thoughts would be deeply appreciated. > > Thanks, > > Chip > -- > View this message in context: http://forum.world.st/big-ui-decisions-tp3160359p3160359.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 22, 2010

Re: [Pharo-project] PharoCore #12884

by StÃ©phane Ducasse

> Hi, > > I just updated my 1.2 core to #12884 with 3 updates and my MC repos are gone from my packages, only the standard repos remain. > > Maybe this is a sign of something that went wrong. no this is just that some package where home-orphaned and marcus issued a command to clean (because you can have duplicate repo with the same name but different password -- > a hell) and reassign all the package repo to package. So your packages got flushed too apparently. Sorry. Stef > > Sven > >

Dec. 22, 2010

Re: [Pharo-project] [TODO] 1.2 Core + Full

by Mariano Martinez Peck

On Wed, Dec 22, 2010 at 9:18 AM, Luc Fabresse <luc.fabresse(a)gmail.com>wrote: > Hi Marcus, > > Thanks, your mails are good to push me ahead ;-) > > I think that #3455 is ready for integration (make 2 tests pass in dev). > and #3447 too (provided CS or just remove the method). > Luc, in the cae of 3447, you should commit to the Shout repo since this is not part ofpharo core. BTW....which version of ShoutWorkspace was being installed...because I already fixed that in: Name: ShoutWorkspace.1-maiano.6 Author: maiano Time: 12 May 2010, 7:53:35 pm UUID: 8265a4c8-d212-4ac1-b2d5-79b5722ed9c3 Ancestors: ShoutWorkspace.1-Alexandre_Bergel.5 Removed menuCommandOn: aBuilder from ShoutWorkspace as such item is already in the manu (in the part of most common tools) together with SystemBrowser, Test Runner and Monticello Browser. If they are not there, then they are not under "Tools". cheers mariano > > #Luc > > > 2010/12/22 Marcus Denker <marcus.denker(a)inria.fr> > > For 1.2 to to be released, we need to >> >> a) get all tests green. >> There are right now 9 failing tests in Core and 9 additional one in the >> full image. >> >> 9 of 7915 tests fail: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… >> >> 18 of 10284 tests fail: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… >> >> some of those are test-server artefacts that only fail on the testserver. >> >> b) Bug Tracker. Here the issues need to be either resolved or decided to >> be not show-stoppers >> (there will be a 1.3 release! So somehting that is already not in 1.1, >> why do we need in in 1.2? >> A release is just a usable snapshot of an on-going process) >> >> 23 reports are tagged as 1.2: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID… >> >> 8 reports are tagged as 1.2 for the full image? >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage&c… >> >> All failing tests do have bug-tracker entries. >> >> Marcus >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >

Dec. 22, 2010

[Pharo-project] big ui decisions

by Chip Nowacek

Thanks for your help so far. Now that I've had a chance to get my feet wet, start an eval of VW, watch Peter Fisk's progress, etc. I've hit a scary point. To go the distance, my app needs the maturity and capacity of Squeak/Pharo/VW(?). And, near- and long-term, it needs an elegant, cogent, captivating, intelligent, engaging, interactive front end. I've considered doing it in Flash or Silverlight or AIR (fat client) or straight JavaScript - though splitting the tiers and forgetting the backend seems like a lot of deferred pain. I know I have to worry about deployment. I am. I'd rather do it through the browser. And, even though DabbleDB and others are some of the coolest apps ever, I don't see Seaside cutting the front-end mustard (at least the way I understand things at this point). I sure wish there was a lightening-fast, browser-based, morphic-3-supporting VM so I could run ST on both tiers. A sexy, Smalltalk Lively-Kernel. I'm still trying to get Clamato to work. So, in your professional, experienced opinions, can I get a front end on Pharo (either in-image via Rome/Athens or some cooler-than-I've-seen, through-the-browser front end)? With all due respect to the Founding Fathers, I can't do eToys. Should I just do the whole client tier in in JS for the prototype and then hook to Seaside later? Any thoughts would be deeply appreciated. Thanks, Chip -- View this message in context: http://forum.world.st/big-ui-decisions-tp3160359p3160359.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 22, 2010

[Pharo-project] PharoCore #12884

by Sven Van Caekenberghe

Hi, I just updated my 1.2 core to #12884 with 3 updates and my MC repos are gone from my packages, only the standard repos remain. Maybe this is a sign of something that went wrong. Sven

Dec. 22, 2010

Re: [Pharo-project] Issue 3459 in pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString:

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #2 on issue 3459 by stephane.ducasse: includesSubstring: aString caseSensitive: caseSensitive / includesSubString: http://code.google.com/p/pharo/issues/detail?id=3459 Why do you want to have only one method? Having two is nice, you get a fallback. when you do not want to specify the case.

Dec. 22, 2010

Re: [Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows

by pharo＠googlecode.com

Updates: Status: Accepted Labels: Milestone-1.2 Comment #1 on issue 3458 by stephane.ducasse: bug in the class MultiByteFileStream when Pharo running under Windows http://code.google.com/p/pharo/issues/detail?id=3458 Tx

Dec. 22, 2010

Re: [Pharo-project] Issue 3474 in pharo: BmpReadWriterPlugin primitives should be used

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #1 on issue 3474 by stephane.ducasse: BmpReadWriterPlugin primitives should be used http://code.google.com/p/pharo/issues/detail?id=3474 Tx torsten.

Dec. 22, 2010