Join Today
+ Reply to Thread
Results 1 to 3 of 3
  1. Default Building E680i's native applications is simple, however

    As you know, Motorola did not use Trolltech's Qtopia to build applications for E680i. They use EZX Application on top of Trolltech's embedded Qt. Here is the sofware structure:

    EZX Aplication
    |
    Qt embedded
    |
    Linux


    So building E680i's native applications is simple, things you need:

    qt-embedded-2.3.6
    E680i's EZX header files
    E680i's libezx* libraries
    linux-arm-gcc binaries
    tmake 1.8

    Unfortunately, Motorola did not public E680i's EZX header files. Without E680i's EZX header files, we can not use qt designer to build E680i native applications. We will not know how to handle E680i touch screen or sound...
    because we dont know ZApplication objects and its function declaration in the header files.


    EZX OPIE project team has worked around to build applications for E680i, building E680i applications base on EZX's QtPalmtop without E680i header files.

    I believe they are facing the same problem right now. Without knowing E680i's EZX header files, they can not active Opie to support E680i touch screen, sound in their applications!

    Why Motorola did not public E680i's EZX header files? If I have E680i header files, my first qt application will be a scientific calculator application support touch screen on E680i. I also believe others will build thousand native applications for E680i.

    Why Microsoft and Symbian users can easily build their own native applications for their smartphone? Why Motorola did not want us to build native applications for Linux phone? Why Motorola makes such a lovely open-source Linux phone become closed-source?

    I hope one day, Motorola will pay attention to this www.motorolafans.com and read this article. I hope Motorola knows that their fans, their supports are facing and suffering the problem on building native applications for their phone. I hope Motorola will public E680i's header files and release documents on how to use E680i's ZApplication objects and its functionaries.

    In conclusion, smartphone on Linux platform can not compare to Symbian's, Palms' or Windows Mobile's, each with thousands of native applications.

    I give up my attempt to build E680i native application without Motorola's support. E680i is just a smart phone without support. It is just a phone, no need to spend so much time for it.

    We have to sit and wait Motorola China releases new firmwares, new native applications by themself.





    Freedom from lust is happiness in the world,
    the going beyond all sensual desires.
    But the crushing out of the conceit "I am"-
    this is the highest happiness.

  2. #2
    Join Date
    Feb 2006
    Location
    Beijing China
    Posts
    6

    Default Re: Building E680i's native applications is simple, how

    motorola is working on opening its native SDK. However it takes time. There're much need to be thought of, like compatibility, etc...

    Hopefully, this work can be done by next year

  3. #3
    gtada Guest

    Default Re: Building E680i's native applications is simple, how

    Swingseagull:
    I'm curious... where did you find information that "Motorola is working on opening its native SDK"?


 
+ Reply to Thread

Similar Threads

  1. Building own charger for e680i
    By deswong in forum E680i General Chat
    Replies: 13
    Last Post: 11-10-2008, 07:13 AM
  2. Running native applications...
    By mserougi in forum A1200 General Chat
    Replies: 3
    Last Post: 09-24-2006, 06:54 AM
  3. Replies: 9
    Last Post: 01-08-2006, 04:01 PM
  4. A simple way to fix c5ab's contact issue
    By chiennk in forum E680i General Chat
    Replies: 8
    Last Post: 12-29-2005, 09:44 PM
  5. Workaround to avoid all native apps be 'AppName'
    By rhizod in forum E680i General Chat
    Replies: 9
    Last Post: 07-19-2005, 01:14 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Single Sign On provided by vBSSO

Search Engine Optimization by vBSEO 3.6.0 RC 1