Archive for August, 2008

New developer in Dokeos – Herodoto

Herodoto is joining the Dokeos development team as an independent (and distant) developer today. He will be in charge of integrating the wiki tool, under my coaching. The wiki was previously a separate plugin in Dokeos, so we hope it will be stabilised and integrated in time for 1.8.6 at the beginning of October.

Herodoto (aka Juan Carlos) has already contributed a few patches to Dokeos in the past and he has a series of good idea to improve Dokeos’ messaging system overall (combine and improve forum, announcement, dropbox and the messaging plugin all together).

Depending on his contributions in the future, we might encourage such new blood to join Dokeos in the next months, to help in the move to Dokeos 2.0, by having experienced developers coaching them.

Hug a developer

Categories: English, General Tags:

Entrando al planeamiento de Dokeos 1.8.6

August 28, 2008 3 comments

Hoy conversé con Eric Marguin, mi contraparte francesa, y nos quedamos programando más o menos una semana definida para la publicación de Dokeos 1.8.6. Esto sera en la semana 41 si todo sigue según lo planeado, lo que cae entre el 6 y el 10 de octubre del 2008.

Aunque no podremos hacer el rediseño completo de la herramienta de ejercicios como lo habíamos programado, hemos agregado bastante opciones a este y completado otros desarrollos de otras herramientas. Todavia es demasiado temprano para hablar de esto, pero regresaré en medio setiembre para aclararlo todo.

Entering schedule for Dokeos 1.8.6

Today I had a phone chat with Eric Marguin, my french counterpart, and we ended up scheduling more or less a fixed week for the release of Dokeos 1.8.6. This will be week 41 if all goes according to plan, which is between the 6th and the 10th of October 2008.

Although we won’t be able to do the complete quiz tool revamp we wanted, we have been adding quite a lot to that and completing our developments on other tools. It’s still too soon to talk about all that, but I’ll be back around mid-September to make it all clear.

Quick-change header for eTiny

eTiny (OpenERP’s web server) shows default header images and style that might not really suit your needs.

OpenERP with default style

OpenERP with default style

Being GPL, you can modify that at will, but you have to know how.

Although it’s probably not the best way to do it, you can easily alter the existing images to show something a little different.

This is all done (on a Debian/Ubuntu server) by changing the files in /usr/lib/python2.4/site-packages/eTiny-1.[0.1.1]-py2.4.egg/tinyerp/static (the part between brackets may vary) to suit your tastes.

The important files are

  • css/style.css
  • images/developped_by.png
  • images/mainmenu_button.png
  • images/openerp_big.png
  • images/openerp_small.png
  • images/sidebar_button_bg.png

So just make a backup, open them, change them and put them back in to get a very light (but refreshing change).

Open ERP using blue style

Open ERP using blue style

OpenERP y el mercado peruano

August 24, 2008 3 comments

Dokeos Latinoamérica esta estudiando ahora la posibilidad de adecuar OpenERP al mercado peruano (a lo menos en la parte del plan contable).

Esto brinda mayores posibilidades para empresas e instituciones peruanas de finalmente tener un sistema ERP de grande tamaño a menor costo que las soluciones Oracle y SAP.

Deberiamos entrar en fase operativa con este sistema en el fin de setiembre. Desde ahí empesaremos a proveer esta solución como uno de nuestros productos principales.

Categories: comercial, proyectos, Spanish Tags: , , ,

Caching in eTiny, OpenERP’s web server

I recently learnt that eTiny, OpenERP’s web server, is actually caching pages when in “production” mode (this mode can be changed in the configuration file which is /etc/etiny-server.cfg if you followed the documentation here).

This means that installing some modules may not have a direct visual effect if you have already seen a page before altering it with the module installation.

To avoid caching, you can either change the eTiny server mode in /etc/etiny-server.cfg (to “development” I guess), or simply restart the eTiny server. This will erase the cache.

Of course, none of these methods is actually acceptable once the server is in production, but at least there is a way… (I suppose a way to clean the cache via a script while the server is running would be good).

%d bloggers like this: