I knew it could be done, but did not build it yet: a message counter using SVG! Now I have a working version in the Example App (not published yet). Let’s say it’s better not to mix PNG and SVG favicons as browsers are not fond of switching from one type to another.

Will do as soon as I find out how I can do it for free I already use one instance for Phoenix Localized Routes

While creating the message counter example, I found some inconveniences in using the lib and needing to mix in ‘raw’ Live Head. So…..

version 0.2.0-rc.0

A new version has been released as RC on Hex; it powers the updated example page which hopefully will be online soon, so you can all come up with fancier gifs of ‘animated’ favicons!

afbeelding1200×672 51.1 KB

Features

Create and restore snapshots

The new operations snap and restore make it possible to store the result of many operations under a chosen name and restore it at a later time by only sending the snapshot name over the wire.

• snap - Takes a snapshot of all attribute values.
• restore - Applies a snapshot to selected elements

In the Live Favicon Example application it is used to send all changes required to switch between an dynamic SVG counter and static PNG message-icon once, and toggle the state between them; creating a flashing notification. As it also makes a snapshot of the state before the favicon begins to flash, the icon on the page can be restored to it’s value as soon as the user had read the unread messages.

Use multiple placeholders

You can now use multiple custom named placeholders, instead of only one {dynamic} per attribute.

Fixes

• Unstable order of change execution when using multiple queries / libs.

BREAKING

• the attribute value of dynamic is now used as name for the target placeholder. As a result, it is not possible anymore to target a specific attribute. Migration is as easy as using different names per attribute when necessary.

TESTERS NEEDED!

This is quite a major release as a lot of logic was rewritten in the underlying lib. However, for most there won’t be breaking changes so the upgrade should be safe.

Please upgrade to the RC version and let me know if you experience any issues (or better: how many issues it solves!)

{:phoenix_live_favicon, "~> 0.2.0-rc.0"}

See also: the diff of Example App and especially how it uses the new snapshots and custom dynamic placeholders.

Release 0.2.0 (changelog)

Changes
No fundamental changes to rc.0 so the post above is accurate. The example app has been updated to use the new 0.2.0.

Better documentation
The README has seen some work too and a few GUIDES were added.

Migration guide
As this is a breaking release due set_dynamic being redefined, you should update your mix.exs file to include:

 {:phoenix_live_favicon, "~> 0.2.0"}

When using set_dynamic from 0.1.x you can rewrite them to
set_dynamic("dynamic", value). Notice it targets a specific placeholder instead of an attribute. When you used multiple {dynamics} on different attributes, you should rename every dynamic placeholder to be unique. See the docs of set_dynamic/3

Release 1.0

The lib version has been bumped to 1.0.0 in order to reflect stability. Please update your dep in mix.exs.

{:phoenix_live_favicon, "~> 1.0"}

looks great! - what does the browser support like nowadays?