porting

Qt3 used to provide QMenuBar::insertItem with QWidget* parameter. This way any custom widget could be added to menu bar - for example a clock-widget. In Qt4 there is no such overloaded method. What would be the best way to reach the same goal - adding custom widgets to a menu bar? The custom widgets should be integrated in the layout of menu bar. Does anyoune knows the background, why this overload of insertItem was removed in Qt4 API? Best regards. there's a QMenuBar::addAction ( QAction * action ) method, to add an arbitrary QAction to the menu bar. For example, it could be a QWidgetAction ,

I have a large codebase that targetted Flash 7, with a lot of AS2 classes. I'm hoping that I'll be able to use Flex for any new projects, but a lot of new stuff in our roadmap is additions to the old code. The syntax for AS2 and AS3 is generally the same, so I'm starting to wonder how hard it would be to port the current codebase to Flex/AS3. I know all the UI-related stuff would be iffy (currently the UI is generated at runtime with a lot of createEmptyMovieClip() and attachMovie() stuff), but the UI and controller/model stuff is mostly separated. Has anyone tried porting a large codebase of

I would like to port Firefox OS to my device (that is not supported by Mozilla but it has Android 4.2). I've read from net that some of the drivers haven't been developed yet, but if FFOS uses the kernel from Android, then it can load the drivers from my Android ROM, right? From this point, my real question is: if I build my FFOS ROM correctly, would I still have some bugs from hardware/drivers? Thank you! Leakspin, I'll try to give you some context on whether it's doable, and what has been done yet. if FFOS uses the kernel from Android, then it can load the drivers from my Android ROM, right?

Hi I am trying to modify the statusbar icon in android. The file, statusbar_background.9.png is to modified. 1. But could some one suggest me how to make it transparent? As for the customization, can we resize status bar width to a relative size? means,based on number of icons present on the screen? I am modifying the file /frameworks/base/packages/systemui/src/com/android/systemui/statusbar/statusbarservice.java Please give me some suggestion Thanks Ab user637465 Finally I found the answer for my question. I changed the following: android:background="@drawable/statusbar_background" to android

I've deloped an Android game which supports almost resolutions in the market (240x320, 320x480, 480x800, 480x854, 600x1024). My problem is when I'm trying to support tablets, I don't understand why Android divide the resources in different folders (hdpi, ldpi, mpdi, large-mdpi, ...) when that qualifiers isn't useful! I have several graphics sets (according width) but I'm going crazy, for example, with the tablets 480x800 with density mdpi or ldpi! It's is impossible reach every device. So, do you know any way to divide drawables/bitmaps in folders but only accesible through resolution?? Yes, I

I'm using an application developed in Sun Solaris 8 and it depends of the architecture SPARC ( the application using some librairies of the system Solaris 8) . Is it possible to export that application from SPARC to intel x86 ? Can i export also in another OS like Ubuntu, Windows or other ? I hope that was clear and if you need more information i'll try to clarify. Thanks. I'm assuming we're talking about a native application here (a machine code binary). Short answer: No to both questions. Long answer: Is it possible to export that application from SPARC to Intel x86? Yes, but that would

Chrome I have a Chrome Extension that behaves like a web app (apart from using chrome.* APIs and Cross-Origin Requests) with multiple html pages which all use the background.html to communicate with a NPAPI plugin. The extension's structure (from the extension's root) is as follows: background.html plugin/ (NPAPI plugin bundles) frontend/ main.html foo.html bar.html .. The background.html is loaded upon extension install and loads the NPAPI plugin, running indefinitely (until browser closes or extension is deactivated/removed). Upon clicking the extension's toolbar button, main.html is opened,