I was wondering if you would like some help finishing off the class documentation for Paladin, and help compile together the tips etc. into one central help file or HTML system.
I'm a software developer by trade (have been for 7 years now) from England. Feel free to contact me on my email address on these forums.
Thank you for your offer. I feel so guilty for not working on it for such a long time due to work commitments. Anyway, there won't be anymore enhancements for build 0.9.0.
If I have the time to work on another version, it will be on .NET 2.0.
It's a shame to stop the product at 0.9 as it is easily the best entity system out there in my view - the best documented and easy to use, and of course free.
Most of the class documentation is complete, however there are a few classes missing which I'll list shortly. Most significantly is the Populate method in the BusinessComponent.
Honestly, I do feel bad for not being able to continue the project. Work commitments just took my life away
Thank you for the good comments. I'm glad that you like my work.
Looks like most of the documentation is stubs except the summary tags, so I think I'll abandon my offer for now :P
The populate documentation would be extremely handy though. Are there any plans to open source the project via gotdotnet.com ? Or just keep it freeware? I can understand the reluctance in open sourcing a project, as you end up having to manage what goes into the code and doing the tech manager job
chenc wrote: Looks like most of the documentation is stubs except the summary tags, so I think I'll abandon my offer for now :P
Hahaha... I see you noticed what you were asking for Anyway, most of the scenarios are already highlighted in the SampleKit. There isn't a need for MSDN style documentation.
chenc wrote: The populate documentation would be extremely handy though. Are there any plans to open source the project via gotdotnet.com ? Or just keep it freeware? I can understand the reluctance in open sourcing a project, as you end up having to manage what goes into the code and doing the tech manager job
There was a time that I thought about it but I guessed I will just keep it as it is for now - a free dll.