I agree with you about the more general point that there need to be proper standards about the basics of how S2 layouts work. Having a competition with a very short deadline and few rules is not a good way to achieve consistency, but I'm not sure what is.
Regarding the specific issue with the user layer being rewritten, though, can you not get round it by defining the custom comments in the theme layer? That's what I usually do when I'm messing around with S2 styles anyway. Or am I missing something here?
It seems everytime I add/change something in the layer, it deletes all the code for the custom comments. I don't know why it's only eatting that and not anything else.
Ironically, when I finally decide to make a new layout, and convert to S2, I pick the insane evil layout for my first try. *facepalm*
Known issue, bit of an oversight on my part when I gave myself only 36 hours to come up with Nebula in the first place. Working on rectifying about six other known issues today, should have a megapatch shortly.
yeah. after a while i decided to cruise zilla, found your bug entry, and in turn the comm you made, and the bug/todo list.
there are several factors to the not-well-builtness of the layouts. among them being not having standars, the pre-existing layouts not being standardized, having a short amount of time for the contest, etc.
not a direct attack to you, just a big heap of annoyance that boiled over.
i apologize if you took it personally. and if not, that's great too. :)
Once upon a time I did some work towards having the customize interface change the property settings without destroying the other stuff in the user layer. It worked by having the system parse the existing layer code, change the right property set stuff and then write out new S2 code containing all of the same stuff that was there before. Unfortunately it depended on the S2 compiler's “Canonical S2” backend which hasn't worked since the compiler was ported from Java to Perl way back in the day.
I would like to fix this, but it's one of those annoying things that isn't too hard in itself but is blocked by a separate time-consuming and tedious task which would also probably end up just getting stuck in Zilla and never committed.
Comments 7
Regarding the specific issue with the user layer being rewritten, though, can you not get round it by defining the custom comments in the theme layer? That's what I usually do when I'm messing around with S2 styles anyway. Or am I missing something here?
Reply
Ironically, when I finally decide to make a new layout, and convert to S2, I pick the insane evil layout for my first try. *facepalm*
Reply
i like having my set commands in my user layer. and nothing else.
and having my custom code in my theme layer. and nothing else.
might just have to deal.
i still think something should happen about it tho.
Reply
Reply
there are several factors to the not-well-builtness of the layouts. among them being not having standars, the pre-existing layouts not being standardized, having a short amount of time for the contest, etc.
not a direct attack to you, just a big heap of annoyance that boiled over.
i apologize if you took it personally. and if not, that's great too. :)
Reply
Once upon a time I did some work towards having the customize interface change the property settings without destroying the other stuff in the user layer. It worked by having the system parse the existing layer code, change the right property set stuff and then write out new S2 code containing all of the same stuff that was there before. Unfortunately it depended on the S2 compiler's “Canonical S2” backend which hasn't worked since the compiler was ported from Java to Perl way back in the day.
I would like to fix this, but it's one of those annoying things that isn't too hard in itself but is blocked by a separate time-consuming and tedious task which would also probably end up just getting stuck in Zilla and never committed.
Reply
Reply
Leave a comment