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

Re: [Pharo-dev] two question about fasttable

by Christophe Demarey

Hi, > Le 29 nov. 2016 Ã 08:45, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > >> >> On 29 Nov 2016, at 00:00, Ben Coman <btc(a)openInWorld.com <mailto:btc@openInWorld.com>> wrote: >> >> >> >> On Tue, Nov 29, 2016 at 5:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> Hi, >> >>> On 28 Nov 2016, at 21:32, stepharo <stepharo(a)free.fr <mailto:stepharo@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. >> >> >> >> 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â¦ > > 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 :) To me, the name datasource is misleading in this case. I would expect to find an abstraction that takes data from a database, or a file or in-memory object, etc. yes, something like TableCellSource or TableCellProvider is more intention revealing. Christophe

Nov. 29, 2016

Re: [Pharo-dev] two question about fasttable

by Esteban Lorenzano

> On 29 Nov 2016, at 00:00, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Tue, Nov 29, 2016 at 5:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi, > >> On 28 Nov 2016, at 21:32, stepharo <stepharo(a)free.fr <mailto:stepharo@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. > > > > 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â¦ 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

Nov. 29, 2016

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

by Sven Van Caekenberghe

Hi Tim, > On 29 Nov 2016, at 00:57, 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. > > 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 Right, that is not a good example, at all. I don't like it. Good of you to give feedback. I would rather says something like ./pharo Pharo.image eval '42 factorial' The stdio example leads way too far (difference between return value and output, newlines, weirder syntax, for Pharo at least, different kinds of quotes, the handling of !). Sven

Nov. 29, 2016

Re: [Pharo-dev] Bloc: Problems Running

by Sean P. DeNigris

Aliaksei Syrel wrote > Please refer to > https://github.com/pharo-graphics/Bloc/blob/master/INSTALL.md in order to > install bloc. $ wget -O- https://goo.gl/HQAPI5 | bash -> Oops, no wget on Mac $ curl https://goo.gl/HQAPI5 | bash -> line 1: syntax error near unexpected token `newline'... `<HTML>' $ curl https://raw.githubusercontent.com/pharo-graphics/Bloc/master/scripts/get-dev | bash -> Still no wget :/ $ curl http://get.pharo.org/60+vm | bash $ ./pharo Pharo.image eval --save "Metacello new baseline:'Bloc';repository:'github://pharo-graphics/Bloc/src';load:#git:development." "Error: External module not found" from LGitLibrary>>libgit2_init ugh... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Problems-Running-tp4924930p4925076.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 29, 2016

How to report website text bugs?

by Tim Mackinnon

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. 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

Nov. 28, 2016

[pharo-project/pharo-core]

by GitHub

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

Nov. 28, 2016

[pharo-project/pharo-core] 600389: 60308

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 600389fe241ad85f120ff1b13fa58cc436af0808 https://github.com/pharo-project/pharo-core/commit/600389fe241ad85f120ff1b1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-29 (Tue, 29 Nov 2016) Changed paths: M ScriptLoader60.package/ScriptLoader.class/instance/load primitives/newerVersionsIn_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60307.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60308.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60307.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60308.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60308 19276 Endless loop with ExecutionDisplayPlugin https://pharo.fogbugz.com/f/cases/19276 19344 No event about auto deletion of empty protocol when last method is moved from it https://pharo.fogbugz.com/f/cases/19344 17771 Empty stderr/stdout files should be deleted on image shutdown https://pharo.fogbugz.com/f/cases/17771 http://files.pharo.org/image/60/60308.zip

Nov. 28, 2016

Re: [Pharo-dev] two question about fasttable

by Ben Coman

On Tue, Nov 29, 2016 at 5:29 AM, 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. > > > so maybe TableCellSource / TableCellProvider ? cheers -ben

Nov. 28, 2016

Re: [Pharo-dev] two question about fasttable

by Esteban Lorenzano

> On 28 Nov 2016, at 22:25, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > The datasource is a wrapper/binding between the real object and the view (table/list) and provides the necessary stuff for display and interaction between them. Returning custom UI elements (cells and rows) from the datasource is part of what makes it possible to reuse the same table/container morph for lists/tables/trees. this ^ :) Esteban

Nov. 28, 2016

Re: [Pharo-dev] two question about fasttable

by Esteban Lorenzano

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. 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/… <https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/…> 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/ >

Nov. 28, 2016