- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

by Esteban Lorenzano

> On 7 Feb 2017, at 10:57, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > The uperchase character is the symbol on the key. > > In OS X the uppercase characters are used: > http://cdn.osxdaily.com/wp-content/uploads/2011/07/access-library-lion.jpg <http://cdn.osxdaily.com/wp-content/uploads/2011/07/access-library-lion.jpg> > > In Chrome too: > http://addoncrop.com/cdn/2014/12/Google-Chrome-Menu-Settions-option.png <http://addoncrop.com/cdn/2014/12/Google-Chrome-Menu-Settions-option.png> > > On Windows too: > http://www.howtogeek.com/wp-content/uploads/2012/03/650x250xcontext-menu-sh… <http://www.howtogeek.com/wp-content/uploads/2012/03/650x250xcontext-menu-sh…> > > Cheers, > -- Pavel > > 2017-02-06 17:57 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>>: > https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed <https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed> > > The system should display Ctrl + s and not Ctrl + S > > Because people are pressing Shift to get S and this is not working. > We should distinguish between uppercase and lowercase. > The reader cannot guess that S is not the same as s + shift. > There is no way that a user can know that they should NOT press shift when looking at Ctrl + S (because there is no noshiftPressed). > Ctrl + S means press Shift. > key shorcuts are for key, not for character, thatâs why they point to the key in the keyboard. this is the universal standard, so I do not think we need to change it. as Pavel explain, is like that : - on mac: symbols + key - on linux and windows: modifiers + key (e.g. "Shift + S", "Ctrl + Shift + S") cheers, Esteban

Feb. 7, 2017

Re: [Pharo-dev] FileStreams and encoding ( opening a readStream on a FileRerefence)

by Sven Van Caekenberghe

OK, I committed the following in Zn #bleedingEdge: === Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.46 Author: SvenVanCaekenberghe Time: 7 February 2017, 11:07:31.306364 am UUID: a2928299-1dda-4fdf-b15e-e5d7bed2373e Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.45 Add ZnCharacterEncoder class>>#knownEncodingIdentifiers to return the collection of all known encoding identifiers in the system - thx Nicolai Hess for the request Make sure #null is resolved to ZnNullEncoder Add ZnCharacterEncoderTests>>#testKnownEncodingIdentifiers === Name: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.28 Author: SvenVanCaekenberghe Time: 7 February 2017, 11:07:50.782471 am UUID: 938d1683-b8c4-4861-b1e1-f876b57405ef Ancestors: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.27 Add ZnCharacterEncoder class>>#knownEncodingIdentifiers to return the collection of all known encoding identifiers in the system - thx Nicolai Hess for the request Make sure #null is resolved to ZnNullEncoder Add ZnCharacterEncoderTests>>#testKnownEncodingIdentifiers === Thanks again for the feedback, this is a useful addition. > On 6 Feb 2017, at 22:33, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-02-04 13:40 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 4 Feb 2017, at 13:01, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi Nicolai, > > > > The FileSystem API is a bit inconsistent, yes. > > > > This is how you can use it: > > > > (FileLocator temp / 'foo.txt') writeStreamDo: [ :out | > > out binary. > > (ZnCharacterWriteStream on: out encoding: #utf8) << 'Ã©lÃ¨ve' ]. > > > > (FileLocator temp / 'foo.txt') readStreamDo: [ :in | > > in binary. > > ZnCharacterReadStream on: in encoding: #utf8) upToEnd ]. > > > > (FileLocator temp / 'foo.txt') binaryReadStreamDo: [ :in | > > (ZnCharacterReadStream on: in encoding: #utf8) upToEnd ]. > > > > There is no #binaryWriteStreamDo: > > > > The API around File is more correct, IMHO. > > > > Does this help ? > > > > Yes, thanks for the fast response. > > > > What exactly is your question ? > > > > I am looking at the issues with FileList, there are some parts that don't work anymore (see FileList>>#contents, it calls some unimplemted methods), and it uses TextConverter and somoe parts of the older File api. > > It looks like most other (newer) parts are using ZnCharacterReadstream for encoding, but I couldn't find a way to use it together with FileReferences (most parts of the FileList already operate with the newer FileSystem API. > > OK. > > From my standpoint and understanding, I would always use binary streams with explicit Zn converters, this combination is much easier to understand and better implemented with more features. > > If you encounter any problem or have any questions, I will gladly try to help you. > > :-) > Is there a way to list all supported encodings, similar to TextConverter class >> #allEncodingNames ? > I only found > ZnSimplifiedByteEncoder class >> #knownEncodingIdentifiers > and > ZnByteEncoder class >> #knownEncodingIdentifiers > and nothing for all supported utf-8/16 ... encodings. > > nicolai > > > > Sven > > > > > On 4 Feb 2017, at 12:09, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > Hi > > > How can I specify the character encoding when opening a readStream on a FileRerefence. > > > > > > I found this, that works: > > > > > > | readStream fileContent | > > > readStream := (File named: aFileName) openForRead. > > > fileContent := ZnCharacterReadStream on: readStream encoding: encoding. > > > fileContent upToEnd asString. > > > > > > But if I try to do the same with a readStream from a FileReference > > > > > > | readStream fileContent | > > > readStream := aFileName asFileReference readStream. > > > fileContent := ZnCharacterReadStream on: readStream encoding: encoding. > > > fileContent upToEnd asString. > > > > > > I get an error SmallInteger DNU #asciiValue, > > > > > > this is because, in the first method, we create a binary filestream, and if we > > > use readStream from a FileReference, the stream is a MultibyteFileStream. > > > > > > How can I us ZnEncoder for a readstream from a FileReference? > > > > > > (and is it on purpose that both readStream method (openForRead/readStream) > > > return different kinds of binary streams?) > > > > > > > > > nicolai

Feb. 7, 2017

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

by Pavel Krivanek

The uperchase character is the symbol on the key. In OS X the uppercase characters are used: http://cdn.osxdaily.com/wp-content/uploads/2011/07/access-library-lion.jpg In Chrome too: http://addoncrop.com/cdn/2014/12/Google-Chrome-Menu-Settions-option.png On Windows too: http://www.howtogeek.com/wp-content/uploads/2012/03/650x250xcontext-menu-sh… Cheers, -- Pavel 2017-02-06 17:57 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed > > The system should display Ctrl + s and not Ctrl + S > > Because people are pressing Shift to get S and this is not working. > We should distinguish between uppercase and lowercase. > The reader cannot guess that S is not the same as s + shift. > There is no way that a user can know that they should NOT press shift when > looking at Ctrl + S (because there is no noshiftPressed). > Ctrl + S means press Shift. >

Feb. 7, 2017

Re: [Pharo-dev] Debugger hang when step throught

by Denis Kudriashov

2017-02-07 10:30 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > More simple way to reproduce: > > #(2) select: [:i| i] > > > Problem somehow related to mustBeBoolean error. If you try debug > > #(2) select: [:i| i / 0] > > > Debugger will fallback into #/ method at ZeroDivide statement. But with > mustBeBoolean trick it's not work. > I open issue 19662 <https://pharo.fogbugz.com/f/cases/19662/Debugger-step-through-mustBeBoolean…> . Also I found another funny issue. Try debugIt following expression: 1 ifTrue: [2]. You will be wondering that debugger will not able to open.

Feb. 7, 2017

Re: [Pharo-dev] Debugger hang when step throught

by Denis Kudriashov

More simple way to reproduce: #(2) select: [:i| i] Problem somehow related to mustBeBoolean error. If you try debug #(2) select: [:i| i / 0] Debugger will fallback into #/ method at ZeroDivide statement. But with mustBeBoolean trick it's not work. 2017-02-07 8:03 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > tx for the report hilaire. > Indeed I can reproduce your bug > - I pasted it > - I did debug it > over over and through trhough and my system froze. > > On Mon, Feb 6, 2017 at 7:04 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > >> Hello, >> >> The faulty code bellow when debugged and 'step through' cause the >> debugger to hang: >> >> self inform: '1'. >> #(2 3 4) select: [:i| i] thenDo: [:n| self inform: n printString ]. >> self inform: '5'. >> >> It seems trapped in an infinite loop, you can more or less get control >> back with Alt+[.] >> >> >> When step in, the debugger properly report the error. >> >> Pharo #60362. >> >> >> I did not see similar bug report, shall I? >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> >

Feb. 7, 2017

[pharo-project/pharo-core] f197e6: 60376

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f197e65799a3ccc19b3e78e644e89e95b89e7e30 https://github.com/pharo-project/pharo-core/commit/f197e65799a3ccc19b3e78e6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-07 (Tue, 07 Feb 2017) Changed paths: A OpalCompiler-Core.package/IRMethod.class/instance/mapping/sourceNodeExecuted.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60375.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60376.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60375.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60376.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60376 19661 When coding in the debugger I get an error sourceNodeExecuted https://pharo.fogbugz.com/f/cases/19661 http://files.pharo.org/image/60/60376.zip

Feb. 7, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 7, 2017

Re: [Pharo-dev] Segmentation fault while installing Scale

by Guillermo Polito

Hi, We are looking at it with Santi. I see in the log that you're using an ubuntu 12? I tried in a debian jessie and Santi in an ubuntu 14 and we could not reproduce it. Also the travis ci of scale uses ubuntu 12 and the installation works in there... Could you give more details about your system? Thanks, Guille and Santi On Tue, Feb 7, 2017 at 8:43 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hi Andrey, > > Thanks for providing both a way to reproduce and the log so we can have > you machine details. I see that the VM was compiled from build #589 on > jenkins with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end. > > Scale works only on Linux and when I try the wget command from Mac it does > not work so I can't reproduce right now. > > I suggest that for now you try to use one of the newer VMs (from > http://files.pharo.org/vm/pharo-spur32/linux/ , you're > using stable-20160504.zip, pick another one, I suggest a more recent one > than from May last year, either stable-20160623.zip > or pharo-linux-i386itimer-201702061308-aa78f27.zip) and then use the > "classic installation" to be able to use another VM than the one downloaded > by the wget script until someone can have a look into your problem. > > Best, > > Clement > > On Tue, Feb 7, 2017 at 8:00 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> Hi andrey >> >> can you tell us on which OS and version and which VM do you use (there is >> a System report browser where you can find the information. >> >> Tx >> >> >> On Mon, Feb 6, 2017 at 8:20 PM, Andrey Tykhonov <atykhonov(a)gmail.com> >> wrote: >> >>> Hi all! >>> >>> While executing the following command: >>> >>> $ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setup >>> Scale.sh | sudo bash > stderr.log >>> >>> I got the Segmentation fault error. You can see it in the contents of >>> stderr.log which is attached to the email. Here you can see the >>> output of the mentioned command: >>> >>> ``` >>> --2017-02-03 19:35:16-- https://raw.githubusercontent >>> .com/guillep/Scale/master/setupScale.sh >>> Resolving raw.githubusercontent.com... 151.101.128.133, 151.101.192.133, >>> 151.101.64.133, ... >>> Connecting to raw.githubusercontent.com|151.101.128.133|:443... >>> connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: 1021 [text/plain] >>> Saving to: âSTDOUTâ >>> >>> - 100%[========================= >>> ====================================>] 1021 --.-KB/s in 0s >>> >>> 2017-02-03 19:35:16 (274 MB/s) - written to stdout [1021/1021] >>> >>> Cloning into '/tmp/scale'... >>> remote: Counting objects: 1457, done. >>> remote: Total 1457 (delta 0), reused 0 (delta 0), pack-reused 1457 >>> Receiving objects: 100% (1457/1457), 656.60 KiB | 714.00 KiB/s, done. >>> Resolving deltas: 100% (799/799), done. >>> Note: checking out 'f70fdb90cf66d443140b6fe84cad9848163bf32e'. >>> >>> You are in 'detached HEAD' state. You can look around, make experimental >>> changes and commit them, and you can discard any commits you make in this >>> state without impacting any branches by performing another checkout. >>> >>> If you want to create a new branch to retain commits you create, you may >>> do so (now or later) by using -b with the checkout command again. >>> Example: >>> >>> git checkout -b <new-branch-name> >>> >>> --2017-02-03 19:35:18-- http://get.pharo.org/50+vm >>> Resolving get.pharo.org... 128.93.162.72 >>> Connecting to get.pharo.org|128.93.162.72|:80... connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: 2901 (2.8K) [text/html] >>> Saving to: âSTDOUTâ >>> >>> - 100%[========================= >>> ====================================>] 2.83K --.-KB/s in 0.001s >>> >>> 2017-02-03 19:35:18 (3.56 MB/s) - written to stdout [2901/2901] >>> >>> Downloading the latest 50 Image: >>> http://files.pharo.org/get-files/50/pharo.zip >>> Downloading the latest pharoVM: >>> http://files.pharo.org/get-files/50/pharo-linux-stable.zip >>> Downloading PharoV50.sources: >>> http://files.pharo.org/get-files/50/sources.zip >>> Creating starter scripts pharo and pharo-ui >>> >>> Fetched -> BaselineOfScale-SantiagoBragagnolo.4 --- >>> filetree:///tmp/scale/src [:] --- filetree:///tmp/scale/src./pharo: >>> line 11: 19176 Aborted "$DIR"/"pharo-vm/pharo" --nodisplay >>> "$@" >>> Syntax Error on line 26: 'Unmatched '' in string literal. ->' >>> ============================================================= >>> 01: | scapeParentDirectory pharoParentDirectory scaleX scaleuiX | >>> 02: >>> 03: system stdout << 'Uninstalling scale' << String cr. >>> 04: >>> 05: system saveImageAs: #/ asFileReference / #tmp / #'uninstall.image'. >>> 06: " The image must be stored elsewhere for deleting all the files " >>> 07: >>> 08: scaleX := '/usr/local/bin/scale' asFileReference. >>> 09: scaleX exists ifTrue: [ system call: ' rm ', scaleX fullName ]. >>> 10: system stdout << 'Uninstalling executable scale' << String cr ; >>> flush. >>> 11: >>> 12: scaleuiX:='/usr/local/bin/scale-ui' asFileReference. >>> 13: scaleuiX exists ifTrue: [ system call: ' rm ', scaleuiX fullName ]. >>> 14: system stdout << 'Uninstalling executable scale-ui' << String cr ; >>> flush. >>> 15: >>> 16: scapeParentDirectory := '/usr/local/scale' asFileReference. >>> 17: pharoParentDirectory := '/usr/local/pharo' asFileReference. >>> 18: >>> 19: scapeParentDirectory exists ifTrue: [ system call: ' rm -rf ', >>> scapeParentDirectory fullName ]. >>> 20: system stdout << 'Removing scale folder' << String cr ; flush. >>> 21: >>> 22: pharoParentDirectory exists ifTrue: [ system call: ' rm -rf ', >>> pharoParentDirectory fullName ]. >>> 23: system stdout << 'Removing pharo folder' << String cr ; flush. >>> 24: >>> 25: >>> 26: system stdout << 'Done >>> _^_ >>> Syntax Error on line 39: 'Unmatched '' in string literal. ->' >>> ============================================================= >>> 01: | scaleParentDirectory scaleFile scaleUIFile pharoParentDirectory| >>> 02: >>> 03: " DEPLOY " >>> 04: system stdout << 'Deploying scale command';cr. >>> 05: >>> 06: scaleParentDirectory := '/usr/local/scale' asFileReference. >>> 07: >>> 08: scaleParentDirectory exists >>> 09: ifTrue: [ >>> 10: system stderr << 'There is already an installation. Please >>> uninstall before' >>> 11: ] ifFalse: [ >>> 12: scaleParentDirectory ensureCreateDirectory. >>> 13: scaleFile := scaleParentDirectory / 'scale'. >>> 14: scaleUIFile := scaleParentDirectory / 'scale-ui'. >>> 15: system workingDirectory / '..' / 'scale' copyTo: scaleFile. >>> 16: system workingDirectory / '..' / 'scale-ui' copyTo: scaleUIFile. >>> 17: system workingDirectory / '..' / #build / 'uninstall.st' copyTo: >>> scaleParentDirectory / 'uninstall.st'. >>> 18: system stdout << 'Deploying Pharo';cr. >>> 19: >>> 20: pharoParentDirectory := '/usr/local/pharo' asFileReference. >>> 21: pharoParentDirectory ensureCreateDirectory. >>> 22: #( 'pharo' 'pharo-vm' 'pharo-ui') >>> 23: do: [ :file | system workingDirectory / file copyAllTo: >>> pharoParentDirectory / file ]. >>> 24: >>> 25: #( 'Pharo.image' 'Pharo.changes') >>> 26: do: [ :file | system workingDirectory / file copyAllTo: >>> scaleParentDirectory / file ]. >>> 27: >>> 28: >>> 29: system stdout << 'Giving permissions to run';cr. >>> 30: >>> 31: system call: 'chmod +x ', (pharoParentDirectory / 'pharo') >>> fullName. >>> 32: system call: 'chmod +x ', (pharoParentDirectory / 'pharo-ui') >>> fullName. >>> 33: system call: 'chmod +x ', (pharoParentDirectory / >>> 'pharo-vm/pharo') fullName. >>> 34: system call: 'chmod +x ', (scaleParentDirectory / 'uninstall.st') >>> fullName. >>> 35: system call: 'chmod +x ', scaleFile fullName. >>> 36: system call: 'chmod +x ', scaleUIFile fullName. >>> 37: system ln: scaleFile to: '/usr/local/bin/scale' asFileReference. >>> 38: system ln: scaleUIFile to: '/usr/local/bin/scale-ui' >>> asFileReference. >>> 39: system stdout << 'Done >>> _^_ >>> ``` >>> >>> Could you please help me find a workaround in order to bypass this issue? >>> >>> Thank you in advance! >>> >>> -- >>> Andriy >>> >>> >>> >> >

Feb. 7, 2017

Re: [Pharo-dev] [QA] Debugger buttons explained

by Thierry Goubier

Hi Hilaire, I find your use case interesting. It used to be the case, that one could discover an application commands by exploring the objects making up the GUI... Now, with Spec or Glamour, is that still the case? It seems not any more. Doru, can you confirm? Regards, Thierry 2017-02-06 21:48 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > Ok, give a look to SpecDebugActionButton, this class has no user, only > progma reference, not easy to track the logic. > > Never mind I test on a halt in its #update method. Nothing happen when > opening the debugger. May be there is instance in memory, no idea under > which name it is referenced, may be not. > > Inspecting the debugger window does not help, it is a kind of generic > morph. > > Never mind, can try to look at the menu item "Debug it" in the > playground window, I used to find the action there. Oops, get lost > there, I see #debugSelection looks promising, see announcement. Get lost > again. > > No idea, someone else should put these tooltips in the appropriate place. > > > > Le 06/02/2017 Ã 21:14, Hilaire a Ã©crit : > > No user of actionType, but I guess user or pragma, how do you guys track > > the logic from here > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 7, 2017

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

by denker

> On 7 Feb 2017, at 08:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > No it is important. > There is no point to have a supercool system that looks so bad and turn people off. > But I do not get it your 13136 was integrated. > > No, this is exactly an example of this âeven the tiniest most obvious thing needs workâ. The slice was done for an older version, nobody cared to update it for the current development version, in the end the issue was closed as *nobody* cared to put 5 minutes inâ¦ There is no magic. "This issue is about Pharo3, with Pharo4 already released and Pharo5 under development, the changes can not be merged due to too many changes in the touched code. Please check Pharo5 and, if this change is still needed, resubmit a new slice. I will close this issue as "Stale (timeout)â.â Marcus

Feb. 7, 2017