Skip to content

Feat/use template classic#118

Merged
JJ merged 5 commits intodevelopfrom
feat/use-template-classic
Jul 23, 2020
Merged

Feat/use template classic#118
JJ merged 5 commits intodevelopfrom
feat/use-template-classic

Conversation

@antoniogamiz
Copy link
Collaborator

No description provided.

We generate around 1700 html files, with basically the same menu and
submenu for every page (except for the selected entry). With this
change, we reduce the processing time of Template::Mustache.
Now the default template has two different template specifications,
but hey, it's faster.
If you use 'visibility', the contents will expand the parent box leaving
a gap. However, 'display' does not render the div block at all.

Refs: #117
Copy link
Contributor

@JJ JJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So now you're using both templagint engines?

@antoniogamiz
Copy link
Collaborator Author

It's the only way to pre-populate...

@antoniogamiz
Copy link
Collaborator Author

antoniogamiz commented Jul 23, 2020

I mean, we can revert the use of Template::Classic, but then we add an overhead of 300-400 seconds approx.

@JJ JJ merged commit 5d03877 into develop Jul 23, 2020
@antoniogamiz antoniogamiz deleted the feat/use-template-classic branch July 24, 2020 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants