Skip to main content

PhoneME Windows Mobile MIDP Wish List

1 reply [Last post]
mara_fenske
Offline
Joined: 2008-08-01
Points: 0

I am only going to list these items as "wish list" items because I am unable to do them myself because I have no legit C experience, but here are a few things that I would love to see added/fixed/reimplemented in the PhoneME builds for Windows Mobile MIDP (Feature and Advanced Dual Stack):

* The latest builds of Advanced Dual Stack have serious virtual keyboard issues. It is a pain to try and pull up the virtual keyboard by using the menu each time you want to enter data into a text field in an application. Furthermore, on many devices the keyboard rarely opens even when you choose the Virtual Keyboard in the options - it then literally becomes impossible to enter data if you have no hardware keyboard available. Builds about 6 months ago always had the keyboard button in the bottom-center part of the screen. It may have taken a bit of space but it was easy to access and consistently worked. Is there a way to bring that back?

* I have seen recordstores recently require more than 2MB of data in a single store. The new builds of PhoneME look like they only allow 2MB. Is it possible to increase that? What issues does it cause to increase this capacity? I'm assuming it must hurt something, otherwise the limitation wouldn't even be specified at all. I would expect 4 or 5MB to be enough for most solutions, but that is just my guess based upon a few applications I have used.

* About 6 months ago, there was a build for Windows Mobile 2003 that allowed for Windows Mobile 6.x devices that had high resolutions but small screens to have lower resolution when running PhoneME. This seemed to work well. What is strange now, is that none of the new builds seem to lower the resolution enough to have decently large fonts. My working example is the Palm Treo Pro. It is a Windows Mobile 6.1 device. It has a high resolution but a small actual screen. Builds from ~6 months ago for Win Mobile 2003 reduce the resolution enough that text is large enough for most people. However, now all builds of Windows Mobile do not lower the resolution enough for text to be large enough for most people. Has something changed that could be reverted to allow for this?

* Previously I opened a thread regarding a hard crash in any PhoneME build (even non-Windows Mobile builds) when you clicked on the space below a standard command options menu. Is there a way to prevent this crash for the Windows Mobile builds?

Thanks all for any help. Especially to Davy who appears to have done much of the Windows Mobile work.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davyp
Offline
Joined: 2007-01-03
Points: 0

> I am only going to list these items as "wish list"
> items because I am unable to do them myself because I
> have no legit C experience, but here are a few things
> that I would love to see added/fixed/reimplemented in
> the PhoneME builds for Windows Mobile MIDP (Feature
> and Advanced Dual Stack):
>
> * The latest builds of Advanced Dual Stack have
> serious virtual keyboard issues. It is a pain to try
> and pull up the virtual keyboard by using the menu
> each time you want to enter data into a text field in
> an application. Furthermore, on many devices the
> keyboard rarely opens even when you choose the
> Virtual Keyboard in the options - it then literally
> becomes impossible to enter data if you have no
> hardware keyboard available. Builds about 6 months
> ago always had the keyboard button in the
> bottom-center part of the screen. It may have taken
> a bit of space but it was easy to access and
> consistently worked. Is there a way to bring that
> back?

Yes, I added some code to check whether a real keyboard was integrated
into the device and showed the virtual keyboard button accordingly, but it
may be that this detection code that relies on the registry is not that
accurate for all devices. It worked on my own device and on a colleague's
device I could borrow for a sec. I am afraid that is all the testing can do
with real hardware.

It has been a while since I posted new binaries on my website (because I
have been busy with other stuff), but I will set the button back in my next builds.

> * I have seen recordstores recently require more than
> 2MB of data in a single store. The new builds of
> PhoneME look like they only allow 2MB. Is it
> possible to increase that? What issues does it cause
> to increase this capacity? I'm assuming it must hurt
> something, otherwise the limitation wouldn't even be
> specified at all. I would expect 4 or 5MB to be
> enough for most solutions, but that is just my guess
> based upon a few applications I have used.

Yep, it is basically the RMSConfig.STORAGE_SUITE_LIMIT option
that controls how much space is available. The value was initially set to
200k in one of the configuration files.
midp/src/configuration/configuration_xml/wince/constants.xml

I already increased it to 2MB so it should not be a problem to
increase it a bit more to 4 or 5MB.

> * About 6 months ago, there was a build for Windows
> Mobile 2003 that allowed for Windows Mobile 6.x
> devices that had high resolutions but small screens
> to have lower resolution when running PhoneME. This
> seemed to work well. What is strange now, is that
> none of the new builds seem to lower the resolution
> enough to have decently large fonts. My working
> example is the Palm Treo Pro. It is a Windows Mobile
> 6.1 device. It has a high resolution but a small
> actual screen. Builds from ~6 months ago for Win
> Mobile 2003 reduce the resolution enough that text is
> large enough for most people. However, now all
> builds of Windows Mobile do not lower the resolution
> enough for text to be large enough for most people.
> Has something changed that could be reverted to
> allow for this?

I removed that build because I added some code to always
lower the resolution to a default 96DPI resolution. I have
not checked the builds on my website lately, but in a Windows
Mobile 6 emulator with VGA resolution (480x640) using
a local build the fonts are rescaled and readable.

Unfortunately I do not have a real device with a resolution
higher that 240x320. Check the new builds when they
arrive on my website to see if the issue persists.

Do you also have the problem when you install the Windows
Mobile 2003 builds on your WM6.1 device?

> * Previously I opened a thread regarding a hard crash
> in any PhoneME build (even non-Windows Mobile builds)
> when you clicked on the space below a standard
> command options menu. Is there a way to prevent this
> crash for the Windows Mobile builds?

I have not looked into it. It may be a platform generic issue.

> Thanks all for any help. Especially to Davy who
> appears to have done much of the Windows Mobile work.

Davy