Thanks for working on this. I have some "process" tasks for you.
1) I just skimmed the commit email and noticed that the files need Apache headers. 2) I think you mentioned that some of this code was originally written by someone else? I think we need an email from him in the mailing list archives so we have an official "paper trail". You could forward one from him or he can write a new one. We also need to determine what kinds of licenses and copyright attributions are required for his work, if any. On 4/16/13 7:33 AM, "Harbs" <harbs.li...@gmail.com> wrote: > I just pushed an initial skeleton framework of the panel with some placeholder > components there to give an idea what the different components look like. Some > of the methods I used for styling is a bit hacky, but it worksŠ > > All the code needed for styling in both a light and dark UI is there. There's > also a NativeComboBox which I like to use instead of the normal ComboBox. You > can see the difference in behavior if you run the extension. > > None of the UI layout or functionality implementation is done yet. When I find > some time, I'll start with laying something out, unless someone else gets to > it first. > > In terms of a UI, I'm thinking of populating a TextArea with the FXG XML that > can be copied and pasted elsewhere or a direct export to file. > > Harbs > > On Apr 15, 2013, at 10:35 AM, Harbs wrote: > >> I'd like to start that project to export FXG from creative suite apps. >> >> Some questions: >> 1) Should I start this on a personal github account, or have we settled on >> something else? >> 2) CS Extensions have dependencies on a number of Adobe swcs. How do we >> handle the project vis a vis Apache's policies and binaries? I don't think >> those dependencies can be includedŠ >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
