| Newsgroups |
gmane.comp.mobile.bitpim.devel |
| Message-ID |
<[email protected]> |
> 'body': [ {'type': 'text', 'data': 'foo bar'},
> {'type': 'audio', 'format': 'qcp', 'data': buffer(....)},
> {'type': 'video', 'format': 'avi', 'data': buffer(....)}
> ]
I vote for this format.
>So the question is if this is overdesigning and abstracting too far,
>or if there is merit in the code and schema behind memos and SMS
>being shared, as well as some of the UI code.
I agree that a memo can be a type of SMS or MMS, and this design can be extended for SMS and MMS (including sharing storage and UI code). But at this point, I'd like to keep them separate. Furthermore, right now we already can download some MMS components such as images and videos (albeit soundless on certain phone models :-), so a different question might be what else do we need or can we provide with a SMS/MMS tab?
-Joe Pham
______________________________________________________________________
Speed up your surfing with NetZero HiSpeed.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.netzero.com/surf to sign up today!
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click