I think that there is no activity in life that I love more than studying (perhaps coding ). I love to get in touch with new things, especially new technologies, new way of coding, etc. Another thing I love is software design. So, I really enjoyed spending all day to start up studying for my project design.

After I set up another thing or two in the project’s wiki page, I announced it in the dev list and in the talk-it list. Then I went into the #osm channel to get in touch with other developers there, telling my wiki page URL and trying to get some feedback.

I’ve received a few hints, which I reported in the wiki page as well, crediting everyone. As I’ve got in touch with Mapnik users/developers, I’ve also received a link to a Mapnik’s rule file and to a little help about it. I think that a little bit of study about Mapnik internals will give me more ideas to improve the abstractness of my architecture and JS API.

Then I’ve started to study and take notes about Osmarender rule file internals, writing down some new ideas also. But I don’t want to anticipate anything now, because I’ve to study more to be sure. I’ve studied Osmarender a few when I was writing my application, but now that I’ve more awareness of it.. I have to confess that I’m really loving it

However, as far as I can tell, I’ve found similarities in Osmarender’s and Mapnik’s rule file… perhaps, if I can get a good design, there is room for some Mapnik compatibility for this frontend. But… now I’ve to stop dreaming, and don’t forget GSoC deadline

I’ve found also something odd: dragging and dropping, by error, an XML Osmarender’s rule file in Firefox 2, I’ve found that he got rendered automatically! This is not something really new, I know what’s behind this functionality.. but now.. why using a JS call to the XSLTProcessor Firefox 2 crashes (with the same rule,osm data, osmarender.xsl version)? Beside this: I knew that Firefox 2 doesn’t handle node-set() XSL instructions… why is it working? Perhaps I was wrong when I’ve found this, perhaps 2.0.0.13 version handles node-set() instructions… perhaps there is something magical in my Kubuntu laptop. I’ve to dig inside this in the next days (along with some Osmarender rules’ playing), because more cross-browser compatibility means more users, and more users means more OSM spreading, and more OSM spreading means GOOD!