[ixpmanager] Customer User Problems

[Barry O'Donovan]

Kyle Spencer wrote:
> In my view it's a necessary feature for branding and localization
> purposes (e.g. language).

Skinning isn't really the way to solve I18N and L10N - that needs a root
and branch effort throughout the code with proper use of language
libraries.

However skinning is very useful for:

 - header / footer changes
 - alternations to stock configs such as route server stuff
 - alternations to explanatory text

The big issue with skinning is that you'll need to track your changes
and compare to changed stock files on upgrading as you may miss out on
new features (menu links) or feature enhancements.

We tend to include a list of changed templates with every release.

> It's just incredibly clunky in IXP Manager because site code is mixed
> in with two overlapping skin systems.

The next release will have us about 60% of the way there. Then another
should hot foot it after that being us to 75%. There after we're
planning on working on the customer area which should have is 85/90%.
We'll then just gather whatever's left and move it over.

IXP Manager v4 was always billed as a framework migration release. We'll
stamp v5 when all the old stuff is gone.

 - Barry