- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3385 in pharo: TextEditor doest not understand #model
by pharo＠googlecode.com Dec. 9, 2010

Dec. 9, 2010

Status: Accepted Owner: guillermopolito New issue 3385 by guillermopolito: TextEditor doest not understand #model http://code.google.com/p/pharo/issues/detail?id=3385 The accessor should be added to load last version of OCompletion in Core 1.2

5 13

[Pharo-project] [ANN 1.2beta] pre-build beta#12272
by Marcus Denker Dec. 9, 2010

Dec. 9, 2010

https://gforge.inria.fr/frs/download.php/28042/PharoCore-1.2beta-12272.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3391 in pharo: BlockClosure>>assertWithDescription: sends #logFailure:
by pharo＠googlecode.com Dec. 9, 2010

Dec. 9, 2010

Status: Accepted Owner: da...@teleport.com New issue 3391 by da...@teleport.com: BlockClosure>>assertWithDescription: sends #logFailure: http://code.google.com/p/pharo/issues/detail?id=3391 In a PharoCore image (Pharo1.1.1 #11414 or Pharo1.2a #12271) the only sender of #assertWithDescription: is RxMatcher>>split: ... which wouldn't be that bad, except that BlockClosure>>assertWithDescription: sends #logFailure: which is only implemented in TestCase .... Soooo, it appears that assertWithDescription: should only be sent from instances of TestCase (and send removed from RxMatcher>>split:) or the send of #logFailure: removed from BlockClosure>>assertWithDescription: ... Found this on in GemStone testing while trying to figure out a test case that would trigger a failure of #assertWithDescription:, which BTW, I couldn't do .... so the #assertWithDescription: is probably unnecessary (or we need a test case to trigger the assertion)...

1 4

[Pharo-project] [update 1.2] #12273
by Marcus Denker Dec. 9, 2010

Dec. 9, 2010

12273 ----- Issue 3388: Fix some red tests in Pharo1. Issue 3385: TextEditor doest not understand #model Issue 3391: BlockClosure>>assertWithDescription: sends #logFailure: -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3388 in pharo: Fix some red tests in Pharo1.2
by pharo＠googlecode.com Dec. 9, 2010

Dec. 9, 2010

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3388 by stephane.ducasse: Fix some red tests in Pharo1.2 http://code.google.com/p/pharo/issues/detail?id=3388 marcus I started to fix some tests. These two ones are ready for inclusion. Attachments: fixingSystemNavigationtests.2.cs 1.3 KB

1 1

[Pharo-project] Morph wont delete in pharo, cant select it...
by Joseph T. Bore Dec. 9, 2010

Dec. 9, 2010

am i doing something obviously wrong?: i have downloaded Pharo 1.1.1 (single click) for Mac OSX bring up the image then: Morph new openInWorld, do it. (get a nice blue square, perfect) click to pick it up and move it around, all is well control click, brings up menu for morph here is where the problems start delete menu option, Blue square wont go away... add halos menu option gives halos but they are on the PasteupMorph (the desktop i think). i cant find any way to get rid of this morph, will i have a blue friend forever? im sure im doing something obviously wrong, just dont know what it is...

8 11

[Pharo-project] Finder issue?
by Francisco Ortiz PeÃ±aloza Dec. 9, 2010

Dec. 9, 2010

Hi, after loading last Shout on PharoCore the new Finder isn't working properly. Let's see PluggableShoutMorph>>initialize registers Shout in AppRegistry as the default MorphicTextEditor but FinderUI>>buildSourceTextArea uses a PluggableTextMorph. I think it should be using the more dinamic *MorphicTextEditor default*insted of the hardcoded PluggableTextMorph. Am i right? Francisco

2 5

[Pharo-project] Issue 3389 in pharo: should add SimpleMorphic in core
by pharo＠googlecode.com Dec. 9, 2010

Dec. 9, 2010

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3389 by stephane.ducasse: should add SimpleMorphic in core http://code.google.com/p/pharo/issues/detail?id=3389 so that it does not rot. Now I pubished it into PharoTaskForces

1 1

Re: [Pharo-project] [ANN] 1.2 Dev Packages are loading :)
by Marcus Denker Dec. 9, 2010

Dec. 9, 2010

On Dec 7, 2010, at 8:42 PM, Guillermo Polito wrote: > Ok, I've done some fixes to OB and OC, and committed them to PharoTaskForces as a temporary solution. > > To load current configuration: > > Gofer it squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > (ConfigurationOfPharo project version: '1.2-beta2') load. > > Can Hudson help us in building Dev images? Yes, will set up a build for 1.2 today. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

6 10

[Pharo-project] Global shortcut keys in Pharo
by Tony Fleig Dec. 9, 2010

Dec. 9, 2010

I find myself wanting global keyboard shortcuts for such things as invoking an external browser, switching focus between windows, opening new tool windows, executing various World menu options, executing my own scripts, etc. After working for years in corporations doing Windows-based development in Microsoft Visual Studio, I find the necessity of constantly reaching for the mouse in Pharo to be cumbersome and unproductive. I was able to add some shortcut keys to invoke commands that I prepared by sending messages like this: World respondToCommand: $l bySending: #startExternalWebBrowser to: TFCommands. However, this only works when no window has the keyboard focus. I followed the keystroke handling path in the debugger and I think I can probably find a place to hook in some special handling for my globally-accessible keystrokes. My questions are: 1. Has somebody already done this? 2. Is there a "standard" or "best practice" way of accomplishing this? Regards, TF

5 9