Re: representing a possible future object in a form?

Preston Having not done this before (but maybe needing to soon...) the grid approach seems the best solution. Actually this is not really a Django issue per se; more a "mismatch" between the "excel-type" view and the underlying database reality. Django is just the middle-man, translating

Re: representing a possible future object in a form?

On Nov 18, 12:18 am, Derek wrote: > It would be great if perhaps one of you could write up a more detailed > description (i.e with code) of this as a blog entry... or maybe a wiki page? Derek, before I posted the vague description above, I looked at my code for an example

Re: representing a possible future object in a form?

It would be great if perhaps one of you could write up a more detailed description (i.e with code) of this as a blog entry... or maybe a wiki page? On 17 November 2010 18:10, bobhaugen wrote: > I've done this several times, and Toby's description is pretty much > what I

Re: representing a possible future object in a form?

I've done this several times, and Toby's description is pretty much what I have done. Sometimes three levels of non-data-model classes to represent the matrix: a table class a row class a cell class Then formsets to populate the rows with data entry fields. Then builder methods to morph the

Re: representing a possible future object in a form?

Preston, I had a similar problem to solve when working on a research project that collected a lot of data from companies, much of which was missing. As I understand it, your data set is effectively a sparse, two-dimensional matrix [1], and you want to be able to edit this in the browser. I'd