However, the reduced size of the device, which makes it easier to carry in one hand, as well as an opening of Maemo to a broader audience has brought interest from many users have in having wider support for portrait mode in Fremantle.

Currently, applications can be designed to work either in landscape or portrait mode, and the methods to do so are available to developers wishing to implement them, but portrait mode is not mandatory for development.

The implementation of Portrait Mode across the whole Fremantle UI is a complex task, which will require skills from UI designers, software developers and some intensive, and possibly, time consuming, work process. It is currently unknown if Nokia is going to add Portrait Mode for Fremantle by themselves. In case they aren't, members of the community are interested in working to address this issue.

There are many challenges to add portrait mode to Fremantle:

Challenge 1: The UI has to be designed for it. This includes the re-designing of the dashboard for portrait mode, and if necessary, re-positioning of the on-screen buttons, icons and shortcuts when the user changes from landscape to portrait in the different menus and sections of the OS.

Challenge 2: The widgets: The default desktop is clean, which allows the user to install the widgets in the way he finds more comfortable, in any position in the screen. This implies the development of a method to change the widgets from their landscape position to portrait in a friendly and coherent way.

Challenge 3: A landscape input method has to be designed and developed. This would mean the addition of a portrait on-screen keyboard. This keyboard may be numeric (like a phone) or qwerty. It would need text prediction and correction capabilities. From the visual standpoint, it would be visually pleasing for it not to cover the whole screen and to be semi-transparent.

Challenge 4: Some applications will have to be re-designed for Portrait Mode, or another applications with similar functions will have to be developed and promoted (browser, media player, among others).

The Maemo Merchandise Shop (MMS) can start with the regular common stuff like T-shirts, tea/coffee mugs, water bottles, usb drives, caps, stickers, etc.

This can be done either by Nokia or by someone interested/experienced in the community. They can do this either for-profit or not-for-profit.

Throw in your votes if you think this is well-worth the effort. Enough votes might turn this into reality!

This item is duplicated - I am marking this one as duplicate since it has no solutions to it.

Following the example of stackoverflow.com, it would be more useful to have the most 'useful' (thanked) responses appear first - allowing the reader to process this info on the first couple pages (the most likely to be read before running out of patience).

its also a very good idea to have  option to switch between folder view and threaded view ,,,why?

1-becouse some of the messages aren't actually related together but they are from the same sender, 

and some of the messages may content an bank pin number for example and u may want to access this message directly so u want to save it in customized folder created by your self

2- Draft folder very important folder and must have. for example: you are writing message and have to get a number or link or whatever from another app or even from outside,  so u save the massage till u get what u need or till the time is correct to send it maybe after 2 day u should have the ability to save another one without erasing that one this is what called draft folder.

So it may be as follows

U have the inbox folder , out-box , sent-item , and draft with ability to create a new folder to sort some of the messages by your own but in the inbox folder u got the option of having the messages sort by date or by sender witch it (threaded view)

Desired:

- UPNP control point (command sinks to start playing from sources)

- UPNP server (sourcing to other devices)

- Playing from UPNP sources (already implemented)

I can see how making this as an widget will present problems, But if it's an app that always run in the background and then pounce into action when a Message is received we should be able to have something like the concept.

It would have to have it's own full screen application, perhaps masquerading as a desktop screen by copying the same background on the fly.*

I am no programmer, So I'm clueless. But any theory's are welcome