Advice on stable jquerymobile/multiview versioni combination that can be used in production

[mliga666]

I'm going to release an app in a couple of week and looking for a stable combination. I don't need many of the features, just splitview with scroll on right panel, 2 panels only in landscape, left pane on a popover in portrait mode.

[frequent]

@mliga666 : I'm busy on another project, but I will try to put in a little time next week to try and fix (#40, #41)some open bugs.

The plugin is more or less stable (except for some extensive cleanup needed). I'm still chasing bugs in the navigation and adjusting panel (and nested page) dimensions is a real pain to get right. But other than that, it's running ok.

[Golodhros]

@mliga666: We have tried lately to get Multiview in production in my company, but we didn't manage to do it.

In small tablets like kindle fire or nook color we have performance issues. In the latest iPads it works fine, although we are having a memory leak problem in iPad1, but I am not sure if it is a Multiview problem or a JQMobile problem.

[frequent]

@mliga666, @golodhros - I will work on mv tomorrow, will try to fix some issues I'm having, plus your latest issues. i'm also testing on ipad 1, so if you can, please give me some more info on performance issues/memory leak, so I can try to have a look.

[Golodhros]

@frequent Well, I am afraid that iOs doesn't tell too much about it. It just sends a memory warning and closes the application right away.

I was using the jQuery 1.1.2 based multiview, but I am not sure if the problem was with multiview or not.

Thanks!

[frequent]

hm. I haven't seen this on iPad 1. I have one page that runs multiview plus datatables with automatic ajax-server updates. This is the only page not stable on iPad 1 in my application. All other pages seem to work fine.

What I noticed though is that if you have a page which has a lot of widgets that need to be enhanced, iPad 1 crashes if you try to do anything before widgets are enhanced (scroll, click somewhere, etc). Not necessarily related to multiview though. I haven't seen a memory warning with multiview until now. The only function I'm having trouble with performance-wise is panelHeight (similar to JQM updatelayout, recalculates wrapper/panel/page/content heights after transitions). This fires way too often and slows things down considerably. Other than that there shouldn't really be any performance issues. At least nothing I'm aware of. Some other things aren't working tough. Let's see what I can come up with tomorrow. Rgs.

[Golodhros]

@frequent Many thanks!

I will check that on iPad1, it makes sense.

The performance issues are mainly with small tablets like Kindle Fire and Nook Color, in iPads everything works fine.

Regards,