RE: Tinymail's .NET bindings

[Philip Van Hoof <spam pvanhoof be>]

On Thu, 2006-10-26 at 19:17 +0800, Nitin Mahajan nokia com wrote:
> Hi!

Did you set the accounts's count preference in GConf?

/apps/tinymail/accounts/count = 1
/apps/tinymail/accounts/0/name = Test
/apps/tinymail/accounts/0/proto = IMAP
/apps/tinymail/accounts/0/type = store
/apps/tinymail/accounts/0/hostname = server
/apps/tinymail/accounts/0/username = username

You can read the source code of the sample account-store in
libtinymail-gnome-desktop for more information on how to make accounts
for the demo-ui. On a gnome desktop, it's going to use that
implementation.

ps. Please use the mailing list for asking questions about tinymail.


> By using the demo UI can I see the summary view of my e-mail account at
> AOL.
> 
> I tried same on gnome desktop by following through the instructions in
> README. I can see only the blank UI, nothing else. It even did not ask
> me for a password.
> 
> Couldu please give some clarity on using that demo application?
> 
> -Nitin Mahajan 
> 
> -----Original Message-----
> From: tinymail-devel-list-bounces gnome org
> [mailto:tinymail-devel-list-bounces gnome org] On Behalf Of ext Philip
> Van Hoof
> Sent: Thursday, October 26, 2006 4:09 PM
> To: tinymail-devel-list gnome org
> Cc: gtk-sharp-list lists ximian com
> Subject: Re: Tinymail's .NET bindings
> 
> On Mon, 2006-10-16 at 11:17 +0200, Philip Van Hoof wrote:
> 
> > For people interested in working on the .NET bindings for tinymail:
> 
> I have attached a manual version of what I have in mind. A binding
> generator should create something like this (which doesn't look
> impossible), maybe make xslts of this manual stuff and feed those xslts
> the different types, methods, properties and etcetera parsed from the .h
> files?
> 
> It doesn't look like GAPI generates something that already looks like
> this. An open question is whether the interested people are rather
> interested in creating a new generator or whether they prefer adapting
> gapi?
> 
> I prefer generated language bindings. But the quality of the binding
> itself is by far more important than its 'generatability'.
> 
> I named the files the same as the namespace would be. Per two such
> namespaces, a .dll will be created. For example:
> 
> Tny and Tny.Proxy will be libtinymail-sharp-1.0.dll Tny.Ui and
> Tny.Ui.Proxy will be libtinymailui-sharp-1.0.dll Tny.Ui.Gtk and
> Tny.Ui.Gtk.Proxy will be libtinymailui-gtk-sharp-1.0.dll Tny.Camel and
> Tny.Camel.Proxy will be libtinymail-camel-sharp-1.0.dll Tny.Platform and
> Tny.Platform.Proxy will be libtinymail-platform-sharp-1.0.dll
> 
> The types in the Proxy namespaces implement P/Invoke-ing to the GObject
> library. The other types, using the Proxy types as the real in a proxy,
> implement converting the proxy-calls to whatever is cool in the higher
> level programming language. I think those types cannot be 100% generated
> whereas the proxy types can (even without any customisation). I would
> prefer the generated proxy types to be left untouched (maybe let GAPI
> generate them after enhancing GAPI?)
> 
> Almost none of the tinymail API isn't suitable for parsing/generating a
> language binding for. I have specifically put a lot time in making sure
> it's all easy (no typical C types like doubly linked lists, pointers or
> other such things are being returned or accepted as a parameter, all
> such are converted to full GObject types, except things like "gchar*"
> and "gint" of course).
> 
> That way it will be possible to have a Tny.List type that implements
> IList and IEnumeratable, and a Tny.Iterator that implements IEnumerator
> etc etc (or however they are called on .NET today). Those will wrap the
> GObject types TnyList and TnyIterator (just examples).
> 
> ps. I know at least Bart is working on .NET bindings for tinymail.
> 
> --
> Philip Van Hoof, software developer
> home: me at pvanhoof dot be
> gnome: pvanhoof at gnome dot org
> work: vanhoof at x-tend dot be
> blog: http://pvanhoof.be/blog
-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: vanhoof at x-tend dot be
blog: http://pvanhoof.be/blog