TMW in iphone

[Shikamaru]

Can i instal TMW on iphone?? (i think not) so if not, its much hard to do a version for iphone?

[Crush]

The digital restriction management system of the iPhone makes it impossible to install any applications not ratified and signed by Apple (unless you hack it). To get a program signed by Apple you have to pay a "iPhone Developer Program fee".

Congratulations for paying money for a device where the manufacturer decides what sofware you are allowed to run on it.

[Shikamaru]

And on the Samsung Omnia??? Is it the same?

[Shikamaru]

Can you asnwer me Crush?pls

[Shikamaru]

Say me if any phone in the world can get TMW

[Jaxad0127]

Phones running Android can probably handle it, given they have enough storage for everything.

[Crush]

I don't know anything about the Samsung Omnia besides what you can read on Wikipedia and I don't own any smartphone myself, so I can not give you a definite answer.

But when a device can run any other homebrewed applications written in C++ and based on SDL it is not unlikely that TMW can run on it.

But being able to run TMW does not also mean that it is playable. To really enjoy it you will also need a QWERTY keyboard, an equivalent to a mouse and a screen with a resolution which is large enough to show the larger gui windows. I recommend at least 400 pixels width and height, and even then you should know the key shortcuts for all gui windows by hearth.

Note that this only applies to the unchanged TMW as it is now. Thanks to the open source development model anyone can modify the TMW client and distribute the modified version. So when you want a version of TMW which is playable within the restrictions of your system (small screen, exotic input methods etc) you can ask someone who has experience with developing software for said system to create a TMW fork which is modified to be usable on it.

[Crush]

When I would want to create a fork for a small screen device (not that I have the intention to do so) I would first start with changing the engine from 32x32 pixels per tile to 16x16 tiles. I would do this by scaling all images to half their size when loaded. All pixel values in xml files (animations, particle effects etc.) would also need to be halved when loaded. I would recommend to do these modifications of the content at load-time because distributing already modified content together with the client would break the existing auto-update system.

Then I would rework the layout of all GUI windows for the smaller screen size. The buttons in the upper right corner should be replaced with a drop down menu (or any other solution which keeps them out of sight when not needed).

The controls would have to be reconceptualized for the input tools of the device. The device might have no standard keyboard but only a number pad, no mouse or only a mouse but no keys (touchscreen). So some creative thinking might be required here.

And last but not least I would replace the font file with something optimized for small screens so that I can use a font size which is as small as possible.