This application is not used any more and exists only for history. Post new tickets on the Github account.
Cette application n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Ticket #509 (closed enhancement: fixed)

Opened 6 years ago

Last modified 2 years ago

Ability to change jelix context on the fly

Reported by: laurentj Owned by:
Priority: normal Milestone: Jelix 1.4
Component: jelix Version: 1.0.2
Severity: blocker Keywords:
Cc: Blocked By:
Blocking: Documentation needed: no
Hosting Provider: Php version:

Description

When creating unit tests, or if we want to migrate jelix-scripts to a real jelix application, it should be interesting to have an api which allow us to change the context of Jelix :

  • by loading an other configuration file
  • by changing all values of JELIX_* constants (so we need to replace these constants by static property in a Jelix class for example)
  • by changing values of all $gJ* global variables.
  • old values are saved in a container, somewhere, so we could switch between several application.

We need to study consequence of this changes, in session for example.

Change History

comment:1 Changed 5 years ago by laurentj

  • Milestone set to Jelix 2.0

comment:2 Changed 5 years ago by laurentj

In fact, jelix should be reentrant.

comment:3 Changed 3 years ago by laurentj

All JELIX_APP_* have already replaced by some parameters on a jApp object, in jelix 1.3. The jApp object supports also contexts, but a context is only about paths for the moment (not gJConfig etc..).

We still have to support the swap on $gJ* objects.

comment:4 Changed 3 years ago by laurentj

  • Status changed from new to confirmed

comment:5 Changed 2 years ago by laurentj

  • Status changed from confirmed to closed
  • Resolution set to fixed
  • Milestone changed from Jelix 2.0 to Jelix 1.4

With last improvements into jApp, we can say that it is ok now.

Note: See TracTickets for help on using tickets.