concept.
Cheers!
Marco
From: dev-general-boun...@lists.oxidforge.org
[dev-general-boun...@lists.oxidforge.org] on behalf of Stefan Moises
[moi...@shoptimax.de]
Sent: Tuesday, January 21, 2014 11:42 AM
To: dev-general@lists.oxidforge.org
Subject: Re: [oxid-dev-general] P
...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Stefan
Moises
Gesendet: Dienstag, 21. Januar 2014 11:42
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors
Hi,
yes, some type of dependency management is a must for
Hi,
yes, some type of dependency management is a must for the OXID module
system!
As a workaround, we have started a simple module managing dependencies
("smx_module_deps"), at the moment you can only add other module ids
which your module depends on, e.g. in metadata.php you can add:
*
Hi Roman,
I can provide you with our own "module connector" though we like to call
it framework. Don't let the name fool you, its basically a lightweight
class that does what OXID can't: Bring streamlined OOP to modules.
In our view the metadata files are really a bad design decision. The
sy
ot;
Datum: Dienstag, 21. Januar 2014 09:50
An: "dev-general@lists.oxidforge.org"
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors
I really don't like the use of an connector but some of my team-member
argument that it's good to put all reusable extensions in o
I really don't like the use of an connector but some of my team-member
argument that it's good to put all reusable extensions in one
connector-module instead of putting them in every module, that we are
developing.
My argument against a connector is the problem with the dependencies
while an up
Dienstag, 21. Januar 2014 09:38
An: "dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>"
mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors
Hi,
same for me: I also don't like them. If yo
Hi,
same for me: I also don't like them. If you have dependencies between
modules go for composer or something the like.
Best would be if OXID could come up with an extension in the
metadata.php in which you could tell "this module is based on that other
module".
Best regards
Joscha
//---
...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Marcel Müller
Gesendet: Dienstag, 21. Januar 2014 08:44
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors
Hey!
I don’t like such additional connector modules. They
Hey!
I don’t like such additional connector modules. They have their own bugs and
generating system-wide errors, mostly. Especially when the module has an own
style and/or database tables far from oxid. I had scenarios within a customer
tried to remove a connectors modul and gets a lot of tro
Hi folks,
me and my team are developing a concept for us, how to develop modules
for oxid. We are now at the point where we have to decide to develope a
connector-module for all our coming modules or not.
We know that some agecies use their own connector to integrate their
modules in oxid. A
11 matches
Mail list logo
