Steve,
In the meanwhile I found the answer to the second question but not for the
first.
I forgot the existence of VisualItemModel which is precisely what I needed.
Memory is in fact a problem but my users won’t tolerate a big time between view
switch.
StackView also allows me to define the transition between views which allows me
to give a richer visual experience as well.
I will definitely need to optimize the memory usage in each module as well as
the internal architecture to reduce the memory footprint.
I ended up with the following solution which is now allowing me to fast switch
between views even on the iPad 2:
MouseArea {
onClicked: {
if (navigationBarList.currentIndex!=index)
{
navigationBarList.currentIndex = index
stackView.replace({"item" : modulesModel.children[index]})
}
}
}
VisualItemModel {
id: modulesModel
Module1 {
width: stackView.width
height: stackView.height
}
Module2 {
width: stackView.width
height: stackView.height
}
Module3 {
width: stackView.width
height: stackView.height
}
Module4 {
width: stackView.width
height: stackView.height
}
}
StackView {
id: stackView
initialItem: {"item" : modulesModel.children[settings.initialModule]}
}
Thanks!
Regards,
Nuno
> On 07 Jan 2015, at 10:53, Nuno Santos <nunosan...@imaginando.pt> wrote:
>
> Hey Steve,
>
> That seems a nice suggestion.
>
> Questions:
>
> - How do you disable or change the animations between index change?
> - How do you disable interaction with the list itself, because I would need
> to interact with the content of the page.
>
> I will give it a try in the meanwhile.
>
> Thanks!
>
> Regards,
>
> Nuno
>
>> On 05 Jan 2015, at 23:06, VStevenP <vstevenpa...@yahoo.com
>> <mailto:vstevenpa...@yahoo.com>> wrote:
>>
>> Hi Nuno,
>>
>> You might wish to consider using a ListView whose delegate is a Component
>> which contains a Loader.
>>
>> That way, app pages are just delegate instances created and managed by the
>> ListView. You can use the cacheBuffer property of the ListView to manage
>> how many delegates (pages) are instantiated a.k.a. loaded.
>>
>> My group is using this technique to handle loading and unloading of related
>> application pages. It's easy to flick between the related pages this way,
>> helping to ensure that nearby pages are loaded and cached, and therefore
>> quickly available to the user, while other pages which are not neighboring
>> pages can be loaded later as needed by the ListView.
>>
>> I don't think you'll want to load all your application pages at the start.
>> Here's why: The QML engine can sometimes keep up to 4 copies of your pages.
>> This was explained at QtDevDays, but I can't recall the exact details. Any
>> way, if your app pages use decent size graphics, the amount of actual RAM
>> used by a page can be up to 4X that at certain times. Therefore, it makes
>> sense to have an evolved page loading strategy, so you don't use excessive
>> RAM in tablet and embedded environments, where RAM resource may be more
>> scarce.
>>
>> Steve Pavao
>> Korg R&D
>>
>> From: "interest-requ...@qt-project.org
>> <mailto:interest-requ...@qt-project.org>" <interest-requ...@qt-project.org
>> <mailto:interest-requ...@qt-project.org>>
>> To: interest@qt-project.org <mailto:interest@qt-project.org>
>> Sent: Tuesday, December 30, 2014 6:00 AM
>> Subject: Interest Digest, Vol 39, Issue 60
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Tue, 30 Dec 2014 09:10:12 +0000
>> From: Nuno Santos <nunosan...@imaginando.pt
>> <mailto:nunosan...@imaginando.pt>>
>> Subject: [Interest] Stack view and lazy loading of big Qml files
>> To: Interests Qt <interest@qt-project.org <mailto:interest@qt-project.org>>
>> Message-ID: <756c12de-64f5-4e60-9322-80882481f...@imaginando.pt
>> <mailto:756c12de-64f5-4e60-9322-80882481f...@imaginando.pt>>
>> Content-Type: text/plain; charset=utf-8
>>
>> Hi,
>>
>> I have a stack view which will be used to load the main content of
>> application views.
>>
>> Currently, when I select a new view, I pass the url of the correspondent Qml
>> file. I use the replace method because in fact i?m only interested in the
>> transition animation.
>>
>> The problem is that in arm devices like android and ipad, the transition is
>> not immediate due to the fact that the Qml being loaded are quite heavy.
>>
>> The app users won?t understand that so I wanted to load all the views
>> without showing them and instead of passing the url I would pass the id of
>> the component.
>>
>> My questions are:
>>
>> What is the best way of doing that?
>> Where should I keep the elements without having them rendered on the screen?
>> Is there any other way of making this?
>>
>> Thanks in advance,
>>
>> Regards,
>>
>> Nuno Santos
>>
>> ------------------------------
>>
>
> _______________________________________________
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
