schooltool-developers team mailing list archive

[Alan Elkner <aelkner@xxxxxxxxx>]

Hey Justas,

I'm working on getting the report system to work with the flourish
skin, and it's proving to be a real pain.  I've been trying to add the
flourish versions of the various views and viewlet managers/viewlets,
but it's complicated like crazy trying to figure out what goes where
and how to register stuff.

For one thing, the meta directives do the actual registration of the
report links, so I created a new directive, flourishReportLink, that
registers against the flourish manager and viewlet classes as well as
againt the flourish layer.  I think I got that one right.

I then created just the student version of the reports view, which in
flourish views, seems to be just a place holder for other things to
register against.  So I went ahead and created a viewlet registered
against that view and the page content viewlet manager with the name
of “studentreports”.  The viewlet in turn renders a div containing a
tal command, provider:FlourishReportLinks, which in turn tries to
render the report links viewlet manager, which in turn needs to render
the viewlets, which were hopefully successfully auto-registered by the
new meta directive.  You see how confusing this gets?

Since we haven't even started to think about the gradebook, I took it
upon myself to register one of the student reports (for manual testing
purposes) with the flourishReportLink directive right in the
basicperson flourish.zcml, but it's only temporary until we move onto
the gradebook package.

I committed what I have even though it doesn't work.  You can go ahead
and merge my branch to trunk because the reports view is new, and it
doesn't break anything else.  Please have a look at the diff and
otherwise get the report system loaded into your mindspace so that we
can discuss it at the meeting and hopefully work on it after.

Thanks,
Alan