In order to get Google Earth running on Kubuntu or Ubuntu 7.10 on the Intel GMA X3100 in anything like an useable way, you need to start it like this

$ LIBGL_ALWAYS_INDIRECT=1 google-earth/googleearth

I hope this helps someone ;)

Considering that eZ opensourced their Online Editor this summer, I have decided to stop development on my editor for now. Anyone interested in further development is free to do so of course.

I've been testing eZXHTML yesterday on 3.8. For all I can tell after my admittedly short test, it does work (I couldn't test the image insertion as 3.8 keeps crashing when I try to upload images, no matter if eZXHTML active  or not). This would mean that the current XHTML parser could be used with 3.8.

However, there's been a total rewrite of the whole ezsimplified ezxml  parser which should likely be reviewed by us and see if we should instead base our code on it. A Short glance over it suggests it is complex as usual. It is implementing a few new features like but I'm not so sure how important that really is.

Due to the as yet unfixed IE6 crashes I downgraded Xinha back to the previous snapshot R491. The actual revision is rather arbitrary but I know it did work ;)

Some people reported absolutely abysmal speed in IE6 and with big (as in: >50KB) docs even in Firefox. Turns out the CountChars plugin was solely responsible for this: http://xinha.python-hosting.com/ticket/655 I disabled it and now I can edit and scroll in huge documents (as in 100K HTML) in Firefox just fine. And even IE6 now works quite acceptably.

So in case you were wondering about the performance, grab the latest SVN! Or test here if you're skeptical of such extreme claims.

Xavier suggested that it should also be possible to use custom templates when displaying newly created object for editing (i.e. embedded into the other object that's currently being edited) and so there's now a content/view/eoradd.tpl that you can override. The default one does exactly the same as before, so most people won't notice any difference ;)

As I had mentioned here I have been thinking about enabling custom designs for the edit part of enhancedobjectrelation. I now added two more selection modes that use a new node/view/enhancedobjectrelation.tpl view (which by default simply redirects to line view) providing for easy overriding for other classes.

As a proof of concept, I added an override for the image class. It's definitely much friendlier to actually SEE what image one just selected ;)

Since Kristof Coomans doesn't seem to care to blog about the cool stuff keeps on coding, I'll do it today as this time he managed to do something close to the holy grail in eZPublish hacking: attribute level edit permissions

In my limited testing just a few minutes ago, this worked perfectly and solves a long standing problem in ez.

Respect and thanks a lot for this!

Some short ideas of what should go into EOR 2.0:

• template based selection of relation. Right now, it's kinda hard to select things like images with only the name in many cases so there should be an option to provide object specific layouts to chose from (think node_view_gui view=eor), with the default likely be something like text_linked or just an alias to line
• AJAX based key word searches: Something along the lines of how the current xeditor image insertion keyword search works wouldn't be very hard. Or possibly without AJAX, just JS based filtering?
  
• AJAX browse: This is something that should be integrated into ez anyway.
  

I'm sure there are other things that you'd like to see, so feel free to comment ;)