Maybe you remember me some days ago talking about research and object recognition. I finished it and had to present the theoretical background and practical working example. What can I say? I worked the night before my examination until seven o’clock in the morning to get it working. Without a written speech, sleep or something else helpful I talked about my program. The result was 14 of 15 possible points which is quiet good.
Now about the Imageprocessing part. I wrote a program that gets structural information from an obstacle you hold into the camera. The title is “Objectrecognition of presented obstacles” and this is done using a motion-detection for the movement. A scene background-substraction is done to get only the moved obstacle. Then there is a median-colour lookup after a lof of filters have been applied. Closing, Retinex and Blobcounter to mention only some of them.
The last final part which I like most is the artificial neuronal network that recognizes the shape of the obstacle. I used a simple feed forward net and the results were also quiet good.
You can read the full article here. I am sorry but it is not written in English so you can only read if you understand German.
Maybe you remember me some days ago talking about research and object recognition. I finished it and had to present the theoretical background and practical working example. What can I say? I worked the night before my examination until seven o'clock in the morning to get it working. Without a written speech, sleep or something else helpful I talked about my program. The result was 14 of 15 possible points which is quiet good.
Now about the Imageprocessing part. I wrote a program that gets structural information from an obstacle you hold into the camera. The title is "Objectrecognition of presented obstacles" and this is done using a motion-detection for the movement. A scene background-substraction is done to get only the moved obstacle. Then there is a median-colour lookup after a lof of filters have been applied. Closing, Retinex and Blobcounter to mention only some of them.
The last final part which I like most is the artificial neuronal network that recognizes the shape of the obstacle. I used a simp
Here is a preview of current html output. As you can see the classes show in the classes-list the name of their base-class which is wrong. The general output idea is based on LiveDocs and I hope you will not miss any feature.
From code to Html.
- Start creation of Xml using “as3toxml input classpath output title”
- Walk through every file and directory.
- Analyze the code and safe the structure in outpu Xml
- Start creation of Html using “xmltohtml skin input output”
- Load input Xml (which is output of as3toxml) and parse it
- Create for every output file a special Xml which will be transformed into Html using Xslt
The last step is an interesting one if you want to create your own output. You are able to edit some Xslt files or write your own. You may also use Xslt with the original Xml to create a dynamic output. In my eyes it is easier for me to create the packages-list from something like
[html]
Sorry, code is gone because WordPress was eating it …
[/html]So there is an internal pre-processing of the original Xml. My knowledge about Xslt and especially XPath is just not enough for some better methods. But this way is now also much faster. I hope you like it and give me some days to finish this tool.
Here is a preview of current html output. As you can see the classes show in the classes-list the name of their base-class which is wrong. The general output idea is based on LiveDocs and I hope you will not miss any feature.
From code to Html.
Start creation of Xml using "as3toxml input classpath output title"
Walk through every file and directory.
Analyze the code and safe the structure in outpu Xml
Start creation of Html using "xmltohtml skin input output"
Load input Xml (which is output of as3toxml) and parse it
Create for every output file a special Xml which will be transformed into Html using Xslt
The last step is an interesting one if you want to create your own output. You are able to edit some Xslt files or write your own. You may also use Xslt with the original Xml to create a dynamic output. In my eyes it is easier for me to create the packages-list from something like
[html]
Sorry, code is gone because Wordpress was eating it ...
[/html]So there is an internal pre-process
There was one great tool to create a documentation for AS2. It was called BLDoc from Bline-Express. The only problem with this tool is that it does not work with Actionscript3. So I started working on a AS3 documentation tool called AS3toXML because it is only analyzing the code and creates a Xml without any nice visual output. That will be the next tool I will create. XMLtoHTML or something like that. Now back to the first application which is nearly finished.
I need your whishes and suggestions!
Yeah, thats true! I want you to help me to have a powerful tool to create Actionscript3 documentations. So here we go. I will post feature lists and Xml output. I wish you to use the comment function to tell me about possible mistakes since I do not know very much about Xml. I want you to tell me how things can be done better and feature requests.
Updated:
- Tags like @deceprated. I should have got all common tags now. If you know a tag you would like go ahead and leave a comment
- Support for the new namespace feature that AS3 offers (access of class members can be public/private/internal/protected or defined by namespace)
- Design changes. @see, @link, @throws and @req (requires) are now using same layout as multi-tags that can be used several times
- Fixed code-analyzer to work with very screwed code and multiline declarations/values
Pending:
- XSLT to format the output since the XMLtoHTML application is also finished now
- Support for meta-tags (still need a list of all that tags)
Continue reading ‘AS3 Documentation Tool AS3toXML’
There was one great tool to create a documentation for AS2. It was called BLDoc from Bline-Express. The only problem with this tool is that it does not work with Actionscript3. So I started working on a AS3 documentation tool called AS3toXML because it is only analyzing the code and creates a Xml without any nice visual output. That will be the next tool I will create. XMLtoHTML or something like that. Now back to the first application which is nearly finished.
I need your whishes and suggestions!
Yeah, thats true! I want you to help me to have a powerful tool to create Actionscript3 documentations. So here we go. I will post feature lists and Xml output. I wish you to use the comment function to tell me about possible mistakes since I do not know very much about Xml. I want you to tell me how things can be done better and feature requests.
Updated:
Tags like @deceprated. I should have got all common tags now. If you know a tag you would like go ahead and leave a comment
Support for the new namespa
Published on
Jun 14, 2006 in
misc.
Tags: c++.
