Neat ideas!
My main point of feedback is that you're dealing with a *HUGE* problem
-- dabbledb represents literally years of work, and trying to
reproduce that in a single summer is seriously unrealistic.
I think you should scale back your proposal. "inspectfile" would be a
nifty addition to Django, and quite within the scale of SoC. It's not
quite that small, really -- there's a metric ass-load of data formats
out there, and dealing with 'em will take some hard thinking. Probably
some sort of plugin architecture and interactive "questionaire" bits,
too.
Essentially, it's better to do a small thing really, really well than
only half-implement something bigger.
Jacob
+1
My tip would be to be really clear about your goals: what will you
accomplish, when, and what counts as a success?
This is a really cool idea, I hope we get to see more of it.
>
> Jacob
>
>
>
> >
>
> My main point of feedback is that you're dealing with a *HUGE* problem
> -- dabbledb represents literally years of work, and trying to
> reproduce that in a single summer is seriously unrealistic.
Yes, I realize that the types of migrations that dabbledb does are
currently not very possible with Django. I guess I am just looking at
it for ideas of how to make things easier.
> I think you should scale back your proposal. "inspectfile" would be a
> nifty addition to Django, and quite within the scale of SoC. It's not
> quite that small, really -- there's a metric ass-load of data formats
> out there, and dealing with 'em will take some hard thinking. Probably
> some sort of plugin architecture and interactive "questionaire" bits,
> too.
>
> Essentially, it's better to do a small thing really, really well than
> only half-implement something bigger.
So maybe I should ditch the web-interface and just make a good, robust
inspectfile.
Thanks,
Collin
Glad my hint wasn't all that subtle :)
I, for one, would use ``inspectfile`` all the damn time.
Jacob