gtk-sharp packages available for neo

Mikkel Meyer Andersen openmoko at
Fri Oct 5 19:13:33 CEST 2007


You shouldn't be sorry - I'm glad for proposals and new ideas!

I'm still not sure whether this is the right angle to attack this 
problem from, but until I hear something else (from for example Cliff 
Brake who announced the gtk-sharp packages.

You're rigth about C# - it's developed by Microsoft, but it's a 
industrial standard (ECMA) and it has several high-level aspect which I 
fancy a lot. That's why I want to use it - simply because I'm more 
productive in C# than in C++ (yet).

Actually I'm still quite sure that I'm going to develop mostly on C++ at 
OpenMoko-related stuff, but I became quite curious when I saw the mail 
earlier from Cliff. So I'm diving into it to learn a bit :-)


Joshua Layne skrev:
> On Fri, 05 Oct 2007 18:59:11 +0200, Mikkel Meyer Andersen
> <openmoko at> wrote:
>> Hi,
>> Thanks for your response.
>> Yes, I did see that. And I have the src locally
>> (~/moko/openmoko/trunk/src/target/OM-2007/openmoko-libs/libmokoui) which
>> is also well-documented.
>> The problem is that C# cannot use the C-files as references (directly),
>> but instead has to use the libraries (the result of the C-files after
>> compilation) with a lot of interoping - and that is really a error-prone
>> task (just as an example byte in C corresponds to unsigned char in C#
>> etc).
>> To the C-files could be used as documentation for making the interoping,
>> and that's exactly what Swig does. So I'm going to test if those
>> autogenerated C#-classes is usable.
> ok, sorry I couldn't be of more help - I am never sure if everyone else has
> the same "crack addiction" that I have about all news openmoko-related.  I
> check a few times a day :)
> I am not a C# (or really C-anything developer), so while I understand the
> basic details of your response - I have never had to do anything like that
> - sounds like an ugly integration though.  The abstraction you propose in
> your follow-up email sounds like a good way to manage it though.
> The benefit of using C# is to run code developed for WM?
> I don't know much about it as a language except that it was originally
> (IIRC) developed for windows (by MS?)
> I hope you don't mind, but I am copying the list on this - it might be
> educational to more than me.
>> Regards,
>> Mikkel
>> Joshua Layne skrev:
>>> On Fri, 05 Oct 2007 18:05:21 +0200, Mikkel Meyer Andersen
>>> <openmoko at> wrote:
>>>> Hi,
>>>> How shoud I refer to libmokoui (e.g. MokoApplication and MokoAlignment)
>>>> from within a Mono-application?
>>> I assume you have seen this?
>>> from Thomas' blog.
>>> it looks pretty well documented - not sure if you meant v2 above though
>>> (although prob development should be done against v2 if possible)
>>> HTH,
>>> j.
>>>> Can anyone be so kind to just post a very small hello world-program?
>>>> I've been through the MokoMakefile-procedure, so I have all the
>> sources.
>>>> Best regards,
>>>> Mikkel Meyer Andersen
>>>> Mikkel Meyer Andersen skrev:
>>>>> Hi,
>>>>> Oh, that's really nice! Thanks a lot - also for the quick reply. Well,
>>>>> on the other hand I'll not get much sleep this weekend now :-) Just
>>>>> kidding, thanks.
>>>>> Regards,
>>>>> Mikkel Meyer Andersen
>>>>> Cliff Brake skrev:
>>>>>> On 10/5/07, Mikkel Meyer Andersen <openmoko at> wrote:
>>>>>>> Is this meaning that it's possible to make C#-applications to
>> OpenMoko
>>>>>>> with GTK as GUI (as opposed to e.g. WinForms)?
>>>>>> Yes.
>>>>>>> How much of the Mono
>>>>>>> library is supported? I'm having a bit trouble finding documentation
>>>> on
>>>>>>> this on the wiki, sorry.
>>>>>> Everything in the main mono package as far as I know -- just install
>>>>>> as much as you need.  You can browse the following for a list of
>>>>>> components:
>>>>>> I'm sure additional mono libs and apps from other projects will be
>>>>>> added in the future as there is need.
>>>>>> Cliff
> _______________________________________________
> OpenMoko community mailing list
> community at

More information about the community mailing list