Hello,
Before deciding which solution to adopt, it seems to me that the advantages of a programming tool in Allplan are:
- to be able to customise elements
- to be able to perform repetitive tasks
- to be able to create new specific items
- to be able to reduce work time
- to be able to use external plugins or content
Users expect all Allplan's capabilities to be involved. Everything must be controllable: all the objects (walls, slabs, openings, rooms, etc.), all the drawing and modification functions, all the management of attributes and formats (colors, hatchings, patterns, layers, etc.), all the animation management (environment, position, lights, etc.), all the rendering functions, all the specific functions (reinforcement, terrain, etc.) and all the exchanges (imports, exports and printing). In fact, total control of Allplan!
Allplan's effort must therefore be to make all the functionalities available. And this effort is very important. It is the basis for "passionate" or "experienced" users to be able to make full use of Allplan's performance in their fields. It also allows partners to develop complementary tools without being limited or constrained. Overall satisfaction can only be improved. It therefore seems that using something like Grasshopper would enable us to achieve this goal, where visual scripts and additional functions in Python, C# or VB can be used and mixed. It could replace all Allplan's attempts (NOI, SmartPart, PythonPart, Visual Scripting). With one complete environment, everyone would win: concentrated effort for Allplan, simplified learning for users, extended possibilities for users and partners.
Allplan would then be a real platform that covers all areas of construction.
