Novel Hamburger Alternative

[Acorn]

Someone might find this CSS construct of the Yin-Yang symbol of use as an alternative to the hamburger icon for a menu.

CSS-Yin-Yang novel Hamburger icon.xar

Very lightweight. No http: image calls.
Can be scaled.
Portable - only the Black Circle holds the CSS in its Head.
Can be cloned by just putting <div class="yin-yang"></div> into a new Placeholder's Body.
Hover & Click actions can be adjusted...

Acorn

[Boy]

Thanks for the offering, Acorn! Nice effect.

You've created quite a library of useful tools to expand regular XDA functionality over the years. I also appreciate the (intended?) fact that many of them can be used in non-Plus version, even XDP 19 (which I still use).

Two suggestions, if I may:
Add the TG link in the design file (I do this but sometimes forget) so it's easy for users to refer back to directions and discussions.
An index with links would also be handy (but I realize that the creation and maintenance of it might require a lot of work).

[Acorn]

Thanks for the offering, Acorn! Nice effect.

You've created quite a library of useful tools to expand regular XDA functionality over the years. I also appreciate the (intended?) fact that many of them can be used in non-Plus version, even XDP 19 (which I still use).

Two suggestions, if I may:
Add the TG link in the design file (I do this but sometimes forget) so it's easy for users to refer back to directions and discussions.
An index with links would also be handy (but I realize that the creation and maintenance of it might require a lot of work).

Boy, all good suggestions.

It would be easier for the user to grab the TG Link and add that themselves to the XAR file.
I usually add the https://www.talkgraphics.com/tags.php?tag=nugget Link to achieve an 'index'.

I'll work something out.

Acorn

[Boy]

I usually add the https://www.talkgraphics.com/tags.php?tag=nugget Link to achieve an 'index'.

That's already a useful link, Acorn.

[Acorn]

@Boy, I've done a lot of thinking about self-documentation of my designs. Most of what I offer to TG is an off-the-cuff solution that I have 'invented' without fuller analysis. Sometimes, they are rough and ready but often are more elegant that the Xara approach, which may not even possible. Xara pre-processes excessively and CSS is necessarily post-processing Add a filter to an image and Xara delivers another image; use a graphic for a bullet and Xara creates an image for each bullet used, text lines are split apart with SPAN Tags, justified text has no spaces between words, in-line CSS is ultimately detrimental, Xara tables are not HTML Tables, gradients are set in stone, ...). Xara's HTML Filter is slowly evolving to realise more HTML and CSS3 compliancy and so I hope that my offerings are some sort of incentive to Xara.

What I normally do for documentation is force an info.txt file to become an External Asset and have a link on the Pasteboard so that when clicked it allows me to add ideas and comments on the design.
This forces the <filename>_xar_files folder to store this info.txt file.

The main advantages are I do not need to save the XAR file at all for these text comments additions and searching for them is simple as they exist in plain text form so once found the associated XAR file is too.

I have considered other approaches.
Here is an alternative I have just developed: info.xar. It required 20 separate Saves to reach its current form. The new Plus v24.0 embedded approach would be even worse.
I cannot discover its purpose without either opening it. No desktop search will work.
The Preview only works for Plus versions using SVG or CSS for regular shapes. The design is a work in progress to show the processes I go through to curate good additions to the Xara product.
It just so happens that this particular approach is extremely quirky that I would have dumped it normally and switched to an anime.js solution. It pays to record and document failures.

In the bad old days, Xara overlooked that it had left its internal WIX Export in production versions.
So, Xara sort of removed it by screwing it up (Plus version Error: There was a error part part way through saving the file causing it to be incomplete).
.WIX is basically an unpacked version of the .XAR file and is in human-readable format so useful for finding version history and plain text... (oh and can also be smaller in size as you could remove the Preview Bitmap, unlike .XAR files) ... Its loss would be offset a little if Xara could recode it properly and re-introduce .WIX fully or add back its File > Document Information > History capability.
Xara hid that in a Registry setting and because it was rarely used, its buggy nature was also never addressed and so it was dropped because it was buggy and rarely used.

Go figure.

Acorn

[Boy]

Thanks for the extensive follow-up, Acorn. I don't have a full understanding of your analysis and argument but I do appreciate the fact that the XDA give you limited room to maneuver.