Yeah, this is my first attempt at using Haystack and I'm a bit lost at the moment, thinking about adding back the direct to database search method until I'm more familiar with Haystack. I also don't like the idea of having to schedule a job just index the search file, and the default Python based search backend for Haystack is not cluster friendly.
There was a rough roadmap online for a while but other commercial software were using it to get ideas for improvements on their products and not contributing back in any way to Mayan, so I took it down, and instead working on features directly requested by users of Mayan. I could really use help with documentation and unit tests. My initial plan was to keep all the improvements on the development branch, and work only on bug fixes for the master branch (the stable version). But since the development and master branch have diverged so much and since the development branch is still to unstable to call it Mayan 1.0, my new approach is going to be to bridge the gap by moving code from development to master. If you or anybody else wants to dig deep into the code, the new priority is getting as much code moved to the master branch starting with the navigation, icon rendering and app registration code; code cleanup and organization (moving links to a links.py file as well as an icon.py file, remove isolated functions and turn them into simple classes with contextual methods) is also a big priority to make it easier for developers writing 3rd party apps for Mayan. The changes you noted are a good example of the kind of clean ups taking place: the api.py file was removed from most apps and is only present if the app exposes an API for external use by other apps; the register_links method was removed as links are now a classes (instead of simple non contextual dictionaries) and registered as soon as they are created only bound to a view or object class later on with the bind_link function; icons are also a class, this allows for switching icon sets very easily instead of depending on the Silk icon set text names. If there is interest I can write a shared GDrive document to coordinate efforts. --Roberto On Sunday, December 16, 2012 11:57:07 PM UTC-4, Lachlan Musicman wrote: > > Hola, > > I've forked the dev branch to start working on the code base, and was > after a few tips: > > 1. When running ./manage syncdb --migrate --noinput to get started with > testing, I'm getting Haystack errors. I've managed to squash a couple, but > I don't want to stray too far from the herd - there seems to be a missing > HAYSTACK_SITECONF file? should it be > HAYSTACK_SITECONF='apps.dynamic_search.search_index' > > 2. Is there a roadmap that is being followed or a list of "TODOs" that I > could use for guidance on what to do next? I've got a couple of ideas, but > don't want to tread on toes... > > cheers > L. > > > -- > ...we look at the present day through a rear-view mirror. This is > something Marshall McLuhan said back in the Sixties, when the world was in > the grip of authentic-seeming future narratives. He said, “We look at the > present through a rear-view mirror. We march backwards into the future.” > > http://www.warrenellis.com/?p=14314 > --
