Skip to main content

Creating A CHEAT SHEET For XML: Making Life Easier

When CHEAT SHEETS are allowed, all I want to do is celebrate!

I was half way through Unit 15 in the Artes Latinae Project, when I realized that there were a lot of frames that needed repetitive XML code.  Rather than retyping everything over and over, I decided to make a cheat sheet!  I opened my "Notes" on my Mac, and typed up a very nice and organized cheat sheet that contained all of the codes I needed for my project.

I was feeling pretty proud of myself until I tried to load my project.  I kept getting error messages.  I would do an XMLLINT on my file and the errors kept popping up.  I could't figure out what the problem was so I finally had to ask Marco for help.

As usual, he came running to the rescue.  The code where I was getting errors on "appeared" correct, but on further inspection by him, he found that my "quotation marks" looked slightly different.  Apparently, when I typed the code in "Notes", it changed the quotations to curly instead of straight (like in my Sublime Text Editor for XML).  Just that slight change caused error messages to appear all over the place.

I quickly learned the importance of making a cheat sheet IN my Sublime Text Editor (with XML selected) so that the code would not be altered.   Here is what my new cheat sheet looked like once I made it in Sublime:

I was able to position this XML cheat sheet file next to my Sublime file that contained the XML code for my project; that way, I could copy and paste side by side.  It made coding repetitive codes go fast.

      The picture on the left is of the Artes Latinae Project, the picture on the right is my cheat sheet.

                   I guess there are times in life where cheat sheets are definitely encouraged!


                      Follow me as I learn to build my website bit by bit!    IronTreeDev.com


Photo by Ben White on Unsplash


Comments

Post a Comment

Popular posts from this blog

XPATH and XPATH Expressions In XMLLINT

XPATH And XPATH Expressions Earlier, I told you about xmllint and xmllint for html files .  Let's say you just want to parse the <span> tags within your html file or just your <span lang="el"> tags? Enter:  Xpath. Xpath is yet another option available within the xmllint language. Remember, an Xpath is used to navigate through elements and attributes in xml and html documents.  Xpath uses Xpath Expressions to select nodes or node sets within a document. Example 1 .  Looking for all of the <span> tags within an html document. xmllint -- html -- xpath " // span" StedmanLesson10.html xmllint = This tells the command line that we are going to be using the xmllint language. space = because we always have space in between commands -- = Remember, these are the two hyphen-minus characters that we need to tell the command line that we are going to use an xmllint option. html = This is the xmllint option we want to ...
Post a Comment
Read more

XMLLINT for HTML: Cleaning up the HTML Code

Getting That MESS Cleaned Up! In an earlier post, we learned about xmllint .  Today, I want to talk about cleaning up the code for an HTML file. When we have an xml file, xmllint is used.  For an html file, we use the following command in the command line: xmllint --html <filename goes here>         Here is an actual command on my command line for running xmllint for my StedmanLesson10.html file. In the photo above, you see that I start off the command with xmllint. The next thing is a space and then a --html.  The two -- are two hyphen-minus characters that are used to specify long options (Basically there are options that can be used within xmllint.  The two hyphen-minus characters are saying an option is going to be used.  In this case, that option will be html - because we are going to do an xmllint on an html file). After that you see a space and then the name of the html file I want t...
Post a Comment
Read more

DevOps Skills Part 2: Talking Like a Toddler

http colon whack whack dub-dub-dub dot google dot com What in the world did I just say?   I sound like a toddler talking in words and sounds that make no sense at all! 🙊The funny thing is, if you talk to a person involved with DevOps, they will know and understand exactly what you said! 😲 whack = "/"  That forward slash symbol on a Mac key board that is usually placed under the ? ...... that is referred to as a "whack".  Think of a duck quacking who forgot to sound the "q". 🙈 That forward slash (/) "whack" is the path separator that will eventually lead to the file on your web server.  Let's say the url is www.cloviscorp.com/collegium/grammar/index.html , then the browser will first find the webserver (in this case:  www.cloviscorp.com).  It then starts in that server's filesystem at the docroot (/var/html/www) and then continuing through to /collegium/grammar , where the file index.html resides (at the webserver's f...
Post a Comment
Read more