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

Re: [Pharo-dev] Release with Dark Theme

by stepharo

+1000000000 Le 24/4/15 12:15, Marcus Denker a Ã©crit : >> The short term real life goals are: >> >> - unify keyboard shortcuts. >> - improve event handling so that the use of a magic mouse does not produce dozens of events that make the UI go crazy >> > Yes! > > Marcus > > >

April 24, 2015

Re: [Pharo-dev] Small ScreenTheme [was: Release with Dark Theme]

by stepharo

+ 1 >> In a related domain, I am launching a petition for a SmallScreenTheme > > and a large screen one too. 24 or 40" UHD has lots of empty space, and > default browser sizes are too small > > The first thing to do is to make sure we don't create more legacy code > with hardcoded sizes for fonts, borders, margins, padding. > > Stephan > > > >

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by stepharo

Le 24/4/15 11:06, phil(a)highoctane.be a Ã©crit : > > > On Fri, Apr 24, 2015 at 9:45 AM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > That's a bit harsh, the fonts are the same ;-) > And it is of course possible that you don't like it, it is a > matter of taste. > The contrast thing is also taste, but for some people it solve > certain vision problems. > > Exactly. > When you have floaters all day long, the last thing you want is a > f*cking white screen. > > Now, I am using 3.0 with DawnTheme, which is more like SublimeText (in > a 3.0). > > I tried the 4.0 and it is nice. Now, icons should get a pass because > the artefacts on the edges are not nice. > > If there is some little petty cash available, that's the kind of job > that can be done supercheap on something like > https://en.99designs.be/. That would be good use of > consortium/association money for example. > > Why bother with graphics work when you can get things done > professionaly for close to nil? do you know the people? Because I would really be in favor getting people doing this job. > > Phil > > > > > > On 24 Apr 2015, at 09:27, Norbert Hartl <norbert(a)hartl.name > <mailto:norbert@hartl.name>> wrote: > > > > That's funny because I tried it two days ago the first time and > I didn't like it. I had troubles to get anything but bitmap fonts. > After setting all things up I was a bit disappointed that contrast > wise it doesn't work for me. Can someone send a screenshot with > one setup that he/she considers good? > > > > thanks, > > > > Norbert > > > >> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano > <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> > >> I disagreeâ¦ DarkTheme is just for certain tastes, while regular > one, while probably dated, is more âstandardâ. > >> Also, DarkTheme is not ready. yeah, yeahâ¦ it works and works > fine most of the timeâ¦ but not *all* the time (take for example > find string dialogâ¦ I never found the time to fix it, and nobody > complained soâ¦ :P). Finally. we need to adopt SVG icons (in my > TODO list since a couple of months, I will deliver soon, I hope), > otherwise they do not look good (this is a problem eclipse itself > had itâ¦ we are just inheriting it :) ) > >> > >> But a good question would be: How can we push forward our UI, > besides using a darker or clearer theme? > >> I would like to hear some opinions here :) > >> > >> Esteban > >> > >> > >>> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > >>> > >>> comments about color is to be taken with care. > >>> > >>> > >>> Le 24/4/15 02:48, Sean P. DeNigris a Ã©crit : > >>>> Why didn't/don't we make it the default for 4.0? Everyone > seems to love it, > >>>> and people are commenting that the UI looks dated. > >>>> > >>>> > >>>> > >>>> ----- > >>>> Cheers, > >>>> Sean > >>>> -- > >>>> View this message in context: > http://forum.world.st/Release-with-Dark-Theme-tp4821496.html > >>>> Sent from the Pharo Smalltalk Developers mailing list archive > at Nabble.com. > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > > > >

April 24, 2015

Re: [Pharo-dev] TDD and BDD

by stepharo

Le 24/4/15 12:26, Christophe Demarey a Ã©crit : > Le 22 avr. 2015 Ã 20:19, stepharo a Ã©crit : > >> Christophe >> >> I do not have the answer just the constraints. >> This is hyper important that the solution does not change much SUnit. >> This way we do not end up with a mess with Sunit version. >> >> It is better to have a separate package. > I ckecked and we already diverged a lot from the SUnit standard (use of Traits, announcements, etc.). > Do you want I integrate the refactoring to have the test selectors selection coherent? > If yes, my proposal just adds 'or: [ selector name beginsWith: 'should' ]. I do not see the point of having a separate package. > If no, does it mean that we should never touch the SUnit package? No this is just that for now we do not express dependencies to a Sunit package number :) but when we will start to do it, it may be more complex. I got some problems with SUnit and SUnitToo in VW. Not fun.

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by Thierry Goubier

Le 24/04/2015 13:40, Christophe Demarey a Ã©crit : > > Le 24 avr. 2015 Ã 13:15, Sean P. DeNigris a Ã©crit : > >> philippeback wrote >>> We'd be having package level comments, that would be another story. >> >> Now that we have real package objects, is there anything that prevents it? I >> also wanted this for a loooong time... >> > > We can already add a description in the PackageManifest but the tooling support is missing. > It would be nice to have that appear as a Readme.md at the package level in the filetree format, like classes comment are transcribed. By the way, we have a Pillar to md step. Would we have a md to Pillar converter somewhere? Thierry

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by Christophe Demarey

Le 24 avr. 2015 Ã 13:15, Sean P. DeNigris a Ã©crit : > philippeback wrote >> We'd be having package level comments, that would be another story. > > Now that we have real package objects, is there anything that prevents it? I > also wanted this for a loooong time... > We can already add a description in the PackageManifest but the tooling support is missing.

April 24, 2015

Pharo on Centos/RHEL/ 7.1

by nacho

Hi, I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned. Here is the list of the libs needed. May be it would be a good idea to put it there in the page, somewhere. Or at least inside the README.txt that comes in the zip. I would append something like: "As the Pharo virtual machine is still 32bits you will need some 32bit libraries. You can get them by executing the following command as root: sudo yum install alsa-lib.i686 glibc-devel.i686 mesa-libGLU.i686 libICE-devel.i686 libSM-devel.i686 freetype.i686 And after that Pharo should run perfectly." Cheers Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 24, 2015

Re: [Pharo-dev] RPackage: 'accessing' vs 'all accessing' Protocol

by Sean P. DeNigris

stepharo wrote > a mistake to me. No problem. I just didn't want to change it in case it was something special... ----- Cheers, Sean -- View this message in context: http://forum.world.st/RPackage-accessing-vs-all-accessing-Protocol-tp482146… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by Sean P. DeNigris

philippeback wrote > We'd be having package level comments, that would be another story. Now that we have real package objects, is there anything that prevents it? I also wanted this for a loooong time... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Updated-WebDoc-tp4821426p4821598.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 24, 2015

Re: [Pharo-dev] Release with Dark Theme

by phil＠highoctane.be

On Fri, Apr 24, 2015 at 12:45 PM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Le 24/04/2015 12:21, phil(a)highoctane.be a Ã©crit : > >> >> >> On Fri, Apr 24, 2015 at 10:48 AM, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 24/04/2015 10:11, phil(a)highoctane.be <mailto:phil@highoctane.be> >> a Ã©crit : >> >> >> >> On Fri, Apr 24, 2015 at 8:38 AM, Esteban Lorenzano >> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com> >> <mailto:estebanlm@gmail.com <mailto:estebanlm@gmail.com>>> wrote: >> >> I disagreeâ¦ DarkTheme is just for certain tastes, while >> regular one, >> while probably dated, is more âstandardâ. >> Also, DarkTheme is not ready. yeah, yeahâ¦ it works and >> works fine >> most of the timeâ¦ but not *all* the time (take for example >> find >> string dialogâ¦ I never found the time to fix it, and nobody >> complained soâ¦ :P). Finally. we need to adopt SVG icons (in >> my TODO >> list since a couple of months, I will deliver soon, I hope), >> otherwise they do not look good (this is a problem eclipse >> itself >> had itâ¦ we are just inheriting it :) ) >> >> But a good question would be: How can we push forward our UI, >> besides using a darker or clearer theme? >> I would like to hear some opinions here :) >> >> >> >> I'd like to have some solution for that "windows popping up >> everywhere" >> thing. AltBrowser has some good ideas. >> >> In fact I'd like to have AltBrowser and Nautilus together (as in >> additional entries in the "Browse", "Browse Scoped", ..."Alt >> Browse", >> "Alt Browse Scoped") >> >> Also, having a way to see a class with all the methods in a long >> pane. >> Yeah, Smalltalk is all about short methods but it is hard to >> explain >> things to people when looking at a ravioli at a time. >> >> >> Like the Newspeak browser? >> >> >> Don't know about that one. >> > > http://bracha.org/hopscotch-wasdett.pdf > > Look for the IDE description (i.e. Figure 1). A web browser metaphor, > where you can open all elements and edit in place; not that different from > what it could be in Self. > > I believe it's not as efficient in practice as it could be, for editing > code. But for overall viewing, could be very effective. > > I toyed with multiple selection in the AltBrowser (i.e. opening multiple > edit panes on the right) but never went that way. Maybe merging both could > be an idea: Newspeak browser + tree navigation on the left :) > yes, that's more fiiting what I have in mind. > > >> >> Navigating hierarchies should be made easier (switching on the >> "hier/flat" button gets tiring). >> >> >> This one is difficult to solve. >> >> >> Maybe a popup with the hierarchy would do (with some keybinding, like C-h) >> > > In AltBrowser, I'm searching around how to do that, so what I have is: > > - menu navigation commands (super, first subclass, sibling) with a memory > (back), but I'm not satisfied because often what I want is see both at the > same time. Back really works well, but maybe with a button on the toolbar > (or linked to the back and forward keys on my Chromebook? Not used to that > keyboard layout yet) > > - What I use most often is: right click on superclass name in the > description, choose browse to open a browser on the superclass... Not too > bad for what I want. Works for any class name everywhere, which is very > convenient. > > - I also have a hierarchy command which opens a browser scoped on the > hierarchy. For certain types of searches, it can be very convenient (i.e. > all callers of printString in the hierarchy...) > > But, still: three ways to do the same thing? Clearly could be better. > > Thierry > > >> I need to see how spotter will make this easier anyway. Still >> not using >> it, need to bring all my code to 4.0 before. >> >> >> I'm a bit: Spotter is an external tool to the browser. If my >> searches are well answered in the browser, I'll prefer to avoid >> switching back and forth between two GUIs. >> >> It would be nice to have a closer integration between Browser and >> Spotter. When looking at methods, Spotter and AltBrowser show a very >> similar GUI: context tree on the left (i.e. where is the element in >> the overall scheme), element/work pane on the right. Like all the >> tree-based browsers have done in the past, really (the Star browser, >> the Whisker browser). >> >> Which makes Spotter a kind of reimplementation of a tree browser >> with object-driven representations on the right... was that a >> project by Alain Plantec in the Squeak days? >> >> Thierry >> >> Phil >> >> >> >> >> >> >> >> >> > >

April 24, 2015