<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julianna Zakula on Medium]]></title>
        <description><![CDATA[Stories by Julianna Zakula on Medium]]></description>
        <link>https://medium.com/@julianna.zakula?source=rss-5bec0bc6c1d1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b_JNzOwfpOzuu9YQi5fgNA.jpeg</url>
            <title>Stories by Julianna Zakula on Medium</title>
            <link>https://medium.com/@julianna.zakula?source=rss-5bec0bc6c1d1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:14:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julianna.zakula/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Final Thoughts]]></title>
            <link>https://medium.com/@julianna.zakula/final-thoughts-675569cc6f75?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/675569cc6f75</guid>
            <category><![CDATA[writdm]]></category>
            <category><![CDATA[self-evaluation]]></category>
            <category><![CDATA[selfeval]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Sat, 23 Jul 2016 13:45:14 GMT</pubDate>
            <atom:updated>2016-07-23T13:45:14.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h264vvyaNhcCWP3vnNS16Q.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/startup-start-up-notebooks-creative-593327/">Pixabay</a></figcaption></figure><p>Taking the digital writing course, <a href="https://writingdigitalmedia.com/latest">NMAC 3108</a>, has been an invaluable experience and will benefit me greatly in both my college and work careers.</p><h4>Skills Learned</h4><p>Many of the projects in NMAC 3108 were done for the real world as well as for class. These hands-on and practical applications taught me many important skills, including how to:</p><ul><li>Write for a professional community</li><li>Develop a professional persona</li><li>Collaborate online</li><li>Structure digital writing content</li></ul><h4>Final Understanding</h4><p>After completing this course, I have a much different understanding of writing for digital media than I had at the beginning of the semester. Before, it had never crossed my mind that writing for a digital platform would be any different than writing an academic essay. However, I soon discovered that digital writing is a whole different ball game. An online audience reads in a whole different manner than a print audience does. Instead of striving for a maximum word count, one must be as brief and to the point as possible.</p><h4>Evaluation</h4><p>For this course, I would give myself an A. In each assignment, I strove to meet both the assignment requirements and also provide the best material I could for my expert community. I also collaborated and communicated with my classmates throughout the semester. I provided constructive feedback on soft drafts and also participated in the class’s wiki discussions. Most importantly though, I learned how to effectively present content on a digital platform. This alone, I think, was worth the time and effort spent in completing this course.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=675569cc6f75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding the Needle…]]></title>
            <link>https://medium.com/@julianna.zakula/finding-the-needle-882af6577f33?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/882af6577f33</guid>
            <category><![CDATA[elearning]]></category>
            <category><![CDATA[creativecon]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Wed, 20 Jul 2016 12:13:54 GMT</pubDate>
            <atom:updated>2016-07-20T12:13:54.642Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kdjRDQpgRF973gOUmBQ0w.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/film-projector-movie-projector-596519/">Pixabay</a></figcaption></figure><p>In my <a href="https://writingdigitalmedia.com/creative-mashup-8c8c1690dc84#.opysux1gj">last blog post</a>, I chose <a href="https://en.wikipedia.org/wiki/Discrete_mathematics">Discrete Math</a> as it is applied to Computer Science as my topic for <a href="https://litmuse.net/creative-contribution-59d8599b8acc#.bgbmwrn2a">Lesson 4</a>. I also decided to incorporate interactive animations and video into my content to better explain the concepts of Discrete Math. However, before I could start creating my content, I had to find a platform to present it.</p><h4>eLearning Platforms</h4><p>After reading up on how to present <a href="http://www.elearningnc.gov/about_elearning/what_is_elearning/">eLearning</a> content, I found a list of several possible free <a href="https://elearningindustry.com/free-authoring-tools-for-elearning">eLearning authoring tools</a> including:</p><ul><li><a href="https://www.easygenerator.com/">EasyGenerator</a></li><li><a href="http://www.smartbuilder.com/">Smartbuilder</a></li><li><a href="http://www.learningtools.arts.ubc.ca/">Learningtools</a></li><li><a href="http://www.dipity.com/">Dipity</a></li><li><a href="http://www.udutu.com/">Udutu</a></li><li><a href="https://scratch.mit.edu/">Scratch</a></li></ul><h4>Narrowing Down the List</h4><p>After glancing over the websites of the eLearning platforms above, I quickly eliminated all but EasyGenerator, Smartbuilder, and Scratch. The other platforms do not support interactive objects and thus I would be unable to create interactive animations for the course.</p><h4>The Platform</h4><p>Out of the three platforms chosen above, I decided to go with EasyGenerator. Its website is simple and easy to use while the other two sites are a bit confusing to navigate. EasyGenerator also structures its courses in a more traditional format making the interface more intuitive for users.</p><h4>Next Steps</h4><p>I’ve already created the basic layout of my course and decided on its subtopics. Over the next couple days, I will write the actual course content, create my animations, and incorporate video into the course. Then my project will be ready for soft evaluation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=882af6577f33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creative Mashup]]></title>
            <link>https://medium.com/@julianna.zakula/creative-mashup-8c8c1690dc84?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c8c1690dc84</guid>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[createcon]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Sat, 16 Jul 2016 12:17:14 GMT</pubDate>
            <atom:updated>2016-07-16T12:17:14.150Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-2zZDBsSLZJuEN6H-fXDw.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/abstract-flower-artwork-art-1474819/">Pixabay</a></figcaption></figure><p>The <a href="https://litmuse.net/creative-contribution-59d8599b8acc#.1b25ln9fe">final lesson</a> of <a href="https://litmuse.net/writing-for-digital-media-de3b011df20e#.1ttxn09sj">NMAC 3108</a>, as <a href="https://medium.com/u/623fc1470dee">Gerald R. Lucas</a> puts it, is to be the culmination of everything learned this semester. The basic requirements are to:</p><ul><li>Combine two modes of digital writing</li><li>Contribute to the knowledge of my expert community</li><li>Explain a concept or process</li></ul><h4>My Topic</h4><p>For my lesson 4 topic, I decided on <a href="http://mathworld.wolfram.com/DiscreteMathematics.html">Discrete Math</a> as it is applied to Computer Science. This semester, I took a course in Discrete Math and found some of its topics to be quite difficult to understand. So, I thought it would be fun to explain these concepts in the way I learned them and hopefully help others in the process. This topic also satisfies the concept requirement and contributes to my expert community, Information Technology.</p><h4>Digital Writing Modes</h4><p>I am still looking into different digital modes of presenting my content. In researching <a href="http://elearning/">eLearning</a>, video and interactive animations seem to be two of the number one “must haves” in online courses. As Christopher Pappas notes in the following article, animated videos greatly increase the audience’s engagement and retention in an online course.</p><p><a href="https://elearningindustry.com/the-top-6-animated-video-software-in-the-elearning-market">The Top 6 Animated Video Software in the eLearning Market - eLearning Industry</a></p><h4>Next Steps</h4><p>This week, I will decide which digital platform to use in presenting my content. I will also narrow down which topics to cover in Discrete Math by how much they relate to Computer Science. Then I can begin creating and writing my content!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c8c1690dc84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking Back…]]></title>
            <link>https://medium.com/@julianna.zakula/looking-back-212a59163e17?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/212a59163e17</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[norman-mailer]]></category>
            <category><![CDATA[wikipedia]]></category>
            <category><![CDATA[wiki]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 11:44:33 GMT</pubDate>
            <atom:updated>2016-07-13T11:44:33.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIT4fiJJRbhXsNrpiZ6KfQ.jpeg" /><figcaption>Image Caption: <a href="https://pixabay.com/en/tablet-touch-screen-reading-glasses-600649/">Pixabay</a></figcaption></figure><p>Today, my classmates and I are adding finishing touches to the wiki entry “<a href="https://en.wikipedia.org/wiki/Advertisements_for_Myself">Advertisements for Myself</a>,” in preparation for tomorrow’s submission. Looking back over the past two weeks of work, I am amazed at what a little rewriting and polishing can do. In this post, I will discuss some of my work and improvements on the wiki entry.</p><h4>Assessing the Summaries</h4><p>The majority of my editing was done on the wiki section, “Part 5: Games and Ends.” This section covers the corresponding part of the same name in Mailer’s book. The old wiki entry listed the contents of Part 5 in Mailer’s book but did not provide summaries for each item. Thus, its readers could deduce very little about this section of Mailer’s book from the given information.</p><h4>Improving the Summaries</h4><p>First, to increase my knowledge of Part 5, I read each of its advertisements and included works. I also did a bit of research on Mailer’s history to get a feel of where the author was coming from. Then, I briefly summarized each of the items in Part 5 and added them to the wiki entry.</p><h4>Other Work</h4><p>I also cleaned up the wiki entry’s references, removing several redundant citations and linking those that did not have an external source. After removing the redundant citations, I also proofread the entry to ensure that no footnotes were still linking to the removed references.</p><h4>Rating</h4><p>On a scale of one to ten, I would rate my wiki efforts as a nine. The new entry provides a much greater amount of information so that readers know exactly what to expect from Mailer’s book. The summaries are also kept brief and to the point to enhance the entry’s scan-ability.</p><p>Although the section, Part 5, is greatly improved compared to the old version, I feel that I might have been able to polish it a bit more and add more support to my summaries. Hence, the nine rating. Eventually, as my schedule allows, I plan to improve and polish this section a bit more on my own.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=212a59163e17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Neutrality in Wikipedia]]></title>
            <link>https://medium.com/@julianna.zakula/neutrality-in-wikipedia-b4d6974f3a9e?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4d6974f3a9e</guid>
            <category><![CDATA[norman-mailer]]></category>
            <category><![CDATA[wikipedia]]></category>
            <category><![CDATA[wiki]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Sat, 09 Jul 2016 01:46:29 GMT</pubDate>
            <atom:updated>2016-07-09T01:46:29.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYLy3W5IMuuHq8Y3Xtfhvw.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/system-network-news-personal-927147/">Pixabay</a></figcaption></figure><p>As mentioned in my <a href="https://writingdigitalmedia.com/over-communication-good-or-bad-6767c4eb5bb1#.45jshu5na">last blog post</a>, I had started reading Norman Mailer’s book <a href="https://www.amazon.com/Advertisements-Myself-Norman-Mailer/dp/0674005902"><em>Advertisements for Myself</em></a>, specifically Part 5. This week, I completed my readings and also did a bit of research on preventing bias when writing/editing Wikipedia entries.</p><h4>Neutrality or NPOV</h4><p>A neutral point of view or NPOV is what every Wikipedia writer strives to achieve and is one of Wikipedia’s official policies.</p><p><a href="https://en.wikipedia.org/wiki/Wikipedia:NPOV_tutorial">Wikipedia:NPOV tutorial</a></p><p>An NPOV article presents its content fairly, proportionately, and covers all the content’s significant viewpoints. These viewpoints must also be credited by reliable sources in order to be considered NPOV.</p><h4>Achieving NPOV</h4><p>As noted in the Wikipedia article above, in order to limit bias in Wikipedia entries:</p><ul><li>Use numerous citations</li><li>Use neutral Language</li><li>Avoid insinuations</li><li>Use attributions when making accusations</li></ul><p>The above tips both help reduce personal bias and add credibility to an entry.</p><h4>Practical Application</h4><p>The above findings will help me greatly in creating summaries on Part 5 of Mailer’s book. To keep personal bias out of my overviews, I can support my statements with authoritative sources. Using an impartial tone will also help prevent my personal opinions from affecting my content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4d6974f3a9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Over-communication: Good or Bad?]]></title>
            <link>https://medium.com/@julianna.zakula/over-communication-good-or-bad-6767c4eb5bb1?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6767c4eb5bb1</guid>
            <category><![CDATA[wiki]]></category>
            <category><![CDATA[norman-mailer]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Wed, 06 Jul 2016 12:06:29 GMT</pubDate>
            <atom:updated>2016-07-06T12:06:29.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4v7VbqSqMKMf-xRRzsipQ.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/business-internet-web-technology-1012761/">Pixabay</a></figcaption></figure><p>This week, I started reading Norman Mailer’s <a href="https://www.amazon.com/Advertisements-Myself-Norman-Mailer/dp/0674005902"><em>Advertisements for Myself</em></a>, in preparation for contributing to my class’s <a href="https://litmuse.net/collaboration-wdmwiki-afb46f80b4e0#.73gmwdlnx">wiki project</a>. In discussing and researching this project with my classmates, I learned quite a bit about online collaboration.</p><h4>Over-communication vs Under-communication</h4><p>In his article about collaborating online, Fisher states that over-communication is much better than under-communication.</p><p><a href="https://www.opm.gov/policy-data-oversight/performance-management/teams/building-a-collaborative-team-environment/">Building a Collaborative Team Environment</a></p><p>Miscommunication, or not communicating enough, can cause many problems among a team, including:</p><ul><li>Hard feelings</li><li>Role conflicts</li><li>Distrust</li><li>Productivity loss.</li></ul><h4>Effective Communication</h4><p>To avoid the problems brought about by miscommunication, Lee Polevoi suggests <a href="http://quickbooks.intuit.com/r/employees/how-to-avoid-miscommunication-in-your-workplace/#sm.001z0xvvv110wdchpts21kcksqklm">three major tips</a> to increase communication among team members.</p><ol><li>Discuss Expectations</li><li>Take Responsibility</li><li>Be clear and to the point</li></ol><p>The three suggestions above can help prevent team confusion over individual responsibility, expectations, and instructions.</p><h4>Application</h4><p>In the class’s wiki discussions this week, it was decided that each team member would take a portion of Mailer’s book to summarize. After some discussion, we decided which portions each would summarize and also established the format in which to write the summaries.</p><p>Thus, the class as a whole has already used many of the elements of good communication. Responsibility and format expectations were established. However, continued communication is very important in order to maintain focus and stay on track.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6767c4eb5bb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This week, I looked over lesson 3 of NMAC 3108.]]></title>
            <link>https://medium.com/@julianna.zakula/this-week-i-looked-over-lesson-3-of-nmac-3108-fd095a184d15?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd095a184d15</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[wiki]]></category>
            <category><![CDATA[norman-mailer]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Sat, 02 Jul 2016 11:25:03 GMT</pubDate>
            <atom:updated>2016-07-02T11:25:03.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2d_WmqFy0Mx6YORF09kDQ.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/book-open-black-reference-concept-164758/">Pixabay</a></figcaption></figure><p>This week, I looked over <a href="https://litmuse.net/collaboration-wdmwiki-afb46f80b4e0#.li4f7h3dh">lesson 3</a> of <a href="https://litmuse.net/writing-for-digital-media-de3b011df20e#.xw1osg44y">NMAC 3108</a>. In this lesson, the class is to collaborate on improving the Wikipedia stub about <a href="https://www.amazon.com/Advertisements-Myself-Norman-Mailer/dp/0674005902"><em>Advertisements for Myself</em></a> by Norman Mailer.</p><p><a href="https://en.wikipedia.org/wiki/Advertisements_for_Myself">Advertisements for Myself</a></p><h4>Areas of Improvement</h4><p>As <a href="https://medium.com/u/623fc1470dee">Gerald R. Lucas</a> notes in his article, “<a href="https://litmuse.net/writing-on-a-wiki-66d288cebab4#.p9t4tpli6">Writing on a Wiki,</a>” a good stub contains the following elements:</p><ul><li>Strong Title</li><li>Correct Structure</li><li>Lead Section</li><li>Headings &amp; Subheadings</li><li>Paragraphs</li><li>Links</li><li>Images</li><li>Footnotes &amp; References</li></ul><p>In reading the “Advertisements for Myself” stub, I noticed that it was lacking in many of the above areas. Instead of paragraphs, the stub uses long bulleted lists to display the contents of each section in Mailer’s book. As Dr. Lucas says, bulleted lists should be used sparingly in a wiki entry, if at all.</p><p>The stub also provides only a one or two sentence summary for each section in Mailer’s book. These summaries could be fleshed out a bit more similar to the Wikipedia stub on “Before the Dawn.”</p><p><a href="https://en.wikipedia.org/wiki/Before_the_Dawn_(book)">Before the Dawn (book)</a></p><h4>Importance of Research</h4><p>To successfully complete this assignment, research will be critical. Referencing and adding sources to the stub’s content will ensure its credibility. It will also help us, the editors, in presenting the most accurate information to our audience and in avoiding personal biases.</p><h4>Plan of Attack</h4><p>In the class’s wiki discussions today, we decided that the best way to go about this assignment is for each of us to take a portion of Mailer’s book to read and write a short summary on. We can then add the main sections, proofread, format, and add references to complete the stub.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd095a184d15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revise, Revise and Revise some More!]]></title>
            <link>https://medium.com/@julianna.zakula/revise-revise-and-revise-some-more-f768d6fd4eaa?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f768d6fd4eaa</guid>
            <category><![CDATA[publication]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[revising]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Wed, 29 Jun 2016 11:39:47 GMT</pubDate>
            <atom:updated>2016-06-29T11:39:47.762Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_MNZYNZc6pmdOx8M21Ztw.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/work-coffee-papers-red-pen-red-1357001/">Pixabay</a></figcaption></figure><p>This week I wrote and published the following two articles on Medium to complete <a href="https://litmuse.net/write-for-a-publication-71553cca3b36#.tnth6e6u5">lesson 2</a> of <a href="https://litmuse.net/writing-for-digital-media-de3b011df20e#.1lcgjmok2">NMAC 3108</a>.</p><ul><li><a href="https://medium.com/front-end-hacking/inline-editing-with-angular2-58b43cc2aba">Inline Editing with Angular2</a></li><li><a href="https://medium.com/bitmaker-software/my-most-puzzling-angular-2-errors-181c1331435b">My Most Puzzling Angular 2 Errors</a></li></ul><h4>Writing the Articles</h4><p>Although writing for a publication was completely new for me, I really enjoyed this assignment. It was a refreshing challenge and the fact that I was completing homework and contributing to my expert community at the same time was very rewarding and motivating.</p><p>Writing for a publication also taught me how important revision is in the writing process. I had taken several writing courses prior to NMAC 3108, and each stressed the importance of reviewing and redrafting. To me this meant rereading my essays once or twice to correct misspellings and grammatical errors. However, revision took on a whole different meaning after I published my two articles.</p><h4>Revision</h4><p>In writing my articles for a publication, I was targeting a much larger audience than just <a href="https://about.me/grlucas">Dr. Lucas</a> and my classmates. Thus, the readability and credibility of the information presented in the articles was very important. I was writing not only for a grade but also to contribute to a professional community. Consequently, I:</p><ul><li>Proofread my articles many times</li><li>Obtained feedback from several colleagues</li><li>Rewrote significant portions of both articles</li></ul><p>In the end, I had two considerably more polished articles than I had started out with. In comparing the first drafts with the final drafts, I realized that revision can make a huge difference and is much more important that I’d initially thought.</p><h4>Summary</h4><p>This assignment was fun and I plan to continue publishing articles in the future. I will also start revising more in all of my writings, both assigned and unassigned. Next week I look forward to starting the <a href="https://litmuse.net/collaboration-wdmwiki-afb46f80b4e0#.9o81epjpl">Wiki project</a> and collaborating with my classmates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f768d6fd4eaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Most Puzzling Angular 2 Errors]]></title>
            <link>https://medium.com/bitmaker-software/my-most-puzzling-angular-2-errors-181c1331435b?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/181c1331435b</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angular2]]></category>
            <category><![CDATA[angular-2-errors]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Tue, 28 Jun 2016 16:48:37 GMT</pubDate>
            <atom:updated>2016-06-28T16:48:37.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*piP--AwF2qtStWZ0-b5Exw.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/error-crash-problem-failure-63628/">Pixabay</a></figcaption></figure><p>Transitioning to a new library almost always presents a bit of a challenge. All the familiarity with the old framework is gone and a new one must be learned all over again, including error messages.</p><p>In the process of creating my first Angular 2 application, I came across several confusing errors. Here is a list of the most puzzling ones and their fixes.</p><h4>The Errors</h4><p><strong>Error: (SystemJS) SyntaxError: Invalid or unexpected token(…)</strong></p><p>I used a block comment to comment out an import statement at the top of a component file. Using a line comment instead fixed the error. See this <a href="https://github.com/systemjs/systemjs/issues/1020">Github issue</a> for more information.</p><p><strong>EXCEPTION: Error: Uncaught (in promise): Template parse errors: Can’t bind to ‘selector name’ since it isn’t a known native property</strong></p><p>When I imported a custom component, I forgot to add it to my main component’s directives array. Adding ‘directives: [customComponent]’ to the main component’s metadata <a href="http://stackoverflow.com/questions/34317044/angular2-exception-cant-bind-to-routerlink-since-it-isnt-a-known-native-pro">solved the problem</a>.</p><p><strong>GET http://localhost:8080/app/custom.component.ts.js 404 (Not Found)</strong></p><p>I got this error when I moved a custom component file into a different directory. My code editor automatically adjusted the custom component’s import path to reflect its new location. However, it also added ‘.ts’ to the end of the path. Removing the extension solved the problem. A similar issue related to moving component files can be found on <a href="https://github.com/johnpapa/angular2-tour-of-heroes/issues/58">Github</a>.</p><p><strong>Uncaught TypeError: Cannot read property ‘apply’ of undefined</strong></p><p>This error was caused by:</p><pre>this._renderer.invokeElementMethod(this.myElement, ‘focus’, []);</pre><p>In the Angular 2 <a href="https://github.com/angular/angular/blob/master/CHANGELOG.md">2.0.0-beta.1 release</a>, the <a href="https://angular.io/docs/ts/latest/api/core/index/Renderer-class.html">Renderer</a> was changed to accept a native element instead of an ElementRef. To fix the error, I changed the above code to:</p><pre>this._renderer.invokeElementMethod(this.myElement.nativeElement, ‘focus’, [])</pre><p>Know of any head-scratcher’s yourself? If you come across any, please mention in the comments or send it on <a href="https://twitter.com/jjzakula">twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=181c1331435b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitmaker-software/my-most-puzzling-angular-2-errors-181c1331435b">My Most Puzzling Angular 2 Errors</a> was originally published in <a href="https://medium.com/bitmaker-software">bitmaker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inline Editing with Angular2]]></title>
            <link>https://medium.com/front-end-weekly/inline-editing-with-angular2-58b43cc2aba?source=rss-5bec0bc6c1d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/58b43cc2aba</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angular2]]></category>
            <category><![CDATA[inline-editing]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Julianna Zakula]]></dc:creator>
            <pubDate>Tue, 28 Jun 2016 10:36:57 GMT</pubDate>
            <atom:updated>2016-06-28T10:36:57.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZHbI-cPlsBRCI6Jx91mOw.jpeg" /><figcaption>Image Credit: <a href="https://pixabay.com/en/monitor-programming-933392/">Pixabay</a></figcaption></figure><p>In this tutorial, we are going to create an Angular 2 inline edit component modeled after <a href="https://vitalets.github.io/angular-xeditable/">Angular-xeditable</a>, which was developed for Angular 1.</p><p>Currently, an <a href="https://github.com/valor-software/ng2-xeditable">Angular 2 xeditable</a> is under development, but in this project I am trying to achieve 3 things:</p><ul><li>Toggling an editable value between a text and form display</li><li>Canceling or reseting the editable value</li><li>Saving the editable value</li></ul><p><a href="https://plnkr.co/UykXDaVLxbWGXtkW9gAF">Here is the full working example.</a></p><h4>Example Implementation</h4><p>The inline edit component we are going to create will use the following structure.</p><pre>&lt;inline-edit [(ngModel)]=”editableText” (onSave)=”saveEditable(value)”&gt;&lt;/inline-edit&gt;</pre><h4>1. Create the Inline Edit Component</h4><p>First, we need to create an InlineEditComponent with the following content:</p><p><em>File: inline-edit.component.ts</em></p><pre>import {Component, Provider, forwardRef} from &#39;@angular/core&#39;;<br><br>import {ControlValueAccessor, NG_VALUE_ACCESSOR} from &quot;@angular/common&quot;;<br><br>const INLINE_EDIT_CONTROL_VALUE_ACCESSOR = new Provider(<br>    NG_VALUE_ACCESSOR, {<br>        useExisting: forwardRef(() =&gt; InlineEditComponent),<br>        multi: true<br>    });<br><br>@Component({<br>    selector: &#39;inline-edit&#39;,<br>    providers: [INLINE_EDIT_CONTROL_VALUE_ACCESSOR],<br>    styleUrls: [&#39;./inline-edit.component.css&#39;],<br>    templateUrl: &#39;./inline-edit.component.html&#39;<br>})<br>export class InlineEditComponent implements ControlValueAccessor, ngOnInit{<br>    <br>    constructor() {}<br>    <br>    // The internal data model<br>    private _value:string = &#39;&#39;;<br>    <br>    // Placeholders for the onChange and onTouch callbacks<br>    public onChange:any = Function.prototype;<br>    public onTouched:any = Function.prototype;<br><br>    // get accessor<br>    get value(): any { return this._value; };<br><br>    // set accessor including the onChange callback<br>    set value(v: any) {<br>        if (v !== this._value) {<br>            this._value = v;<br>            this.onChange(v);<br>        }<br>    }<br><br>    // Will update the internal data model with incoming values<br>    writeValue(value: any) {<br>        this._value = value;<br>    }<br><br>    // ControlValueAccessor interface<br>    public registerOnChange(fn:(_:any) =&gt; {}):void {this.onChange = fn;}<br><br>    // ControlValueAccessor interface<br>    public registerOnTouched(fn:() =&gt; {}):void {this.onTouched = fn;};<br><br>}</pre><h4>2. Define the Inline Edit View</h4><p>Now we need to create our inline edit view, which will display the editable value as text when the user is not editing and display it in a form control when the user is editing.</p><p><em>File: inline-edit.component.html</em></p><pre>&lt;div id=&quot;inlineEditWrapper&quot;&gt;<br><br>    &lt;!-- editable value --&gt;<br>    &lt;a&gt;{{ value }}&lt;/a&gt;<br><br>    &lt;!-- inline edit form --&gt;<br>    &lt;form  #inlineEditForm=&quot;ngForm&quot; class=&quot;inlineEditForm form-inline&quot;&gt;<br>        &lt;div class=&quot;form-group&quot;&gt;<br><br>            &lt;!-- inline edit control  --&gt;<br>           &lt;input #inlineEditControl class=&quot;form-control&quot; [(ngModel)]=&quot;value&quot;/&gt;<br><br>            &lt;!-- inline edit save and cancel buttons --&gt;<br>           &lt;span&gt;<br>                &lt;button type=&quot;submit&quot; class=&quot;btn btn-primary&quot;&gt;&lt;span class=&quot;glyphicon glyphicon-ok&quot;&gt;&lt;/span&gt;&lt;/button&gt;<br>                &lt;button class=&quot;btn btn-default&quot;&gt;&lt;span class=&quot;glyphicon glyphicon-remove&quot;&gt;&lt;/span&gt;&lt;/button&gt;<br>           &lt;/span&gt;<br><br>        &lt;/div&gt;<br>    &lt;/form&gt;<br>&lt;/div&gt;</pre><h4>3. Add Basic Styling</h4><p><em>File inline-edit.component.css</em></p><pre>a {<br> text-decoration: none;<br> color: #428bca;<br> border-bottom: dashed 1px #428bca;<br> cursor: pointer;<br> line-height: 2;<br> margin-right: 5px;<br> margin-left: 5px;<br>}</pre><pre>.inlineEditForm{<br> display: inline-block;<br> white-space: nowrap;<br> margin: 0;<br>}</pre><pre>#inlineEditWrapper{<br> display: inline-block;<br>}</pre><pre>.inlineEditForm input, select{<br> width: auto;<br> display: inline;<br>}</pre><pre>.editInvalid{<br> color: #a94442;<br> margin-bottom: 0;<br>}</pre><pre>.error{<br> border-color: #a94442;<br>}</pre><pre>[hidden] {<br> display: none;<br>}</pre><h4>4. Add Methods Logic</h4><p>We must now add the logic that will toggle between our editable value’s text and form displays. We’ll also add a cancel method that will allow the user to reset the editable value.</p><pre>import {Component, Output, Provider, forwardRef, EventEmitter, ElementRef, ViewChild, Renderer} from &#39;@angular/core&#39;;<br>import {ControlValueAccessor, NG_VALUE_ACCESSOR} from &quot;@angular/common&quot;;<br><br>const INLINE_EDIT_CONTROL_VALUE_ACCESSOR = new Provider(<br>    NG_VALUE_ACCESSOR, {<br>        useExisting: forwardRef(() =&gt; InlineEditComponent),<br>        multi: true<br>    });<br><br>@Component({<br>    selector: &#39;inline-edit&#39;,<br>    providers: [INLINE_EDIT_CONTROL_VALUE_ACCESSOR],<br>    styleUrls: [&#39;./inline-edit.component.css&#39;],<br>    templateUrl: &#39;./inline-edit.component.html&#39;<br>})<br>export class InlineEditComponent implements ControlValueAccessor, ngOnInit{<br><br>    // inline edit form control<br>    @ViewChild(&#39;inlineEditControl&#39;) inlineEditControl;<br>    @Output() public onSave:EventEmitter&lt;any&gt; = new EventEmitter();<br><br>    private _value:string = &#39;&#39;;<br>    private preValue:string = &#39;&#39;;<br>    private editing:boolean = false;<br>    <br>    public onChange:any = Function.prototype;<br>    public onTouched:any = Function.prototype;<br><br>    get value(): any { return this._value; };<br><br>    set value(v: any) {<br>        if (v !== this._value) {<br>            this._value = v;<br>            this.onChange(v);<br>        }<br>    }<br><br>    constructor(element: ElementRef, private _renderer:Renderer) {}<br><br>    writeValue(value: any) {<br>        this._value = value;<br>    }<br><br>    public registerOnChange(fn:(_:any) =&gt; {}):void {this.onChange = fn;}<br><br>    public registerOnTouched(fn:() =&gt; {}):void {this.onTouched = fn;};<br><br>    // Method to display the inline edit form and hide the &lt;a&gt; element<br>    edit(value){<br>        this.preValue = value;  // Store original value in case the form is cancelled<br>        this.editing = true;<br><br>        // Automatically focus input<br>        setTimeout( _ =&gt; this._renderer.invokeElementMethod(this.inlineEditControl.nativeElement, &#39;focus&#39;, []));<br>    }<br><br>    // Method to display the editable value as text and emit save event to host<br>    onSubmit(value){<br>        this.onSave.emit(value);<br>        this.editing = false;<br>    }<br><br>    // Method to reset the editable value<br>    cancel(value:any){<br>        this._value = this.preValue;<br>        this.editing = false;<br>    }<br><br>}</pre><h4>5. Update Inline Edit View</h4><p>Now it’s time to add to our view, the functionality provided by our methods in step 4.</p><pre>&lt;div id=&quot;inlineEditWrapper&quot;&gt;<br><br>    &lt;!-- editable value --&gt;<br>    &lt;a (click)=&quot;edit(value)&quot; [hidden]=&quot;editing&quot;&gt;{{ value }}&lt;/a&gt;<br><br>    &lt;!-- inline edit form --&gt;<br>    &lt;form  #inlineEditForm=&quot;ngForm&quot; class=&quot;inlineEditForm form-inline&quot; (ngSubmit)=&quot;onSubmit(value)&quot; [hidden]=&quot;!editing&quot;&gt;<br>        &lt;div class=&quot;form-group&quot;&gt;<br><br>            &lt;!-- inline edit control  --&gt;<br>           &lt;input #inlineEditControl class=&quot;form-control&quot; [(ngModel)]=&quot;value&quot;/&gt;<br><br>            &lt;!-- inline edit save and cancel buttons --&gt;<br>           &lt;span&gt;<br>                &lt;button type=&quot;submit&quot; class=&quot;btn btn-primary&quot;&gt;&lt;span class=&quot;glyphicon glyphicon-ok&quot;&gt;&lt;/span&gt;&lt;/button&gt;<br>                &lt;button class=&quot;btn btn-default&quot; (click)=&quot;cancel(value)&quot;&gt;&lt;span class=&quot;glyphicon glyphicon-remove&quot;&gt;&lt;/span&gt;&lt;/button&gt;<br>           &lt;/span&gt;<br><br>        &lt;/div&gt;<br>    &lt;/form&gt;</pre><pre>&lt;/div&gt;</pre><h4>Next Steps</h4><p>The basic structure of our inline edit component is now complete and implements the minimal features of inline editing:</p><ol><li>Toggling in and out of edit mode</li><li>Saving</li><li>Canceling</li></ol><p>In one of my next blog posts, we will add some more advanced features to support validation, multiple types of form controls, and form control attributes such as required and placeholder.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58b43cc2aba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/front-end-weekly/inline-editing-with-angular2-58b43cc2aba">Inline Editing with Angular2</a> was originally published in <a href="https://medium.com/front-end-weekly">Frontend Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>