Все темы

Совершенно потрясающий новостной блог. Рекомендуется к прочтению перед завтраком, обедом и ужином вместо всех прочих новостей, особенно ж%поголикам, эмо-патриотам и т.д.

http://sdelanounas.ru/

Зафрендить в ЖЖ:
http://community.livejournal.com/sdelano_u_nas/

Видео

Here's a tool which allows to debug native-code Android applications when GDB does not work. It is not so quick to use as a normal debugger but it usually works well. The repository contains function call history writer and an utility to convert it into a human-readable text and generate stack trace for the moment of crash, for all threads. Please find more information in the how-to file provided.

http://gitorious.org/android-instrument-function-debug

Катастрофа самолета Ту-154М № 101 Республики Польша

Yesterday I finished basic integration of "Lite" plugin and QtAndroidCore library yesterday, so now it should be working out of box. "Lite" is a new single-window plugin written by our team (the windowing part is done by marflon, actually) from scratch. There's a separate version of QtAnimatedTiles which builds for Lite, however, differences with the other version are tiny (just 2 lines in Java code and different app name in manifest) and I will take out the old one soon. Also, "Lite" will be the default plugin. mw_grym will be probably discontinued later, unless it will be revived for OpenGL support (not sure it won't be better to add support into Lite instead).

For these who didn't read my previous post on QtAndroidCore, it's the library which integrates Qt and Android except for windowing system and functions which definitely should go into QtMobility (like positioning, cell network functions, and etc.)

Both mw_grym and lite support all additional functionality implemented in QtAndroidCore and core Java - just check the sources to get the impression of amount of stuff needed to be done in addition to windowing layer to make a real-life application working.

·· [Read more · Читать дальше] ·· »»»

Видео
Via technoshiza.