[10:54]<hannesw> documenting some code is a very good way to find inconsistencies in naming etc. [10:54]<hannesw> http://dev.helma.org/ng/helma.skin/ [10:55]<hannesw> simono: should we use block-style subskins in ng? with start _and_ end tag? [10:56]<hannesw> and should we rename "subskin" to "block" or something similar? [10:56]<hannesw> earl: are you here? [10:56]<simono> hannesw, not sure about end-tags... i'm still thinking about how to layout the skins with inheritance [10:57]<hannesw> ah, gotta reply to your last helma message... [10:57]<hannesw> i think you missed that skin inheritance in helma follows prototype inheritance [10:57]<hannesw> so you can only extend a skin in a parent prototype [10:58]<hannesw> put base.skin in HopObject so you can extend it anywhere. [10:58]<hannesw> or in Global, if it's a global skin... [10:58]<simono> okay, was expecting more from skin-extend [10:59]<simono> extending a skin that is defined in a different prototype doesn't seem to far fetched [10:59]<simono> o/c we can work around that [11:02]<hannesw> Well just put it in HopObject! That's the way Helma 1 works, isn't it? [11:06]<simono> yes, wasn't so clear for me that skin-extension and inheritance are coupled. [11:10]<hannesw> coupled is the wrong word. It would be really hard to implement it any other way in h1 [11:17]<simono> okay. extending still saves us code, so its all good :) [13:34]<earl> hannesw: yep [13:42]<hannesw> hi earl, nice to see you :-) [15:29]<earl> hannesw_: did you want anything specific before :) ?