12-14-2018
I took a new look at Font Awesome, and I think I have a good way forward for the code tags icons (block and inline code tags):
- Replace the main code tag icon "code" with Font Awesome (fas fa-code); and,
- Replace the inline code tag icon with Font Awesome (fas fa-terminal).
References:
These are the best choices from the FA icons, as far as I can see (easiest to read, etc).
6 More Discussions You Might Find Interesting
1. What is on Your Mind?
I was reformatting the "advanced" WYSIWYG editor with bootstrap css and while there made the post icons to be invisible by default; so if you click on the text below the editor:
Post Icons - Click to view the full list of message icons to add to your post:
... (0 Replies)
Discussion started by: Neo
0 Replies
2. What is on Your Mind?
Finally making some progress on getting rid of the 10 year old buttons with modern day fonts and icons thanks to a responsive web design tutorial by Brad Traversy who's video pointed me to Font Awesome.
The buttons and icons were pretty easy to implement but it too me a number of hours... (39 Replies)
Discussion started by: Neo
39 Replies
3. What is on Your Mind?
Hey,
There was a small bug in the Quick Editor function in postbit, but I fixed it (basically a double quote was missing from an element id):
<div id="post_message_$post" class="neo-message-area">$post</div>
Was
<div id="post_message_$post class="neo-message-area">$post</div>
Should... (1 Reply)
Discussion started by: Neo
1 Replies
4. What is on Your Mind?
Just changed the mobile site to use Font Awesome icons.
Here is the new top navbar view (unregistered users)
https://www.unix.com/members/1-albums214-picture903.jpeg (2 Replies)
Discussion started by: Neo
2 Replies
5. What is on Your Mind?
Here is an update on the site renovation:
After a lot of analysis and example programming, including testing out a number of Javascript framework and libraries, in the short term, we are getting the most bang-for-the-buck from these three basic, core tech areas:
Bootstrap (CSS and... (2 Replies)
Discussion started by: Neo
2 Replies
6. What is on Your Mind?
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
https://www.unix.com/members/1-albums215-picture966.png
The reason for this change is to continue our move toward Font Awesome... (4 Replies)
Discussion started by: Neo
4 Replies
LEARN ABOUT DEBIAN
test::synopsis
Test::Synopsis(3pm) User Contributed Perl Documentation Test::Synopsis(3pm)
NAME
Test::Synopsis - Test your SYNOPSIS code
SYNOPSIS
# xt/synopsis.t (with Module::Install::AuthorTests)
use Test::Synopsis;
all_synopsis_ok();
# Or, run safe without Test::Synopsis
use Test::More;
eval "use Test::Synopsis";
plan skip_all => "Test::Synopsis required for testing" if $@;
all_synopsis_ok();
DESCRIPTION
Test::Synopsis is an (author) test module to find .pm or .pod files under your lib directory and then make sure the example snippet code in
your SYNOPSIS section passes the perl compile check.
Note that this module only checks the perl syntax (by wrapping the code with "sub") and doesn't actually run the code.
Suppose you have the following POD in your module.
=head1 NAME
Awesome::Template - My awesome template
=head1 SYNOPSIS
use Awesome::Template;
my $template = Awesome::Template->new;
$tempalte->render("template.at");
=head1 DESCRIPTION
An user of your module would try copy-paste this synopsis code and find that this code doesn't compile because there's a typo in your
variable name $tempalte. Test::Synopsis will catch that error before you ship it.
VARIABLE DECLARATIONS
Sometimes you might want to put some undeclared variables in your synopsis, like:
=head1 SYNOPSIS
use Data::Dumper::Names;
print Dumper($scalar, @array, \%hash);
This assumes these variables like $scalar are defined elsewhere in module user's code, but Test::Synopsis, by default, will complain that
these variables are not declared:
Global symbol "$scalar" requires explicit package name at ...
In this case, you can add the following POD sequence elsewhere in your POD:
=for test_synopsis
no strict 'vars'
Or more explicitly,
=for test_synopsis
my($scalar, @array, %hash);
Test::Synopsis will find these "=for" blocks and these statements are prepended before your SYNOPSIS code when being evaluated, so those
variable name errors will go away, without adding unnecessary bits in SYNOPSIS which might confuse users.
AUTHOR
Tatsuhiko Miyagawa <miyagawa@bulknews.net>
Goro Fuji blogged about the original idea at <http://d.hatena.ne.jp/gfx/20090224/1235449381> based on the testing code taken from
Test::Weaken.
LICENSE
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
Test::Pod, Test::UseAllModules, Test::Inline, Test::Snippet
perl v5.10.1 2009-07-06 Test::Synopsis(3pm)