> An example: I like Suzy Creamcheese's Blog application but she used > django.contrib.comments in it, and I want Joe Schmoe's slashdot style > commenting system. I also want people who have blogs to be able to post > their own photos, but Suzy Creamcheese's Blog application uses a BlogAuthor > model for biographical data and needs it set as the PROFILE model and John > Shaft's photo gallery application uses a Profile model for biographical data > and also needs it set as the PROFILE model. I can't integrate these without > hacking on them. But if Suzy wrote her Blog application to implement IBlog > and IBlogManager which contained extension points for IComment and > ICommentManager, I could integrate the two systems without having to alter > code. And if both the BlogAuthor model and the Profile model implemented the > same interface then I could still use them together as User can provide the > extension point for that interface. This was design error of applications creators. Let's think what Django could do to prevent such errors. > Or if I'm using Satchmo and I've written an excellent CRM system in Django, > I want Satchmo to use the shipping and contact information that I've defined > in my CRM system, and if they both implemented IPerson, IPostalAddress, and > IPhoneNumber, I could drop in those replacements. Without that, I'm bound to > either duplicate my data across the two applications, hack Satchmo to use my > CRM, or constrict my CRM system to require Satchmo. I can see abstract idea. But don't see right implementation idea. 1) You can do this all without all javaish interfaces. Python metamodel is open for changes when program is running. 2) Interfaces are not python way of doing stuff. google: duck typing. Please take my arguments into account and reconsider your idea with them.
-- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
