(Third try.) Can someone answer the questions below the screenshot showing the truncated labels? They are repeated here: 1) Can anyone suggest a fix (a code fix) for the truncated labels shown below in the screenshot of the Setting window? This happens in the Git client too? It happens when a fixed-width font is chosen as the default font. This is a design flaw in the GUIs. Cycling Settings (or any other Windows showing the same truncated-labels problem) isn’t a fix, even if the window renders correctly the second time. The damaged area of the window is still not being invalidated correctly and then redrawn, or it is, and then is partially overdraw by the data fields to the right of the labels. Changing the font to any fixed-width font causes this problem, even without changing the default font size (10). You can see this by expanding all nodes in Settings, and paging down through them. The longest labels will be incompletely rendered. A possible solution is to use a 2-column layout, where the left column displays right-justified labels and the right one displays the matching left-justified data, checkbox, dropdown, etc. The left label-column could be auto-sized on opening after the longest label’s size is determined. I mention this problem many months ago, in the midst of another failed port from VW, and presented the same screenshots. Stef made some comments about how this should not be happening, and seemed to be unhappy with the situation. I thought therefore that there would be some resolve to fix the issue broadly throughout the dev environ, but I don’t know what came of that. I figured the fix was waiting for Spec2, which is now here. Is there a Spec2 expert here who can suggest how to use the new framework to fix the problem? 2) Will all Pharo tools be rewritten in Spec2, and does its formatting scheme solve the label-formatting problem, as font size is changed? 3) Why don’t we opt for easy elastic/zoomable GUIs by implementing Pharo as a web app? Has this been discussed? Willow is looking very good. Is rendering speed still a problem for a complex web GUI served by localhost? For the localhost case, the speed difference seems to be approaching 0. Shaping From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of shaping@uurda.org Sent: Sunday, 19 April, 2020 09:32 To: Pharo Development List <pharo-dev@lists.pharo.org>; pharo-users@lists.pharo.org Subject: Re: [Pharo-users] [Pharo-dev] FW: Label truncation in new Pharo 8.0 64-bit (stable) On 2020-04-19 03:01, Sven Van Caekenberghe wrote: Works for me (this font is larger than the default one). macOS, Pharo 9 64bit The screenshot below is taken on Windows 10 Pro. This time I did not change the theme. I did also update the fonts listed in the dialog before choosing FiraCode. The labels are still truncated. This is another new Pharo 8 64-bit (stable) with only the font changed. Why would formatting not work on Windows 10? Can any Windows 10 Pharo users verify this problem? On 19 Apr 2020, at 06:05, Shaping <shaping@uurda.org <mailto:shaping@uurda.org> > wrote: Can anyone suggest a fix for the truncated labels shown below in the screenshot of the Setting window? This happens in the Git client too. Will Pharo tools be rewritten in Spec2, and does its formatting scheme solve generally the text-formatting problem, as font size is changed? Why don’t we opt for easy elastic rendering of GUIs by implementing Pharo as a web app? Has this been discussed? Willow is looking very good. Shaping From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> ] On Behalf Of Shaping Sent: Saturday, 18 April, 2020 04:16 To: 'Any question about pharo is welcome' <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> >; 'Pharo Development List' <pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: [Pharo-users] Label truncation in new Pharo 8.0 64-bit (stable) Hi everyone. Below is a Pharo 8.0 64-bit (stable) image (installed with the new Launcher 2.0) with two changes: -Light theme selected. -FiraCode 11 chosen as the default font. <image001.png> Truncated labels in the GUI on font change has always been a problem. Am I the only one experiencing this? Shaping From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> ] On Behalf Of Sanjay Minni Sent: Friday, 17 April, 2020 11:05 To: Any question about pharo is welcome <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: Re: [Pharo-users] issues in setting up a new project on Github/Iceberg Thanks tried just https and this worked too I suppose once cloned it does not really matter whether it was done using "clone from github.com" or "clone remote repository" --- Sanjay Minni +91-9900-902902 On Fri, 17 Apr 2020 at 19:43, Guillermo Polito <guillermopolito@gmail.com <mailto:guillermopolito@gmail.com> > wrote: Hi, El 17 abr 2020, a las 15:30, Sanjay Minni <sm@planage.com <mailto:sm@planage.com> > escribió: Hi Guillermo, Ok then given your comments - right now got it working as such - initially created as private in Github - changed to public - created clone from github - (did a repair repository (dont know why) and created "src" and designated it as source folder) - did a commit and push - changed repository back to private seems to work can you give an example on how the "Remote URL" field is to be filled up - note its not taking HTTP as i am not sure about the syntax, assume SSH, Github, MyName, MyRepository, will try that as well you should be able to use the URLs provided by the clone buttons in Github/gitlab/bitbucket, both https and ssh. <image004.png> note Just for Info to other users: I am using Windows 10, it seems to have SSH tools inbuilt and was able to use ssh (with passphrase) without hiccup, by putting my key files path in pharo setting-> ...-> use custom SSH keys, and uploading the .pub key in Github :) Thanks --- Sanjay Minni +91-9900-902902 On Fri, 17 Apr 2020 at 18:36, Guillermo Polito <guillermopolito@gmail.com <mailto:guillermopolito@gmail.com> > wrote: Hi Sanjay, This is a bug in Iceberg github integration that tries to access the repository to get metadata using Github REST API using anonymous access apparently. And since your project is private, this fails. As a workaroung, I suggest you to clone using the last option that requires an url only: <PastedGraphic-3.png> This option will not use the Github API, so you should find no problems. I’m planning doing an Iceberg sprint and fix many issues in the coming weeks. (Also if somebody wants to join, this is an open call :)) Guille El 17 abr 2020, a las 12:49, Sanjay Minni <sm@planage.com <mailto:sm@planage.com> > escribió: Using Pharo 8 64 bit on Windows 10 I am trying to setup a new project on Github using Iceberg following the document "Manage your code with Iceberg dtd 25 March 2019) After creating the project in github when I try to clone from Github as (I am at doc item1.4) The system throws an error and the project does not appear in iceberg although the files are downloaded. This happen in both cases whether I use HTTP or SSH What is going wrong ? also: assuming the clone is made, as per next item in doc 1.5, the directory "src" is created after the clone is made. is that correct ?... then how will the packages sources be mapped to ..\src <http://forum.world.st/file/t368721/1-GettingFirstEmptyProjFromGit.jpg> <http://forum.world.st/file/t368721/0-GithubProjectCreation.jpg> ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html