From: Christopher H. <ch...@ch...> - 2005-05-11 14:47:39
|
On Wed, 11 May 2005, Sam Tregar wrote: > On Wed, 11 May 2005, Christopher Hicks wrote: >> Has anyone found a way to restrict elements to a single site or does >> doing so require seperate krang instances? For end users having >> seperate krang instances wouldn't cause any pain and it would be >> slightly less confusing when dealing with the element list. But for >> our designers and support folks it would be a pain to need to switch >> instances with every phone call. > > Yes, you'd need separate instances at present. At one point we talked > about supporting permissions to limit access to elements. I think > that could be used to do what you're asking for. Another alternative > would be to allow Krang::ElementClass::children() to be dynamic. (Or > maybe it already can be? I keep going back and forth on whether I > think it will just work or not. Suffice it to say that it's never > been done.) Thanks for your thoughts on this. This is way down on our krang tweak priority list, but if I come up with a solution I'll definitely share it. -- </chris> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) |