Derek Hoy wrote: > For your application, you could have a simple Scale model, with a > field for the xml definition, to give you complete flexibility, then > build the forms using the scales, and just save a generic data-point > with the scale id and a value.
Well, to tell you the truth, I did not quite get what your application is actually doing. But it sounds a bit too much for my application's needs. At first I had grand visions of doing fancy models for everything but then I figured that it just makes more sense to keep it simple and stupid. The occasional special cases (such as the special scales) I can just implement with some special "hacks". But thanks for the suggestion, I'll keep it in mind for the future. Mikko --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
