Thanks for the hard work. Does this mean a reinstall is necessary? We
will need to take this into account when releasing the new home
application that we don't forget update scripts :)
Best regards
Sven
Op 6/05/11 10:59, Philippe Van Eerdenbrugghe schreef:
Great work
Systho
Le 6/05/2011 10:39, Hans De Bisschop a écrit :
Hi all,
This past week I've been working on a few updates and a little
cleanup of the Chamilo 2.0 portal homepage. For the most part these
changes don't break anything, but to bring everything up to the same
standards and to allow for the implementation of new functionaity due
to recent platform-wide changes, a few "tweaks" were necessary.
1. A storage unit containing all possible widgets was added, named
"home_block_registration". It contains a list of blocks
available for the homepage with their respective context (=
namespace of the package). This (in addition to previously made
architectureal changes) makes it possible to have blocks for
every single package on the system and most notably individual
content objects. This should help reduce the number of cyclic
dependencies. For those blocks like "streaming" that allow you
to use multiple types of objects I would propose individual
blocks per object type.
2. The /home_block/ storage unit no longer contains a reference to
a /context /and /component /but instead now refers to a
registration_id. The get_context method is still available and
retrieves (and caches) the registration object when needed.
/get_component/ was replaced by /get_block/ and marked as
deprecated. It will continue to work as expected for now
though. People using a PHP IDE will more then likely be
notified about the deprecation status whenever they try to call
the method.
3. Taking (2) into account, a few storage changes were required in
the /home_block/ storage unit/. context /and /block /were
removed and replaced by /registration_id/. This implies a
reinstall or manual update of this table is required. At the
same time /home_block_registration/ needs to be created and
populated.
4. ddddd
Following the move from application to context-based blocks it seemed
somewhat natural to apply the same to settings, which were also still
(more or less) limited to applications. The implications:
1. In the /admin_setting/ storage unit, /application /was replaced
by /context/. Existing content remains unchanged.
2. /get_application/ and /set_application/ have been marked
deprecated and were replaced by get_context and set_context. As
with the changes in the home_block, an intelligent PHP IDE
should alert you when you encounter calls to these deprecated
methods. Please replace them with the new methods when you
encounter such calls.
3. Practically speaking all packages can now have settings. A
visual interface to allow configuration of more then just the
application settings still needs to be implemented.
Best regards,
Hans
--
*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
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
--
Met vriendelijke groeten
Sven Vanpoucke
Digitaal Leren
Directie Onderwijs
Hogeschool Gent
http://digitaal-leren.hogent.be/
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
