On Fri, Jan 13, 2017, at 11:58 PM, Samuel Gaist wrote:
> Short summary, we have three possibilities:
> 1) Own module (and current implementation)
> 2) One “core" module and one GUI module to separate concerns for system
> not requiring a GUI connection (Jake’s suggestion)
> 3) Put everything in
Hi,
On Sun, Jan 15, 2017, at 12:24 PM, J-P Nurmi wrote:
> There have been some discussions about rewriting the entire item-view
> framework. I personally believe that would be best done in a major
> release. :)
I guess you're talking about the generic positioner-based view stuff
here, but I
Hi,
> On 14 Jan 2017, at 19:20, Mark Gaiser wrote:
>
> That new TableView is really going to support models that derive
> QAbstractTableModel? Without any changes required on the model side? So if it
> works in QTableView (C++ widget) then it will work in the new TableView
Hi,
On 14 Jan 2017, at 17:24, Robin Burchell
> wrote:
I have a longer mental list of things that concern/bother me with
current model/views (some of which we've already discussed), maybe I
should try write that up in some form, if you
Just submitted first change set:
https://codereview.qt-project.org/#/c/182341/
Planning to add three more calendars and separate index array (to
reduce overhead on locales) this week. Persian calendar is still one
day behind. Seems to be related to julian day base. The original
algorithm counts