~blog~

Django-treemenus new release 0.5

I have just packaged a new release 0.5 for django-treemenus

That release should only concern people working on Django's development version after the merge of the newforms-admin branch. I also hear that Django 1.0 alpha has just been released, so that's good timing ;)

If you're using Django's trunk prior the NFA merge, then you can stick to 0.4.

I've also included the German translation kindly provided by Thomas Kerpe (thanks Thomas!). Available languages are now: English, French, Dutch, Russian and German. Please keep sending me your translations and they will be included in future releases.

Also, I'd be very interested to hear testimonials of people using this app. How do you use it? Do you use the menu extension mechanism? How would you like to see this app improved? Any feedback/criticism is very welcome ;)

Comments

# Rob van der Linde 22 Jul 2008, 6:36 p.m.

Hi Julien, I'm glad that you have upgraded treemenus to work with NFA. I have been on NFA for a while now and was hoping treemenus would be upgraded soon to support it, thanks for this.

Since you're asking how people are using treemenus, well, my case is a little different I suppose, as I actually mod treemenus a little to include it in a lightweight CMS I am building on top of Django. The CMS is nowhere near finished but will be open off course. I use a StaticPage class, similar to flat pages but with more options. I mod treemenus to also support a StaticPage as a foreign key for each node, so the user can choose a page from a dropdown list for each node. I also added other functionality such as only showing nodes if a user is logged in or is in a specific group, or is an admin, basic privileges, etc.

I have not yet upgraded to 0.5, as I only just seen this post, so I got a bit of coding to do, to get it working with this new version still, but hopefully should do this in the next few days.

One of the things I have noticed though, which I considered changing maybe, is if you have a fairly large menu, things start getting really slow. This might be because for each node it's rendering a small template. I was considering maybe changing it in my modified version, but haven't given it much thought yet.

# Brian Rosner 23 Jul 2008, 12:52 a.m.

This is good hear Julien! I am looking forward to checking this out very shortly.

# Julien Phalip 23 Jul 2008, 7:17 p.m.

@Rob

Thanks for sharing your thoughts. I'm looking forward to seeing the finished CMS you're building! By the way, you say that you've added some functionality (e.g. management of priviledges, etc.). Did you hack treemenus or did you use the extension mechanism that comes with it? From what you describe, that mechanism could do the job without the need for hacking the existing code.

Considering speed issues. I haven't noticed anything related yet, but please let me know if you spot a problem, and open a ticket at google code. I'll see what I can do.

@Brian

Thanks for dropping by. Let me know what you think if you have a chance! It'd be great to hear some feedback from one of the core devs of the new admin system ;) Cheers!

# Rob van der Linde 23 Jul 2008, 9:14 p.m.

I was hacking Treemenus mainly, but probably shouldn't have really. It's not too late to undo things, and look properly into the extension mechanism, which I will do some time soon when I get the time this weekend.

The speed issue was with a very large menu mainly. But before getting too far into that, I will try to implement Treemenus 0.5 without the hacks using the extension mechanism and see how that goes first.

# Julien Phalip 24 Jul 2008, 4:03 p.m.

Hi again Rob,

Just so you know, I'm currently refactoring the codebase of treemenus so that it uses all the goodness of NFA. The result should remain backward compatible and should also make it a lot easier to customise and extend. So, stay tuned for more ;)

Post a comment