Gavin Morrice wrote:
Hi - Why not develop the plugin in your app's /lib directory first?
Once you're happy with how it works, you can transfer it over to the
plugin's /lib directory
That way you don't have to restart the server or change your apps
That's exactly what I was going to suggest. I have several lib files I
develop parsers with and other app factorization methods with that I
will eventually place into a plugin for later use. As I'm in
development, I keep them there so I can change and keep going along.
Plugins are for finished pieces that you want to use in multiple
projects. If you are developing something that will be used in multiple
projects, get it working first and then create a plugin for it.
Otherwise, if it's just a one-off type of deal, keep it internal..