November 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Pharo 5 and retina displays in 2016?

by Tim Mackinnon

Adding this to the Dev user group - is there really no solution for this? I read a few old messages from 2012 about different fonts but nothing seemed to work from what I could see. Has everyone just been putting up with the fuzziness and got used to it? As a new Retina display user, I love the clarity in other apps and find it quite jarring in Pharo. I was going to do a brown bag session on Smalltalk with the current team Iâm working with, however as they all have retina Macs, I think I may reconsider this as unless you love the language its another thing for people to throw stones at. As Stephan mentions below, were Tobiasâ changes not viable? Is there anything we can do to help get them safely in - or can I try it on an experimental branch? Tim > On 29 Nov 2016, at 21:02, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 29/11/16 00:34, Tim Mackinnon wrote: >> Or is this still the same issue thatâs been hanging around for a long >> time as its hard to easily fix? > > Tobias Pape wrote some vm changes that solved the problem this summer, and they somehow interfered, so were reverted. I posted some pictures > on twitter 10/11-7 of it working with both Pharo & Squeak. > > Stephan > > > >> Hi Guys - its been a while since Iâve had a chance to get back into some coding in Smalltalk, and took the plunge again with a new laptop and Pharo 5, however the screen is really blurry? >> >> Doing a google search, I can see this same question raised back in 2012, but has there been no progress in this intervening years or has a workaround not been documented for google to find? Or has everyone just got used to it, and I need to hand in there... >> >> I have tried using a different font - but not sure what constitutes a true-type font (are these the same as free-type mentioned in the Settings Browser?). Has anyone found a font that makes everything look crisp (I tried Helvetica but its only marginally better). >> >> Or is this still the same issue thatâs been hanging around for a long time as its hard to easily fix? >> >> Tim

Nov. 30, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Glenn CavarlÃ©

Hi, Interessting, i did not know that Bloc was available in Pharo-Launcher... The CI job from ci.inria.fr is not fully working in the sense that it does not install Moz2D plugin, only sources are loaded in order to run tests. This means that, even if you download image+vm from jenkins, it will not work. We need new dependencies on the jenkins slave but it was so complicated to just make the new slave working (3 weeks), that i postpone the installation of new other dependencies for the moment (planned for 2017). "User" and "Dev" versions are maybe confusing names. We can change them with for instance "Default" and "Contribution"... Do you have a proposal to make them clearer ? > The vm is a recent download from get.pharo.org/vm50 Compatibility with 50 image+vm is not ensured, Bloc is currently developed using http://get.pharo.org/vm60. If you face some issues again, please take a look at: https://github.com/pharo-graphics/Bloc/blob/master/INSTALL.md https://github.com/pharo-graphics/Bloc/blob/master/CONTRIBUTING.md and report us anything confusing. Thanks @Denis and @Sean for your interest in Bloc, Regards, Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Bloc-Problems-Running-tp4924930p4925241.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 30, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Sean P. DeNigris

Sean P. DeNigris wrote > What would it take to add the various setups to the CI matrix? This > complexity will be a high barrier to feedback... In fact, if the current artifacts are unusable, it would probably be better to disable them, like Esteban did for the 5.0 VM job... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Problems-Running-tp4924930p4925230.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 30, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Nicolas Passerini

2016-11-29 13:08 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > And my problem was related to feature/issue of Iceberg to require github > keys. This is interesting for my, which operation did demand for your github keys? I mean, were keys need for that operation or did Iceberg ask you for keys before they are needed?

Nov. 29, 2016

Re: [Pharo-dev] How to report website text bugs?

by stepharo

On Tue, 29 Nov 2016 00:57:36 +0100, Tim Mackinnon <tim(a)testit.works> wrote: > Hi Guys - how is the best way to report website and text bugs? > > As I know the English is not always a first language (and you guys are > busy writing code anyway) - its up to us native English speakers >to > chip in where we can. Thank you for this take :) > I was pleased to get the notice that on OSX Sierra I need to do > something extra to get Pharo to work, however the text could be slightly > >corrected eg. (Bolded words changed) > > Are you using macOS Sierra? > Due to changes in security policies of macOS, you will need to put the > VM in the /Applications folder. > We are working to fix this temporary inconvenience. > > > Also - the Hello world command line example on the front page doesnât > work on a standard Terminal on a Mac (you get an error: > > $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" > -bash: !'": event not found > >> The culprit is of course the â!â Character so a better example might be: > >>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" > Hello WorldStdioStream: 'stdout' > > Although, in this case, is it expected that the return string is merged > with some other output text >(e.g. the StdioStream:â¦.?). I think its an > impressive example, but it just doesnât quite look right? > > > Tim -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by stepharo

On Tue, 29 Nov 2016 10:46:09 +0100, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >> Called by the table view to return the data object associated with the >> specified row and column. > https://developer.apple.com/reference/appkit/nstableviewdatasource/1533674-… If dataSource does not return view then you are right for the name. Now in Pharo the name is wrong and may be the design too :) > > Cheers, > Alex > > On 29 November 2016 at 10:44, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: >> >>>> On 29 November 2016 at 10:39, Esteban Lorenzano <estebanlm(a)gmail.com> >>>> wrote: >>> not true.it returns an NSView. >> >> Could you name a method (send a link to a documentation) that is >> implemented by DataSource and returns an NSView? >> >> According to documentation NSView for an item at row/column index is >> created and returned by NSTableView: >> https://developer.apple.com/reference/appkit/nstableview/1528831-view >> >> I didn't find any NSView related method in DataSource. Am I looking in >> a wrong place? >> >> Cheers, >> Alex > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by stepharo

On Tue, 29 Nov 2016 09:58:41 +0100, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > "DataSource" is responsible for providing visual elements that represent > items in a data set. who said that. I could say exactly: DataSource is responsible to cut data so that they are delivered by row or columns. > > I don't see how word "Store" fits here, because DataSource does not > store anything. Store in the sense of serving something. > DataSource is also not the best name since it is not a data source > itself. Clearly not > An object that is now called DataSource, basically just knows a single > function that from mathematical point of view can be defined as >follows: > f: Object -> Morph . You see, it is a mapping, not a souse or store. > > Cheers, > Alex > > On 29 November 2016 at 09:44, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: >> >>>> 2016-11-29 9:35 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>>> yes, something like TableCellSource or TableCellProvider is more >>>>>>> intention revealing. >>> >>> No, because is not *just* a cell provider.TableDataSource, TableStore, >>> TableProvider, yes. >>> >>> I kind of like âTableStoreâ. >> >> And if we have TableMorph then this guy should be TableMorphStore IMO. > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by stepharo

> > No, because is not *just* a cell provider.TableDataSource, TableStore, > TableProvider, yes. > > I kind of like âTableStoreâ.Also we have other stores in image: > FileSystem storesâ¦ which conceptually do more or less the sameâ¦ so > better to unify concepts/>namesâ¦ what do you think? TableMorphStore? Because I was really shocked to see that it returned Morph. > > Esteban > >> >> Christophe > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by stepharo

>>> >>> >>>>>>>> - Then I miss an important design point. Why datasource returns >>>>>>>> Morph? >>>> I do not get get why a data source should return UI element. To me it >>>> violates layers. >>> >>> no, because thatâs its purpose: to provide the table with the cell >>> elements (which are by definition Morphsâ¦ any kind of >>>morphs).a >>> TableDataSource is not a spec, is the provider of cells. >>> >>> >> >> so maybe TableCellSource / TableCellProvider ? > > Iâm not against changing its name, in general the family of names are > âDataSourceâ, âStoreâ, etc. so I imagine that âProviderâ fits (even if I > >tend to hate names style âManagerâ, âFactoryâ, âProviderâ, because > there are too genericâ¦ sometimes is that what you have :P) > But is not just a âcell providerâ, it does something more, is a general > model of the TableMorph: it provides cells, headers and interaction > >capabilities (like drag&drop)â¦ so it is more like a "table data > providerâ, TableDataSource, TableStore, TableProvider are then better > >names, IMOâ¦ Please please please. So I was always confused. > > this changes will impact Pharo 7â¦ is very good that we can have a > discussion like this now, that we have the time to reach a consensus >:) > > Esteban > >> >> cheers -ben > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by stepharo

On Mon, 28 Nov 2016 22:29:08 +0100, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, >> On 28 Nov 2016, at 21:32, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> - Could we rename FastTable into Table? > > not for Pharo 6 but Pharo 7 yesâ¦ in fact, I think it should be called > TableMorph. > (Also we need to refactor a lot, to eliminate the FT prefix, etc.) > >> >> - Then I miss an important design point. Why datasource returns Morph? >> I do not get get why a data source should return UI element. To me it >> violates layers. > > no, because thatâs its purpose: to provide the table with the cell > elements (which are by definition Morphsâ¦ any kind of morphs).a > TableDataSource is not a spec, is the provider of cells. What a ugly name then... Why this is not a CellMorphFactory or something like that. > > I got inspired for Cocoa NSTableView design (and NSTableViewDataSource), > and thatâs what it does.See for example here: > https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/…>TablesProgrammatically/PopulatingView-TablesProgrammatically.html > This function: >- (NSView *)tableView:(NSTableView *)tableView > viewForTableColumn:(NSTableColumn *)tableColumn > row:(NSInteger)row > > is the equivalent of our FTDataSource>>cellColumn:row: > > Esteban > >> >> Stef >> >> >> >> --Using Opera's mail client: http://www.opera.com/mail/ >> > -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 29, 2016