[Scummvm-devel] Status of ScummVM Android port

[Oystein Eftevaag]

On 09.03.11 05.32, Max Horn wrote:
> Am 07.03.2011 um 19:38 schrieb Oystein Eftevaag:
>
>> On 01.03.11 12.54, Max Horn wrote:
>>> P.S.: Actually, I guess the android port is not quite alone here. E.g. I am still waiting for Oystein to reply to the various iPhone bug reports I pointed him to several times now; seems my emails to him always get lost, even half of those sent via -devel :(. Oystein, should you receive this for a change, here is the relevant link once again:<https://sourceforge.net/tracker/?group_id=37116&atid=418820&status=1&keyword=iphone>
>> Sorry for the delayed response; I just got back from GDC (Ron Gilbert's
>> Maniac Mansion postmortem was excellent by the way :) ).
>>
>> Yep I've seen them, it's just been way too long since I've been able to
>> find both the time and the motivation to do much at all with the iOS
>> port.
> Sad to hear that :(, but it happens to all of us at some point, I guess. I don't find much time for ScummVM myself either. :/
>
>> Last major update I did last year was to make the overlay use the
>> native device resolution, but there's still issues to work out there
>> (hence why the nightly trunk builds are crashing). That's probably the
>> biggest issue right now other than the mouseclick issues in the Gob
>> engine; the rest should all be minor.
> OK... Is this documented somewhere, or easily verifiably?
>

The crash was fairly reproducible I think, but it's a while since I 
looked at it. Some resolution-related assert in the GUI system somewhere 
(almost certainly caused by the backend though).

I thought it was this: 
http://sourceforge.net/tracker/?func=detail&aid=3087507&group_id=37116&atid=418820
But reading the comments, it's no longer happening for original 
reporter, so it may be a non-issue now. If so, the mouse-click issue for 
Gob is the only release-critical one I think.

>> If someone else wants to take a crack at it I'll gladly help with the
>> setup of the toolchain (there's instructions on the wiki), or get the
>> xcode project up to speed.
> Right, having a version of create_project with xcode support (for iPhone primarily, but extra support for OS X won't hurt either) would be super-helpful in this regard.
>
Absolutely. The current xcode project can build both iOS and OS X 
builds, but yeah keeping it manually updated obviously isn't going to 
work very well.

>> Otherwise it'll have to wait until things
>> calm down on my side.
>
> We definitely should try to find somebody to (co-)maintain the iPhone port then. Considering how active the iPhone community is, I am quite hopefully that this would be possible; we just have to let people know that we are looking for help. So, a news item, a forum post, etc., for this would be good.
>

There's a whole heap of improvements that can be made to the port, 
particularly in terms of user friendlyness (improving controls and 
adding some GUI for them), so more eyes on this would be great.

> The question is: Who is gonna write it?
>
> Bye,
> Max
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Scummvm-devel mailing list
> Scummvm-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scummvm-devel