cached_softhyphen and defaulting to language = active translation #6

Closed
wants to merge 3 commits into
from

Conversation

Projects
None yet
2 participants
@lenz

lenz commented Jun 6, 2012

Hi!

At first, thanks for sharing this great app!
I added a template filter "cached_softhyphen".
It makes the template filter more useable or at least a more considerable choice in production for cases where saving to the database is not an option. For example if you don´t want to fork an App.
I also made the language param default to the active language.

Maybe you like it :)

Cheers,

Lenz

@palewire

This comment has been minimized.

Show comment Hide comment
@palewire

palewire Jun 7, 2012

Member

Thanks for this. I'm kind of slammed at the very moment but I'll get to it as soon as I can. It's appreciated!

Member

palewire commented Jun 7, 2012

Thanks for this. I'm kind of slammed at the very moment but I'll get to it as soon as I can. It's appreciated!

@palewire

This comment has been minimized.

Show comment Hide comment
@palewire

palewire Jun 21, 2012

Member

Just out of curiosity, why not cache it in your model in the James Bennett style I sketch a bit here?

Member

palewire commented Jun 21, 2012

Just out of curiosity, why not cache it in your model in the James Bennett style I sketch a bit here?

@lenz

This comment has been minimized.

Show comment Hide comment
@lenz

lenz Jun 22, 2012

Doing it in the model/db is definitely the way to go!
But if you have a 3rd party app with own models that should be hyphenated and you don´t wont to fork the app the cached version is an alternative which can be adopted in the templates without making the page slow.

lenz commented Jun 22, 2012

Doing it in the model/db is definitely the way to go!
But if you have a 3rd party app with own models that should be hyphenated and you don´t wont to fork the app the cached version is an alternative which can be adopted in the templates without making the page slow.

@palewire

This comment has been minimized.

Show comment Hide comment
@palewire

palewire Jun 28, 2012

Member

Could this be solved with fragment caching at the template level?

Member

palewire commented Jun 28, 2012

Could this be solved with fragment caching at the template level?

@lenz

This comment has been minimized.

Show comment Hide comment
@lenz

lenz Jul 15, 2012

It could be done with fragment cache but performance and freshness would suffer!
Fragment cache would not calculate a hash over the text to determine the cache key. Therefore fragment cache must be purged regularly for freshness of data and therefore the cached/hyphenated version has to be recalculated regularly.

lenz commented Jul 15, 2012

It could be done with fragment cache but performance and freshness would suffer!
Fragment cache would not calculate a hash over the text to determine the cache key. Therefore fragment cache must be purged regularly for freshness of data and therefore the cached/hyphenated version has to be recalculated regularly.

@palewire

This comment has been minimized.

Show comment Hide comment
@palewire

palewire Jan 11, 2013

Member

I think i'm going to pass on this one and file it as #wontfix. Chalk it up to my questionable judgement.

Member

palewire commented Jan 11, 2013

I think i'm going to pass on this one and file it as #wontfix. Chalk it up to my questionable judgement.

@palewire palewire closed this Jan 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment