This framework exists beacause, as an experienced developer, I’m never truly satisfied with the frameworks available. This doesn’t mean that frameworks like Symfony are not good enough to develop most of the projects. ***. But I rather work based on a framework that I can easily extend than loosing time investigating the documentation (most of times incomplete) of third party frameworks.

Oh, the name, right… The name might sound a little random, but there are a few reasons why I choose it; it was not taken yet, it’s something very portuguese and it’s funny to compose class names like OliveTable, OliveField or OliveTree.

Seriously Olive is a short name and unusual one so class names, not only sound good, they stand out and avoid conflicts.

No way. Absolutely not. Re-branding and re-designing can be fun, abd factoring is just too cheap these days. Go ahead and take it, Olive takes that as a compliment.

Olive is a library that facilitates developing applications according to a certain approach.

Olive is not an application. Olive is absolutely not a CMS. But it may serve to develop one. Actually, I’m serioulsy thinking about it.

That’s an easy one. Nothing.

Olive is “just” a library. Each application makes use of the classes and functions in it’s own way. I’ve been designing my apps according to a certain optimized model, trying to fully apply the power of the framework, but there are, obviously, other possible approaches.

Every (almost) thing in the library is OOP strucutred, i.e, everything is in classes. There are a few source files with seperate functions: some are legacy code from my old librarys, some are adpated from several sources on the Internet and not yet fully integrated.

Maybe you should read the About page too.