New CODE and ICODE Editor Button Icons

What is on Your Mind?
1

As promised, I have changed the CODE tag icon and the ICODE tag icon in our WYSIWYG editors to use Font Awesome.

  • CODE Tag = fa-code
  • ICODE Tag = fa-terminal

874×567 46.3 KB

The reason for this change is to continue our move toward Font Awesome for icons and Bootstrap for CSS, in general.

Also, this solves some issues we were having with Bootstrap tooltips not working properly for these icons.

Cheers

PS: Still looking for suitable FA icons to replace "move margin left" and "move margin right" but nothing useable has jumped out so far. Also, will replace the "make the editor bigger and smaller errors on the right with FA arrows at some point in time....

2

Update: Found FA icons for indent:

  • Indent fa-indent
  • Outdent fa-outdent

Ref:

Not sure how I missed 'em... maybe they are new in the FA release 5? Or maybe I missed 'em earlier.

So when I get a chance, I'll update indent and outdent in the editors as well.

3

Update:

Just made the switch to FA for the indent, outdent, increase-size and decrease size icons. This completes the FA switch for these editor icons, except for the smiley picker.

889×565 38.1 KB

Next, I think I will work on using Bootstrap Carousel classes for the attachments in posts.

Carousel . Bootstrap

and perhaps (50/50) using Bootstrap classes for pagenav classes:

Pagination . Bootstrap

4

OK... Bootstrap Update.

Have tested Bootstrap carousel for post attachments and Bootstrap does not work as good as our current attachment code using Swiper

Swiper - Most Modern Mobile Touch Slider

So, will not transition our attachment code in posts to Bootstrap from Swiper.

Bootstrap Carousel seems great if we had some big banner of slides at the top of a page with a bunch of images in carousel, which we don't have or need.

However, I may consider Bootstrap Carousel for the albums, but at this times, seems not necessary.

5

Update: I don't think I will transition the pagnav HTML templates to Bootstrap at this time. The $pagnav looks fine the way they are and there are bigger fish to fry.

However, I may address the long standing issue of having man page repositories which are huge single pages; and I may use Bootstrap when or if I decide to rewrite the man page repos to use page nav so the pages will not be huge single page listings of thousands of links to man pages.