Right now, I'm weighing the idea of being a Graphisoft Developer, but there are few issues that aren't clear for me which are:
Thank you in advance
Solved! Go to Solution.
Regarding licences for client - you can connect your GDL objects to client Archicad licence. Check my libraries shared in this forum - I've done such a protection there. On C++ you also can request Archicad licence number and connect to it, or, because C++ gives you endless possibilities - you also can create there your own licence system.
One more note: I was thinking about start making C++ Add-Ons too. But finally came to different idea - instead of C++ I have decided to develop GDL on very detailed level. Don't forget - maybe half of Archicad functionality is based on GDL - even if you start making your own C++ Add-On - most likely you would face to the fact, that you need GDL too in this Add-On. Currently I'm developing Automaton as Open-Source project on GDL - as I want to introduce more simplified, alternative to standard Add-Ons workflow of making your own apps for Archicad.
The answer to your question is simple - if you want to develop something – just do it. There is nothing stoping people to develop apart of themselves. Programming languages are very flexible and give unlimited possibilities of doing anything - one of another way. Finally the most important is to have an idea - what kind of tool you want to produce and what initial structure and algorithms of this tool must be. In programming exist pseudo-codes and logical graphical schemes - that later can be translated to any system or language. Without having this logical scheme - drawn or even in person imagination there is no point to start coding something. Otherwise it's like start construction without having architectural and structural project. Unfortunately this is very common mistake of all beginners.
Good to hear from you! Let me try to answer most of your questions:
1. Developer Archicad License: this gives you an easy access path to a full Archicad, at a lower (well, actually quite cheap) price. We aim to support those developers who otherwise don't have access to Archicad, and would like to learn and experiment.
As a practitioner, this is a full license, with no limitations, except that it is not an SSA license, so you won't be able to use features which are available only to SSA customers.
2. It depends on you. You can ask for a hardware key, and plug it into any of your computers, or for a soft license, which you have to transfer with License Manager between the machines (but there's a limit on that if I remember well). Or, alternatively, you can buy two licenses 😉
3. The created add-ons/GDL objects will work in any version, unless you yourself tie them to your actual license.
4. This is a hot topic 🙂 The short answer depends on how sophisticated you want to be with your protection, because the "client license" can take many forms, from a single hardware dongle to a mix of single and net licenses. Some of these can be covered, but some of them are quite hard. At the moment we don't have a full scale solution you can easily build in, so as an alternative you can try to find a different protection scheme.
5. Learning C++:
- if you'd like to learn the basics of C++, then I'd refer you to courses that can be found on the internet (e.g., Udemy, Coursera, or LinkedIn Learning)
- if you'd like to learn the C++ API for Archicad, please look into the examples in the development kit, and we also have a Maze Generator sample in the blog section of the developer site.
6. I don't know much about that, but I think there's a landing page on graphisoft.com where you can start, and I think we also have a course on that as part of Graphisoft Learn.
7. Windows/Mac Intel/Mac ARM platforms
- GDL is fully cross platform, so any object you create on Windows should work on any other platform. Also, any GDL object created in previous versions of Archicad should work with the latest version of Archicad.
- the C++ API is source compatible as long as you use the frameworks from the development kit, and standard C/C++ (like STL). This means that you can transfer the source between the platforms, but you'll have to compile and link your code for each platform separately (well, we haven't fully decided on the Mac Intel/ARM version, maybe one binary will be enough). This means that you'll have a separate MyFancyAddOn.apx for Windows, and a MyFancyAddOn.bundle for macOS.
Also, you'll have to recompile and re-link the C++ add-ons for each major version of Archicad, even though the source may be the same. We provide API development kits shortly before the release of the major Archicad version to developers, so that they could prepare their add-ons.
1. I looked at the License agreement, and it seems there's no restriction on that, so you can use that for modeling purposes as well, you just cannot transfer that license to anyone else (e.g., if you have a coworker who is doing the modeling, s/he'll have to buy a full license).
Also, if you cease to develop for Archicad, then please buy a full license.
And of course, if you make enough money out of development, please also buy a full license 😉
3. Yes, you just have to ask tech support for that previous version, they'll be able to provide the application. But then you'll have to start to develop the GDL object in that earlier version, to be safe on the compatibility side.
4. Well, it's better to ask the fellow developers...
My basic idea would be to tie the protection to the serial number of the AC license in some way, e.g., generate a serial number from it and verify its validity.ű
5-6-7. You are welcome 🙂
6++ -- we'll keep that in mind.