On Wed, Apr 6, 2011 at 7:44 AM, DaNmarner <danmar...@gmail.com> wrote: >> 1) It's almost illegible. Between your mail client's munging of line >> wrapping, and the completely unreadable code samples, it's very >> difficult to tell if you have presented a good idea. > > Pardon the format. I actually auto-wrapped the text with vim and copy > pasted at the first time. Realizing the result is ugly, I actually > deleted it from the thread (using the google group web) and reposted > without extra formatting. I was going to apologize for the duplication > but didn't want to further spam everyone on this list. > > I believe what you read is the first copy, and the 2nd would be > better. > >> 2) You haven't done the one thing that the Django GSoC wiki recommends >> -- provide, as a proof of your concept, an expression of Django's own >> serializers using your proposed serialization syntax. >> >> If you'd done any research on the topic, you'd find that I've raised >> the second point every single time this topic is proposed -- in fact, >> there's a currently active django-dev discussion with another student >> proposing a serialization project. > > I regret that the unfortunate format stopped you from reading through > my proposal, but my code example merely presented a case where the > "extra" customization is provided: excluding fields, renaming key > names, serializing nested objects. > > If none of above needs exist, then the user *don't* need to write > anything. A default configuration would be used. And that, I assumed > from the beginning, would be the current format the serializers use.
Granted. However, saying "It will exist" isn't a compelling argument for us to pick your project. I already know it will exist. What I don't know is what it will look like under your proposal. So - show me what it would look like. Show me how I, as a third party, would use your proposed syntax to define output that would match Django's existing serialization scheme. Yes, this serialization format will exist as a built in default; but I should be able to reproduce that format in my own code if I want. And then, for bonus points, show me how to define a serializer that matches the pathological case that I posted in the other thread. The point here is to provide a practical demonstration that your proposed syntax is flexible and clear enough to do the job it needs to do. I don't doubt for a second that you want to do this project, and that *you* think that you can do it. However, you still need to convince *us* of that fact. We're not going to accept a proposal without a clear indication that your proposal is at least heading in the right direction are at least on the right track. Yours Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
