I would like to know if it is possible to highlight a cross-reference by editing an RStudio theme. Right now, I am able to do this for my references by adding the following to an rstheme (credit to Diego Trindade's answer here):
.ace_list, .ace_markup.ace_list, .ace_storage {color: #66db80;}
This highlights anything in my text that looks:
#article_referenced
I would like to do the same thing but for cross-references that call a code chunk label:
\#ref(fig:chunk-label)
But I am not sure if this is possible. The reference from RStudio only mentions the most common things that I can change, but nothing related to this. If anyone knows how to do this or any documentation I could go to for a more complete reference I would really appreciate it.
I have a short question. How can I change mark inside checkbox from standard tick to dot? I already have a circle shape. All I want is my checkbox looks like radiobutto. How can I solved this?
While I agree with ProgrammerPer that this might not be a great idea from a user experience perspective, sometimes manipulations like this are necessary.
If I'm understanding the OP's question, I think the only way this could be accomplished is to mirror the checkbox functionality with a div (for example) so it can have a custom 'ticked' view.
This a great resource for customizing inputs: http://wtfforms.com/
Also, this post and the article linked in it, might be worth a read regarding the UX implications: https://ux.stackexchange.com/questions/41924/is-it-acceptable-practice-to-use-checkboxes-as-radio-buttons
Hope this helps!
First off, I don't know what this is called. So I am going to explain it.
While using Sublime Text Editor and editing HTML it would autocomplete certain parts of the text. Stuff it knew without a doubt that I would be typing.
For example:
<div> </
By the time I've typed that, it would auto-complete to
<div> </div>
Now, I'm wondering what this is called and how I can enable this when using Atom.
I know this is probably a silly question, but I have looked through the answers myself and I just don't know what this is called in actuality, so I can't seem to find anything related to it and it would probably be faster to get a quick answer here.
Thank you.
U can type the command without braces it will automatically complete the tags... I tried it and works well...
ex: write p instead of
Hope you understand.....
cheers :)
Try this from inside the Atom Editor. See my Atom Cheatsheet at https://github.com/pd-gmit/atom-cheatsheet/blob/master/atom_cheatsheet.md for more tips.
Ctrl Space L
I was wondering how to create word processor buttons in html such as:A Bold Button,An Italic button and text size increase button.(THEY DON'T HAVE TO BE PRETTY) any ideas would be GREATLY APPRECIATED! THANKS!
You won't be able to achieve this with HTML alone. This sounds like a job for javascript. What you are looking for is called a rich text box, and there are a few decent open-source options around. You should consider using these before building one from scratch. For instance, WordPress uses TinyMCE: http://www.tinymce.com/ . It is definitely worth a look.
Suppose you're developing a web site and blind users will be a significant chunk of your target market. If the web site includes document editing functionality, what would be appropriate WYSIWYM tools? Are languages like Markdown, Textile and Wiki Formatting really accessible or are they inconvenient to blind users?
I'm a blind programmer and while I haven't used most of the languages you mention I've found that any markdown language is fairly easy to use if you have the desire to learn it. I've had no problem using either HTML or several markup languages for wiki's. Part of it will depend on how invested the users are in your site. If it's a site that will be visited infrequently or for short periods of time, it's much less likely that a user will take the time to learn the required markup whether they are blind or not. Unfortunately, I have not found an accessible JavaScript WYSIWYG editor but I find it easier to manually enter the markup so haven't looked very hard.
the first question is: how important is semantic structure? could you get away with plain text. You could do simple parsing like treating blank lines as paragraph markers, treating a series of lines which begin with * as a bulleted list, identify URLs and make them into links, etc.
As a blind developer myself, I have no problem in understanding languages like Markdown. But if it's a syntax I'm unfamiliar with, I'll only learn it if I expect to use the site very often, or care deeply about the content.
Two final thoughts come to mind: while I certainly experience some accessibility challenges using TinyMCE, you could develop something much simpler - provide less than 10 formatting options, like inserting hyperlinks, making lists, centering text, setting the style (such as heading) etc.
And lastly, when I talk to non-technical blind people, they often just write their content in Word and paste into a wiki or blog post. This sounded strange when I first heard it, but it does make sense. So an ideal solution would accept pasted in content.
In closing - it depends how important this is, and how much effort you want to expend. Maybe a Markdown editor with a live preview (like on this site), buttons for inserting simple formatting like URLs, and the ability to paste in rich text would tick all boxes :-)
On a web page, the most accessible embedded text editor for blind users is one that uses standard HTML, such as a <textarea> element, with a corresponding <label> element:
<label for="editor">Enter your text here using wiki markup:</label>
<textarea id="editor"></textarea>
If a WYSIWYM tool is built using standard accessible HTML, then blind users can easily enter text into it, with full confidence that they're entering text in the right place. Then the question becomes: Which is the better markup language? They all require memorization, but some may be more intuitive than others. One way to find out which is best would be to do some usability testing with a wide variety of target users. Also be sure to providing easy, accessible access to syntax help.
Picture yourself working in pure text 80x4 display (just open a console and resize appropriately), then use vi/emacs/ed and you'll soon realize what markup will get in the way.
Try to do as much work as possible to understand plain text, else use light markup like POD, finally things like AsciiDoc are very powerful but needs training.
I don't know about WYSIWYG/WYSIWYM tools, but I do know that complying with W3C standards (especially their HTML5 en CSS3 drafts) while writing your own editor code will help a lot.
In CSS you can specify speed and intonation of speech. In HTML you can specify alternative text (alt attribute in many elements) that screen readers are compatible with. Be sure to know when to use the abbr and the acronym elements. Use the former when you want the screen reader to read the meaning of an abbreviation and the latter when the acronym should be read as a word (e.g. ASAP, NATO and OS).
For the editor itself, I recommend creating a WYSIWYG editor that uses divs and spans. Screen readers will understand easily the structure of a document. For the current line, use a text box; for every other line that's not being edited, convert the contents immediately to valid HTML.
If you find a good tool, be sure to post it here. I'm looking for one too. :-)