This project looks really interesting and I'm surprised that I'm the first to write a post. Is there some secret communication channel? :)
What do you suggest for getting started with agg sharp? I started with the anti grain documentation but I can't find the right c# classes for it. For example the basic getting started example contains a rendering_buffer. A little push in the right direction would be really appreciated. I'm sure I can use it, but I'm not quite sure how..
Thanks,
Jacob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1. Get the code from the download page (or SVN)
2. Open the DemoSelector project (examples\win32_api\DemoSelector)
3. Run some of the samples and see how they work. The best manual is always the code. I would love to put together better documentation at some point but I don't have time at the moment.
There has been a lot of modification to the original AGG code to make it more c# like and to make it more literate code. All the basic code to do what AGG does is in the AGG.dll.
Lars.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm looking for something even simpler.
The problem with the samples are that they are clocked up with a lot of UI stuff. I'm missing something just showing how to use the renderers, for example how do I draw a line or polygon with a specific color and width. Please no use of the AGG.UI namespace. No samples shows how to do this. They all start out with a drawing with references to the UI controls and outputting the result to them.
I consider myself an expert on .NET but without the doc, no code summaries or a completely simple sample to wrap your head around first, the learning curve is exceptionally steep. I DO NOT agree that the best doc is the best documentation (especially when the code doesn't come code summaries that explain the method and parameters).
We already have plenty of UI controls available, but the System.Drawing namespace needs a better alternative and AGG might be it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK I finally figured it out, but this is sooo far from following .NET guidelines as you could possibly imagine, and the samples are not covering the code enough to actually document it in any usuful way. IMHO porting something also means changing the naming guidelines to follow the standards for the platform you are porting to and to some extent take advantage of existing functionality already there.
Furthermore I can't really see how I can create an image file from a byte array without using System.Drawing.Bitmap.
Sorry to bitch - I know this has taken great effort - but following the naming guidelines and supply code summaries are musts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks your work, and I think you are very nice and you are very busy ,really I need it very much, and want to do something with .net ,but maybe I need a draft description paper about how to deal with these dlls or cs files,if you have some draft help paper or document about how to get starting! please let me know thanks very much!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would love to have more documentation but I don't have time (or need) to write it. The latest .95 has many more samples and better API. Hopefully it is easier to understand.
Lars.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking about cleaning up the source and interfaces. I also have a few performance fixes with big impact. A new repository is probably the best solution.. Are you interested on joining? I'm thinking about a repo solely for antigrain.
Jacob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The code overt here is much improved from this. It should also be much easier to make a branch and then merge new stuff in.
I would love any help you want to give or suggestions you have. We have been developing the code much more in the last year and I hope to put up at least auto generated docs very soon.
Lars.
Thanks, Lars.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
This project looks really interesting and I'm surprised that I'm the first to write a post. Is there some secret communication channel? :)
What do you suggest for getting started with agg sharp? I started with the anti grain documentation but I can't find the right c# classes for it. For example the basic getting started example contains a rendering_buffer. A little push in the right direction would be really appreciated. I'm sure I can use it, but I'm not quite sure how..
Thanks,
Jacob
The thing your going to want to do is:
1. Get the code from the download page (or SVN)
2. Open the DemoSelector project (examples\win32_api\DemoSelector)
3. Run some of the samples and see how they work. The best manual is always the code. I would love to put together better documentation at some point but I don't have time at the moment.
There has been a lot of modification to the original AGG code to make it more c# like and to make it more literate code. All the basic code to do what AGG does is in the AGG.dll.
Lars.
I'm looking for something even simpler.
The problem with the samples are that they are clocked up with a lot of UI stuff. I'm missing something just showing how to use the renderers, for example how do I draw a line or polygon with a specific color and width. Please no use of the AGG.UI namespace. No samples shows how to do this. They all start out with a drawing with references to the UI controls and outputting the result to them.
I consider myself an expert on .NET but without the doc, no code summaries or a completely simple sample to wrap your head around first, the learning curve is exceptionally steep. I DO NOT agree that the best doc is the best documentation (especially when the code doesn't come code summaries that explain the method and parameters).
We already have plenty of UI controls available, but the System.Drawing namespace needs a better alternative and AGG might be it.
OK I finally figured it out, but this is sooo far from following .NET guidelines as you could possibly imagine, and the samples are not covering the code enough to actually document it in any usuful way. IMHO porting something also means changing the naming guidelines to follow the standards for the platform you are porting to and to some extent take advantage of existing functionality already there.
Furthermore I can't really see how I can create an image file from a byte array without using System.Drawing.Bitmap.
Sorry to bitch - I know this has taken great effort - but following the naming guidelines and supply code summaries are musts.
thanks your work, and I think you are very nice and you are very busy ,really I need it very much, and want to do something with .net ,but maybe I need a draft description paper about how to deal with these dlls or cs files,if you have some draft help paper or document about how to get starting! please let me know thanks very much!
I would love to have more documentation but I don't have time (or need) to write it. The latest .95 has many more samples and better API. Hopefully it is easier to understand.
Lars.
Hi Lars,
I'm thinking about cleaning up the source and interfaces. I also have a few performance fixes with big impact. A new repository is probably the best solution.. Are you interested on joining? I'm thinking about a repo solely for antigrain.
Jacob
Hi Jacob,
We have consolidated all our code onto bitbucket. You can find the code at: https://bitbucket.org/MatterHackers/agg-sharp.
The code overt here is much improved from this. It should also be much easier to make a branch and then merge new stuff in.
I would love any help you want to give or suggestions you have. We have been developing the code much more in the last year and I hope to put up at least auto generated docs very soon.
Lars.
Thanks, Lars.