Skip to content
This repository was archived by the owner on Oct 8, 2021. It is now read-only.
This repository was archived by the owner on Oct 8, 2021. It is now read-only.

Page life cycle with pagecontainer: Reasons to keep 'pageshow' event #7283

Closed
@wauwau0977

Description

@wauwau0977

This is not a bug request, i would like to raise an design / architectureal issue. Starting in JQM 1.4 onwards, page life cycle events (e.g. pageshow) are deprecated in favour of 'pagecontainershow'. Please consider the case below, where i think it's not a nice replacement.

We use JQM in a rather big project with several developers, where we try to split up the app in functional "modules". For this we also use separated files to give the app a certain structure. It was very convenient to have a way to implement the page specific handlers on the page itself for actions like templating and custom JavaScript preparations, etc...

Now, with the container i still can do that, but i must control the logic centrally and then dispatch again to the page module... Architectural wise, that's a strange approach...

I would love to see again a way to bind "life cycle" logic to a page again. Since programmers will work on pages as their logical work unit and they want to control the life cycle on that logical work unit...

Cheers,
Patrick

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions