iPhone, iPod Touch, and iPad RIVA Client v1.2 Released!

[SamVimes2]

Originally Posted by wuench

Is that true for all images or just media images? Are media and template images cached separately? It would be nice if you guys could document these restrictions so we can design our templates accordingly.

We are really into tuning things now, so it might be easiest just to make the cache size configurable by the user with some feedback on how much is currently used, and a clear cache button. I mean, we have 8-16GB on these devices, that should be plenty of room to cache everything necessary, regardless of size. It's not necessarily the size of the file that costs, these devices have plenty of bandwidth, the cost is in having to make that trip across the network to retrieve it, especially over 3G (latency).

There are 3 separate caches (one each for regular images, media images, and web images) that I believe all have those same restrictions.

While the devices do have plenty of 'disk', they actually don't have a lot of RAM. the current restrictions exist because as cute as the i* gizmos are, you can easily crash them by filling up the memory. so restrictions are necessary on how much image data the app holds in memory at any one time, and the disk caching was added after the fact and just mirrors whatever is in memory. so we have to rethink and disintermediate the two with the goal of minimizing bits travelling over the wire. it's a work in progress and Brian can speak to it much more intelligently than I can.

[MavRic]

Is there such a thing as an imagepack for the interface editor with buttons, switches, etc that look like the standard iphone/itouch stuff used in the settings menu's etc?

[Bodshal]

Slightly odd, and perhaps a coincidence, but I updated my iPad and iPhone to 4.2.1 (GM seed) yesterday and now the RIVA client hangs for a looooong time at initial connection and upon any action, eventually timing out.

[Bodshal]

Originally Posted by Bodshal

Slightly odd, and perhaps a coincidence, but I updated my iPad and iPhone to 4.2.1 (GM seed) yesterday and now the RIVA client hangs for a looooong time at initial connection and upon any action, eventually timing out.

Appears that 4.2 on iOS now does IPv6 transparently for many apps - the RIVA client included. I was using the DNS entry that my master server registers in the Active Directory DNS... which includes its IPv6 address and it had to wait for that to timeout for each and every connection it made.

Switched it over to a DNS name that's a bit more static and IPv4 only and it works perfectly again.

Chris.

[bryanb]

I asked Dean again yesterday about viewing security camera video on a RIVA client like the iPad. Now that iOS is multitasking, this may help solve the problem. This was his comment, "If it can multi-task, then you can probably talk Brian into allowing you to use the ExecApp command to invoke some program or another, and we can arrange to have that command passed to the clients if it isn't already being." Brian and Sam is this approach something that you could work on? Thanks.

[potts.mike]

Does the ios sdk allow for one app to open another app?

[wuench]

Originally Posted by potts.mike

Does the ios sdk allow for one app to open another app?

No. IOS apps are totally compartmentalized. While a lot of things may be possible, it is against the guidelines and wouldn't make it through the approval process. You can launch the stock apps though, like safari, maps, all within your application context.

[SamVimes2]

We've long talked about using a scheme similar to the regular windows IV, where a browser windowlet 'floats' on top of the RIVA canvas. This would not require any multitasking.

We'd have to work with Dean on how best to incorporate it into the RIVA protocol. The discussion is shelved at the moment.

[wuench]

Yeah, that seems to me like it would be pretty simple to duplicate what the IV does for browser support. I would make it an optional RIVA feature, though, not all platforms might be able to support it.

But implementing ExecApp wouldn't be possible, unless you want to require jailbreaking. That is why you don't see a bajillion launcher and "front end" apps on the Iphone like you do on every other platform.

Like any browser though, Safari can do a lot. Most of the apps you see that do file access are just launching Safari to access a local file (within the app context, file space isn't shared either). They don't write PDF, Word, Excel, etc support into their apps, that's just Safari.

[Dean Roddey]

I assume that the browser would be what's getting launched anyway, since it's likely that's how the cameras would be viewed probably. But, does that mean that the launching app gets killed?