On Mon, Nov 19, 2012 at 8:01 PM, David Faure wrote:
> On Monday 19 November 2012 19:39:19 Mark wrote:
>> 4. in org.kde.kio, add a KDirModel subclass (DirModel) and add a
>> indexForItem that returns a FileItem object. (this is a
>> QDeclerativeItem)
>
> Right, which enforces my point about making
On Monday 19 November 2012 19:39:19 Mark wrote:
> 4. in org.kde.kio, add a KDirModel subclass (DirModel) and add a
> indexForItem that returns a FileItem object. (this is a
> QDeclerativeItem)
Right, which enforces my point about making this separate: it comes with a
dependency on a different Qt
On Mon, Nov 19, 2012 at 7:00 PM, David Faure wrote:
> On Monday 19 November 2012 18:11:06 Mark wrote:
>> On Mon, Nov 19, 2012 at 12:05 PM, David Faure wrote:
>> > On Saturday 17 November 2012 18:02:59 Mark wrote:
>> >> On Sat, Nov 17, 2012 at 5:04 PM, Aaron J. Seigo wrote:
>> >> > On Saturday, N
On Monday 19 November 2012 18:11:06 Mark wrote:
> On Mon, Nov 19, 2012 at 12:05 PM, David Faure wrote:
> > On Saturday 17 November 2012 18:02:59 Mark wrote:
> >> On Sat, Nov 17, 2012 at 5:04 PM, Aaron J. Seigo wrote:
> >> > On Saturday, November 17, 2012 16:22:07 Mark wrote:
> >> >> Why don't we
On Mon, Nov 19, 2012 at 12:05 PM, David Faure wrote:
> On Saturday 17 November 2012 18:02:59 Mark wrote:
>> On Sat, Nov 17, 2012 at 5:04 PM, Aaron J. Seigo wrote:
>> > On Saturday, November 17, 2012 16:22:07 Mark wrote:
>> >> Why don't we just make KFileItem available in QML.
>> >> It doesn't hav
On Saturday 17 November 2012 18:02:59 Mark wrote:
> On Sat, Nov 17, 2012 at 5:04 PM, Aaron J. Seigo wrote:
> > On Saturday, November 17, 2012 16:22:07 Mark wrote:
> >> Why don't we just make KFileItem available in QML.
> >> It doesn't have to be a QML component, but if KFileItem where to have
> >>
On Sat, Nov 17, 2012 at 5:04 PM, Aaron J. Seigo wrote:
> On Saturday, November 17, 2012 16:22:07 Mark wrote:
>> Why don't we just make KFileItem available in QML.
>> It doesn't have to be a QML component, but if KFileItem where to have
>> Q_PROPERTY lines then most of the data would already be pos
On Saturday, 2012-11-17, Mark wrote:
> On Sat, Nov 17, 2012 at 4:40 PM, Kevin Krammer wrote:
> > Hi Mark,
> >
> > On Saturday, 2012-11-17, Mark wrote:
> >> So i was thinking: Why don't we just make KFileItem available in QML.
> >> It doesn't have to be a QML component, but if KFileItem where to h
On Saturday, November 17, 2012 16:22:07 Mark wrote:
> Why don't we just make KFileItem available in QML.
> It doesn't have to be a QML component, but if KFileItem where to have
> Q_PROPERTY lines then most of the data would already be possible to
> make available
because this means making KFileIte
On Sat, Nov 17, 2012 at 4:40 PM, Kevin Krammer wrote:
> Hi Mark,
>
> On Saturday, 2012-11-17, Mark wrote:
>
>> So i was thinking: Why don't we just make KFileItem available in QML.
>> It doesn't have to be a QML component, but if KFileItem where to have
>> Q_PROPERTY lines then most of the data wo
Hi Mark,
On Saturday, 2012-11-17, Mark wrote:
> So i was thinking: Why don't we just make KFileItem available in QML.
> It doesn't have to be a QML component, but if KFileItem where to have
> Q_PROPERTY lines then most of the data would already be possible to
> make available. I did this in my co
Hi,
In my project i need to use the KDirModel and KFileItem
functionalities. KDirModel is exposed through the custom class that
Marco Martin made [1] and it works. However, that custom class does
(apparently) need to expose some QML ready data hence the get function
[2] (from line 99).
So i was t
12 matches
Mail list logo
