Aaron J. Seigo wrote:
> On Sunday 06 August 2006 15:52, Olivier Goffart wrote:
>
>>> and the contactlist data structure ought to be able to feed directly into
>>> views.
>>>
>> What do you mean ?
>>
>
> having a data structure for contacts, a view and then a bridge between those
> t
2006/8/7, Matt Rogers <[EMAIL PROTECTED]>:
> On Monday 07 August 2006 01:12, Michel Hermier wrote:
> > 2006/8/7, Matt Rogers <[EMAIL PROTECTED]>:
> > > On Sunday 06 August 2006 02:09, Michel Hermier wrote:
> > > > 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> > > > > Hello.
> > > > >
> > > > > S
On Monday 07 August 2006 01:12, Michel Hermier wrote:
> 2006/8/7, Matt Rogers <[EMAIL PROTECTED]>:
> > On Sunday 06 August 2006 02:09, Michel Hermier wrote:
> > > 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> > > > Hello.
> > > >
> > > > So we are going soon or later to drop the Q3ListView stuff
2006/8/7, Matt Rogers <[EMAIL PROTECTED]>:
> On Sunday 06 August 2006 02:09, Michel Hermier wrote:
> > 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> > > Hello.
> > >
> > > So we are going soon or later to drop the Q3ListView stuff for the
> > > contactlist.
> > >
> > > I have made an experimenta
> WILL YOU PLEASE STOP SENDING ME EMAILS?IV'E HAVE ASKED YOU NICELY AND
> YOU TAKE NO NOTICE.THATS WHY I'M SHOUTING!
We have taken notice and a few people have politely sent you instructions on
how you can manually remove yourself from this list and stop your receiving
of these emails.
However,
On Sunday 06 August 2006 04:11, Olivier Goffart wrote:
> Le dimanche 6 août 2006 09:09, Michel Hermier a écrit :
> > 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> >
> > This model is better in the seens that you divide the data, from it's
> > rendering. This way you can have multiple view using
On Sunday 06 August 2006 02:09, Michel Hermier wrote:
> 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> > Hello.
> >
> > So we are going soon or later to drop the Q3ListView stuff for the
> > contactlist.
> >
> > I have made an experimental contactlist using QAbstractItemModel.
> >
> > I have to s
This is a long post. If you're not willing to read it all (but you should
really read it all), here's the executive summary:
There should be one main contact list model. It should replace
Kopete::ContactList and continue to provide the same functionality as that
class does. We should start out
On Sunday 06 August 2006 15:52, Olivier Goffart wrote:
> > and the contactlist data structure ought to be able to feed directly into
> > views.
>
> What do you mean ?
having a data structure for contacts, a view and then a bridge between those
two that needs to maintained is not necessary these d
On Sunday 06 August 2006 16:11, Edward Barr wrote:
> Aaron J. Seigo wrote:
> > On Sunday 06 August 2006 10:30, Olivier Goffart wrote:
> >> Le dimanche 6 août 2006 17:07, Michaël Larouche a écrit :
> >>> One thing for sure, it will save us maintainability in lorg term and
> >>> will give us more pow
Hi Aaron, thanks for your reply.
Le dimanche 6 août 2006 21:47, Aaron J. Seigo a écrit :
> On Sunday 06 August 2006 10:30, Olivier Goffart wrote:
> by keeping the data coupled to the view, you will never be able to
> experiment too wildly with views and uses of that data because the effort
> of d
Aaron J. Seigo wrote:
> On Sunday 06 August 2006 10:30, Olivier Goffart wrote:
>
>> Le dimanche 6 août 2006 17:07, Michaël Larouche a écrit :
>>
>>> One thing for sure, it will save us maintainability in lorg term and will
>>> give us more power and flexibility.
>>>
>> For sure ?
>>
On Sunday 06 August 2006 10:30, Olivier Goffart wrote:
> Le dimanche 6 août 2006 17:07, Michaël Larouche a écrit :
> > One thing for sure, it will save us maintainability in lorg term and will
> > give us more power and flexibility.
>
> For sure ?
>
> It seems more complex.
> And more complex = har
> > For me what you wrote is the way to go. Only one final comment. Make
> > an intermediate Kopete::AbstractContactTreeViewModel, and use this
> > intermediate in all the views.
> > So that we could provide the real and direct
> > Kopete::ContactTreeViewModel and maybe somewhere else the
> > Kopet
Le dimanche 6 août 2006 17:07, Michaël Larouche a écrit :
> Le August 6, 2006 07:54, Olivier Goffart a écrit :
> > I'm not saying that we should not use the Model/View stuff.
> > But I still doesn't see the need of it.
> >
> > No need to rush on that technology because it's new fashion in Qt.
> >
>
Le August 6, 2006 07:54, Olivier Goffart a écrit :
> I'm not saying that we should not use the Model/View stuff.
> But I still doesn't see the need of it.
>
> No need to rush on that technology because it's new fashion in Qt.
>
> We could simply use a QTreeWidget with LVI like this is done.
> It se
Le August 6, 2006 03:09, Michel Hermier a écrit :
> 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> > Hello.
> >
> > So we are going soon or later to drop the Q3ListView stuff for the
> > contactlist.
> >
> > I have made an experimental contactlist using QAbstractItemModel.
> >
> > I have to say i
Le dimanche 6 août 2006 12:00, Michel Hermier a écrit :
> This is a sorting and presentation problem it can be done by adding
> some filter models.
Or doing two completely different models...
(Or using QTreeWidget without model)
I can assure you there will be not duplicated code.
> [...]
I'm n
>
> >
> > So do we have a real interest in such features, I would say yes,
> > because you can also add some filter model layers. And this is
> > interesting by example for the chat lists.
>
> That's an interesting point.
> Could we share the main contactlist model with the chatwindow member list
>
Le dimanche 6 août 2006 09:09, Michel Hermier a écrit :
> 2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> This model is better in the seens that you divide the data, from it's
> rendering. This way you can have multiple view using the same model that
> are
> affected when you affect one off the v
2006/8/6, Olivier Goffart <[EMAIL PROTECTED]>:
> Hello.
>
> So we are going soon or later to drop the Q3ListView stuff for the
> contactlist.
>
> I have made an experimental contactlist using QAbstractItemModel.
>
> I have to say i'm still not convinced by the supposed advantage of
> QAbstractItem
Hello.
So we are going soon or later to drop the Q3ListView stuff for the
contactlist.
I have made an experimental contactlist using QAbstractItemModel.
I have to say i'm still not convinced by the supposed advantage of
QAbstractItemModel.
We could as well use QTreeWidget, and have subclass
22 matches
Mail list logo
