What is the goals/direction for Plogger? Is it to become all things to all people, or be a quick-n-simple php-gallery that's database-based? should all options have option buttons in the options page? Should there be more otpions? less options?
at what point does answering requests turn simple Plogger into bloated Plogger?
I like the script a lot, and can how it can/will be extended. But how far can/should Plogger go?
At some point in the future we will implement a plugin architecture, this way we can have quick and simple Plogger, which can then be extended with plugins as needed.
Michael, why do plogger need limits anyway. Yes, as you said, all extra options and features can be made optional in the admin panel and with just one click, each feature is enabled. May be beside the option, it can be mentioned that this feature is optional. This way it can be both quick and simple galley besides having some cool features towards world domination. I dont think its a bad idea to have optional features to make plogger an advanced gallery besides being very very simple. What do you guys think?
Michael, I think you bring up a good question, when do you stop adding features and bells and whistles? We've seen what happens to scripts that grow out of control (I'm looking at you Coppermine), and it isn't pretty. 10 MB for an image gallery? Really, what do these huge galleries do that Plogger can't? Plogger is lightweight now, and I think it is entirely feasable to evolve the software while still maintaining the "less is more" philosophy of the current release.
The whole driving force behind Plogger was to create something that would unobstrusively integrate into any website. Plogger has an unassuming and simple design that makes it look at home in almost any setting. In this sense, Plogger is more of a component than a stand-alone gallery, and really the whole spirit of the thing is that you take it and make it your own.
I think that in the future we may be adding a few more features, while at the same time keeping the user experience intuitive and usable.
I think ultimately your software is successfull if people enjoy using it. If you keep the design simple, intuitive, and powerful, people most definitely will. Does that answer your question?
"Plogger has an unassuming and simple design that makes it look at home in almost any setting. In this sense, Plogger is more of a component than a stand-alone gallery, and really the whole spirit of the thing is that you take it and make it your own."
This is the reason I chose Plogger as the gallery for my site. Great script!
gangavalli -- I don't necessarily think that plogger "needs" limits, but I was specifically thinking about Coppermine -- a full-featured system that I got bogged-down in and gave up on, eventually.
I want plogger to have more features, but to never get to a Coppermine feature/complexity swamp.
I agree with anti. Keep the basics of Plogger clean, simple and transparent and in the future add some plugin structure to it. That's what attracted me to Plogger in the first place. Coppermine and Gallery or way too big. And the simple galleries are too simple. Just like Honda started doing in the eighties with some of their motorcycles :) (I had one for 14 years). They had made an engine that was strong, reliable and versatile. Then they build a lot of motorcycles based on that same engine for twenty years and more. All very different. Some very basic, some rather modified with all kinds of extras, but all based on the same frame and engine.
The question of course is, what belongs to the basics and what is an extra? To me the basic Plogger should run stable (bulletproof) on most servers and the interface should be simple and intuitive. A few more things should be added to make it a bit more attractive (some of them are already talked about in this forum and through the 'tickets' on the Trac pages), and that's it.
But you never know what will happen with it in the end. Like, for instance, I'm riding a Yamaha bike at this moment ;).