To content | To menu | To search
Friday, June 19 2009
By letiemble on Friday, June 19 2009, 08:12 - Ecrits
A la suite de la planche XKCD d'aujourd'hui, ma navigation m'a amenée sur la page Wikipedia du mathématicien Paul Erdös. S'il ne faut en retenir qu'une seule chose, c'est qu'il n'était pas dépourvu d'humour:
"Les premiers signes de la sénilité sont quand un homme oublie les théorèmes. Le deuxième signe, c'est quand il oublie de fermer sa braguette. Le troisième, c'est quand il oublie de l'ouvrir !". Paul Erdös.
Saturday, May 16 2009
By letiemble on Saturday, May 16 2009, 10:55 - Apple
Wednesday, April 29 2009
By letiemble on Wednesday, April 29 2009, 09:20 - DotNet
Monobjc 2.0.342.0 was released on April 2009, the 15th. One major addition in Monobjc is the support of SM2DGraphView graphing framework. It is the first round to include a graphing framework, and I hope to enhance the support in the next releases.
Sunday, December 21 2008
By letiemble on Sunday, December 21 2008, 10:48 - DotNet
Monobjc 2.0.313.0 was released on December 2008, the 17th. One major addition in Monobjc is the support of Sparkle update engine. Sparkle is one of the most used framework in the Cocoa world, as it makes updating an application a breeze. The main problem with Sparkle in Monobjc was the private framework embedding. With Sparkle, updating a Monobjc application has never been so simple. Check out the tutorial for Monobjc and Sparkle.
Saturday, December 13 2008
By letiemble on Saturday, December 13 2008, 18:06 - DotNet
I am pleased to see that Monobjc can be now used with Delphi Prism thanks to RemObjects Software. Marc Hoffman has a nice blog entry about this integration.
Thursday, November 13 2008
By letiemble on Thursday, November 13 2008, 08:25 - DotNet
Many people want to package their .NET application for Mac OS X. And above all, they want the experience to be painless, which means that they want to ship an application that runs, whether Mono is installed or not.
The process of packaging a .NET application for Mac OS X basically follows 4 steps:
The process can be even more complicated if you are using reflection, dynamically discovered library and so on. So let's keep thing simple.
This is the easy part. You just have to find recursively all the .NET dependencies of the .NET executable. As every .NET assembly contains its references, it is trivial.
The native loader generation is simplified by the fact that Mono allows .NET assemblies to be loaded from embedded binary streams. So for every .NET assembly, we generate a binary array and use the magical functions of Mono. If there are configuration files to embed, the process is the same.
Once the native loader is compiled, the otool command can give us all the native dependencies. So we gather all the native library needed to run our application. But on Mac OS X, the dynamic loading is based on paths recorded in each native library. This is the point of the next step.
This is the tougher part of the packaging. Now that you have all the native dependencies, you must be sure that you only have unique dependencies. Why, because we you gather dependencies, you can find either specific version of a library or compatibility version of a library. Failing to make these reference unique can lead to unexpected behavior (mostly cryptic crashes). That where the otool command is useful as the first line always contains the specific version of a library, even if run against a compatibility version symbolic link. Then the install_name is used to change absolute path to relative path containing the macro @executable_path.
All this steps can be tedious and error prone. That's why, in the Monobjc, the packaging is done by a NAnt task: <mkbundle/> (you can find its options on this page). This task can handle most of the need for .NET application packaging in a truly simple way. And as a bonus, this task is not linked to the Monobjc bridge, so you can use it even if you don't use the Monobjc bridge.
Tuesday, November 11 2008
By letiemble on Tuesday, November 11 2008, 15:12 - DotNet
By letiemble on Tuesday, November 11 2008, 15:08 - Internet
La citation du jour nous vient de Bruno Kerouanton (excellent blog sur la sécurité informatique):
"La sécurité, tout le monde s’en fout :
- Au boulot, c’est le problème de l’employeur, pas de l’employé.
- A la maison, c’est comme les chiottes. Il y a un PC par maison, toute la famille s’en sert à tour de rôle pour y faire ses besoins quotidiens, et lorsque c’est sale, c’est le dernier qui est passé dessus qui nettoie."
Pas de commentaire.
Friday, October 10 2008
By letiemble on Friday, October 10 2008, 19:45 - DotNet
Maybe you have already got this error while (re)installing IPv6 on Windows XP:
C:\>ipv6 install Installing... Failed to complete the action Error 0×800704b8
The fix has to do with the Windows security database, which may not be up-to-date. To fix this database, type the following command:
C:\>esentutl /p C:\WINDOWS\security\Database\secedit.sdb Microsoft(R) Windows(TM) Database Utilities Version 5.1 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating REPAIR mode... Database: C:\WINDOWS\security\Database\secedit.sdb Temp. Database: TEMPREPAIRxxxx.EDB Checking database integrity. Scanning Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... Integrity check successful. Note: It is recommended that you immediately perform a full backup of this database. If you restore a backup made before the repair, the database will be rolled back to the state it was in at the time of that backup. Operation completed successfully in 4.469 seconds.
Once the above command is passed, everything should be ok.
C:\>ipv6 install Installing... Succeeded.
See http://support.microsoft.com/?scid=kb%3Ben-us%3B318711&x=10&y=14 for more informations.
Wednesday, September 17 2008
By letiemble on Wednesday, September 17 2008, 10:31 - Virtualization
I am a long term fan of VMWare Fusion, and I have followed with interest the various beta of VMWare Fusion. Today, I have installed the 2.0 final release, and I immediatly see that something has changed. Things seems to go faster, snappier and slicker. So, if you own a Mac and wants to go into the desktop virtualization world, try out VMWare Fusion.
« previous entries - page 1 of 10