2016-11-29 11:07 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com>: > > On 29 Nov 2016, at 10:36, Thierry Goubier <thierry.goub...@gmail.com> > wrote: > > > > 2016-11-29 10:14 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com>: > >> >> On 29 Nov 2016, at 09:58, Aliaksei Syrel <alex.sy...@gmail.com> wrote: >> >> "DataSource" is responsible for providing visual elements that represent >> items in a data set. >> >> I don't see how word "Store" fits here, because DataSource does not store >> anything. DataSource is also not the best name since it is not a data >> source itself. >> 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.* >> >> >> Store != Storage. >> A store is a place where you go to get stuff (same as FileSystem stores: >> they give you access to different filesystems, as a FTDataSource gives you >> access to different data structures) :) >> In Gtk3, you have GtkListView, and GtkListStore, for example. >> And DataSource is another stuff in Cocoa, from where I borrowed the >> design: https://developer.apple.com/reference/appkit/nstable >> viewdatasource >> >> So… I still rest my argument. >> >> Anyway… we will NEVER reach a 100% agreement. We just need to go with >> what fits better current design/general idea. >> > > If you can't find the perfect meaning... just make sure there is no > misunderstanding (i.e. DataSource is kind of confusing). Memorable can > compensate for 'not exactly the right name'. > > I like the FastTable moniker because it convey some of the design intent. > As I like the core principle. > > I don't like the overall design; it has a lot of the PluggableTreeMorph > caracteristics, such as being a single widget trying to do everything with > an API that's dozens of pages long... And we know what will be the > community opinion on such widgets 10 years down the line. > > It's fitting that it has a lot to relate with GTK / Cocoa designs. Places > where people design huge objects because they live in a 'each function is > 20 to fifty lines long' world and don't understand what fine grained > objects / a live environment can be. > > > widgets are huge objects by definition (specially a table… or a text > editor). >
It would be really great to make them a bit more composable / modular... > but well, you can propose a refactor… Pharo 7 will be the good moment for > it :) > Ah, if only I had the time... Thierry > > Esteban > > > Thierry > > > > >> >> Esteban >> >> >> Cheers, >> Alex >> >> On 29 November 2016 at 09:44, Denis Kudriashov <dionisi...@gmail.com> >> wrote: >> >>> >>> 2016-11-29 9:35 GMT+01:00 Esteban Lorenzano <esteba...@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. >>> >> >
