Let me say it simple, nowhere not anymore in the next few years. I have the feeling I heard from your words that you are seeking a point in time when all things are on the way and available consistent from the software shipped to documentation. System documentation generated every night works in maintenance scenarios but honestly if someone brings me the best helpfile and the most accurate one, I tell you it's false. I am still seeking for a way to comment the helpfile the same way I comment in a book. A helpfile must be in sync with the code. This is the goal finally this is the challenge for EMB.IDE and Wiki must be enough. I am satisfied then when I don't need the help because it's available in the IDE, best via comments. Firemonkey will differ too from the documentations perspective, the more and accurate the better of course. Way documentation is used today as a result from the impact JavaDOC had > 10 years ago. From this perspective the Firemonkey is part of the paradigm shift and the Some additional help retrieved from the comments should be enough. The properties and behavior as well as the class hierarchy will have to tell you how the class should be used and of course you must be in the position to read from this. Solid knowledge of software architecture principles maybe design pattern or whatever is a must. The paradigm shift is less in the fire monkey. and then they come out with a paradigm shift like
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |