[sword-devel] SwordReader PocketPC and SmartPhone CAB files.
sonwon.1 at gmail.com
Wed Jul 9 19:32:46 MST 2008
David Trotz wrote:
> Most all Windows Mobile applications follow this guideline. While I agree it does feel more constrained; sometimes it takes limits to inspire creativity.
That is why I waited 24 hours to respond, I was trying to think of
another way, nothing came to me. I hope others have an idea because I
like the looks of the new menubar.
> Certainly lets discuss this further. I would like to hear others opinions as well; including Albert Sites and Barry Drake.
I will look forward to hearing the opinion of others.
> If we diverge to two separate menus we need to implement some way to keep them in sync, so that when a smartphone developer adds a menu item reflecting some new feature the windows mobile devs get the menu automatically as well, and visa versa.
Well if we create an ugly menubar it could contain just two menus with
the rest being control buttons to shortcut frequently used options. The
two menus could be synced between both menubars. I would likely want to
compress the Navigate and Menu into icons to maximize the ugly menubar
space. I think both menubars would be fairly static this way. Some of
the ugly menubar items would be repeated in the menus. I don't see this
as a problem. And provide the option for the user to choose which
menubar to use unless they have a SmartPhone, I like choices. Although
I would prefer to not have an ugly menubar but would choose
functionality over appearance, within reason of course. :)
I'll shut up now, until others have a word.
> In Christ,
> David Trotz
> -----Original Message-----
> From: SonWon <sonwon.1 at gmail.com>
> Sent: Wednesday, July 09, 2008 3:52 PM
> To: SWORD Developers' Collaboration Forum <sword-devel at crosswire.org>
> Subject: Re: [sword-devel] SwordReader PocketPC and SmartPhone CAB files.
> David Trotz wrote:
>>> The gui looks real clean. I would prefer the navigate features to be
>>> single tap access instead of having to tap into a menu. Is there a
>>> reason behind the current menu system, like M$ usability guidelines?
>> The menu was driven by the Smartphone which can only have two menu
>> items. We decided that a single menuing system between the versions
>> would make things a lot easier to maintain. Plus on Windows Mobile 6
>> when you go to 3 or more menu items you loose the shiny menu look, and
>> get the plain menu's instead. (Not sure if that made much sense)
> I don't think I would agree with using a single interface for both
> systems. While there are many similarities there are also many
> differences. By dumbing down the interface on the Windows Mobile you
> loose a lot of the power of the platform. The Windows Mobile platform
> can compete with a desktop in many ways. I don't believe the SmartPhone
> can get as close to the desktop as Mobile can, too little functionality.
> I do find the loss of the 'shiny menu' distressing. I think it would be
> a worth while trade off to make the user interface more efficient.
> Perhaps the interface could be user selectable and defaulted based on
> the platform?
> Any chance of reopening this discussion? I guess I just did. :)
>> In Christ,
>> David Trotz
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
I choose God and all that my choice entails in this life even unto death and look forward to the new life that will come.
More information about the sword-devel