What's Babuine Component Model?

Babuine Component Model is a Component Software Framework.

WTF?

Oh, ah; well, from the begining. Please if you are interested keep on reading.

And a component is?

Following the Szyperski wisdom's a component could be defined as:

The characteristic properties of a component are that it:

There are a lot of component definitions, I believe that Meyer's one and Szyperski's one are the most complete.

And you provide ...?

We provide a framework, a different framework in order to write components. We provide a component container, to use with your final applications. We provide the connection rules. We provide best practices for writting nice components. For example, the framework forces you to use a MVC architecture into all components.

Personally, I think that this isn't a pattern, is a rule. And it's necessary to separate the logic, and the view.

The framework allows you design with another design patterns.

Beeej, all frameworks are intrusive into my code.

Could be, but this framework has been designed for usability. You don't have to adapt the code to the framework, the framework adapts to your code, and will make you think with components.

The framework allows you to create a rapid components. You don't have to think about how to solve this method in this platform, you only add value to your components. More things forces you to make waste.

Blah, the reuse doesn't exist.

Sometimes when you are coding, you are always repeating the same code. Could you tell me how many times you have written the list search algorithm?

Reusable code is quite hard to achieve, but using this framework you make sure that you have or will have a lot of components written and tested, and ready to use. You can delegate some hard taks into a component, and the component will make it for you. You achieve develop faster and nicer.

Agiles

Yeah, I love agile programming. I'm working on a system that keep your code bug free. You only have to concentrate in write useful code. A lot of testing is the solution, for now ...

You can use any methodology to develop components.

DBC

Yes, It's basic for me and for this philosphy. When you deploy a component you don't take care of who will use it. I belive this is the way.

But, really exists this?

Yes, isn't a joke.

You can try it at project's page: Project Page and I'm currently working on it and other stuff. There is a wiki too. Right now it doesn't have any content, but I'll update it soon.

And is it free software?

Yes, it's Open Sourced License. Currently it's released under LGPL license. The knowlegde belongs to the humanity.

You can use it, rewrite it, and I'll be happy to receive any feedback. If you are interested in components, software construction, software engineering don't hesitate to contact me: nestor@babuine.net

I'm looking for developers, ideas, features, artists, documenters...

Valid XHTML 1.1