At the moment the best alternative is the write the application in OpenGL ES or HTML5. The choice depends on the type of application. Both will need a small wrapper on each platform. PhoneGap is a good choice if you go with HTML5.
I'm not sure how viable the OpenGL ES option is for Windows Phone, but then I personally loathe that platform anyway.
As for look and feel consistency, look at Angry Birds to see that that is not needed at all.
KDE is working on a mobile UI: http://plasma-active.org/.
Math in ODF is MathML.
be google
Sorry No constellation prize for you.
Indeed, the comment was not stellar.
That sounds very much like Android Intents and Activities.
An Intent provides a facility for performing late runtime binding between the code in different applications. Its most significant use is in the launching of activities, where it can be thought of as the glue between activities. It is basically a passive data structure holding an abstract description of an action to be performed.
Sarcasm noted.
Most of the price is in getting clean bills into the machine in a secure way and keeping them there until someone makes a transaction.
Still, I prefer paying for that instead of seeing advertising.
Each application on facebook get's a private API. In FOSS, this key is present in the source code. That is not permissible according to facebook terms of service. In effect, they are blocking FOSS software. An alternative is to use a different key for each user.
More info: https://bugs.kde.org/show_bug.cgi?id=276609
But you don't have to live in either. There's a whole life out there where you do not need them.
Who needs noscript when you can use a personal proxy with web configuration interface. That way, I get noscript and requestpolicy in a more finegrained way for all my browsers and need to configure it only once.
I wrote my own with Node.JS and will probably add storage to it at some point. The only downside is that does not work for https connections.
The areas would improve over time by editing. An area or set of areas is, for most topics, an improvement over a single point. Few areas will be perfect, certainly initially, just like the articles themselves are not perfect. But as often, here too perfection is the enemy of success.
Many boundaries are defined by states. In case of disagreement, multiple areas can be mentioned, just like different versions of the facts, with an explanation of the origins, can be present on a Wikipedia page.
The best way forward, is to add support for areas to WikiMedia so people can start improving the pages. The points can also be retained to mean the center of a certain area.
This approach is incomplete though. It create wrong information. No place is just a spot, it's usually an area, some places are a volume. It would be much better to give users the ability to paint an area on the map instead of just one point.
Some examples:
area where a species lives in summer
area of a country or city (London has coordinates 51Â30â26âN 0Â7â39âW, but it covers an area of 1,579 square kilometers)
area of seas and events.
The notion that articles relate to points and not to areas, is a simplification.
There does not seem to be an easy UI for this. Remember: it should be easy for simple users.
Personally I'm more interested in seeing the permissions model of Android applied to a standard Linux Distro, possibly an Android x86 that allows installation through apt-get, or some other repo system. (must be script-able for sys-admin use)
Indeed, the fine-grained permission model of Android should come to Linux.
- One file per application
- Easy to override permissions for application (e.g. restrict net access for an application to a certain IP address or domain or restrict access to the file system to one folder)
Such requests always meet with developers claiming that memory will be used inefficiently, yet, mobile devices work fine this way. It's time Linux was developed to meet the requirements of simple users.
Anyone can make an omelet with eggs. The trick is to make one with none.
