The only way to avoid that problem is to make homepage blocks package /
context based like most other things on the platform, instead of
application based (the pre-namespace / package way of doing things).
Once that's done, it should be possible to move those blocks to their
respective content object and eliminate the nasty dependencies. If the
block depends on more then one object I would guess we still have a problem.
Hans
On 12/04/2011 15:32, Philippe Van Eerdenbrugghe wrote:
Here I come again with my damn cyclic dependencies ^^
almost all the classes under the path "repository\php\blocks\type\*"
have dependencies to content_objects.
Does someone have an idea to break it ?
For those who don't care : cyclic dependencies are preventing a
modular application, so as long as we haven't break all those links,
we can't download a small core package and cherrypick the additional
packages. Cyclic depdencies also make the upgrade process incredibly hard.
Systho
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
--
*Hans De Bisschop*
Hoofddeskundige ICTO | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
hans.de.bissc...@ehb.be <mailto:hans.de.bissc...@ehb.be> |
www.erasmushogeschool.be <http://www.erasmushogeschool.be/>
Kom eens langs: www.erasmushogeschool.be/infodagen
<http://www.erasmushogeschool.be/infodagen>
of lees onze elektronische nieuwsbrief: ehbrief.ehb.be
<http://ehbrief.ehb.be/>
P Before printing, think about the environment
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
