On 11/11/15 02:06, S Page wrote:
On Tue, Nov 10, 2015 at 2:39 PM, Isarra Yos
<zhorishna(a)gmail.com> replied:
On 10/11/15 21:59, S Page wrote:
The tutorial is pretty good IMO, the problem is
it forced repetition
This may just be because I did it at three in the morning; it probably
doesn't need that much. I'll see if I can clean that up a bit. >.>
D'oh, I'm sorry, I meant the on-wiki three-part skinning thing that's been
around for a while and introduces in a nutshell as "This page is part 1 of
a three-part tutorial".
Oh, I want to murder that. Have I mentioned that? I think I have, but if
I haven't, I'D LIKE TO MURDER THAT. It doesn't even say how to do the
important bits, while focussing on bits nobody in their right mind will
ever even touch, with no real structure or sensible organisation. It's
ludicrous.
Re:
https://www.mediawiki.org/wiki/User:Isarra/How_to_make_a_motherfucking_skin
I have a dream where both extensions/BoilerPlate and skins/Example are a
script that prompts for your extension or skin name, clones it into
YourProject, sets up the example as a non-master remote (so you can track
updates to the skeleton), and does the mindless file renames and search and
replace to YourProjectName. [1]
Or not even having the remote necessarily (letting people just download
it so they can mess around without necessarily leaving any sign around
they did), but yes, that sounds very useful.
Also you can
probably delete any random things that say 'composer' or
'grunt' or
whatever in the filenames. Not really sure why those are in the
example skin. That's a bit confusing.
Nope, they're gold. It means you can run npm test and composer test and
automatically have a growing set of basic tests and coding checkers run for
you. See BoilerPlate's README.md [1] , maybe the same instructions should
be copied to skins/Example.
Isn't that all broken by default because it's still using the example
config?
The good advice in your Step 4 and Testing could fit
well into Skinning
Part 3.
Frankly the fact that there are three parts means most users are never
going to make it to part three. Which is also something to... not do?