ebassi is currently certified at Master level.

Name: Emmanuele Bassi
Member since: 2004-02-27 09:34:26
Last Login: N/A

FOAF RDF Share This

Homepage: http://www.emmanuelebassi.net

Notes:

I'm graduating as a CS major in Italy, with a course on system and network security in the Università degli Studi of Milan. As a OSS developer, my interests lie in userland network applications. I maintain the Gnome2::Print, Gnome2::GConf and Gtk2::SourceView Perl packages, and contribute to the gtk2-perl project. I'm currently working on the new recently used resources implementation for Gtk, which is part of Project Ridley.

Projects

Recent blog entries by ebassi

Syndication: RSS 2.0
16 Sep 2005 (updated 9 Nov 2005 at 11:08 UTC) »

Using advogato (and my log), since I'm not on the Planet (yet).

I've just read Daniel's post, and since shame is a powerful drive, here's my non-requested answer.

I'm one guy - quite possibly, the only one - that switched from a full-fledged XML parser like libxml2 to GMarkup. Believe you me: I would have rather stayed within the blissfulness of DOM, within the ease of development of a complex and powerful parser, within the safety of one of the best XML parser around the F/OSS world.

I would have used libxml2 (and in fact, I did begin using it) - because of the work that DV (and every other developer involved) put into libxml2; I state that again: it's a wonderful library, and it's great to have it, and for it I'll have to buy Daniel enough beer to knock him unconscious until Gnome 2.14. :-)

That said, I switched to GMarkup because libxml2 is also a heavy dependency for Gtk+. It's a 1M+ library, and a dependency some devices can't afford to have on the chain - I think specifically of embedded devices.

Supporting a platform standard like the storage for recent files and bookmarks only on desktop boxes, because they can afford to have libxml2 pre-installed is not an option.

I remember discussing on the XDG list with Daniel and others about the desktop-bookmark spec; the spec started as a GMarkup format, and then I was convinced to use XBEL. It was a good idea - and once properly standardised, it could lead to data sharing between various environments; a goal that the previous recent-files spec missed badly.

Having GMarkup to parse a valid XBEL stream, even with every limitation it has (UTF-8 only, a bit shaky XML:NS support, etc.), has been possible (even thinkable) just because I had beside my open Gedit window another window with a XBEL parser written using libxml2, reminding me how a full-fledged XML parser should work.

So, thanks Daniel for libxml2 - your great work has been and it's still really appreciated and useful. Sadly, there are requirements, in this world, and many times they collide with what we would like.

Using advogato (and my log), since I'm not on the Planet (yet).

I've just read Daniel's post, and since shame is a powerful drive, here's my non-requested answer.

I'm one guy - quite possibly, the only one - that switched from a full-fledged XML parser like libxml2 to GMarkup. Believe you me: I would have rather stayed within the blissfulness of DOM, within the ease of development of a complex and powerful parser, within the safety of one of the best XML parser around the F/OSS world.

I would have used libxml2 (and in fact, I did begin using it) - because of the work that DV (and every other developer involved) put into libxml2; I state that again: it's a wonderful library, and it's great to have it, and for it I'll have to buy Daniel enough beer to knock him unconscious until Gnome 2.14. :-)

That said, I switched to GMarkup because libxml2 is also a heavy dependency for Gtk+. It's a 1M+ library, and a dependency some devices can't afford to have on the chain - I think specifically of embedded devices.

Supporting a platform standard like the storage for recent files and bookmarks only on desktop boxes, because they can afford to have libxml2 pre-installed is not an option.

I remember discussing on the XDG list with Daniel and others about the desktop-bookmark spec; the spec started as a GMarkup format, and then I was convinced to use XBEL. It was a good idea - and once properly standardised, it could lead to data sharing between various environments; a goal that the previous recent-files spec missed badly.

Having GMarkup to parse a valid XBEL stream, even with every limitation it has (UTF-8 only, a bit shaky XML:NS support, etc.), has been possible (even thinkable) just because I had beside my open Gedit window another window with a XBEL parser written using libxml2, reminding me how a full-fledged XML parser should work.

So, thanks Daniel for libxml2 - your great work has been and it's still really appreciated and useful. Sadly, there are requirements, in this world, and many times they collide with what we would like.

Using advogato (and my log), since I'm not on the Planet (yet).

I've just read Daniel's post, and since shame is a powerful drive, here's my non-requested answer.

I'm one guy - quite possibly, the only one - that switched from a full-fledged XML parser like libxml2 to GMarkup. Believe you me: I would have rather stayed within the blissfulness of DOM, within the ease of development of a complex and powerful parser, within the safety of one of the best XML parser around the F/OSS world.

I would have used libxml2 (and in fact, I did begin using it) - because of the work that DV (and every other developer involved) put into libxml2; I state that again: it's a wonderful library, and it's great to have it, and for it I'll have to buy Daniel enough beer to knock him unconscious until Gnome 2.14. :-)

That said, I switched to GMarkup because libxml2 is also a heavy dependency for Gtk+. It's a 1M+ library, and a dependency some devices can't afford to have on the chain - I think specifically of embedded devices.

Supporting a platform standard like the storage for recent files and bookmarks only on desktop boxes, because they can afford to have libxml2 pre-installed is not an option.

I remember discussing on the XDG list with Daniel and others about the desktop-bookmark spec; the spec started as a GMarkup format, and then I was convinced to use XBEL. It was a good idea - and once properly standardised, it could lead to data sharing between various environments; a goal that the previous recent-files spec missed badly.

Having GMarkup to parse a valid XBEL stream, even with every limitation it has (UTF-8 only, a bit shaky XML:NS support, etc.), has been possible (even thinkable) just because I had beside my open Gedit window another window with a XBEL parser written using libxml2, reminding me how a full-fledged XML parser should work.

So, thanks Daniel for libxml2 - your great work has been and it's still really appreciated and useful. Sadly, there are requirements, in this world, and many times they collide with what we would like.

I've moved my log on my personal web site, here:

Context Switch

(I know, it's been some time - it's that just now I remembered having an account on advogato)

21 Apr 2004 (updated 21 Apr 2004 at 23:43 UTC) »

* geek: I've taken the test reported by teknofile: 56.80473%. I guess it helped that I'm a trekker and a sci-fi reader/fan. ;-)

4 older entries...

 

ebassi certified others as follows:

  • ebassi certified seb128 as Master
  • ebassi certified akpm as Master
  • ebassi certified hp as Master
  • ebassi certified rml as Master
  • ebassi certified murrayc as Master
  • ebassi certified dsandras as Master
  • ebassi certified fxn as Journeyer
  • ebassi certified garnacho as Journeyer
  • ebassi certified miguel as Master
  • ebassi certified federico as Master
  • ebassi certified ffrederick as Apprentice
  • ebassi certified pbor as Journeyer
  • ebassi certified jamiemcc as Apprentice

Others have certified ebassi as follows:

  • ffrederick certified ebassi as Journeyer
  • lerdsuwa certified ebassi as Apprentice
  • murrayc certified ebassi as Journeyer
  • fxn certified ebassi as Journeyer
  • pbor certified ebassi as Journeyer
  • jamiemcc certified ebassi as Journeyer
  • behdad certified ebassi as Master
  • lucasr certified ebassi as Journeyer
  • pcburns certified ebassi as Journeyer
  • eopadoan certified ebassi as Master
  • loopback certified ebassi as Master
  • csv certified ebassi as Master
  • amigadave certified ebassi as Master

[ Certification disabled because you're not logged in. ]

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!

X
Share this page