Debugging Your MonoTouch Apps: The Future
One of the "paper cuts" developers have been having with developing their MonoTouch 4.0.x (and earlier) applications is that for some networking setups, the IP of the developer's workstation detected by MonoDevelop and given to the iPhone or iPad device for debugging purposes is not correct. This often happens if the WiFi is a different network than the network that the developer's machine is connected to (although there are other scenarios as well).
Since it does not seem to be widely known about, allow me to point out that current versions of MonoTouch allow developers to modify the IP that the runtime should connect to for debugging via the iOS Settings app found on any iPhone or iPad (or Simulator). You can see a screenshot of this per-App Settings page in the screenshot to the left. Each of these fields are editable, allowing you to override the defaults filled-in by MonoDevelop.
For our upcoming 4.1 release, Rolf Kvinge and I (but mostly Rolf) have been working on improving this. Rolf has modified the code to check the value of the IP provided in the per-App Settings and if it is set to nil or "automatic", the debugger falls back to checking for a file bundled with the app called MonoTouchDebugConfiguration.txt which can list any number of IP's to try and connect to, each one being on a separate line prefixed with "IP: ". For example:IP: 10.0.1.31 IP: 192.168.1.31 IP: 204.11.102.79
The runtime will then attempt to connect to each of these IPs asynchronously until it establishes a connection to one of them (at which point it aborts the other waiting connections). This config file solution will hopefully help simplify things for developers a bit by allowing them to pre-configure which IPs to try for their local network configuration w/o having to manually override the iPhone debug settings on the device or simulator.
For Phase 2 of our plan for World Domination, Rolf is hard at work adding support to MonoDevelop and the runtime to allow for USB debugging which will obsolete the above functionality in future versions where the developer has a MonoDevelop which supports USB debugging. For developers stuck on an older MonoDevelop (like 2.4), the solution illustrated above requires no changes to MonoDevelop and so will be available for use.
Mounting /usr in the initrd
Hi,
I changed the openSUSE mkinitrd to mount the /usr filesystem in the initrd, if /usr is a separate partition. I hope this will calm down some heated discussions about systemd, udev, etc. It’s not 100% ready yet, some setups like root or /usr on nfs or md might not work as expected (*), but the common usecases should be covered. Try updating mkinitrd from the Base:System project and let me know if it works for you. Before testing it, you should do a backup of your initrd:
# cp /boot/initrd-`uname -r`{,.orig}
and create a section in /boot/grub/menu.lst pointing to the /boot/initrd-*.orig file.
Preparing my talk about conflict management for the Desktop Summit
This is my favorite place to prepare my talk for the Desktop Summit in Berlin. It is about conflict management in communities and teams. Watch it on Aug. 6th from 12:00 until 12:30, room: Audimax.
!@#$% Spam...
Sorry for the annoyance, but it's better this way. Given that I'm not blogging too often, this shouldn't be much of an issue anyways.
PackageKit backend for Software Center: short week 9 report
Hi all,
It’s nice to write to you again. I’ve been having a 10 days vacation (that’s why there was no week 8 report), enjoyed it and now I’m back with fresh forces.
This short (started slowly on Tuesday) week’s activity regards:
- almost fixing a bug that prevents my PackageKit software-center from prime time: package information isn’t correctly refreshed after an installation/removal
- starting work on the openSUSE integration (the corresponding Distro class, removal of forgotten apt related imports, dependency identification and testing).
I will continue work on this side and hope that by the end of the next week, will have everything working and up for testing in openSUSE.
Cya
NB: I will have to provide for testing a trunk version of pygobject since a release is delayed by another awaited merge;
A utility for merging configuration / sysconfig files – Week 10 Report

Source: http://www.openclipart.org
Hello again,
this is my report for the 10th week of GSoC. Unfortunately i wasn’t able to create the beta packages i was hoping. There are still some issues to be resolved within the aug_process_tree that hopefully will be solved this weekend.
This week news:
– During some tests i carried out: small errors and space for small tweaks in code was found. Solved all of errors found.
– Code Improvements:
–>New function: struct tree **tree_get_children(struct tree * node)
–>More checks for null values etc in tree matching comparing etc
–>Better handling of comments and null labeled nodes within the configuration files parsed by augeas. I had an idea this week, after discussing with my mentor Michal, the idea was concerning the sorting of the comments and how not to mess with their order in the file. A solution was found based to the idea,at least temporary, and it is already implemented.
– Code Changes:
–>Changed functions:
—->struct tree** tree_child_sort_label(const augeas *aug,struct tree *node) now accepts the tree parent node as a parameter, changes in the code within
—->struct treeMatch* tree_compare_children(const augeas *aug,struct tree **first,struct tree **second) now accepts arrays of struct trees, changes in the code within
—->aug_process_tree still under constant changes.
The reason for all the above changes,the continuous code improvements and the delay in the completion of the aug_process_tree is based mainly due to the reason that i want to create functions that will be further useful by other developers of Augeas and will not just fulfill merging of sysconfig files but it will be possible to used/extended to other configuration files as well.
What is to be done:
-Finish aug_process_tree
-Beta Packages
-Test merging functions
-Code improvements?!
ITR with LibreOffice [India]
The goal of this endeavour is that no person who wants to file ITR and does not have MS Excel should suffer because of this partiality by the Government. But we are still a long way from this. The problem is, every year the form changes, since tax rules change, so this migration is going to be difficult in future. We need to get the Government / IT Department to stop favouring MS Excel. They are only making it harder for non-MS Office users. Kindly lets continue this discussion and effort to put pressure on the concerned people to make a change in this department.
KDE 4.7
According to the KDE Release Schedule today is KDE 4.7 day!!
So Happy KDE 4.7 day to you, I just wonder how many different servers in the world are busily compiling and building software for their respective distributions, I know its currently being built for openSUSE as we speak and should be available in the repositories sometime in the next 6 hours lets just see when the official release announcement comes.
openSUSE The Best Desktop Environment
If you see "Starter Edition" it means that most likely after 60 days you have to pay to upgrade to the full version of the software by purchasing a key card from either the supermarket or pc store.
Lets add onto this all the new hardware your going to purchase, Printer, Broadband Router, Scanner etc, each of these programs installs their own software as well as the required drivers which you really don't need!!
Lets take an example here:
O2 Broadband sends you a router - the router by its nature has a web page that you configure all the settings on at o2wirelessbox.lan but step 1 of the unnecessary installation CD states "Insert the CD and install O2Broadband Software" so lets take a look at this.
What does it install? well it installs some daft utility that makes your pc do the work that the router does anyway - what is the point of that? Second it installs a ton of bookmarks that just clutter up your browser and again totally not required.
May advice? use the CD as a new coaster for your cup of tea its pointless!!
Look let me tell you a little secret..
openSUSE is a desktop operating system with graphical environment much like Windows is to Dos (yes believe it or not Dos does still exist underneath all that bloat of Windows).
What's more it comes with a large selection of Pre Installed Applications that are not restricted in terms of days before you need to pay again.
All the applications are fully functional and most have a choice of which one you can use.
3 different office productivity suites (LibreOffice, KOffice2, Gnome Office (AbiWord, gNumeric))
5 different web browsers (Chromium, Opera, Epiphany, Firefox, Konqueror)
Accounting and Finance, Graphic Design, Email, Chat, Instant Messeging
If your running a business paying just 60 quid for openSUSE versus £1000's for Licences for Windows products makes much more sense.
Plus he is the big + if your a small business openSUSE has no licence restrictions and as your business grows you can use the same installation cd on each machine without needing to purchase additional ones!
So to sum up, openSUSE removes bloat ware because Manufacturers don't write it for openSUSE, use the web based configuration utilities its what its their for.
openSUSE removes time limitations on that new computer you just bought.
As your business expands your software budget stays exactly the same.
Bargain!
ruby-dbus 0.7.0 works with 1.9.2 again
- Added ASystemBus and ASessionBus, non-singletons useful in tests and threads.
- Fixed handling of multibyte strings (Issue#8, by Takayuki YAMAGUCHI).
- Allow reopening of a dbus_interface declaration (Issue#9, by T. YAMAGUCHI).
- Fixed ruby-1.9.2 compatibility again (Issue#12).
- Fixed authentication on BSD (Issue#11, by Jonathan Walker).
- Fixed exiting a nested event loop for synchronous calls (reported by Timo Warns).
- Fixed introspection calls leaking reply handlers.
- "rake test" now works, doing what was called "rake env:test"
