I just shipped the bits and release email for Ethos 0.2.0. Ethos is a shared library I put together for adding plugins to your application.
Currently, Ethos is focused on plugins for applications written in C or Vala since they provide the common denominator to enable the largest variety of scripting languages. However, that's not to say you couldn't provide a thunk layer for something else.
Pugins written in C, Vala, Python, and JavaScript are supported. However, Mono support is mostly finished and will be added in a follow up release. Each plugin language is supported through a separate shared library, so your process will not be polluted with languages that are not being used.
I'd like to thank the giftwrap hackers for helping me dog-food and get ethos ready for an initial release.
# dronelabs.com ppa for releases
deb http://ppa.launchpad.net/audidude/dronelabs/ubuntu jaunty main
deb-src http://ppa.launchpad.net/audidude/dronelabs/ubuntu jaunty main
Comments (11)
We in turn appreciate the plugin framework – with platform bindings and a UI for it already provided, it’s a nicer solution than making one from scratch.
Cool, I didn’t know there was hompepage and releases on this super-aweson library. I would really love to use this for rygel[1] but unfortunately it’ll require some significant changes (4-5 days of work) and I’ve lots of things on my TODO so it’ll be a while before I get on this. Just saying that here in hope you (or another fan of this library) would like to contribute to Rygel.
[1] http://live.gnome.org/Rygel
@Zeeshan That sounds great!
I’ve been meaning to check out the Rygel code base actually. giftwrap is written in Vala as well so the bindings should pretty much be ready to go!
However, before I can do that I need to get a release of both Iris[1] and Catalina[2] out the door.
Btw, I *totally* stole your idea wrt the GObject t-shirt and had one made
[1] http://git.dronelabs.com/iris/about/
[2] http://git.dronelabs.com/catalina/about/
I was like “Cool! that would be great” till i read the last part of your reply. Now i am confused whether to be happy or pissed off.
@Zeeshan: But only one of you has the GObject-crown, so please be happy
I wonder if it makes sense that this kind of libraries try to come up with the same way of doing this, following a spec or something.
Why didn’t you follow the same architecture as MonoAddins for example? (Same XML schemas, etc…) This would allow for people to easily switch between plugin frameworks.
I didn’t follow mono.addins because it is over engineered for 90% of the projects out there.
Ethos follows a model closer to gedit, which has arguably been the most successful at fostering community plugins on the gnome desktop.
The xml format from mono.addins is also a PITA to troubleshoot schema issues and what not, while the keyfile is quite simple.
However, I think we can still provide extension points, I just think it makes more sense for applications to do that themselves using ethos as scaffolding.
Still interested in hearing more on the ideas though.
@antimonio: switching plugin frameworks isn’t exactly something you’d be rationally doing on a daily basis. Don’t see it justifying a binding to a common format.
Vadim: well, what I meant indeed is knowledge reuse: if you learn MonoAddins, you would have learnt Ethos as well.
chergert: Well, why don’t you expose your “over-engineering” concerns to the MonoAddins list?
@antimonio It’s not over-engineered for certain situations. Such as MonoDevelop; which needs the level of control it provides.
However, I don’t think many of our desktop applications need that.
Trackback/Pingback (1)
[...] information related to your search Christian Hergert: Ethos 0.2.0 is now available in this link…: News [...]