[Adium-devl] Adium iPhone

[Ofri]

Actually, I didn't remember :) Isn't Apollo for iPhone OS v1 only? Did  
that have the same memory restrictions as v2? Anyhow, that does make  
the task seem much more doable than I imagined.

I think that if someone's being serious with making Adium for iPhone,  
there are two main things that need to done:
1. Make libpurpule compile as a static library and see how it  
functions on a device. Maybe using a jailbroken device and a Pidgin  
build to feel the performance?
2. Decide what features does a mobile Adium need. This goes in two  
ways - look at Adium and strip things out, and think about new stuff  
that's going to be useful on the phone.

When these are sorted we can figure out if/what needs to be optimized  
on libpurple's side and start playing with UI mockups.

Just my thoughts, :)
Ofri

On 22/01/2009, at 22:01, Eric Richie wrote:

> On Thu, Jan 22, 2009 at 2:55 PM, Andreas Monitzer <am at adiumx.com>  
> wrote:
>> On Jan 22, 2009, at 20:49, Ofri wrote:
>>
>>> I must say I'll be surprised if libpurple is going -not- going to  
>>> need
>>> some optimization before being useable on the iPhone. That being  
>>> said,
>>> having libpurple optimized for mobile environment is probably  
>>> going to be
>>> very useful in the future for many people (Android, etc :), and  
>>> should be a
>>> challenging task.
>>
>> I smell GSoC...
>
> Anyone, remember Apollo IM? (http://code.google.com/p/apolloim/) They
> were using libpurple on the iPhone.  These were the jailbrake days of
> development so the process would need tweaking but I would imagine it
> would be largely the same.  That's not to say however that it was
> memory efficient, just merely that it was running.  I also seem to
> recall there being other iPhone clients (AppStore ones) running
> libpurple but I could be wrong on that.
>
> -Eric
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com