Mobile CAB

[Harry Simpson]

Anyone using the mobile Composite UI Application Block out there? Is it
doable and advisable. I actually was bypassing it do to comment in
Wigley/Moth/Foot book about it being "quite difficult to adopt". But then
my VP asked me to look into it a little more.....argh....

I don't want to needlessly over engineer my app but would like the app to be
easily tested and extensible.

Short of this is anyone using the other peices of the Mobile Client Software
Factory? Successes? Horror stories to relate?

TIA much
Harry

 

[Guest]

I'd go back to the VP with the book and point that out to him. I know of no
one that uses it becasue it makes stuff overly complex and just isn't worth
it.

 

[Harry Simpson]

LOL - You da man Chris! Thanks!

Harry

I'd go back to the VP with the book and point that out to him. I know of
no one that uses it becasue it makes stuff overly complex and just isn't
worth it.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com

 

[Simon Hart [MVP]]

I agree with Chris, the composite UI block is too complex. The whole point in
using application blocks is to simplify you're code, well at least one of the
reasons. We do however use the data block and the orientation aware blocks
and find them very useful.

 

[Harry Simpson]

Thanks for the input Simon

I am looking to try to do my syncing (pull mostly - I use a Web service for
updating) on a background thread verses what I do now which is basically to
ask the user to wait while the device updates (using RDA Pull and SQL CE 3.1
agent).
I'd like to have the syncing be done transparently in the background while
the device is in use via WiFi.
Again right now it is a manual step the user must select or, if on the logon
screen - it just syncs every 5 minutes.
Is there an already built framework that does background threaded syncs when
connected and behaves well when not connected. The RDA has always been a
bit of a problem since the SDF table must first be destroyed before a new
RDA table is pulled into the device's SDF database. I've even toyed with
the idea of a totally separate process app running which the sole duty is to
download and replace the SDF on the device periodically so that the device
would always just use the SDF that exists on the device and receive an
updated SDF from this other process periodically.
I could write asynchronous threaded background proc i suppose or is there a
better solution via Smart Device Framework or the Mobile Client Software
Factory?
I'm trying to stay at a design level before coding and things are just
changing way too fast for me to keep a good handle on the bast way to
proceed.

TIA
Harry