One lesson I have learnt from being a perfectionist is that if I'm too idealistic about something I'm working on - it never gets done! It's good to aim high and plan, but nothing beats working code! I think the patch has more value in than out. (another 0.2 cents from me) Stefan Nagtegaal wrote:
Is it really neccessary to include the image.inc file for each page view? We already include too much stuff. Gerhard
So again: Can we not think (i.e. discuss, not code) better solutions for this image.inc and its private plugins? Please? Iwhat we have now is better than nothing, bu8 it introduces a lot of complex, nonstandard stuff. If we continue like this, we *will* lose Drupals best feature: being clean. Examples of non-clean parts are: flexinodes plugins, e-coms private plugin system, locale.module private code splitting, and now image private plugin system. I foresee serious problems, and therefore plead for some thoughts and discussions before action.
Regards, Bèr
As you all know I'm a big fan of consistency. Whatever it's code, GUI's or something else, it _should_ at all times /be/ consistent, because being that either improves usability..
Why I don't think this should be a showstopper is that we already have inconsistent GUI, we have inconsistent code, and at this point I think the feature addition does justify the extra inconsistency. Please, don't get me wrong: I'm not saying drupal is bad, but i'm saying that drupal isn't at the usability level where it /should/ be, or does belong..