nah, the code is written for core1. Basically both core layers provide a
really basic framework to build layout layers on - core2 provides a lot
more framework than core1, though. A bunch of our layouts are effectively
just stylesheets on top of core2, or stylesheets with a tiny bit of extra
code - with core1 layouts typically had to individually write formatting
code for parts of the page (which is why some of LJ's core1 layouts look
really different from each other, and why custom CSS for one layout would
fail basically completely on another layout).
Thinking about it - the CSS parts of the custom generator layout should
work on top of that compiled source, because the element names are the
same. The trouble is that it looks like the custom layout uses an S1 hack
to embed extra HTML into the layout, changing the page structure - those
parts would have to be re-written, I suspect.
(I hope that makes sense, I'm not fully awake right now)
no subject
Date: 2016-01-19 06:25 pm (UTC)nah, the code is written for core1. Basically both core layers provide a really basic framework to build layout layers on - core2 provides a lot more framework than core1, though. A bunch of our layouts are effectively just stylesheets on top of core2, or stylesheets with a tiny bit of extra code - with core1 layouts typically had to individually write formatting code for parts of the page (which is why some of LJ's core1 layouts look really different from each other, and why custom CSS for one layout would fail basically completely on another layout).
Thinking about it - the CSS parts of the custom generator layout should work on top of that compiled source, because the element names are the same. The trouble is that it looks like the custom layout uses an S1 hack to embed extra HTML into the layout, changing the page structure - those parts would have to be re-written, I suspect.
(I hope that makes sense, I'm not fully awake right now)