On 10/2/12 1:59 PM, "Om" <bigosma...@gmail.com> wrote:
>>> 3. Interactive layer: Any object or group of objects in the design area
>>> can be selected, resized, rotated, constrained.
>> Some alternatives are that each component provides its own interaction and
>> tries to utilize a library of interaction widgets so there is common look
>> and feel. Or that you don't actually host a component at all, you host
>> "something else" that proxies the component. Flash Pro hosts
>> "live-preview"
>> swfs, for example. There are trade-offs to all approaches. FB uses your
>> proposal, but there are tons of edge cases and these things called
>> design-view extensions used to make it actually work.
>>
>
>
> I can see where design-view extensions would come into play. Do you have
> any details on how they were implemented? Is there a design-view
> specialization of every component: For example: Panel is extended by
> DesignViewPanel?
>
I don't have a lot of details on the extensions. They were written and
maintained by the FB team. They fact they needed them always bothered me
because it meant there wasn't a true public API to work against for new
components.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
