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

Re: [Pharo-project] 1.3 - thanks, congratulations, etc.

by Marcus Denker

On Mon, Oct 3, 2011 at 8:04 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> I just saw the download link for 1.3 on the web site - thanks to all who worked on it. I'll give it a try shortly. >>> >> There is one last update coming... we fixed some more bugs and need to sync with latest RB/OB, I hope to do that this week. > > I redid the ConfigurationOfRB and OB so they should work. People should let us know. > On Hudson the build is not working (yet it is blue, so strange): Error: Could not resolve: OB-Standard [OB-Standard-lr.548] in /builds/workspace/Pharo 1.3/Pharo-1.3/package-cache http://www.squeaksource.com/PharoOB -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

Oct. 3, 2011

[Pharo-project] [update 1.3] #13315

by Marcus Denker

13315 ----- Do a #cleanUpForRelease -- Marcus Denker -- http://marcusdenker.de

Oct. 3, 2011

Re: [Pharo-project] 1.3 - thanks, congratulations, etc.

by StÃ©phane Ducasse

>> I just saw the download link for 1.3 on the web site - thanks to all who worked on it. I'll give it a try shortly. >> > There is one last update coming... we fixed some more bugs and need to sync with latest RB/OB, I hope to do that this week. I redid the ConfigurationOfRB and OB so they should work. People should let us know. > >> Is Hudson (old ci server) doing correct builds into the future, or is the RC/release one-click what we are going to use for 1.3? >> > > In the future, yes. Now: No. Two problems: > > 1) One Click script needs to be updates to use current VMs > 2) The Core has changes to how Shout works without the Full loading the new Shout and OB needed > > the 2) we need to do ASAP, the 1) we should fix after moving the build to the new Jenkins setup. > > so much to do, so little time... > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 3, 2011

Re: [Pharo-project] [update 1.4] #14185

by StÃ©phane Ducasse

thanks marcus. You are our clock :) Stef On Oct 2, 2011, at 10:13 PM, Marcus Denker wrote: > 14185 > ----- > > Issue 4885: With SystemReporter, we do not need a menu entry for GC statistics > http://code.google.com/p/pharo/issues/detail?id=4885 > > Issue 4884: Move deprecated methods to *deprecated14 > http://code.google.com/p/pharo/issues/detail?id=4884 > > Issue 4882: Keystroke on PluggableListMorph throws an error > http://code.google.com/p/pharo/issues/detail?id=4882 > > Issue 4873: there continue to exist : AnObsoleteSHStyleSetting > http://code.google.com/p/pharo/issues/detail?id=4873 > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 3, 2011

Re: [Pharo-project] 1.3 - thanks, congratulations, etc.

by Marcus Denker

On Oct 3, 2011, at 12:30 AM, Schwab,Wilhelm K wrote: > I just saw the download link for 1.3 on the web site - thanks to all who worked on it. I'll give it a try shortly. > There is one last update coming... we fixed some more bugs and need to sync with latest RB/OB, I hope to do that this week. > Is Hudson (old ci server) doing correct builds into the future, or is the RC/release one-click what we are going to use for 1.3? > In the future, yes. Now: No. Two problems: 1) One Click script needs to be updates to use current VMs 2) The Core has changes to how Shout works without the Full loading the new Shout and OB needed the 2) we need to do ASAP, the 1) we should fix after moving the build to the new Jenkins setup. so much to do, so little time... Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 3, 2011

[Pharo-project] 1.3 - thanks, congratulations, etc.

by Schwab,Wilhelm K

I just saw the download link for 1.3 on the web site - thanks to all who worked on it. I'll give it a try shortly. Is Hudson (old ci server) doing correct builds into the future, or is the RC/release one-click what we are going to use for 1.3? Bill

Oct. 2, 2011

[Pharo-project] [update 1.4] #14185

by Marcus Denker

14185 ----- Issue 4885: With SystemReporter, we do not need a menu entry for GC statistics http://code.google.com/p/pharo/issues/detail?id=4885 Issue 4884: Move deprecated methods to *deprecated14 http://code.google.com/p/pharo/issues/detail?id=4884 Issue 4882: Keystroke on PluggableListMorph throws an error http://code.google.com/p/pharo/issues/detail?id=4882 Issue 4873: there continue to exist : AnObsoleteSHStyleSetting http://code.google.com/p/pharo/issues/detail?id=4873 -- Marcus Denker -- http://marcusdenker.de

Oct. 2, 2011

[Pharo-project] completion appears in the wrong place

by Tudor Girba

Hi, I would like to get my model for a PluggableTextMorph work with ECompletion/OCompletion. To this end, I basically looked around for examples, and found OBTextPanel and its subclasses. So, I basically copied the following methods in my model (GLMSmalltalkCodeModel in the Glamour repo) and things seemed work fine: completionController | controller | controller := self triggerEvent: #getCompletionController. controller ifNil: [controller := self initializeCompletionController]. ^controller initializeCompletionController | controller | controller := self createCompletionController. self when: #getCompletionController evaluate: (MessageSend receiver: controller selector: #yourself). ^ controller createCompletionController ^(ECPreferences useECompletionInsteadOfOCompletion ifFalse: [ OController ] ifTrue: [ ECController ]) model: self Now, the problem is that when the textmorph in which I am rendering this is in a GLMFinder using an implementation similar to the one of OB, and somehow the completion looks to be rendered in absolute coordinates, rather than relative to the window (see the attached screenshots). Any hints regarding what goes wrong? Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Oct. 2, 2011

[Pharo-project] [update 1.4] #14184

by Marcus Denker

14184 ----- Issue 4880: NewTextMorph and TextComposer accepts a one line text http://code.google.com/p/pharo/issues/detail?id=4880 - fix some missing classes (lost due to wrong pacakge when integrating) (SUnit announcements for Natilus, to be merged with existing SUnit Annuncements) -- Marcus Denker -- http://marcusdenker.de

Oct. 2, 2011

Re: [Pharo-project] Does CogDroid work on mobile devices?

by Clara Allende

On 1 October 2011 20:30, Dimitry Golubovsky <golubovsky(a)gmail.com> wrote: > Caludia, > > I looked at the log you sent. > > [2427] after interp_init > [3074] updateDisplay: Display width is 800 (expected 320) > [3074] updateDisplay: Display width is 600 (expected 202) - this is a > typo as I found - this line should say "height" > > says that interpreter was entered, and even tried to update display. > > I don't know what exactly your phone specs are (cannot google this > specific model but Samsung 5500 with other letters mentioned 128 to > 170M RAM). How much RAM does it have? 170 MB > I tried CogDroid on x86-Android > in a VM with 128M RAM. It started, but switching to home screen killed > it (and logcat said the same*, killed because of low memory). Expect > CogDroid to use 50M at minimum. > > So, if you also have some other applications running this may be > simply insufficient memory. > > Most likely... I was suspecting so because of its behavior... So I'll try freeing some memory and see if it works :) Tx a lot! > --------------- > * Of course it is very easy to get root shell and run logcat on x86 > Android since root console is simply there. On my tablet I cannot do > this. > > -- > Dimitry Golubovsky > > Anywhere on the Web > > -- "*Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.*" Linus Torvalds

Oct. 2, 2011