June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] 1.2.2 First Impression

by StÃ©phane Ducasse

thanks Sean the ui part of pharo will probably change again because we are changing a lot in the back... I hope to stabilize soon. Stef On Jun 3, 2011, at 3:33 AM, Sean P. DeNigris wrote: > I moved from 1.1.1 to 1.2.2 for my development work and wanted to share some > things I noticed... > > Overall, 1.2.2 feels cleaner, snappier, and prettier. > > My Favorite Things: > * OCompletion is really fast!!! > * Creating new method protocols - you can type spaces > * Help System starting to fill out, and easily accessible from the World > Menu > > Bugs / Regressions (I don't have time to check if each is still true in > trunk) > * Debugger > * the current statement is highlighted in "invisible blue". It's > impossible to see. > * Creating an accessor - "should be implemented" is highlighted, which is > good; but the window doesn't have focus, and clicking on the window's title > bar doesn't give the source pane focus > * Choosing a protocol for a created method - the selection doesn't jump to > the first matching category name like it did in 1.1.1 > * OB > * Syntax errors - "Nothing more expected ->" is not highlighted, making > you have to first select it before you delete it and correct your mistake > * Surrounding selected text (e.g. with quotes) - the surrounded text > doesn't stay highlighted (the 1.1.1 behavior, which I found very useful) > * Monticello - After changing a category name to a sub-category of a > different package (e.g. "MyLibrary" -> "MyOtherProject-MyLibrary"), the > package is not marked dirty in the MC browser until changes are viewed. > > I'm really excited to see what comes next!! We're creating a great system. > > Sean > > -- > View this message in context: http://forum.world.st/1-2-2-First-Impression-tp3569795p3569795.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 3, 2011

Re: [Pharo-project] ACM Student Research Competition

by StÃ©phane Ducasse

well done!! Stef On Jun 3, 2011, at 4:36 PM, Alexandre Bergel wrote: > Hi! > > There is a news I would like to share with you. Vanessa, a student at the University of Chile, is just back from ICSE, a top conference on software engineering. She presented Hapao (http://hapao.dcc.uchile.cl) a Pharo application, at the ACM Student Research Competition[*]. It was a success: she arrived 2nd in the category undergraduate student. A nice medal for the Pharo community! > > Cheers, > Alexandre > > [*] http://2011.icse-conferences.org/content/src-call > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

June 3, 2011

Re: [Pharo-project] Do we freeze 1.3?

by StÃ©phane Ducasse

sounds like a good plan! Stef On Jun 3, 2011, at 10:10 AM, Marcus Denker wrote: > > On May 25, 2011, at 11:29 AM, Marcus Denker wrote: > >> Hello, >> >> 1.3 seems to stabilize... >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 >> >> just 12 issues left. > > So we have 5 issues left... > > We started to tag issues 1.4 for things that are not show-stoppers: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 > > My idea would be > > -> try to fix the 5 issues next week > -> as soon as they are fixed, set the version number to 1.3 (and open 1.4 so we don't get > drowned in open issues that are easy to add yet not for 1.3) > -> wait 3 weeks, while fixing bugs people find and then announce the release formally. > > The idea is to not have any release canditate, nor 1.3.x releases. > 1.3 will just have updates as soon as somone fixes something important. > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

June 3, 2011

Re: [Pharo-project] OSProcess and CommandShell

by StÃ©phane Ducasse

+1 Stef >> So why don't we set up the Config to always load the latest packages? Can >> the stable be set this way (I guess load the baseline)? > > Because although it can work for the following months in a couple of > years where OSProcess uses something from the image from 2014 it wont > work anymore. It is better to link a stable version to a given version. > This number can be then corrected as tested OSProcess versions are > verified to work in a given image release. Even then, only the stable > version for that pharo release would be updated, not every possible > Pharo image. > > Cheers

June 3, 2011

Re: [Pharo-project] loading code from command line inovcation

by Hilaire Fernandes

Le 31/05/2011 11:17, Igor Stasenko a Ã©crit : > Please, be more precise when saying about VM crash. I reported the PharoDebugLog in a preivious message in this thread. Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

June 3, 2011

Re: [Pharo-project] loading code from command line inovcation

by Hilaire Fernandes

What am I suppose to understand from this url? Le 31/05/2011 10:27, StÃ©phane Ducasse a Ã©crit : > http://code.google.com/p/pharo/issues/list?thanks=4319 > > > On May 30, 2011, at 9:12 PM, Hilaire Fernandes wrote: > >> Some more tests: >> >> 1. this crash the image: >> squeak PharoCore-1.3.image `pwd`/cacaboudin >> >> cacaboudin does not exist >> >> 2. this crash the image: >> squeak PharoCore-1.3.image `pwd`/empty.st >> >> where empty.st is empty >> >> 3. this work: >> >> squeak PharoCore-1.3.image `pwd`/test.st >> >> where test.st only contains: Transcript show: 'hello' >> >> >> >> >> >> >> >> Le 28/05/2011 22:53, Hilaire Fernandes a Ã©crit : >>> Still does not work >>> >>> Hilaire >>> >>> Le 28/05/2011 21:02, Guillermo Polito a Ã©crit : >>>> It seems code loader is not sending #startRetrieval to the UrlDownload >>>> Request, and the Semaphore waits forever. >>>> >>>> I've put a changeset with what I think is a fix in the tracker :). >>>> >>>> On Sat, May 28, 2011 at 2:27 PM, Hilaire Fernandes >>>> <hilaire.fernandes(a)gmail.com >>>> <mailto:hilaire.fernandes@gmail.com>> wrote: >>>> >>>> And the debug is there. >>>> The halt does not crash the VM in normal condition. (ie Alt-[.] is ok) >>>> >>>> Hilaire >>>> >>>> >>>> Le 28/05/2011 19:07, Hilaire Fernandes a Ã©crit : >>>>> And when there are no halt in commandLineHandlerAction:, the image is >>>>> frozen >>>>> >>>>> Le 28/05/2011 18:53, Hilaire Fernandes a Ã©crit : >>>>>> With latest pahro core 1.3, I can't load script with command like >>>>>> >>>>>> >>>>>> squeak pharo "`pwd`\myScript.st" >>>>>> >>>>>> When I put a halt at the begining of commandLineHandlerAction: >>>>>> aCommandLine the VM crash >>>>>> >>>>>> VM is 4.0.3-2202 >>>>>> >>>>>> Hilaire >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Education 0.2 -- http://blog.ofset.org/hilaire >>>> >>>> >>> >>> >> >> >> -- >> Education 0.2 -- http://blog.ofset.org/hilaire >> >> > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

June 3, 2011

Re: [Pharo-project] 1.2.2 First Impression

by Marcus Denker

we should not forget to add issues on the tracker for the problems that are not yet fixed in 1.3... On Jun 3, 2011, at 3:33, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > I moved from 1.1.1 to 1.2.2 for my development work and wanted to share some > things I noticed... > > Overall, 1.2.2 feels cleaner, snappier, and prettier. > > My Favorite Things: > * OCompletion is really fast!!! > * Creating new method protocols - you can type spaces > * Help System starting to fill out, and easily accessible from the World > Menu > > Bugs / Regressions (I don't have time to check if each is still true in > trunk) > * Debugger > * the current statement is highlighted in "invisible blue". It's > impossible to see. > * Creating an accessor - "should be implemented" is highlighted, which is > good; but the window doesn't have focus, and clicking on the window's title > bar doesn't give the source pane focus > * Choosing a protocol for a created method - the selection doesn't jump to > the first matching category name like it did in 1.1.1 > * OB > * Syntax errors - "Nothing more expected ->" is not highlighted, making > you have to first select it before you delete it and correct your mistake > * Surrounding selected text (e.g. with quotes) - the surrounded text > doesn't stay highlighted (the 1.1.1 behavior, which I found very useful) > * Monticello - After changing a category name to a sub-category of a > different package (e.g. "MyLibrary" -> "MyOtherProject-MyLibrary"), the > package is not marked dirty in the MC browser until changes are viewed. > > I'm really excited to see what comes next!! We're creating a great system. > > Sean > > -- > View this message in context: http://forum.world.st/1-2-2-First-Impression-tp3569795p3569795.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 3, 2011

Re: [Pharo-project] [squeak-dev] Re: usability of Pharo and Squeak

by Dale Henrichs

----- Original Message ----- | From: "Andreas Wacknitz" <a.wacknitz(a)gmx.de> | | I hope you will be successful. I don't like programming web | interfaces because I am still not convinced that they are superior | to traditional GUI's. | Especially I don't like the mix of HMTL, JavaScript and CSS, even if | you can replace HTML by Smalltalk with Seaside. | And I also need to be convinced that Seaside is really such a big | thing. I haven't seen advanced GUI's in Seaside yet. | The examples I have seen in the Seaside book and the Seaside site are | all simplistic. | Maybe tODE will change my mind :D Thanks Andreas, For advanced Seaside apps, check out NeXTPLAN[1]... As for tODE, the framework/approach isn't directly tied to Seaside ... I think tODE could be done in Morphic, but a Morphic-based tODE wouldn't serve my needs. Not only does GemStone lack a native GUI, but the GLASS applications are running on machines in a server farm somewhere and native GUIs aren't very responsive over the WAN, whereas serving pages from a remote server can provide acceptable performance. I do agree that I seem to be working with an unholy mixture of HTML, Javascript, and CSS, but Seaside does help hide the ugliness of HTML and Javascript... Dale [1] http://www.slideshare.net/esug/next-planjohanbrichau

June 3, 2011

Re: [Pharo-project] ACM Student Research Competition

by Michael Haupt

Hi, congrats to Vanessa! Another interesting bit of news is that thereby, Microsoft is sponsoring Smalltalk. ;-) Best, Michael Am 03.06.2011 um 16:36 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi! > > There is a news I would like to share with you. Vanessa, a student at the University of Chile, is just back from ICSE, a top conference on software engineering. She presented Hapao (http://hapao.dcc.uchile.cl) a Pharo application, at the ACM Student Research Competition[*]. It was a success: she arrived 2nd in the category undergraduate student. A nice medal for the Pharo community! > > Cheers, > Alexandre > > [*] http://2011.icse-conferences.org/content/src-call > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

June 3, 2011

Re: [Pharo-project] [squeak-dev] Re: usability of Pharo and Squeak

by Andreas Wacknitz

Am 02.06.2011 um 19:07 schrieb Dale Henrichs: > Andreas, > > You are not alone. I too suffer from tooManyWindowsItis ... I am also doing something about it:) > > The project is in it's very early stages ... I'm drawing on kraft paper with fat crayons ... but I am encouraged by the results so far. The system is called tODE "the Object (centric) Development Environment" and is written in Seaside, so it is javascript/web browser based. I am developing the system in Pharo, but it is targeted as the next generation development environment for GLASS. > > I've enclosed a screenshot ... the system uses a single tab in the web-browser, but provides it's own www-style navigation through the Smalltalk object-space (so it is a browser inside of a browser) ... each of the tODE tabs is a view on an object and each object is wrapped by a TOObjectFrame that holds onto the tODE-specific state ... links take you to other objects ... you type Smalltalk-expressions in the input area at the top (and in the workspace tab)... I'm not a javascript guy (which is where the fat crayons come into play:)...You can inspect stacks in a "debugger", I've started work on the Metacello tab....etc. > > With only one window, you never have to open/close another window!:) and with infinite history (at the bottom) you never lose the ability to go back to a previous object ... > > The framework is very small: 21 classes in the TOOBject hierarchy and another 20 support classes, but being built on top of Seaside, it can't be called "light weight". It is designed to be easily customizable and extensible through the use of pragmas ... > > I have just started using the system for development (you got to eat your own dog food), but often have to fall back into Pharo, so the system is really not ready for folks to play with ... yet... I need to solve the debugger issues before I can feel comfortable with letting folks play with it:) > > Finally, while tODE is written on top of Seaside, I don't think that I'm leveraging Seaside for much more than rendering and javascript generation, which means that tODE could be adapted to other GUI frameworks ...I imagine ... > > Dale > Hi Dale, I hope you will be successful. I don't like programming web interfaces because I am still not convinced that they are superior to traditional GUI's. Especially I don't like the mix of HMTL, JavaScript and CSS, even if you can replace HTML by Smalltalk with Seaside. And I also need to be convinced that Seaside is really such a big thing. I haven't seen advanced GUI's in Seaside yet. The examples I have seen in the Seaside book and the Seaside site are all simplistic. Maybe tODE will change my mind :D Regards Andreas

June 3, 2011