2024-06-20 03:56 AM - last edited on 2024-06-24 02:19 PM by Laszlo Nagy
Reading the roadmap about what is coming soon, I hadn’t noticed that Archicad 28 will have a have a full global library to select parts from.
This is a very good idea since I have read many posts where a library part that is available in one region is not in another. This will solve some problems for many users including me who doesn’t use GDL yet.
What do others think about this change ?
Edited extra info:
Content expansion:
Until now, each Archicad language version (INT, USA, GER, JPN, etc.) had its own library collection. With the Global Library, all library content will be available in all Archicad language versions.
Cross-border collaboration:
Regardless of which Archicad language version is used, the template will define the default language and standards (default sizes, attributes, surfaces, pens) of the library parts you are about to place.
Easier plan migration at future version updates
Until now, each Archicad version (…25, 26, 27) had its own library. To use the new Archicad version, users had to migrate the library objects of their existing projects to the new Archicad library.
The Global Library is compatible with all upcoming Archicad versions. Plus, when new library content is released, users can simply add any new Library Package to an existing project without having to go through a migration.”
Faster delivery
The lighter delivery infrastructure allows Graphisoft to deliver library content faster and in greater quantities than before.
2024-06-25 07:43 AM
'Coming soon' means GS are actively working on it.
Sometimes they may arrive in the next update for the current version, and other times not until the next version.
Even then there is no absolute guarantee that it will be the next version, because if something unforeseen happens in testing, it may be held back - that is unlikely to happen though.
It is a pretty safe bet to say 'coming soon' will be in the next version.
Barry.
2024-06-25 08:50 AM
👌
2024-07-01 04:51 PM - edited 2024-07-01 04:51 PM
Global SSA Database - Graphisoft Community
I had that wish some time ago. Maybe that's the first step towards language independent archicad, which is a real pain now if you want to work across different (localisation) borders while using the archicad classification system, which every localisation version has in it's own translated version.
| Archicad 4.55 - 27
| HP Z840 | 2× E5-2643 v4 | 64 GB RAM | Quadro M5000 | Windows 10 Pro x64
| HP Z4 G4 | W-2245 | 64 GB RAM | RTX A4000 | Windows 11
2 weeks ago
hi All,
It seems that Archicad 28 is set to have the new global library as part of its release. It looks promising as it means no more migration of old library versions.
We have several projects that are years in the making. The big question for me is what happens when I library part that we have been using is updated? Does it retain all its properties? Do we need to save a copy of the old library part as a record?
Sam
2 weeks ago
I assume you are not talking about projects that span 26/27 and into 28/29.
There will be no migration of objects from 27 to 28, so just keep using the older libraries.
From 28 on there still will be migration - you just won't notice it because there are no version numbers in the object names (I am still not convinced this is a good idea).
But if it is all done well, any new amended objects (29) will still have all of the same functionality as the older ones (28), just as it has happened in the past.
Should a new object need a complete re-write and is no longer compatible with the older object parameters, my understanding is you will not notice that either.
It will simply keep using the older (obsolete) object (the same as happens until now) but you won't notice because there is no version number as reference.
The new advanced object I assume will have a different name (and be a different object with a new GUID).
I am not sure as we haven't got that far yet, but I am suspecting we will start getting a few 'Dishwasher 01' and 'Dishwasher 02' objects, as I can't imaging you can have an old obsolete object with the same name as a new improved object.
That is why i still like the idea of having the version number in the object name.
Again, my understanding is that from 28 onwards, all old (obsolete) objects will still be contained in the current library, so there will be no need to actually load any migration libraries any more.
Exactly how it will work we will just have to wait and se in a few versions time.
Barry.