- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Alexandre Bergel

Hi! Thanks Kilon for working on the Contr-l key binding. I use this control key binding a lot, and actually, it is really rare when I do a mistake. Having to press OK whenever I do this sounds like a regression to me. Why not always inserting the text in the undo queue before replacing the text? Alexandre > Le 13-10-2013 Ã 8:08, kilon <thekilon(a)yahoo.co.uk> a Ã©crit : > > This is my first pharo bug fix so be gentle :D > > https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-w… > <https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-w…> > > As I explain in the link and in my commit log , I have added a confirm > dialog so the user in case he accidentally pressed CMD+L will click no and > his changes will not be lost. I have verified the bug fix with the latest > pharo build. > > > > -- > View this message in context: http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 14, 2013

Re: [Pharo-dev] when I dropped a CS on pharo 30 I get

by kilon

Thanks for the explanation. I was aware of change sets, I have read about them in PBE though never used them myself. Looks like a interesting concept will take a deeper look later on :) Marcus Denker-4 wrote > On Oct 14, 2013, at 12:25 PM, kilon < > thekilon@.co > > wrote: > >> What is a "CS" ? >> > > changeset. > > There is a subsystem that record all changed method, allows you to sort > them in groups > and "file out" sets of those changes in .cs files. > This was how people worked together in th past, today it is still useful > for deep crosscutting > changes (as you can hand-order the .cs text file if needed) > > Marcus > > > signature.asc (210 bytes) > <http://forum.world.st/attachment/4714291/0/signature.asc> -- View this message in context: http://forum.world.st/when-I-dropped-a-CS-on-pharo-30-I-get-tp4714191p47143… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

Re: [Pharo-dev] Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows

by Goubier Thierry

I have the same bug on Pharo 3.0 on Ubuntu 13.10 64bits. Changed the font, and then all text with an utf8 character got this MNU (but on LogicalFont). Unable to change it back: the font dialog is now showing only one font instead of the 50+ the system has. Thierry Le 14/10/2013 11:22, kilon a Ã©crit : > Windows build is broken to the degree of becoming completely unusable . > Trying to type in any tool, workspace , system browser etc. it displays the > Red Box with the yellow X displaying MNU: FixedFaceFont >> glyphInforOf: > into: > > Went into settings, to change the standard font in case its a font problem. > It could not find my system fonts but it so I choose the one that was > available with force all. Did not solve the problem. > > That means I can't input code in any way. > > Question : why such fundamental and very easy to find out problem went into > the build process ? Are you not checking the build on win / mac and linux > before committing it ? I know Pharo 3.0 is alpha and I most certainly > expect to find a fair share of bugs in it. But this is just to obvious and > easily avoided. Am I missing something here ? > > > > -- > View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-lat… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 14, 2013

Re: [Pharo-dev] when I dropped a CS on pharo 30 I get

by Marcus Denker

On Oct 14, 2013, at 12:25 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > What is a "CS" ? > changeset. There is a subsystem that record all changed method, allows you to sort them in groups and "file out" sets of those changes in .cs files. This was how people worked together in th past, today it is still useful for deep crosscutting changes (as you can hand-order the .cs text file if needed) Marcus

Oct. 14, 2013

Re: [Pharo-dev] when I dropped a CS on pharo 30 I get

by kilon

What is a "CS" ? -- View this message in context: http://forum.world.st/when-I-dropped-a-CS-on-pharo-30-I-get-tp4714191p47142… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

Re: [Pharo-dev] Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows

by kilon

fair enough , I will be testing latest builds in all 3 OSes from now on. So consider me as your "happy to test" bot for now on Writing UI tests sounds reasonable to me. Sure will give it a try . Will also take a look at CI. Camillo Bruni-3 wrote >>> Question : why such fundamental and very easy to find out problem went >>> into the build process ? Are you not checking the build on win / mac and >>> linux before committing it ? I know Pharo 3.0 is alpha and I most >>> certainly expect to find a fair share of bugs in it. But this is just to >>> obvious and easily avoided. Am I missing something here ? > > Because nobody on windows reviewed the slice. > > Your issue is not that easy to detect automatically, and testing a slice > under > 3 platform manually is just overkill... > > So If you want to contribute, write some UI tests ;) and help fixing the > CI > project: http://smalltalkhub.com/#!/~Pharo/ci > > You found the bug, that's what counts. > > > signature.asc (457 bytes) > <http://forum.world.st/attachment/4714286/0/signature.asc> -- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-lat… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

Re: [Pharo-dev] Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows

by Camillo Bruni

>> Question : why such fundamental and very easy to find out problem went >> into the build process ? Are you not checking the build on win / mac and >> linux before committing it ? I know Pharo 3.0 is alpha and I most >> certainly expect to find a fair share of bugs in it. But this is just to >> obvious and easily avoided. Am I missing something here ? Because nobody on windows reviewed the slice. Your issue is not that easy to detect automatically, and testing a slice under 3 platform manually is just overkill... So If you want to contribute, write some UI tests ;) and help fixing the CI project: http://smalltalkhub.com/#!/~Pharo/ci You found the bug, that's what counts.

Oct. 14, 2013

Re: [Pharo-dev] Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows

by kilon

I can't reproduce the problem on Ubuntu. Works fine on my Ubuntu amd64 13.04. Can someone else confirm the problem on Windows ? I use Windows 7 64 bit. kilon wrote > Windows build is broken to the degree of becoming completely unusable . > Trying to type in any tool, workspace , system browser etc. it displays > the Red Box with the yellow X displaying MNU: FixedFaceFont >> > glyphInforOf: into: > > Went into settings, to change the standard font in case its a font > problem. It could not find my system fonts but it so I choose the one that > was available with force all. Did not solve the problem. > > That means I can't input code in any way. > > Question : why such fundamental and very easy to find out problem went > into the build process ? Are you not checking the build on win / mac and > linux before committing it ? I know Pharo 3.0 is alpha and I most > certainly expect to find a fair share of bugs in it. But this is just to > obvious and easily avoided. Am I missing something here ? -- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-lat… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows

by kilon

Windows build is broken to the degree of becoming completely unusable . Trying to type in any tool, workspace , system browser etc. it displays the Red Box with the yellow X displaying MNU: FixedFaceFont >> glyphInforOf: into: Went into settings, to change the standard font in case its a font problem. It could not find my system fonts but it so I choose the one that was available with force all. Did not solve the problem. That means I can't input code in any way. Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ? -- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-lat… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 14, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30480 Home: https://github.com/pharo-project/pharo-core

Oct. 14, 2013