Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi, If you are looking to get eds/evo rid of gtk, you are proned to be lost. Instead, use the dbus api and write a email client in qt. You can glance it https://meego.gitorious.org/meego-ux/meego-app-email. I worked on a qt/qml based email client which spoke to the email daemon over dbus. It is obsolete atm. Thanks for help. I look at this code and it is very interesting from my point of view. It is very close to this what I am trying to achieve. I am not going to use Qml, but I can take it as an example and develop my own app. As I saw Qml is related with Qt QMF component. From Qt Labs description it sounds like very useful framework. Does it means that this application is using Evolution only to store mails and all connection with mail servers (POP, IMAP, SMTP) is handled by QMF? Could you tell me if meego-app-calendar is done in similar way? http://meego.gitorious.org/meego-ux/meego-app-calendar As I saw both projects do not have any activity in last days. Do you know if those projects are still alive or maybe developed as closed-code? Michal ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi Michal, On Thu, Feb 9, 2012 at 2:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, If you are looking to get eds/evo rid of gtk, you are proned to be lost. Instead, use the dbus api and write a email client in qt. You can glance it https://meego.gitorious.org/meego-ux/meego-app-email. I worked on a qt/qml based email client which spoke to the email daemon over dbus. It is obsolete atm. Thanks for help. I look at this code and it is very interesting from my point of view. It is very close to this what I am trying to achieve. I am not going to use Qml, but I can take it as an example My purpose for showing the code is to look at it as an example :) and develop my own app. As I saw Qml is related with Qt QMF component. From Qt Labs description it sounds like very useful framework. Does it means that this application is using Evolution only to store mails and all connection with mail servers (POP, IMAP, SMTP) is handled by QMF? The code I showed you, uses e-mail-factory for everything. It replaced QMF. Could you tell me if meego-app-calendar is done in similar way? http://meego.gitorious.org/meego-ux/meego-app-calendar As I saw both projects do not have any activity in last days. Do you know if those projects are still alive or maybe developed as closed-code? The code is dead, I dont have any closed source on them. I have no idea on the calendar stuff. Sorry. -Srini ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
On Thu, 2012-02-09 at 09:57 +0100, Michal G. wrote: If you are looking to get eds/evo rid of gtk, you are proned to be lost. Instead, use the dbus api and write a email client in qt. You can glance it https://meego.gitorious.org/meego-ux/meego-app-email. I worked on a qt/qml based email client which spoke to the email daemon over dbus. It is obsolete atm. Thanks for help. I look at this code and it is very interesting from my point of view. It is very close to this what I am trying to achieve. Hi, I hope you'll be fine if I step in, thus just a little thoughts: You do not want to use evolution at all. The only thing from it you want (to use/rewrite for your needs) is the EMailSession, which is subclass of CamelSession. This serves for mailer part to work properly and is the central point of all mailer functionality. Then you create an EAccountList, which holds list of all configured accounts (note some of them can be disabled), and with those UIDs you create CamelServices, which are structures to communicate between your instance and the server. There are special UIDs, like local, to access locally stored mails (those under On This Computer in Evolution). Of course, it's not that simple, but it's roughly about it. As far as I understand this, the e-mail-factory project does basically this, it extracts EMailSession out of evolution to evolution-data-server and defines new (DBus) API to access its functionality from outside, by any client using the new API. The e-mail-factory does more things, but regarding things you are looking for, it might be it. Bye, Milan ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi, I need more support as Evolution is huge project and I feel that I am lost. Last days, I just went through code and I compiled EDS but on X86 without Gtk+. Thus, I modified some configuration files and main makefile to be able to compile. Next, I tried to compile Evolution. But there is a lot of dependencies to UI (gtk), which I would like to remove. I would like to replace it for instance with GUI written in Qt. I have question regarding functionality and place where should I look for source code. I think that main components on which I should focus are following folders - libemail-utils - libemail-engine - mail (I am not sure if I should consider this folder) and there is folder modules/mail - what kind of functionality is kept there? Is there other place where code related to email is located? And does Evolution uses system settings for network configuration as default or it must be configured somehow? Michal ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
On Mon, Feb 6, 2012 at 8:18 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I need more support as Evolution is huge project and I feel that I am lost. Last days, I just went through code and I compiled EDS but on X86 without Gtk+. Thus, I modified some configuration files and main makefile to be able to compile. Next, I tried to compile Evolution. But there is a lot of dependencies to UI (gtk), which I would like to remove. I would like to replace it for instance with GUI written in Qt. If you are looking to get eds/evo rid of gtk, you are proned to be lost. Instead, use the dbus api and write a email client in qt. You can glance it https://meego.gitorious.org/meego-ux/meego-app-email. I worked on a qt/qml based email client which spoke to the email daemon over dbus. It is obsolete atm. I have question regarding functionality and place where should I look for source code. I think that main components on which I should focus are following folders - libemail-utils - libemail-engine - mail (I am not sure if I should consider this folder) and there is folder modules/mail - what kind of functionality is kept there? Its for the UI of evolution its logics. -Srini Is there other place where code related to email is located? And does Evolution uses system settings for network configuration as default or it must be configured somehow? Michal ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi Srini, I will go in direction of modifying build process to be able to remove all dependencies to libraries that are not available on my SDK. I think it should be possible, but still I am not sure. My aim is to compile EDS (only mails) with Evolution (only libemail-engine + ??) and your e-mail-factory. Then I'm going to provide some GUI. Communication between those components should be done via DBUS. I am still no aware how content of mail will be visible for user. Or in other words, who will render its content. In addition, I need to estimate how big package (backend) I will have after successful compilation. Could you help me in estimation? Thanks in advance for advices. Michal On Tue, Jan 31, 2012 at 3:06 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I tried to compile EDS with my SDK and unfortunately I did not success. I run autogen.sh --host=arm-oe-linux-gnueabi --enable-gtk-doc-html=no --enable-goa=no --enable-nntp=no --disable-glibtest --disable-weather and during checking of configuration following errors about missing libraries occurs - gtk+-3.0 - gmodule-2.0 - gconf-2.0 - libxml 2.0 - libsoup-2.4 - libgdata - gio - libdb - and some other stuff related to NSS and NSPR. I removed all those checking from configuration.ac to be able to generate Makefile. Some of those libraries could be added to my system, but not all (for instance gtk+). Do you think that I will be able to compile EDS without gtk+? BTW, does 3.6 cycle should be release around September of 2012 or later? Michal On Tue, Jan 31, 2012 at 10:46 AM, Srinivasa Ragavan sraga...@gnome.orgwrote: On Tue, Jan 31, 2012 at 3:00 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Nice to meet the author of Anjal :) I went through code and Wiki yesterday and I am starting to understand just a little piece of very high architecture. I will try to compile EDS with my SDK for my ARM device. But first I need to familiarize with build process. As I understand within EDS there is mail engine - this Camel library which I could use and link dynamically with my GUI. Do you know if there is simple example that shows how to send email message? Camel is just the mail access/storage library. I meant libemail-engine.so in evolution/ project, which runs mails accounts, checks for mails etc. Probably better way will be to use your e-mail-factory. Then I will be able to split GUI and Mail engine on two different processes. Will your e-mail factory be an official part of Evolution soon? e-mail-factory should be in eds in 3.6 cycle, but that depends on how much effort I get to merge evolution to use the mail daemon. I do not understand why you advice me to checkout branch of evolution. I thought that all data engines (mail and calendar) are covered by EDS. e-mail-factory needs libemail-engine, which is in evolution. Evolution needs EDS. And when I compile it I will be able to connect it with my GUI. It could be done over DBUS if I have two processes or just dynamic linking to GUI. Do I think correctly? You GUI should speak over dbus to the daemon (which is a process by itself) to fetch/access mails. Could you say, point me a document that describe how EDS store mails and calendar data. Is it some own database in file or some other mechanism? I don't remember any doc for this, what ever you find could be obsolete in some form I fear. -Srini ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
On Thu, Feb 2, 2012 at 2:49 PM, Michal G. guziemic.s...@gmail.com wrote: Hi Srini, I will go in direction of modifying build process to be able to remove all dependencies to libraries that are not available on my SDK. I think it should be possible, but still I am not sure. My aim is to compile EDS (only mails) with Evolution (only libemail-engine + ??) and your e-mail-factory. Then I'm going to provide some GUI. Communication between those components should be done via DBUS. I am still no aware how content of mail will be visible for user. Or in other words, who will render its content. Evolution uses gtkhtml for rendering mails. Anjal used webkit. You can also use MozEmbed. In addition, I need to estimate how big package (backend) I will have after successful compilation. Could you help me in estimation? Big in the sense size? I have no idea tbh. -Srini Thanks in advance for advices. Michal On Tue, Jan 31, 2012 at 3:06 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I tried to compile EDS with my SDK and unfortunately I did not success. I run autogen.sh --host=arm-oe-linux-gnueabi --enable-gtk-doc-html=no --enable-goa=no --enable-nntp=no --disable-glibtest --disable-weather and during checking of configuration following errors about missing libraries occurs - gtk+-3.0 - gmodule-2.0 - gconf-2.0 - libxml 2.0 - libsoup-2.4 - libgdata - gio - libdb - and some other stuff related to NSS and NSPR. I removed all those checking from configuration.ac to be able to generate Makefile. Some of those libraries could be added to my system, but not all (for instance gtk+). Do you think that I will be able to compile EDS without gtk+? BTW, does 3.6 cycle should be release around September of 2012 or later? Michal On Tue, Jan 31, 2012 at 10:46 AM, Srinivasa Ragavan sraga...@gnome.org wrote: On Tue, Jan 31, 2012 at 3:00 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Nice to meet the author of Anjal :) I went through code and Wiki yesterday and I am starting to understand just a little piece of very high architecture. I will try to compile EDS with my SDK for my ARM device. But first I need to familiarize with build process. As I understand within EDS there is mail engine - this Camel library which I could use and link dynamically with my GUI. Do you know if there is simple example that shows how to send email message? Camel is just the mail access/storage library. I meant libemail-engine.so in evolution/ project, which runs mails accounts, checks for mails etc. Probably better way will be to use your e-mail-factory. Then I will be able to split GUI and Mail engine on two different processes. Will your e-mail factory be an official part of Evolution soon? e-mail-factory should be in eds in 3.6 cycle, but that depends on how much effort I get to merge evolution to use the mail daemon. I do not understand why you advice me to checkout branch of evolution. I thought that all data engines (mail and calendar) are covered by EDS. e-mail-factory needs libemail-engine, which is in evolution. Evolution needs EDS. And when I compile it I will be able to connect it with my GUI. It could be done over DBUS if I have two processes or just dynamic linking to GUI. Do I think correctly? You GUI should speak over dbus to the daemon (which is a process by itself) to fetch/access mails. Could you say, point me a document that describe how EDS store mails and calendar data. Is it some own database in file or some other mechanism? I don't remember any doc for this, what ever you find could be obsolete in some form I fear. -Srini ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Then I will use Webkit. It is available and I was doing simple browser with it. For now, I have Qt port of Webkit and Cairo graphic. Regarding size, I wonder about footprint of Evolution. I checked on my Ubuntu and it is about 12 MB. Hopefully it will required less space after removing of some parts. I found also some interesting post about EDS. http://mail.gnome.org/archives/evolution-hackers/2011-June/msg00028.html As I understand there is some work done to make EDS more UI independent. Do you know if this was done, or work is in progress and in which release it will be? And as release 3.4 is planned for March 2012. Does it means that 3.6 should be available after six months, so around September 2012. Does evolution follows GNOME schedules (new stable version every six months)? Michal On Thu, Feb 2, 2012 at 10:21 AM, Srinivasa Ragavan sraga...@gnome.orgwrote: On Thu, Feb 2, 2012 at 2:49 PM, Michal G. guziemic.s...@gmail.com wrote: Hi Srini, I will go in direction of modifying build process to be able to remove all dependencies to libraries that are not available on my SDK. I think it should be possible, but still I am not sure. My aim is to compile EDS (only mails) with Evolution (only libemail-engine + ??) and your e-mail-factory. Then I'm going to provide some GUI. Communication between those components should be done via DBUS. I am still no aware how content of mail will be visible for user. Or in other words, who will render its content. Evolution uses gtkhtml for rendering mails. Anjal used webkit. You can also use MozEmbed. In addition, I need to estimate how big package (backend) I will have after successful compilation. Could you help me in estimation? Big in the sense size? I have no idea tbh. -Srini ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
On Thu, Feb 2, 2012 at 4:11 PM, Michal G. guziemic.s...@gmail.com wrote: Then I will use Webkit. It is available and I was doing simple browser with it. For now, I have Qt port of Webkit and Cairo graphic. Regarding size, I wonder about footprint of Evolution. I checked on my Ubuntu and it is about 12 MB. Hopefully it will required less space after removing of some parts. I found also some interesting post about EDS. http://mail.gnome.org/archives/evolution-hackers/2011-June/msg00028.html As I understand there is some work done to make EDS more UI independent. Do you know if this was done, or work is in progress and in which release it will be? CamelSettings is done. But Im not sure of what you mean by UI independence. And as release 3.4 is planned for March 2012. Does it means that 3.6 should be available after six months, so around September 2012. Does evolution follows GNOME schedules (new stable version every six months)? Yes. Evo follows GNOME schedules. -Srini Michal On Thu, Feb 2, 2012 at 10:21 AM, Srinivasa Ragavan sraga...@gnome.org wrote: On Thu, Feb 2, 2012 at 2:49 PM, Michal G. guziemic.s...@gmail.com wrote: Hi Srini, I will go in direction of modifying build process to be able to remove all dependencies to libraries that are not available on my SDK. I think it should be possible, but still I am not sure. My aim is to compile EDS (only mails) with Evolution (only libemail-engine + ??) and your e-mail-factory. Then I'm going to provide some GUI. Communication between those components should be done via DBUS. I am still no aware how content of mail will be visible for user. Or in other words, who will render its content. Evolution uses gtkhtml for rendering mails. Anjal used webkit. You can also use MozEmbed. In addition, I need to estimate how big package (backend) I will have after successful compilation. Could you help me in estimation? Big in the sense size? I have no idea tbh. -Srini ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi, Nice to meet the author of Anjal :) I went through code and Wiki yesterday and I am starting to understand just a little piece of very high architecture. I will try to compile EDS with my SDK for my ARM device. But first I need to familiarize with build process. As I understand within EDS there is mail engine - this Camel library which I could use and link dynamically with my GUI. Do you know if there is simple example that shows how to send email message? Probably better way will be to use your e-mail-factory. Then I will be able to split GUI and Mail engine on two different processes. Will your e-mail factory be an official part of Evolution soon? I do not understand why you advice me to checkout branch of evolution. I thought that all data engines (mail and calendar) are covered by EDS. And when I compile it I will be able to connect it with my GUI. It could be done over DBUS if I have two processes or just dynamic linking to GUI. Do I think correctly? Could you say, point me a document that describe how EDS store mails and calendar data. Is it some own database in file or some other mechanism? Michal On Mon, Jan 30, 2012 at 3:37 PM, Srinivasa Ragavan sraga...@gnome.orgwrote: Hi On Mon, Jan 30, 2012 at 6:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Thank you for answer. Yes. I'm looking for mail engine that will be able to communicate for instance over DBUS which some UI. My device does not uses X.org, GTK and Cairo. It future, I would also append my software with Calendar functionality. Calendar is already in EDS available over DBUS. I choosed to work with Evolution because I saw similar email client called Anjal that utilize Evolution but has own UI. I was the author of Anjal. It was build with Gtk/Cairo on top of libevolution-mail. Now after mbarnes's awesome library breaks, I broke mail engine to a independent library that can reside in EDS (in the future) which I currently server over DBUS. You must checkout master branch of eds and evolution. https://github.com/sragavan/e-mail-factory is the dbus engine that Im working on, which is still under development. Some apis are fun and still not up to the mark. But you can use them and it works fine. -Srini. Could you tell me from which git should I clone - http://git.gnome.org/browse/evolution-data-server - http://git.gnome.org/browse/evolution And could you tell where to start, or what should I read some to - build mail engine library (http://mad-scientist.us/evolution.html - should I follow this process) - API of DBUS Michal On Sat, Jan 28, 2012 at 7:35 AM, Srinivasa Ragavan sraga...@gnome.org wrote: Hi Michal, On Fri, Jan 27, 2012 at 5:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1)Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2)Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3)Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4)If I’m about hacking the build process to my needs (removing dependencies) where should I start? IIUC you want to use the engine of evolution, but not the UI. If so, I've been working on a mail daemon which has all the mail logic built in and exposes mail (basic) interface over dbus. If you aren't interested in that, you can look at libemail-engine.so which is a new library that I added a week ago in master which provides most of what you are looking at except the UI. -Srini Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
On Tue, Jan 31, 2012 at 3:00 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Nice to meet the author of Anjal :) I went through code and Wiki yesterday and I am starting to understand just a little piece of very high architecture. I will try to compile EDS with my SDK for my ARM device. But first I need to familiarize with build process. As I understand within EDS there is mail engine - this Camel library which I could use and link dynamically with my GUI. Do you know if there is simple example that shows how to send email message? Camel is just the mail access/storage library. I meant libemail-engine.so in evolution/ project, which runs mails accounts, checks for mails etc. Probably better way will be to use your e-mail-factory. Then I will be able to split GUI and Mail engine on two different processes. Will your e-mail factory be an official part of Evolution soon? e-mail-factory should be in eds in 3.6 cycle, but that depends on how much effort I get to merge evolution to use the mail daemon. I do not understand why you advice me to checkout branch of evolution. I thought that all data engines (mail and calendar) are covered by EDS. e-mail-factory needs libemail-engine, which is in evolution. Evolution needs EDS. And when I compile it I will be able to connect it with my GUI. It could be done over DBUS if I have two processes or just dynamic linking to GUI. Do I think correctly? You GUI should speak over dbus to the daemon (which is a process by itself) to fetch/access mails. Could you say, point me a document that describe how EDS store mails and calendar data. Is it some own database in file or some other mechanism? I don't remember any doc for this, what ever you find could be obsolete in some form I fear. -Srini Michal On Mon, Jan 30, 2012 at 3:37 PM, Srinivasa Ragavan sraga...@gnome.org wrote: Hi On Mon, Jan 30, 2012 at 6:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Thank you for answer. Yes. I'm looking for mail engine that will be able to communicate for instance over DBUS which some UI. My device does not uses X.org, GTK and Cairo. It future, I would also append my software with Calendar functionality. Calendar is already in EDS available over DBUS. I choosed to work with Evolution because I saw similar email client called Anjal that utilize Evolution but has own UI. I was the author of Anjal. It was build with Gtk/Cairo on top of libevolution-mail. Now after mbarnes's awesome library breaks, I broke mail engine to a independent library that can reside in EDS (in the future) which I currently server over DBUS. You must checkout master branch of eds and evolution. https://github.com/sragavan/e-mail-factory is the dbus engine that Im working on, which is still under development. Some apis are fun and still not up to the mark. But you can use them and it works fine. -Srini. Could you tell me from which git should I clone - http://git.gnome.org/browse/evolution-data-server - http://git.gnome.org/browse/evolution And could you tell where to start, or what should I read some to - build mail engine library (http://mad-scientist.us/evolution.html - should I follow this process) - API of DBUS Michal On Sat, Jan 28, 2012 at 7:35 AM, Srinivasa Ragavan sraga...@gnome.org wrote: Hi Michal, On Fri, Jan 27, 2012 at 5:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1) Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2) Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3) Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4) If I’m about hacking the build process to my needs (removing dependencies) where should I start? IIUC you want to use the engine of evolution, but not the UI. If so, I've been working on a mail daemon which has all the mail logic built in and exposes mail (basic) interface over dbus. If you aren't interested in that, you can look at libemail-engine.so which is a new library that I added a week ago in master which provides most of what you are looking at except the UI. -Srini Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi, Thank you for answer. Yes. I'm looking for mail engine that will be able to communicate for instance over DBUS which some UI. My device does not uses X.org, GTK and Cairo. It future, I would also append my software with Calendar functionality. I choosed to work with Evolution because I saw similar email client called Anjal that utilize Evolution but has own UI. Could you tell me from which git should I clone - http://git.gnome.org/browse/evolution-data-server - http://git.gnome.org/browse/evolution And could you tell where to start, or what should I read some to - build mail engine library (http://mad-scientist.us/evolution.html - should I follow this process) - API of DBUS Michal On Sat, Jan 28, 2012 at 7:35 AM, Srinivasa Ragavan sraga...@gnome.orgwrote: Hi Michal, On Fri, Jan 27, 2012 at 5:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1)Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2)Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3)Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4)If I’m about hacking the build process to my needs (removing dependencies) where should I start? IIUC you want to use the engine of evolution, but not the UI. If so, I've been working on a mail daemon which has all the mail logic built in and exposes mail (basic) interface over dbus. If you aren't interested in that, you can look at libemail-engine.so which is a new library that I added a week ago in master which provides most of what you are looking at except the UI. -Srini Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi On Mon, Jan 30, 2012 at 6:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, Thank you for answer. Yes. I'm looking for mail engine that will be able to communicate for instance over DBUS which some UI. My device does not uses X.org, GTK and Cairo. It future, I would also append my software with Calendar functionality. Calendar is already in EDS available over DBUS. I choosed to work with Evolution because I saw similar email client called Anjal that utilize Evolution but has own UI. I was the author of Anjal. It was build with Gtk/Cairo on top of libevolution-mail. Now after mbarnes's awesome library breaks, I broke mail engine to a independent library that can reside in EDS (in the future) which I currently server over DBUS. You must checkout master branch of eds and evolution. https://github.com/sragavan/e-mail-factory is the dbus engine that Im working on, which is still under development. Some apis are fun and still not up to the mark. But you can use them and it works fine. -Srini. Could you tell me from which git should I clone - http://git.gnome.org/browse/evolution-data-server - http://git.gnome.org/browse/evolution And could you tell where to start, or what should I read some to - build mail engine library (http://mad-scientist.us/evolution.html - should I follow this process) - API of DBUS Michal On Sat, Jan 28, 2012 at 7:35 AM, Srinivasa Ragavan sraga...@gnome.org wrote: Hi Michal, On Fri, Jan 27, 2012 at 5:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1) Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2) Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3) Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4) If I’m about hacking the build process to my needs (removing dependencies) where should I start? IIUC you want to use the engine of evolution, but not the UI. If so, I've been working on a mail daemon which has all the mail logic built in and exposes mail (basic) interface over dbus. If you aren't interested in that, you can look at libemail-engine.so which is a new library that I added a week ago in master which provides most of what you are looking at except the UI. -Srini Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1)Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2)Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3)Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4)If I’m about hacking the build process to my needs (removing dependencies) where should I start? Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Compile Evolution Mail as .so file with API for other GUI on ARM device
Hi Michal, On Fri, Jan 27, 2012 at 5:27 PM, Michal G. guziemic.s...@gmail.com wrote: Hi, I've been investigating a possibility of Evolution Mail cross-compilation for Linux X-less device (ARM) and use it as dynamic library that will provide me possibility to expose API that could be utilize by HMI layer. 1) Is it possible to compile Evolution Mail without any user interface (pure –headless)? Or how much work would that require? 2) Does Evolution architecture allows doing such split – mail supporting functionality and GUI? 3) Is it possible to eliminate all unnecessary libs and resources? They’re using valuable device resources and may cause compilation problems. 4) If I’m about hacking the build process to my needs (removing dependencies) where should I start? IIUC you want to use the engine of evolution, but not the UI. If so, I've been working on a mail daemon which has all the mail logic built in and exposes mail (basic) interface over dbus. If you aren't interested in that, you can look at libemail-engine.so which is a new library that I added a week ago in master which provides most of what you are looking at except the UI. -Srini Best regards, Michal Guzieniuk ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
