Skins are just like a seperate function file include.
require_once( ROOT_PATH."sources/lib/post_parser.php" );
$this->parser = new post_parser(1);
and
$this->html = $std->load_template('skin_post');
are really no different, they just serve as an organizational purpose. I can make any file a 'skin' by just using it as an html import. It's not necessary to use the $var = EOF>>>. thing, it just makes it easier because then you can use " without escaping every instance, because End Of File becomes your quotes for the variable string.
So really, you don't use the acp to edit post_parser.php...
I don't see how it's easier. Easier to install mods because the directions use the acp skin manager? Or what?
If you ever try to tear apart a whole group of files and massively change how a section of the board acts and looks, you won't find the skin manager easier.
1. I don't see any way to delete bits.
2. Passed in variables are in it's own seperate little box.
3. <if="ipb.member['id']"></if><else></else> is an if/else statement in the skin manager? How ugly is that. I rather not fool around with fake php code if it's just going to be parsed as php anyways.
4. More organized. All your functions for a file are one click away... unlike the multitude of clicking you'll have to do to do some real editing of a skin.
Using the skin manager can't be referred to as the "right way" of doing skin changes... it's just invision's dumbed down version of real code for people who have no clue what they're doing.
I mean, I still will try to make that one backwards converter work...
But if I can't...