RE: Menus

[Ian B]

>One of the things I love about the Slim (or at least what I've used of
>it so far) is that it's rapid. Once you get used to devices like it
>you probably do end up whizzing around the menu structure
>automatically without thought.

I agree here. Nothing worse than knowing where you want to go and having to
wait. Even over Ethernet these devices are essentially still serial so
there
is a restriction there. The screens are not the fastest devices in the
world
but I have not been able to test this thoroughly yet.

>I daresay a cache would just add to the complexity and be out of the
>question maybe?

Not sure to be honest. Either way using the biggest chip I have a total of
4k of RAM. I can of course use more but access is slower so it will be a
trade off. I am currently testing on a chip with 1k of RAM so I will
hopefully learn some useful lessons from that.

>How about loading a branch of the menu tree at once? So that you can
>shoot down it or back up it quickly without having to load the whole
>lot. There would have to be a pause as the branch was loaded
>initially.

This is an option of course but not one I favour as a gut reaction. My
preference is to get everything on the chip for best performance. Just
leaving the updating question to bridge later in the dev cycle.

Ian


>-----Original Message-----
>From: Stuart Booth [mailto:<a
href="/group/xAP_developer/post?postID=lTTQ3dhAlUACJ1PIuWg4QwKBF_0oCXsX1l2tG7OP_I0Uq57YYLERu0wY-B8Wk-ETVGnsvkaHxE9-HZ8FLP8JJBA">lists@x...</a>]
>Sent: 07 September 2003 23:45
>To: <a
href="/group/xAP_developer/post?postID=qGTSt76OZl49xHyQhCrvlQma8RL_NxwjAY877Yp-_QMA3vrHK082H9Jr7l1omQS505Gxc82fzIalkIFMYwlbW20eM5eS6NU">xAP_developer@xxxxxxx</a>
>Subject: Re: [xAP_developer] Menus
>
>
>On Sun, 7 Sep 2003 23:33:14 +0100, "Ian B" <<a
href="/group/xAP_developer/post?postID=lii7vRDMVzjN2k27ht_KgyabO8v-kun2paS36TVaWz2YMhk_3NmKc9x0NDTZsa8WrctHcE_oxJ4">Ian@M...</a>>
wrote:
>
>>Do I try and hold the menu system (or part thereof) in local memory
or try
>>and update a line at a time from the PC. The answer to this
>little quandary
>>will dictate the level of power of the micro needed etc. I think
>my biggest
>>concern is speed if I don't hold at least some of the data in
memory.
>
>One of the things I love about the Slim (or at least what I've used of
>it so far) is that it's rapid. Once you get used to devices like it
>you probably do end up whizzing around the menu structure
>automatically without thought.
>
>I would probably then agree with you that maybe waiting for each
>screen to appear would get rapidly irritating for a high frequency of
>usage.
>
>Initially I thought it might be possible to cache the immediate
>next/previous screens, but a double sequence would still require a
>load, and maybe a fast/slow alternating response would be even more
>infuriating.
>
>I daresay a cache would just add to the complexity and be out of the
>question maybe?
>
>How about loading a branch of the menu tree at once? So that you can
>shoot down it or back up it quickly without having to load the whole
>lot. There would have to be a pause as the branch was loaded
>initially.
>
>S
>--
>Stuart Booth
>xAPFramework.net - a reusable xAP framework for .net
>
><a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
<a
href="/group/xAP_developer/post?postID=E6zd6n1GRVlNEcTcXbc1fsbujnQCCoyiAqWHds9AqIUjhMD4coeGpQ5lp78FlIdoLYHov3h2qt7_vAES6g">stuart@x...</a>
>
>
>To unsubscribe from this group, send an email to:
><a
href="/group/xAP_developer/post?postID=9h-h3VHxrIo9atWGxOEOluL5Ml6noG8Gjmxr_-VOw3Yffh0hVBnudMJrZ2gqrTPu6JSNQirGatUIfWO2DOuQirdSZvp-c9jvr3U9HwJ4mng">xAP_developer-unsubscribe@xxxxxxx</a>
>
>
>
>Your use of Yahoo! Groups is subject to <a href="http://docs.yahoo.com/info/terms/";>http://docs.yahoo.com/info/terms/</a>
>
>
>