Maemo Wiki Mirror - User contributions [en]

MicroB tweaks

2010-11-29T13:02:06Z

173.212.211.28: /* Also see */

(Maemo 4 only. Maemo 5 status not clear at this time of writing.)

MicroB is the default browser in Maemo 4. While there are alternative browsers for Maemo 4 such as [[Tear]] and [[Firefox mobile]] some users prefer MicroB.

It is possible to tweak the performance and behaviour of MicroB. Please continue to read for some suggestions.

MicroB, being a [[:wikipedia:Mozilla|Mozilla]] based browser, has the same settings as Firefox. These settings are stored in the file <code>/home/user/.mozilla/microb/prefs.js</code>. Only a few of these settings can be changed from the MicroB menus. To change the others open the url about:config in MicroB to edit them one-by-one, or edit prefs.js.

== Settings ==

Even though many of the settings only make sense on a notebook or desktop pc, there are some that can be useful for the Internet Tablets.

Removes cookies when closing MicroB (allow only for session). This only applies to new cookies. To also delete earlier cookies go to Tools -> clear ->cookies in MicroB:

network.cookie.lifetimePolicy 2

Activates smooth scrolling. This is useful when the [http://www.internettablettalk.com/wiki/index.php?title=Internet:Microb_Hardware_Key_bindings d-pad is configured for scrolling]:

general.smoothScroll true

Lets you select the contents of the urlbar with one click, instead of the default triple click:

browser.urlbar.clickSelectsAll true

Sets minimum and default font size in points, in this case 20 points. Depending on the language you use also set font.min-size.fixed.ja (japanese) etc.:

font.min-size.fixed.x-western 20
font.min-size.fixed.x-unicode 20
font.min-size.variable.x-western 20
font.min-size.variable.x-unicode 20
font.size.variable.x-western 20
font.size.fixed.x-unicode 20

Speed tweaks specific for the Internet Tablets:

browser.cache.memory.capacity 8192
browser.sessionhistory.max_entries 4
content.notify.interval 1250000
content.notify.ontimer true
network.http.max-connections 4
network.http.max-connections-per-server 4
network.http.max-persistent-connections-per-server 1
network.http.pipelining.maxrequests 1000
network.http.pipelining true
nglayout.initialpaint.delay 2000

For an explanation of these and other settings in about:config see [http://www.tweakguides.com/Firefox_10.html this article.]

== Editing prefs.js ==

To edit it on the tablet itself:

* if you don't have root access already install 'rootsh' through the application manager
* if you don't have 'nano' installed get it with application manager
* close all MicroB windows
* open xterm
sudo gainroot
invoke-rc.d tablet-browser-daemon stop
exit
cd .mozilla/microb
cp prefs.js prefs.js.backup
nano prefs.js

* scroll to the line you want to change/add and type the changes. Be careful to use the exact format user_pref("nameofthesetting", thevalue); . If you leave out one ';' , '(' etc. then the settings in the file will be ignored by MicroB. If a setting does not exist then add it yourself.
* to save the file click ctrl, x, y, return.
sudo gainroot
invoke-rc.d tablet-browser-daemon start
exit

If you decide to edit prefs.js on your own computer be sure to:

* run as root "invoke-rc.d tablet-browser-daemon stop" before editing and "invoke-rc.d tablet-browser-daemon start" after editing.
* use an editor that uses linux style line endings
* restore the right permissions and ownership of the file when you put it back

== Settings that will not stick ==

Some settings get reset when MicroB starts. This is unfortunate, but you'll have to live with it.

[[http://mxr.maemo.org/garage/source/browser/mozilla/trunk/microb-eal/include/common.h#70 list of interesting strings]]

Replaced:
* snav.keyCode.modifier
* general.useragent.locale
* general.useragent.vendor

Randomly replaced with the value from plugins.flashhack:
* ftv.enabled
* snav.ignoreTextFields
* snav.disableJS
* layout.full.zoom.mode.fast
* plugin.default_plugin_disable
* security.warn_entering_secure
* security.warn_leaving_secure
* security.warn_submit_insecure

For any such setting, you can use bookmarks to
about:config?prefname={name}&prefvalue={value}&sprefname=donotomit

... and just tap on them or if you only have one you can make it your home page.

== How to restore the default settings==

If you mess up prefs.js or just want the defaults back then either restore the backup file you just made, or delete prefs.js file so MicroB will regenerate it with default settings.

to restore the backup:

* close all MicroB windows
sudo gainroot
invoke-rc.d tablet-browser-daemon stop
exit
cd .mozilla/microb
cp prefs.js.backup prefs.js
sudo gainroot
invoke-rc.d tablet-browser-daemon start
exit

...or to delete prefs.js:

* close all MicroB windows
sudo gainroot
invoke-rc.d tablet-browser-daemon stop
rm /mozilla/microb/prefs.js
invoke-rc.d tablet-browser-daemon start
exit

== Also see ==

* [[Ad_blocking]]
* [http://www.internettablettalk.com/forums/showthread.php?t=24405 Selectively disable JavaScript in MicroB]
* [http://browser-extras.garage.maemo.org Browser-Extras, for MicroB extensions]
* [http://www.vistatweaks.net/ Windows tweaks]

[[Category:Users]]
[[Category:Web]]
[[Category:Power users]]

MADDE/QtCreator integration for Mac

2010-09-15T12:21:48Z

173.212.211.28: /* Mac configuration */

{{MADDE}}

= QtCreator and MADDE on Mac OS X =

This is a guide on how to enable MADDE in QtCreator. This is part of the technology preview. After following this guidance you are able to build your sources within QtCreator for your device, and deploy, run and debug your applications with few mouse clicks from your OS X installation.

Requires:

* [[MADDE]] installed on your Mac
* If you want to compile your code natively then you have to have [http://developer.apple.com/tools/xcode/ XCode] installed on your machine

== Install latest QtCreator on your Mac ==

'''You cannot use the latest official QtCreator for this. The version has to be >= 1.3.80! For these instructions the version of the 2010-03-04 is used!''' Find the latest build of QtCreator for Mac OS X here:

http://qt.nokia.com/developer/qt-snapshots

or here

[http://www.mac-how.net/ mac how to]

== Add Qt for Maemo5 ==

You can change the configuration of the Qt-version in your QtCreator installation by clicking:

QtCreator -> Preferences -> Qt4 -> Qt Versions

'''Tip:''' If you do not see any Qt version by default here, you most likely haven't installed the needed Qt libraries to compile your Qt application for your Mac.

In the next step you have to add the Qt version for Maemo5 to the configuration of QtCreator. It is needed to compile your sources for your Maemo device. Click on the "+" in the upper-right corner. The configuration form will ask you to enter a "Version name" and to locate "qmake". You can find it in your MADDE installation folder under:

<MADDE_folder>/targets/<target_name>/bin

For the '''standard installation''' it would be for example:

Version name: Maemo Qt4.5
qmake Location: /Users/<username>/.madde/0.6.14/targets/fremantle-qt-0951/bin/qmake

'''Tip:''' You cannot find the folder if you click on "Choose...", as it is hidden. But after entering "/Users/<username>/.madde/" in the text-field "qmake Location" you can select the rest via the "Choose..." button.

Now you will see Qt for Maemo as a new Qt Version in Qt Creator. But first you will see the red cross next to the Qt Version in the column "Debugging Helper". The last step you have to do now is clicking on "Rebuild" and after a while (you can follow the status in the QtCreator main window) it should look like this:

[[Image:01_mac_qtcreator_madde.png|500px]]

== Configure device run-time in Qt Creator ==

After setting up the connection between your Mac and your device, you will be able to compile, deploy, test and debug your application with a single mouse-click. The description shows the configuration for USB-networking and WLAN and is for each divided into two parts. It shows:

* what to install on device, and
* how to set-up your Mac

=== General device set-up ===

Please find the instructions on how to set up the device runtime from here:

* [[MADDE/QtCreator_integration_for_windows#Install_the_client | Install the client]]

=== Connect via USB-networking ===

==== Device configuration ====

The following guide shows you, what to do on your device to set up the USB connection. This has to be done '''before''' you connect your device with the Mac:

* [[MADDE/QtCreator_integration_for_windows#Configure_the_client_for_USB | Configure the client for USB networking]]

==== Mac configuration ====

Connect the device with your mac, open the network configurations out of the upcoming dialog and enter the following details. Finally click on "Apply". Then the connection should be established.

[[Image:02_mac_usbnetwork.png|400px]]

'''Possible connection problem:'''

In some versions of Mac OS X ''' < 10.5.8''', the system selects the [http://docwiki.gumstix.org/index.php/Setting_up_USBnet#USBnet_on_Mac_OS_X_10.5.X wrong interface] by default, so that you won't be able to connect your device as a network component with the Mac via USB. OS X detects the N900 in those cases as a modem and not as a network device. Follow these instructions to install the necessary driver information:

http://bugcommunity.com/wiki/index.php/Start_Guide_Mac_OS_X_10.5

[http://www.mac-how.net/article/Configuring_your_Mac_Mail_Client/ Configuring your Mac Mail Client]

After installing the patch, you can connect the device and configure the network interface as shown in the screen-shot above.

=== Connect via WLAN ===

If both devices are connected to the same wireless network the configuration is a bit easier, but be aware that the IP address might not be the same all the time. This effects the set up of your QtCreator configuration.

==== Device configuration ====

Please open the mad-developer application. If you are connected already to the wireless network, you can find the IP address in the initial window of the application:

[[Image:10_mac_mad-dev_wlan.png|300px]]

==== Mac configuration ====

Please just make sure, that your Mac and device are connected to the same network.

=== QtCreator Configuration ===

After the connection between your PC and the device is set up, you can configure QtCreator to deploy and run the built applications on device. You can add your device in the configuration. You will find it in:

QtCreator -> Preferences -> Projects -> Maemo Device Configurations

First get the password from the Mad Developer application. You get it by clicking on "Developer Password" in the main view. '''Be aware''' that each time you click on the button, a new password will be created and that the password is only valid for the time it is shown in the application.

[[Image:04_b_client_ready.png|300px]] [[Image:05_client_pw.png|300px]]

====Instructions for USB-network====

Add the password and all the data you see in the screenshot below. Check the box, that you want to use the password as the authentication method. After that click on "test" and see if the connection can be set up.

[[Image:03_mac_qtcreator_usbnetwork.png|300px]]

====Instructions for WLAN====

If your device is using the WLAN interface, please enter the IP address you can see in the mad-developer application on device.

[[Image:04_mac_qtcreator_wlan.png|300px]]

'''Tip''' You can use your ssh key for the connection. Click on "Deploy Key ..." and select your key. If the other settings are correct the key will be automatically deployed on your device, so that you don't have to worry about the passwords anymore.

== Use Maemo5 build settings ==

Now all the configuration is done and you can select Maemo as a build configuration. If you have a project, which you want to compile for Maemo, then click on the project button in the menu of the left side. Now you should seen a screen, like in the screen shot below. If you have the Qt libraries installed, then you will have the "Desktop" as the default option selected.

[[Image:06_mac_qtcreator_init.png]]

'''Tip:'''

* It might be that you don't see the "Desktop" widget in your project configuration. In this case it might be that the configuration of the MADDE is not correct, or that a little bug prevents the widget from showing up. In this case click on "Dependencies" and then go back to "Build".

* If you start a new project you can add the Maemo build-configuration at the beginning:

:[[Image:05_mac_qtcreator_select_madde.png|300px]]

Now press the plus in the widget, which shows, that "Desktop" is selected as default. This should open a new dialog, where you select "Maemo Device". After that you will find a new build-configuration:

[[Image:07_mac_qtcreator_maemo_build.png]]

Now click there on "Run" and select your device, which you have configured before. In the example it was called Maemo5 Device.

[[Image:08_mac_qtcreator_maemo_run.png]]

Finally you can now set in the down left corner, which build configuration you want to use:

[[Image:09_mac_qtcreator_final.png]]

Now you can click on the run button, and your application will be automatically compiled for the Maemo device, delpoyed, and started.

[[Category:Development]]

Internationalize a Python application

2010-07-15T12:14:50Z

173.212.211.28:

This page explains step by step how to add support for translations in a Python application for Maemo.

There are already some [http://www.learningpython.com/2006/12/03/translating-your-pythonpygtk-application/ tutorials online] about how to internationalize (i18n) python applications, but i find them difficult to follow and they lack some needed code and final tricks to make everything work fine.

To support i18n we need to accomplish 5 tasks:
# Define correctly a function '_()' that translates strings
# Mark the strings in the code with that function
# Generate a template for the translators
# Add translations
# Include the translations in the installation

== The overall process ==

From the source code, using a command line tool, we will generate a ".pot" file. It is plain text file containing all strings that need translation in the project. This .pot file only needs to be generated/recreated when the strings change in the code (and _not_ in every build!). There is only one .pot file per project.

Then, from the .pot files and using another command line tool, we will generate the .po files for each language. There is one .po file per language, and it is the file that the translators need to complete. Both .pot and all .po files should be committed in the repository.

But once your program is running, it doesn't use directly .po files, but a binary (compiled) version of them: the .mo files. These .mo files must be re-created on build time (when creating the package) and installed in the right location in the system. These are generated files, so don't commit them in the repository.

From the code point of view, you just need to call few functions to tell gettext where are the translation files, what language do you want to use (usually the locale of the environment), and then it will use its implementation to find the right string.

Ok, this is what we need to do. Let's code.

== Configure gettext Define the '_()' function ==

If you don't care too much about the details, just copy this [https://garage.maemo.org/plugins/ggit/browse.php/?p=mussorgsky;a=blob;f=src/i18n.py;hb=HEAD i18n.py] file in your src/ directory ('''change the APP_NAME''' variable there!), and in every .py file in your module that needs to translate any string, add these lines at the top:
<source lang="python">
import i18n
_ = i18n.language.gettext
</source>
Done. If you are curious about what is going on there, the file has plenty of comments explaining every line.

== Mark strings for i18n ==

This is one of the easiest parts. Browse the source code files that show something on the screen, and wrap the visible strings (window titles, dialog titles, notifications, labels, button labels and so on) with the '_()' function.

For example:
<source lang="python">
# import the _() function!
import i18n
_ = i18n.language.gettext

class Example (hildon.StackableWindow):

def __init__ (self):
hildon.StackableWindow.__init__ (self)
self.set_title ( _("All music") ) <------- ADD THIS!
</source>
== Generate template for the translators ==

Create a po folder in your project (usually at the same level as src/) and run the following command from the top directory of your project. You can do this inside or outside Scratchbox, there is no difference.

xgettext --language=Python --keyword=_ --output=po/PROJECTNAME.pot `find . -name "*.py"`

It will parse files, written in Python, looking for strings marked with the keyword (function name) '_' and saving the output in a file called 'po/PROJECTNAME.pot'. The list of files is the last argument. I like to use "find", but you can manually put a list of files there.

That command will generate the .pot file. Easy, isn't it?

== How to add translations ==

Now you want to get a translation in an specific language. You need to generate a .po for it.

Go to the po/ folder and run this command (again, inside/outside scratchbox doesn't matter):

msginit --input=PROJECTNAME.pot --locale=LOCALE

For instance, if i want a .po file for the spanish translation of my project Mussorgsky, i write:

msginit --input=mussorgsky.pot --locale=es_ES

It will generate a file "es.po" and translators can/must work on that file.

'''IMPORTANT''': by default the generated .po file declares its charset as ASCII. This means that translations with non-ascii characters will provoke an error in the program. To solve this, set the charset to 'utf-8':

"Language-Team: Spanish\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n" <--- THIS MUST BE UTF-8

If you don't know the locale of a language, can check [http://www.roseindia.net/tutorials/I18N/locales-list.shtml this list].

== Include translations in your installation ==

This part is more tricky, because it depends on your build system. I'll explain how it goes with the common python 'distutils' (what makes the usual ''python setup.py install'' command work). In distutils all the magic happens in the ''setup.py'' file.

First of all, if in the previous steps you have added the i18n.py file to your source tree, don't forget to include it in your data_files list!

Then, copy to the root folder of your project the file [https://garage.maemo.org/plugins/ggit/browse.php/?p=mussorgsky;a=blob;f=msgfmt.py;hb=HEAD msgfmt.py]. It is a program that translates the .po files into the binary .mo files that the application needs.

In your setup.py file you need to add all this code. It "overloads" the default 'build' and 'install' instructions to include the translations in the process. Now in 'build' time it will generate the .mo files (using the msgfmt.py we added just now), and in 'install' time it will include the '.mo' files in the data_files list. The code is copied from this a [https://garage.maemo.org/plugins/ggit/browse.php/?p=mussorgsky;a=blob;f=setup.py;hb=HEAD setup.py] file.

<source lang="python">
from distutils.core import setup
from distutils.core import setup
from distutils import cmd
from distutils.command.install_data import install_data as _install_data
from distutils.command.build import build as _build

import msgfmt
import os
</source>
This command compiles every .po file under the po/ folder into a .mo (the .mo files will be under build/locale/)
<source lang="python">
class build_trans(cmd.Command):
description = 'Compile .po files into .mo files'
def initialize_options(self):
pass

def finalize_options(self):
pass

def run(self):
po_dir = os.path.join(os.path.dirname(os.curdir), 'po')
for path, names, filenames in os.walk(po_dir):
for f in filenames:
if f.endswith('.po'):
lang = f[:len(f) - 3]
src = os.path.join(path, f)
dest_path = os.path.join('build', 'locale', lang, 'LC_MESSAGES')
dest = os.path.join(dest_path, 'mussorgsky.mo')
if not os.path.exists(dest_path):
os.makedirs(dest_path)
if not os.path.exists(dest):
print 'Compiling %s' % src
msgfmt.make(src, dest)
else:
src_mtime = os.stat(src)[8]
dest_mtime = os.stat(dest)[8]
if src_mtime > dest_mtime:
print 'Compiling %s' % src
msgfmt.make(src, dest)
</source>
Now we append the previous command to the 'build' command.
<source lang="python">
class build(_build):
sub_commands = _build.sub_commands + [('build_trans', None)]
def run(self):
_build.run(self)
</source>
Installation time: put every .mo file under build/locale in the data_files list (the list of things to be installed) and call the default 'install' operation
<source lang="python">
class install_data(_install_data):

def run(self):
for lang in os.listdir('build/locale/'):
lang_dir = os.path.join('share', 'locale', lang, 'LC_MESSAGES')
lang_file = os.path.join('build', 'locale', lang, 'LC_MESSAGES', 'mussorgsky.mo')
self.data_files.append( (lang_dir, [lang_file]) )
_install_data.run(self)
</source>
Finally, add the new commands in distutils...
<source lang="python">
cmdclass = {
'build': build,
'build_trans': build_trans,
'install_data': install_data,
}
</source>
And don't forget to add this in your setup function, in the setup.py
<source lang="python">
setup(name = 'your project',
...
license = 'GPL v2 or later',
data_files = DATA,
scripts = SCRIPTS,
cmdclass = cmdclass <----- DON'T FORGET THIS
)
</source>
Ok, now everything should be ready. If you run

python2.5 setup.py build

the terminal will print things like

compiling es.po
compiling de.po
...

Usually dpkg-buildpackage uses python2.5 setup.py build and install, so everything should work out-of-the-box with your previous package configuration.

Feel free to complete/correct this wiki page with your own experience.

Take a look [http://www.mac-how.net/ how to uninstall applications on mac]

[[Category:Internationalization]]
[[Category:Development]]
[[Category:HowTo]]