So what about plugins?

Plugins were the great news in the pre 1.0 era, announced May 2008 in Ghent, Belgium, during Owasp APPSEC 2008.
Plugins were discontinued in the post 1.0 era, where the org.owasp.orizon.core.Engine class is the most important part of the new Orizon architecture.

Plugins now need to be introduced back again. We need a way to extend Orizon with custom code, so people can implement new functionalities without having to hack the whole engine.

In example, how can you add a LaTeX formatter to have your reports saved in a TeX file without changing orizon? The answer is simple, you can use a plugin asking the engine to execute your code for you.

Plugins development starts today and it will be a key feature of the upcoming 1.20 version later this year.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s