On Wed, Sep 22, 2010 at 2:48 AM, Klaas van Schelven <
klaasvanschel...@gmail.com> wrote:
> Shawn: thanks
> Just started watching the video and I'm noticing my complaints are not
> unique.
>
> > Wow! I guess your definition of an app and expectation of re-usuability
> > from an app written by someone else
> > is fairly high!
>
> Actually, a big part of the problem is reusing my own apps. Mostly
> since all of them provide models, and every use case either needs
> changes to those.
>
> >
> > We have built serveral news sites based on Django, and a lot of code gets
> > rewritten everytime, because customer requirements are very different. We
> > reuse 90% of code in every project, but 10% gets rewritten or gets
> writtenf
> > fresh.
> >
> That's interesting.
> Do you adapt models across your apps?
> Do you deal with (some kind of advanced) authorization that differs
> over projects?
>
We don't do anything that's extra-ordinary. Tried it and it failed. While I
have not quite experimented in depth with Pylons, the problem what you are
describing about reusability exists in some way or other with every
platform. We've been through almost all major frameworks from Java based
ones to CakePHP to Rails.
I'm sorry to disappoint, but all I do is move code between projects and then
customize models, views and urls according to the needs.
Even an app which is pretty well written like django-registration, I had to
customize it number of times to suite specific needs of some of my
customers, that my versions are impossible to reuse.
> I'd like to know how.
>
> > I know there's a number of apps out there including ones written by
> people
> > like me, which are grossly unusable. I guess that's primarily because its
> > written by developers for a specific work, and when they threw it back
> into
> > the wild, they did not pay enought attention tomake it really re-usuable.
> > However there are quite a few exceptions,
> >
> > I completely agree with your views that with the way you write code with
> {%
> > url in templates, and decorators, reusing the code is a pain. I had to
> scrap
> > a project based on Pinax for the same reason, and then rewrite a mini
> scoial
> > framework, because pinax is not customizable beyond a point.
>
> Yeah I looked at Pinax too (because it is presented as a "reusable
> app") but I was a bit disappointed. (not so much in the app, as in how
> it is an example of reusability).
>
> Problem is "{% url %}" is presented as a Good Thing (DRY) while it
> makes reuse in some ways harder
> What's your alternative, i.e. how do you provide links that are
> project independent?
>
Pinax was a bad experience for me. I am going to give glamkit a try now...
> > However my personal experience is that it's true for most platforms.
> There
> > are always trade-offs and trade-ins when you use a platform.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
--
Ramdas S
+91 9342 583 065
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
