What I am suggesting is that we use the JSON format and URLs that are generated by this combination. If you later decide to implement it in a different framework, you can still use the same external representation.
On Apr 18, 2013, at 4:33 PM, Florian Fuchs <flo.fu...@gmail.com> wrote: > 2013/4/18 Richard Wackerbarth <r...@dataplex.net>: >> Yes, yes. Please re-invent the wheel once again. >> >> And while you are at it, you might just remove the dependancies on zope and >> storm, etc. >> >> I think that you are missing the point that, at this time, this is intended >> to provide the capabilities that MM-core chooses not to implement. >> Those website components (HK and Postorius) are being driven by Django and >> you only make it more difficult to implement them when choose a different >> schema to model/present the data. > > I don't want to re-invent the wheel and I don't advocate dismissing > Django. Django is probably perfect for the prototype. It might also be > perfect for the final thing. But we don't know what database we're > gonna use in the end (which determines if the Django ORM still fits), > or if we'll use many HTML templates etc. If we end up not using many > of the things that make Django great, we might wanna think about if we > want to use it. And might still come to the conclusion that we do. All > I'm saying is: The environment for such an app could be a little > different to Postorius/HK, so let's spend some thought on it. Is this > such a bad idea? > > Florian _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
