Forum OpenACS Improvement Proposals (TIPs): Re: TIP #34 (Proposed): Application package ui separation


I think that a discussion about design patterns for helper procs, whilst being totally necessary, would quickly go beyond the scope of this discussion.

A new TIP to discuss the design pattern for writing good reusable includes seems like a good idea. It would also help keep this discussion focused on separating ui from functionality. I will create this new TIP.

I like the idea of bcms-ui-base/resources (or soon to be lib), but apart from clean conceptual separation, is there a concrete advantage over simply putting them in <package-key>/lib, as it is not much of an overhead and keeps the number of seperate packages down?