poco2013 wrote:Sure it is. But why not using the Classification Manager to store this information? A simple automatic ID system with parent/child key within branches could easy the process. Then a simple favorite label with the element classification, plus a dedicated MVO to show/hide ID/Name/ShortDescription/LongDescription. Finally schedule all assigned classifications an edit the ShortDescription/LongDescription according to the specified product.
Even at that, a typical keynote requires much more information than just element attribute(s), Trying to put long statements into a property would be a nightmare to maintain as standards are constantly changing with regulations.
poco2013 wrote:I might disagree that we are talking Apples and Oranges. All what I'm trying to say - keynote can be more integrated into ArchiCAD using same Python, Json and C++.
The purpose of my post was to solicit suggestions on what should define a good keynote application -- so thank you for your response.
I did consider many of you concerns before hand but found most problematic for the following:
IMNOHO - keynotes are primarily instructions to the builder in a concise form. They are widely diverse from firm to firm and project to project. My primary concern was the ability to maintain the database and to quickly revise, find and apply them according to office standards Your inference that the automatic attachment of a note to a element based on its type can lead to substantial problems and misinterpretations. Labels are perfect for display of element attributes but a better solution is to just use the schedules. Other than a few properties attached by Graphisoft, you can not attach custom properties to a label since labels can not be classified, Even at that, a typical keynote requires much more information than just element attribute(s), Trying to put long statements into a property would be a nightmare to maintain as standards are constantly changing with regulations.
That's why I chose a Json file to organize and segregate the notes in a manner which would be easily understood and under the control of a BIM manager. Every firm could easily define their own display format (style). My intent was to be able to quickly organize, find the appropriate note and apply it with the style of the current office standards. Also a Json file allows the BIM manager to apply Regex expressions to select the applicable note. I did not demo this but it is easily applied.
It is possible within the API to pick up the element parameters and apply them to a note. But that is beyond my Demo at this time. My intent was to show the ease of using a json file, Python and the AddOn Command Handler to handle the placement details.
I agree that it is unfortunate that Python files for this application must be run outside of Archicad, but perhaps that might be solved in the future. In the mean time, the bat file works just fine
IOW, I think we are talking Apples and Oranges..