Hi, thanks for the reply.
Am Mittwoch 29 Dezember 2010 schrieb [email protected]: > 1) These are currently not planned to be released due to limitations of some > of the platforms. Ok, ugly, but we'll have to live with this. So please let me ask the other way round: How are we supposed to handle complex landmarks. Let me give you some examples: - In geocaching, a landmark has attributes (stroller accessible, available at 24/7, not suited for kids ...), complex html descriptions, lists of user comments (logs), relationships to other waypoints, encrypted hints .... How are such complex objects to be used in qt if qlandmark can't handle them? - In OSM a landmark forms the basis of buildings, ways, ... these have a huge number of relationsships, and they also have a huge number of attributes To me it seems the current qlandmark is only usable for a pretty limited number of trivial use cases. Could you give some insight on how you think complex landmarks should be stored by a qt application? My former apps have not used system classes at all for this. Am i supposed to return to that concept for complex applications like geocaching and raw OSM data processing? It would be great if you cound sched some light on how things are supposed to be done. As you see i am willing to do things "right", but i am missing guidance here. Regards, Till _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
