Rule Separators

[franco]

Sure, we can do that. There are enough ideas around as well. I just want everyone to understand that business wise it doesn't make sense to sink more time into the static PHP pages that makes the required transition to MVC/API even harder than it already is. Most of these conversion efforts are self-funded based on direct need.


Cheers,
Franco

[Patrick M. Hausen]

Sure, we can do that. There are enough ideas around as well. I just want everyone to understand that business wise it doesn't make sense to sink more time into the static PHP pages that makes the required transition to MVC/API even harder than it already is.

Absolutely!

Looking forward to finally meeting in person.

[bimbar]

> but still professionally we do fortinet for the better firewall rule UI.

And the incentive to make it happen here is what?

We did discuss in the meeting but the bottom line is it won't help us overcomplicate the situation in static firewall pages that still need an MVC migration. Categories are flexible enough. Building containers from categories would actually put more restrictions on categories in terms of rule location and overlapping use.


Cheers,
Franco

The incentive would be making opnsense better? I don't understand that question.

Still I do understand not wanting to do it in the old firewall UI code - is a migration to MVC planned?

[franco]

> The incentive would be making opnsense better? I don't understand that question.

Better for who? You?

> Still I do understand not wanting to do it in the old firewall UI code - is a migration to MVC planned?

Not fixed in time yet, but working on the firewall end probably 40% carried through by now with most of the easier migrations elsewhere already done in the last decade. The roadmap will likely feature one more firewall page conversion


Cheers,
Franco