Make Modules Great Again - 2: Embedded Library Management

[Karoly Horvath]

Modules are a great productivity tool to manage repetitive complex elements in Archicad, however the current Hotlink Module technology is extremely outdated and thus Archicad is lagging behind all other BIM authoring tools.

One of the key problems is Library management.

Especially the Embedded library.

Module files today include the Embedded library, which leads to duplicate libraries and slowed down project file performance.

Currently the best method for working with modules is the so called Iceberg Method.

 In this method modules are created in negative storyes of the host file and .mod files are placed back into the host to assemble the building.

If the host file contains any elements in the embedded libraries, those elements will be carried into the .mod files and when placed into the host file, the Embedded library elements are repeted as many times as many modules you have. This creates a messy double-up of library elements in the project file.

I understand that .mod files carry the embedded library with them so that if you place the .mod into a separate host model, the libraries will be available, however creating modules in one file then placing them into another one is a dangerous and very-very-very clunky workflow.

Why?

- Attributes between the host and the source file are very hard to match

- It is almost impossible to see context in the Source file while creating / editing modules

- You have to open multiple Archicad projects at the same time, which is hard on your computer and is very time consuming (especially with large projects)

Solution:

- Make it optional to carry embedded libraryes in the module file

This could easily be done in the module file publisher settings when setting up the file format.

Solving this would be one of the first key steps to achieve in place module management.

Also refer to:

Modules: required improvements 

Make Modules Great Again - 1: In Place Module Management 

Make Modules Great Again - 3: Attribute Management 

Make Modules Great Again - 4.0: Schedule Modules 

Make Modules Great Again - 4.1: Schedule Mirrored Modules 

Make Modules Great Again - 5: Modules Source Storey 

Make Modules Great Again - 6: Labels in Mirrored Modules 

[ivad]

None of this would be necessary if there was a way to keep mods entirely internal to your model (like a symbol in Vectorworks, a component in Sketchup, or a family in Revit), instead of creating a separate file that has to be linked back into it. Mod creation and maintenance would be so much simpler and straightforward if they functioned more like their counterparts in these other software: editing in place, single/same set of libraries and attributes, no way to accidentally break a file path, no need to choose between archiving multiple files or changing the file structure for the purpose of archiving.

[Karoly Horvath]

@ivad 

Mate, it looks like you did not quite read the original post.

Request 1 is: in place modules, which means exactly what you are talking about.

The rest of the wishes are there to make in place modules work properly,  or to keep the option of separate module files, which still would be a relevant workflow, work properly. 

Otherwise what you say is ok.