<div class="gmail_quote">On Sat, Apr 3, 2010 at 2:35 PM, Nicklas Karlsson <span dir="ltr"><<a href="mailto:nickarls@gmail.com">nickarls@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Where in the event hierarhy does "subfunction" go if the module does<br>
many things? event.subfunction. or subfunction.event.?<br></blockquote><div><br></div><div>I'd say if you've got a fairly substantial number of classes for a particular function, then you should group them [function].event. I would say certainly use your judgment there. What we want to establish is a general structure. That's just my suggestion. If you have a different viewpoint, please share.</div>
<div><br></div><div>Btw, the main reason this issue comes up in Seam 3 is because the source code is now modularized :) In Seam 2, most of the classes were together and it was more obvious where to stick things.</div><div>
<br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>