On Thursday 13 May 2010 02:18:37 pm Paul McNett wrote: > On 5/13/10 2:07 PM, Ed Leafe wrote: > > On May 13, 2010, at 4:48 PM, Paul McNett wrote: > >>> It was never added to the Class Designer, as dPageStyled came after > >>> the Class Designer was written. I'll see about adding it ASAP. > >> > >> But also, it should be possible to add a non-cdxml based class to a > >> cdxml-based form at runtime. It would just be done in code launched from > >> frm.afterInitAll(). > > > > Yeah, that's true, but when you have a product that features a WYSIWYG > > designer, and the solution is to write code, that's disappointing at best > > and confusing at worst. > > Definitely not ideal, but my point was that it was possible. The user > doesn't have to start from scratch if they find a control that isn't > wrapped or isn't completely wrapped in CD. > > > We should really make it a requirement that before a UI control is > > released, it must be incorporated into the Class Designer. Until then, > > I'll add them one by one. > > Sounds good. Until a new control is wrapped for CD, a ticket should be > outstanding, and before we release, such tickets should be fixed. > > Paul
CD is Ed's baby therefore before I would add code to it I would want permission. I think that would be the right way to do it. But just adding a custom control that is wrapped or whatever would be different. It's unlikely to break anything and could be tested by others. So when you say released do you mean as an SVN or the fixed Dabo? Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
