RM 5 plugin development
Hi All,
I have developed several plugins for RM 4.6, but now they are not working anymore in 5.0.
I get it, that it had to be rewritten and there is a new API, but it is very hard to get started with plugin development for 5.0 as there is no documentation yet.
I have started to reverse engineer the new extensions, but it is really hard to get the philosophy. Can anyone post some words on how to get started or how to transform 4.6 plugins to 5.0?
When can we expect some documentation? It is kind of urgent.
Thanks, Zoltan
I have developed several plugins for RM 4.6, but now they are not working anymore in 5.0.
I get it, that it had to be rewritten and there is a new API, but it is very hard to get started with plugin development for 5.0 as there is no documentation yet.
I have started to reverse engineer the new extensions, but it is really hard to get the philosophy. Can anyone post some words on how to get started or how to transform 4.6 plugins to 5.0?
When can we expect some documentation? It is kind of urgent.
Thanks, Zoltan
Find more posts tagged with
Sort by:
1 - 14 of
141
Hi all,
I continued working on the white paper yesterday and it is nearly finished. We are currently thinking about the way we want to publish it, either free for all or for a small fee in the shop. But anyway I hope it will be available this week.
It describes shortly how to develop operators, what has changed and how the configuration files are built.
Greetings,
Sebastian
I continued working on the white paper yesterday and it is nearly finished. We are currently thinking about the way we want to publish it, either free for all or for a small fee in the shop. But anyway I hope it will be available this week.
It describes shortly how to develop operators, what has changed and how the configuration files are built.
Greetings,
Sebastian
Hi all,
I made it, finally it took me a full week. The tutorial is available now and has somehow overgrown a tutorial: It more or less became a little book...The first version is available in our shop now (as other open source companies, we can't do everything for free). I'd be happy about any suggestions how to improve it further.
Greetings,
Sebastian
I made it, finally it took me a full week. The tutorial is available now and has somehow overgrown a tutorial: It more or less became a little book...The first version is available in our shop now (as other open source companies, we can't do everything for free). I'd be happy about any suggestions how to improve it further.
Greetings,
Sebastian
Hi,

Hence, the whole sentence should read
"You will be able to always download the most recent version for one year".
After purchasing the document, you will find the most recent version of it in a specific part of our web site after you have logged in until one year after the purchase date. This way it is ensured that the document is independent of the version you started with and you don't have to buy it twice, once for let's say version 5.6 and once for version 6.0 (release two weeks later...). I think this is a quite fair model.
All the best,
Ingo
Sebastian forgot three words here: "...for one year". I thought I quickly jump in before he will be cited with this forever
you will be able to always download the most recent version.

Hence, the whole sentence should read
"You will be able to always download the most recent version for one year".
After purchasing the document, you will find the most recent version of it in a specific part of our web site after you have logged in until one year after the purchase date. This way it is ensured that the document is independent of the version you started with and you don't have to buy it twice, once for let's say version 5.6 and once for version 6.0 (release two weeks later...). I think this is a quite fair model.
All the best,
Ingo
I know we are lacking a documentation and I'm working on it. But unfortunately there are so many urgent things to do right now. I cannot give my word, when it will be available.
Greetings,
Sebastian