July 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Freezing Bloc UI

by Alain Plantec

Hello, Thanks for experimenting Bloc!!!. I think that, In this case, this is the font chooser that freezes, not Bloc. You can always come back to Morphic with CMD+Backspace. Then remove the freeze block space, create a new bloc space and switch to it. I guess it is because current standard fonts are strike fonts. Try by selecting source code fonts first, as a consequence default fonts are set to FT fonts. Then open the font chooser. it should be ok. Because of Athens and of TxText, no effort was made to make strike font usable with Bloc. Now, I donât know exactly why the font choose behaves like that. Cheers Alain > On 05 Jul 2015, at 12:37, stepharo <stepharo(a)free.fr> wrote: > > thanks for looking at it. > Bloc needs feedback > > > Le 5/7/15 12:16, Peter UhnÃ¡k a Ã©crit : >> Hi, >> >> when reloading FreeType (Settings > Use free type:) >> >> and then trying to change the font (Standard Fonts >> default) >> some inputs are not drawn and the UI freezes completely. >> >> <Mail Attachment.png> >> >> Interestingly if I press alt+<dot> the UI doesn't respond, but the Image clearly does because there is output in the command line: >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> âUser Interrupt >> [ delaySemaphore wait ] in Delay>>wait in Block: [ delaySemaphore wait ] >> BlockClosure>>ifCurtailed: >> Delay>>wait >> BlMainLoopManager>>interCyclePause: >> BlMainLoopManager>>doOneCycle >> [ >> self doOneCycle. >> Processor yield ] in [ >> [ >> self doOneCycle. >> Processor yield ] repeat ] in BlMainLoopManager>>loop in Block: [ ... >> BlockClosure>>repeat >> [ >> [ >> self doOneCycle. >> Processor yield ] repeat ] in BlMainLoopManager>>loop in Block: [ ... >> [ >> self value. >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ ... >> >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> Peter >

July 5, 2015

Re: [Pharo-dev] Halt in startup?

by Ferlicot D. Cyril

Le 05/07/2015 12:44, stepharo a Ã©crit : > thank cyril > I saw that and I have not idea why one I execute this example3 method > now I get the startup of fresh image. > I would really like to get startUppreference to be loaded on demand. > > Stef > +1 for this. Sometimes I want an image without startup preferences when I have to take some screen for example without the dark theme. I know there is a way to disable the startup preference with command lines, we do it with one of the Pillar's build but we should not have to do that. ./pharo Pharo.image eval --save "StartupPreferencesLoader allowStartupScript: false."

July 5, 2015

Re: [Pharo-dev] having stupid and destructive example should be banned from the system

by Peter UhnÃ¡k

Or rename it to "exampleImageDestruction" ? On Sun, Jul 5, 2015 at 3:19 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > Le 05/07/2015 14:06, stepharo a Ã©crit : > > example3 > > " it's my personal script provided as example" > > "self example3" > > | items | > > items := OrderedCollection new. > > items add: (StartupAction name: 'Self halt' code: [ self halt ]). > > "replace it by your name" > > items add: (StartupAction name: 'WS' code: [ Workspace open ]). > > "replace it by your name" > > StartupPreferencesLoader default > > addAtStartupInPreferenceVersionFolder: items named: 'author.st'. > > > > StartupPreferencesLoader default loadFromDefaultLocations. > > > > Once we execute this.... no image are working anymore! > > > > https://pharo.fogbugz.com/default.asp?15899 > > > > > +1 > There is so many better examples that doesn't destroy your image without > warning. > >

July 5, 2015

Re: [Pharo-dev] having stupid and destructive example should be banned from the system

by Ferlicot D. Cyril

Le 05/07/2015 14:06, stepharo a Ã©crit : > example3 > " it's my personal script provided as example" > "self example3" > | items | > items := OrderedCollection new. > items add: (StartupAction name: 'Self halt' code: [ self halt ]). > "replace it by your name" > items add: (StartupAction name: 'WS' code: [ Workspace open ]). > "replace it by your name" > StartupPreferencesLoader default > addAtStartupInPreferenceVersionFolder: items named: 'author.st'. > > StartupPreferencesLoader default loadFromDefaultLocations. > > Once we execute this.... no image are working anymore! > > https://pharo.fogbugz.com/default.asp?15899 > +1 There is so many better examples that doesn't destroy your image without warning.

July 5, 2015

Re: [Pharo-dev] having stupid and destructive example should be banned from the system

by Tudor Girba

Yes, they should be :) Doru On Sun, Jul 5, 2015 at 2:06 PM, stepharo <stepharo(a)free.fr> wrote: > example3 > " it's my personal script provided as example" > "self example3" > | items | > items := OrderedCollection new. > items add: (StartupAction name: 'Self halt' code: [ self halt ]). > "replace it by your name" > items add: (StartupAction name: 'WS' code: [ Workspace open ]). > "replace it by your name" > StartupPreferencesLoader default > addAtStartupInPreferenceVersionFolder: items named: 'author.st'. > > StartupPreferencesLoader default loadFromDefaultLocations. > > Once we execute this.... no image are working anymore! > > https://pharo.fogbugz.com/default.asp?15899 > > -- www.tudorgirba.com "Every thing has its own flow"

July 5, 2015

having stupid and destructive example should be banned from the system

by stepharo

example3 " it's my personal script provided as example" "self example3" | items | items := OrderedCollection new. items add: (StartupAction name: 'Self halt' code: [ self halt ]). "replace it by your name" items add: (StartupAction name: 'WS' code: [ Workspace open ]). "replace it by your name" StartupPreferencesLoader default addAtStartupInPreferenceVersionFolder: items named: 'author.st'. StartupPreferencesLoader default loadFromDefaultLocations. Once we execute this.... no image are working anymore! https://pharo.fogbugz.com/default.asp?15899

July 5, 2015

Re: [Pharo-dev] Playground shift yellow menu throws MNU

by Tudor Girba

That's a bug. This support should be removed. Doru On Sun, Jul 5, 2015 at 1:26 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > TextModel allows for right (yellow) click menu with shift which gives > another menu. > Now Playground (which uses Rubric) throws > GLMRubricSmalltalkTextModel(Object)>>doesNotUnderstand: #shiftMenu. > (called from RubEditingArea>>lookupShiftMenu) > > I would expect either adding new shifted menu, or disabling this feature. > > Peter > -- www.tudorgirba.com "Every thing has its own flow"

July 5, 2015

Playground shift yellow menu throws MNU

by Peter UhnÃ¡k

Hi, TextModel allows for right (yellow) click menu with shift which gives another menu. Now Playground (which uses Rubric) throws GLMRubricSmalltalkTextModel(Object)>>doesNotUnderstand: #shiftMenu. (called from RubEditingArea>>lookupShiftMenu) I would expect either adding new shifted menu, or disabling this feature. Peter

July 5, 2015

Re: [Pharo-dev] Make TextModel by default for text, not code

by Peter UhnÃ¡k

> > The cleaner way would be to use TextEditor as default EditorClass in > TextModel "beForText" and SmalltalkEditor for "beForCode". > With that, the menublock coude ask the editor class for the default menu > (now it uses SmalltalkEditors menu as default) > That would work only if the TextModel would always have some EditorClass; so if you wanted your custom menu you would have to create a new EditorClass object. While this in principle is ok, Spec already has block-based API so I would stick to it.

July 5, 2015

Re: [Pharo-dev] Make TextModel by default for text, not code

by Nicolai Hess

2015-07-05 11:46 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > I was looking at > https://pharo.fogbugz.com/f/cases/edit/15237/Spec-TextModel-for-plain-text > and it seems that we have (at least ) three different menus. > > TextEditor class>>yellowButtonMenu (TextModel for editing text) > > â > âSmalltalkEditor class>>yellowButtonMenu (default TextModel, for code) > > â > RubSmalltalkCodeMode class>>menuOn: (Playground) > > â > Since we have already disabled code completion in TextModel some time ago > I would propose to set TextEditor's menu by default, and have the Code one > only explicitly (through #beForCode which would also enable the default > codeCompletion). > > Shortcuts interestingly work even without the menu, so it shouldn't break > people's workflow (e.g. you could still inspect things and so forth). > The cleaner way would be to use TextEditor as default EditorClass in TextModel "beForText" and SmalltalkEditor for "beForCode". With that, the menublock coude ask the editor class for the default menu (now it uses SmalltalkEditors menu as default) > > Anyone has any objections? > > Peter > > > >

July 5, 2015