Standartization and integration

[hat3k]

Re: Standartization and integration

Ok, i see. Thanks. The programs are good by the way, thank you anyway!

[LtData]

Re: Standartization and integration

Basically, there are two ways to design software: modular or monolithic. Both have their advantages and disadvantages. Spoon has decided on a modular design so that he can update the modules, such as the codecs or individual programs, without having to wait longer for a large update for everything.

[Wayne]

Re: Standartization and integration

Or WMP, or Nero :teufel8:

I prefer a modular approach so that you only need to install/run those programs required at the time.

Wayne

[hat3k]

Re: Standartization and integration

As an example, CDEX.

sure...

[neilthecellist]

Re: Standartization and integration

As an example, CDEX.

[ChristinaS]

Re: Standartization and integration

It has been explained that it is modular precisely so that different modules can be installed and maintained separately.

They do interact however in case you have not noticed.

What do you mean by "more suitable" - suitable for what?

[hat3k]

Re: Standartization and integration

i see, but what if make an all-in-one edition? I think its easy, and what about to make it more suitable (like for example cdex?)

[LtData]

Re: Standartization and integration

The products are separate to allow separate development cycles and allow people to only download what they want. That is the whole point of dBpowerAMP's codec system also.

[hat3k]

can you make your products all-in-one?