How do you propose merging them? Do you mean to have a single class that figures out what markup to use based on what it’s added to? Or do you mean have two separate classes which are determined in MXML?
There’s probably going to have to be a lot of conditional code to deal with a single class. For example: a transform bead would have to know the markup of the class to know how to properly do the transform. As far as APIs go, it might make sense to have separate APIs, I have not thought that completely through. On Jul 27, 2016, at 10:40 AM, yishayw <yishayj...@hotmail.com> wrote: > Unless Rect and RectComponent have different APIs I would elect to merge > them. We don't want to make the client think too much on what s/he should > use. > > If we change IUIBase.addedToParent() to > IUIBase.addedToParent(parent:IUIBase) we can probably make the necessary > adjustments there. That also works around the mxml compile error question. > > The resultant DOM structure becomes less transparent (Rect could map to > either <rect/> or <svg><rect/></svg>), but I don't think that would confuse > me if I was inspecting the DOM. > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/Changed-svg-namespace-tp54150p54220.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
