[Padre-dev] Big badda boom (MainWindow.pm -> Main.pm, Config 2.0 starts)

[Adam Kennedy]

Just a quick note of warning.

So far this development cycle I've tried to avoid breaking anything big.

But on Saturday I plan to completely destroy all the plugins again.

Firstly, I'm finally going to apply the MainWindow -> Main change I've
been wanting to do for a long time.

The reason it's now safe to do that is that it's time to completely
break configuration for more important reasons.

Config 2.0 sees the end of direct has access to the configuration
variables, and instead you'll need to use accessors.

The reason for this is that Padre::Config is going to become just a
wrapper around 2-3 sub-configs.

The structure looks like this

Padre::Config --> ( Padre::Config::User, Padre::Config::Host,
Padre::Config::Project )

So we'll have one config sub-object that represents the user-specific
padre.yml settings, one that represents the padre.db settings, and an
optional one that represents the project-specific padre.yml file.

When you access config->method it will map the request back to the
appropriate backend, and each setting will need to be aware of which
backends it can be pulled from, in what order.

So this is just a warning, if you want to get any updates to plugins
released to CPAN, please do so now, before we break compatibility
again.

Adam K