<div dir="ltr">Ugh, of course there is stuff like "look at class side" ;-)<div><br></div><div><br></div><div><br></div><div>Best.</div><div>Karl</div><div><br></div><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 4, 2016 at 4:20 PM, Tobias Pape <span dir="ltr"><<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On <a href="tel:04.03.2016" value="+464032016">04.03.2016</a>, at 15:59, karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>> wrote:<br>
<br>
><br>
><br>
> On Fri, Mar 4, 2016 at 3:25 PM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br>
> On 03.03.2016, at 23:28, Chris Cunningham <<a href="mailto:cunningham.cb@gmail.com">cunningham.cb@gmail.com</a>> wrote:<br>
>><br>
>> On Thu, Mar 3, 2016 at 12:31 PM, karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>> wrote:<br>
>> Nice.<br>
>> BTW: there is a lot of empty categories in the Preferences class.<br>
>> We must remove those in a post script or something.<br>
>> Preferences organization removeEmptyCategories<br>
>><br>
>> I'm not sure how to do it ?<br>
>><br>
>> Add it in a package preamble ?<br>
>> Does we then need to remove the preamble again ?<br>
>><br>
>> If I remember right, the preamble (and postlude?) only get run once - when they are first changed. After that, they are skipped.<br>
>> This means you want to leave them in and not remove them - otherwise a person later on would update from Trunk and just get the latest version - which doesn't have the preamble - and the work wouldn't be done.<br>
>><br>
>> Or am I wrong, and this only happens with Class initialization?<br>
><br>
> It happens exactly the same as with class initialization:<br>
><br>
> If the definition (of the script or method) changed, it gets executed.<br>
><br>
> You cannot rely on it having executed, or it only executing once. It’s better to write it in a way that running it again does no harm.<br>
><br>
> We can force execution by issuing an update map, but it’s better to avoid that.<br>
><br>
> For the problem at hand (empty method categories) we also could just add a step to the release builder to ensure all categories are clean.<br>
><br>
> We could run this for all classes I guess. I don't see much value in keeping empty method categories around...<br>
><br>
> Anyone objects ?<br>
<br>
<br>
</span>"look at class side" …<br>
<br>
Best<br>
<span class="HOEnZb"><font color="#888888"> -Tobias<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> Best,<br>
> Karl<br>
><br>
><br>
> - Bert -<br>
<br>
<br>
</div></div></blockquote></div><br></div>