Sponsored Content
Top Forums Web Development New Font Awesome Icons in Quick Reply Editor Post 303027023 by Neo on Friday 7th of December 2018 06:59:28 AM
Old 12-07-2018
Update: Was able to get the ICODE tag to work using Font Awesome in the Quick Reply Editor. Also, removed the PHP code tag in the QRE.

TODO: Need to change the "advanced" and "edit post" editors....
 

6 More Discussions You Might Find Interesting

1. What is on Your Mind?

New jQuery to view Post Icons in Editor

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?

New Icons Coming from Font Awesome

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?

Small bug in the Quick Editor function in postbit

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?

New Mobile Navbar Icons from Font Awesome

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?

Quick Update on UNIX.COM Site Renovation: Bootstrap, Font Awesome and jQuery

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?

New CODE and ICODE Editor Button Icons

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
BLAZE-EDIT(1)						    BlazeBlogger Documentation						     BLAZE-EDIT(1)

NAME
blaze-edit - edits a blog post or a page in the BlazeBlogger repository SYNOPSIS
blaze-edit [-fpqCPV] [-b directory] [-E editor] id blaze-edit -h|-v DESCRIPTION
blaze-edit opens an existing blog post or a page with the specified id in an external text editor. Note that there are several special forms and placeholders that can be used in the text, and that will be replaced with a proper data when the blog is generated. Special Forms <!-- break --> A mark to delimit a blog post synopsis. Placeholders %root% A relative path to the root directory of the blog. %home% A relative path to the index page of the blog. %page[id]% A relative path to a page with the supplied id. %post[id]% A relative path to a blog post with the supplied id. %tag[name]% A relative path to a tag with the supplied name. OPTIONS
-b directory, --blogdir directory Allows you to specify a directory in which the BlazeBlogger repository is placed. The default option is a current working directory. -E editor, --editor editor Allows you to specify an external text editor. When supplied, this option overrides the relevant configuration option. -p, --page Tells blaze-edit to edit a page or pages. -P, --post Tells blaze-edit to edit a blog post or blog posts. This is the default option. -f, --force Tells blaze-edit to create an empty source file in case it does not already exist. If the core.processor option is enabled, this file is used as the input to be processed by the selected application. -C, --no-processor Disables processing a blog post or page with an external application. -q, --quiet Disables displaying of unnecessary messages. -V, --verbose Enables displaying of all messages. This is the default option. -h, --help Displays usage information and exits. -v, --version Displays version information and exits. ENVIRONMENT
EDITOR Unless the core.editor option is set, BlazeBlogger tries to use system-wide settings to decide which editor to use. EXAMPLE USAGE
Edit a blog post in an external text editor: ~]$ blaze-edit 10 Edit a page in an external text editor: ~]$ blaze-edit -p 4 Edit a page in nano: ~]$ blaze-edit -p 2 -E nano SEE ALSO
blaze-config(1), blaze-add(1), blaze-list(1) BUGS
To report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit the discussion group at <http://groups.google.com/group/blazeblogger/>. COPYRIGHT
Copyright (C) 2008-2011 Jaromir Hradilek This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Version 1.2.0 2012-03-05 BLAZE-EDIT(1)
All times are GMT -4. The time now is 04:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy