Okay, it looks like there are a couple things going on here that I'll have to deal with. First of all, I made some optimizations recently that seems to be preventing the "export documentation" option from disabling properly.

Also, I haven't actually designed the plugin for projects that are not published using the Flex SDK, so I'll have to rethink a couple things. Probably, the release configuration and documentation settings should be disabled in this case. In order to automatically generate documentation without problems, it actually needs to publish the project using the Flex SDK to analyze which classes were used upon compilation. That way when I call ASDoc, I can pass every class you used so that no dependencies are missing.

I'll think about adding an option to not publish files that are hidden under the Project panel. I can see how this would be a useful feature.

Hi Elyon,
I would like to know if you can change the templates for the ASDOC generation. I would like to re-style the html output, use my own logo etc... But I would like to do it in the template files.

Where can I change them?

Thanks,

It would be nice if this could generate a 'srcview' directory similar to Flex Builder's for use as a 'view source' link in the application's context menu. Just the directory of viewable code and application structure; the link is simple enough to add in one's application when desired. Any chances of this happening? ...your add-on is nice as-is also.

Greg

Hi everyone!

I just posted a new version of ExportProject, which includes some major changes. If you are upgrading from a previous version, you will need to make sure to double-check your settings.

I realized that my need for exporting a project usually comes from two common use cases: exporting the build directory and exporting the full project. I've divided the original export command into these two features, which each support their own file and folder filters.

I've also moved the commands off the menu bar and into the File and Tools menus. Please let me know how the plugin is working for you and if you have any bugs you see or ideas for improvement.

@mflmartin:

ASDoc supports a "templates-path" argument which lets you define your own path for the XML, XSL and HTML template files. Unfortunately I have not added a way for you to define this argument using ExportProject, but in the meantime you can backup the files located under asdoc\templates in your Flex SDK directory, and edit them to your own satisfaction.

@gsb:

I have seen this feature implemented in Flex projects before, and remember reading conversations along these lines on these forums before I created this plugin. Do you know if this is easy to implement, or if we would need to use our own AS to HTML parser to make this work?

Hi Elyon,
When trying to install the plugin I keep having this error, even if Flash Develop is not running:



(Note that the path is correct, it's an Spanish PC)

I also tried it at work in a french PC, and is not working either. I am on Both machines on Windows XP Sp3.

Any ideas of what is causing this?

Thanks!

By the way... I removed manually the ExportProject.dll from the plugins menu, and when I installed the plugin it just put the old one again... odd.

I managed to install it finally (I had another error with other dll... but it works now...)

The only thing I am not happy with is that you removed the quick icons in the toolbar... I think they were quite useful. How could I add them again manually?

(By the way, I think i never said thank you for the plugin officially, so thank you! good work )


thanks!

I just fixed an issue where the "Export" menu appeared out of place sometimes.

Which toolbar icon were you using the most? I decided that as infrequently as I export my projects, it seemed fair to place the command under the file menu. Was it exporting the project that you wish you had an icon for, or is it creating documentation that now takes too many steps? If I were to place "Create Documentation" under a different menu, do you have a different recommendation for where it would go?

"...Do you know if this is easy to implement, or if we would need to use our own AS to HTML parser to make this work?"

elyon, I do not really know an answer to this.

Like martin, let me say thanks for the updated plugin. I have found it useful as-is.


Greg

I think that adding a "View Source" option is a great idea ... in fact, it was in the back of my mind when I first started building this plugin.

I'll ask some questions on a different post to see if I can find a good solution for this.

Well here at work we use the export option quite often. It is true that it should also be in File> Export project (As this is the natural place where it should always be). But I feel those two icons for the documentation and the exporting were also very handy. And yeah, the documentation takes too many steps in my opinion.

I would suggest a configuration feature to activate/desactivate those icons. (But well, I will just leave the icons as they were before). I don't know if other people miss those two buttons as I do...

Regarding the documentation menu, I think it is ok where it is. I do not see another more suitable place for it. That is a feature that we are using also quite often this days. We are doing a lot of testing and documenting a big framework, so again, the quick acess icon was very handy.

Thank you,

Martín

Okay, your wish is granted. I've just added the tool strip buttons again.

Just make sure that you remove SgmlReaderDll.dll and ExportProject.dll from your AppData (Application Data) directory before installing the new version. Sorry for the inconvenience

Thank you!

gsb,

ExportProject now includes a Source View exporter. If you have a server that supports PHP, you can now create a srcview folder that will let you browse your source files with some highlighting. You should be able to link it up to the context menu using Adobe's view source class or by writing your own quick code to open the page in a new window.

Thanks to senocular, for sharing your file browser!

Great news!

Yes. I have been adding in the zip via the context-menu, no problem. I will have to look up "Adobe's view source class" for I have never used that. I will DL the latest and give it a try later today: some work first though...

Thank you. This should be a very good contribution to the community, allowing better sharing of code and concepts via "viewable" examples - 'see it work and see how it works' all in one link.

greg