Do you mean in those tools? You would have to edit the Flash Catalyst workspace files. The last half of this post<http://www.judahfrangipane.com/blog/2010/09/03/flash-catalyst-jailbreak-for-flex-developers/>describes that workflow although it's not ideal. Or do you mean in a design tool like the one I'm working on? I haven't got to that point yet but there are a couple of approaches I would take.
The first is to go into a skin editing mode when you double click on a component. It's similar to how FC works. Any states or skin parts would show up in a panel. You could then add new states or skin parts. If you added either you would have a choice to modify the existing component (if possible) or create or extend to a new component. There are open source libraries out there that allow you create new AS3 classes at run time. I'm not sure if they support metadata yet but I can't see why that information can't be added. Part of plan is to let the developer use their IDE of choice to create the components and application logic. They would then load the SWF control library at runtime and then wire up the components and events, if that makes sense. They could continue to upload new SWF's and the updated components and application would just be reloaded. So you would create and modify the skinnable component with FB for example, and when that compiled you'd hit refresh on radiate and that component would be pulled in and show the new skin parts and skin states. BTW the application logic would or could be wrapped up in neat packages to be applied to any component anywhere. On Tue, Feb 12, 2013 at 8:12 AM, Sebastian Mohr <flex.masul...@gmail.com>wrote: > @Jude ... thanks for sharing this, > > Any ideas how to implement the roundtrip of custom SkinnableComponents > with declared [SkinPart] and [SkinState] tags as shown in screenshots > of FlashCatalyst and FlashBuilder [1] and the small LoginExample.fxp > project [2]? > > [1] > https://cwiki.apache.org/confluence/display/FLEX/Designer+&+Developer+Tools > [2] > > https://cwiki.apache.org/confluence/download/attachments/30749573/LoginExample.fxp?version=1&modificationDate=1360161322000 > > > -- > Sebastian (PPMC) > Interaction Designer > > Looking for a Login Example with Apache Flex? Please check out this code: > http://code.google.com/p/masuland/wiki/LoginExample > > > On Tue, Feb 12, 2013 at 10:03 AM, jude <flexcapaci...@gmail.com> wrote: > > > I've kindof been sitting on this for a while but I thought I'd put it out > > there. I'd like to create a design and development tool for designers and > > developers. Usually, you have a really good development tool with > adequate > > design tools or a really good design tool with adequate or no > development. > > If Flash Catalyst and FB had continued I'm sure it would have arrived > close > > to the tool I'd like to build and use. I'd say close because I would add > in > > some things like behaviors and other things that may not fit into a > design > > or development only product but would make sense in a combined tool and > in > > the context of the workflow of daily design and development work. > > > > This is a little demo I think I shared at one point, > > http://www.radii8.com/demo/. I've been working on this for a while and > it > > grew mainly out of the need to see what a change looked like without > > recompiling (and for other reasons obviously). It's just a prototype (and > > it's breakable). Click New Project. Drag components from the components > > panel on to the stage. Set properties. Notice the document tree structure > > as it's being built in the document panel. Scroll down and you'll see a > > properties panel, constraint panel, a history panel with undo and redo > and > > a few others. It's no where near where I want it to be. > > > > What's not shown but partially working is a timeline view (to view and > play > > effects), get color under mouse, console, walk up the component tree > > outline view and style inheritance information view. You can use some of > > these features in this drop in class now, > > > > > https://github.com/monkeypunch3/flexcapacitor/blob/master/MainLibrary/src/com/flexcapacitor/utils/MiniInspector.as > > . > > I use this class everyday. Add it to your application, set the options > and > > at runtime command click on a visual element. More of my hopes are here, > > http://www.radii8.com/blog/?page_id=2. > > > > If I could summarize what Polygeek said when asked how he designed > things, > > "First I think of how I'd like it in a perfect world and then work > towards > > that". That. > > *I think that's right. Correct me if I'm wrong. > > > > On Wed, Feb 6, 2013 at 1:26 PM, Sebastian Mohr <flex.masul...@gmail.com > > >wrote: > > > > > Thanks Paul ... made a remark on this. > > > > > > -- > > > Sebastian (PPMC) > > > Interaction Designer > > > > > > Looking for a Login Example with Apache Flex? Please check out this > code: > > > http://code.google.com/p/masuland/wiki/LoginExample > > > > > > > > > > > > On Wed, Feb 6, 2013 at 8:00 PM, Paul Hastings <paul.hasti...@gmail.com > > > >wrote: > > > > > > > On 2/6/2013 7:47 PM, Sebastian Mohr wrote: > > > > > > > >> Sorry ... forgot to add the link to the "Designer & > > > >> Developer Tools" wiki page [1] ;) Any remarks > > > >> welcome :) > > > >> > > > > > > > > FB4.6 can't use MXML design view w/apache flex 4.9. > > > > > > > > > > > > > > > > > >
