Saturday, March 31, 2012
Individual Tutorial & Reflection - Rhetorical Analysis of Moodle
Moodle.org is "a free, open-source PHP web application for producing modular internet-based courses that support a modern social social constructionist pedagogy." According to Moodle, the site's principles of development are based upon four concepts: constructivism, constructionism, social constructivism, and "connected and separate." These concepts can work together to provide a dynamic, student-centered, interactive learning experience in which students themselves can essentially become teachers, while the instructor "change[s] from being 'the source of knowledge' to... and influencer and role model of class culture (Moodle)."
The philosophy held by the developers of this site is in line with my own teaching philosophy, which is what attracts me to this site. Additionally, this site is one that I would like to start using in the near future as an online tool to support my face-to-face ESL classes.
The authors of the site are careful to establish credibility and authority by providing an in-depth explanation of its Virtual Learning Environment (VLE) on their "About" subpage, which is easily located on the navigational toolbar at the top of the site. This subpage provides a description of the site's features and why people like it; documents describing the terms of use, philosophy, pedagogy, basic structure, and key terms; statistics of its use; and a demonstration site.
The intended audience for this site is primarily teachers and students. The developers clearly state their philosophical and pedagogical values in order to appeal to teachers like me who may think along the same lines.
The developers achieve contrast by taking advantage of juxtaposing the white space on the page with various shades of orange. There is an orange border around the edges of the page that is solid toward the top of the page, and then fades through different degrees of transparency as you move toward the middle and bottom of the page until it blends into the white space altogether. The authors of the site encourage you to click on the subpages by providing clickable boxes, most of which also have a graphic and are filled in with a relatively transparent, light orange color.Repetition is another nice feature of the site, and I would use its navigation features as an example of that, because one can move easily through the different subpages by clicking on the various toolbar buttons at the top of the home page, the menu on the right-hand side, or a set of large buttons on the main page. Sub-pages include the About section, which I have already explained; a news page with announcements about the application; a support page with information about documentation, forums, books and manuals, and commercial services; a community page with information about forums, events, registered sites, connected sites, Moodle jobs, recent participants, donations, and the Moodle shop; a development page with information about the developers, documentation, a tracker, and open source code; and a downloads page where you can find standard packages and language packs.
Another example of repetition is achieved is through the manner in which a great majority of the headings are designed. The headings and subheadings are always in a large, bold font, with an long line underneath them. This allows the users to clearly see when a section on a page begins and ends. Additionally, the site consistently uses bullets with links, and alignment is almost always left justified.
Items are grouped together on the page in a logical way to achieve proximity. This can be seen on the front page in the arrangement of the navigational buttons:
The format of this site seems to work well for its intended purpose, and the only complaint that I might have is that it's a little difficult to figure out how to actually get started with setting up a Moodle site. That information seems to get buried under all of the "this is who we are, and this is what Moodle can do" type of information.
With just a small amount of searching, however, it is easy to locate a page that will help you to get started. In the near future, I hope to start playing around with the page (or, as Shelley might say, "I'll bang my head against it...") to see how I can incorporate it into my teaching toolbox. Analyzing the site itself was a great way to get started, because it allowed me to familiarize myself with the basic components.
Saturday, March 17, 2012
Reflection on Four ENGL 866 Blog Posts
This week, I reviewed and replied to the following four blog posts.
Diane Cook - Reflection, reflections, reflections, never-ending-reflections…
I really enjoyed Diane's post because it was really a one-stop-shop of the reflections from this week. I was also drawn to it because she reviewed two of my posts (one from my blog, plus the canonical wiki page) and provide some great feedback and insights. I was also relieved to see that someone else was stressing a bit about work load and lack of hours in the day. I'm not complaining, but I have to admit I have my hands in a lot of pots right now so time management has been a bit of a challenge for me lately. Finally, I enjoyed reading about Diane's adventures in learning JavaScript. I can relate to the feeling that the tutorials I'm choosing aren't fitting my needs. I haven't checked out any of the tutorials on Lynda or Educator.com, so I think I may do some poking around on those sites for my next set of tutorials.
2) Jennifer Buckner - Rhetorical Analysis, VW Beetle Site in HTML5
Jennifer wrote a really fun blog post about the new VW Beetle Site, which uses HTML5. The site is really cool, and I would encourage anyone to check it out. I liked Jennifer's post because it was informative and clear. It was helpful to see how she conducted her rhetorical analysis. The only thing I might do slightly differently would be to try and connect some of the concepts I have learned in tutorials with features I see in my text. Then again, maybe that's not appropriate for a rhetorical analysis...
3) Amanda Lynn David - InDesign Tutorial Part I
I was drawn to Amanda's post because she is working with an application I have never heard of before - InDesign. Since it was completely new to me, I went ahead and watched the first intro tutorial that Amanda posted, and I realized the InDesign is like Microsoft Publisher on steroids. :) Since I knew nothing about her application, I ended up responding to her posts with more questions than comments. I look forward to seeing what she does with the software for her final project.
4) Eric Sentell - Reflection on the Peer Review Process
The last post I reviewed was written by Eric, and it was a reflection on the feedback he received on his Canonical Text Wiki Page. I felt bad for Eric because he received some comments he did not expect/understand, and I hadn't reviewed the wiki by the time he had written the post, so he didn't have much to go on. Anyway, the main thing I learned from his post was that we really do rely on each other for timely, thoughtful, detailed and accurate feedback, and when we don't get the kind of feedback we are looking for, it can be very frustrating. Totally understandable!
Diane Cook - Reflection, reflections, reflections, never-ending-reflections…
I really enjoyed Diane's post because it was really a one-stop-shop of the reflections from this week. I was also drawn to it because she reviewed two of my posts (one from my blog, plus the canonical wiki page) and provide some great feedback and insights. I was also relieved to see that someone else was stressing a bit about work load and lack of hours in the day. I'm not complaining, but I have to admit I have my hands in a lot of pots right now so time management has been a bit of a challenge for me lately. Finally, I enjoyed reading about Diane's adventures in learning JavaScript. I can relate to the feeling that the tutorials I'm choosing aren't fitting my needs. I haven't checked out any of the tutorials on Lynda or Educator.com, so I think I may do some poking around on those sites for my next set of tutorials.
2) Jennifer Buckner - Rhetorical Analysis, VW Beetle Site in HTML5
Jennifer wrote a really fun blog post about the new VW Beetle Site, which uses HTML5. The site is really cool, and I would encourage anyone to check it out. I liked Jennifer's post because it was informative and clear. It was helpful to see how she conducted her rhetorical analysis. The only thing I might do slightly differently would be to try and connect some of the concepts I have learned in tutorials with features I see in my text. Then again, maybe that's not appropriate for a rhetorical analysis...
3) Amanda Lynn David - InDesign Tutorial Part I
I was drawn to Amanda's post because she is working with an application I have never heard of before - InDesign. Since it was completely new to me, I went ahead and watched the first intro tutorial that Amanda posted, and I realized the InDesign is like Microsoft Publisher on steroids. :) Since I knew nothing about her application, I ended up responding to her posts with more questions than comments. I look forward to seeing what she does with the software for her final project.
4) Eric Sentell - Reflection on the Peer Review Process
The last post I reviewed was written by Eric, and it was a reflection on the feedback he received on his Canonical Text Wiki Page. I felt bad for Eric because he received some comments he did not expect/understand, and I hadn't reviewed the wiki by the time he had written the post, so he didn't have much to go on. Anyway, the main thing I learned from his post was that we really do rely on each other for timely, thoughtful, detailed and accurate feedback, and when we don't get the kind of feedback we are looking for, it can be very frustrating. Totally understandable!
Friday, March 16, 2012
Reflection - Canonical Text Wiki Page Peer Review
I reviewed the following two Canonical Text Wiki Pages:Medium is the Massage +
Simulacra & Simulation & The Illusion of the End
The main thing I learned from reading and replying to my classmates' drafts was that the format, structure, and visual design elements of a wiki page are essential when there is a massive amount of complex information that must be presented in a clear and logical way. If used correctly, design elements (following CRAP principles) and engaging format options (embedded objects, links, polls) are more than just aesthetically pleasing, but they actually help the reader move through and digest large amounts of content.
I was excited to see how others were able to connect their texts to the 12 key concepts, because this is one of the main things I have left to do on my own draft. I was especially impressed by the graphic representation developed by the group who read the McLuhan text. I would like to do something similar for how concepts from the first, second, and third waves of cybernetics connect to the 12 key concepts.
I really liked the idea of having a hypertext table of contents to link to different sections of the wiki page. I also liked the idea of having subpages - I'll ask Cheri what she thinks about having subpages for the three waves of cybernetics. If we do that, we can keep the general format of our wiki, but maybe we could add a sidebar for the table of contents. Also, this would mitigate the issue of the columns being different lengths.
Jennifer was the first to comment on our draft. She mentioned that we need to include the information about "how [it's] used/useful to the production process," which we plan to have ready for the final draft. I agree with her critique that we need to fix alignment of subheadings.
Eric had some great comments as well. I liked his suggestion to incorporate the key concepts by showing how the concepts "change humans into post-humans." For example, "how does the PC interface shape cognition, archiving, pattern-recognizing and -creating, perspective, etc." I thought this was a great suggestion. He also said the text was a bit too detailed, and he pointed out the summary sections. Maybe on the main page we could have the brief summary and then link to a sub page for the more in-depth summary by using a "Read more..." type of hyperlink. I also really appreciated his edits! I would like to italicize all quotes as he suggested - I had done that in my sections from the beginning so maybe we can carry that through to the section Cheri prepared as well. Also, he pointed out how we could provide some additional definitions, explain the Macy Conferences, and add some alt-text on graphics. His comments were so helpful. I hope to incorporate some if not all into the final draft.
Amanda made the suggestion to explain the drawings - I'm assuming she meant Hayley's Map of Cybernetics and the graphic in the section called "Mapping the Framework of the Posthuman." I agree that some prose to accompany those images would be helpful.
Diane left a comment as well, and also mentioned some additional terms we could define, and she thought we could mention information about some of what I might call existential questions related to posthumanism.
This exercise was extremely beneficial - it was great to see the work of others, and also to have multiple sets of eyes provide constructive criticism on our work as well. I look forward to cleaning up our final draft and presenting on Monday! Can't wait to hear the other presentations as well...
Monday, February 27, 2012
Reading, Thinking, & Reflecting Post - 2/27
Last week, we were not required to post about the readings from our canonical text, so this week I will be posting about my reflections from the last 2/3 of the text. I annotated the book quite heavily, so I will have to do my best in narrowing down the point of interest that I would like to comment on for the purposes of this blog post.
I suppose I will begin by providing a brief summary of each chapter in How We Became Post-Human. Chapter Four continued with the discussion of the first wave of cybernetics by exploring Norbert Wiener's theories with regard to the relationship between cybernetics and liberal humanism. Chapter Five connected the theories of the first wave of cybernetics with a piece of literature, which was Limbo by Bernard Wolfe. Chapter Six introduced the second wave of cybernetics, which is defined by the shift to the concept of reflexivity, and discussed the theories of Humberto Maturana and Fransicso Varela extensively. Chapter Seven then connected the theories of the second wave of evolution to a piece of literature, which was Do Androids Dream of Electric Sheep by Philip K. Dick. Chapter Eight moved into the third wave of cybernetics, which is characterized by issues regarding the materiality of informatics and the need for embodiment of information (or not). Chapter Nine continued with the third wave of cybernetics and went into a detailed discussion of Artificial Life that was framed around the debate of embodiment vs. disembodiment. Chapter Ten referred back to literature by discussing text such as Blood Music by Greg Bear, Terminal Games by Cole Perriman, Galatea 2.2 by Richard Powers, and Snow Crash by Neil Stephenson. Chapter Eleven provided an overal summary and conclusion for the text.
This book was an enjoyable read, albeit dense with theory at times, and I really liked how Hayles tied literature in as a way to expand on the theories - it made for a great change of pace throughout this text, and reading about the fictional worlds created by each author really drove the points of each theory home. I was especially excited to read the in-depth theoretical analysis of DADoES. Thanks to How We Became Posthuman, my reading list has expanded considerably.
Since the text was basically broken into three sections, I will do the same for this post...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The First Wave of Cybernetics
"Analogy is not merely an ornament of language but is a powerful conceptual mode that constitutes meaning through relation... When analogy is used to constitute agents in cybernetic discourse, it makes an end run around questions of essence, for objects are constructed through their relations to other objects." (pg. 91)
I really enjoyed this quote about analogy, and it reminds me a lot of what we learned about in sociolinguistics when we talked about prototypical schema clouds in the field of cognitive linguistics. Essentially, the theory in linguistics, based on work by Piaget, posits that people form "schema clouds" of meaning that people assign complex meanings to words based on associations they make with a prototypical concept of that word based on their prior experiences with it. I was able to make a further connection with this theory when Hayles was discussing Wiener's theory further by making a connection between the key concepts of pattern and perception by stating that "perception does not reflect reality directly but rather relies on transformations that preserve a pattern across multiple sensory modalities and neural interfaces." (pg 98)
"Analogy is thus constituted as a universal exchange system that allows data to move across boundaries. It is the lingua franca of a world (re)constructed through relation rather than grasped in essence." (pg. 98)
 |
| Schema cloud for the word "egg" |
The Second Wave of Cybernetics
The discussion of the second wave of cybernetics was introducted in Chapter Six with reference to a classic article called "What the Frog's Eye Tells the Frog's Brain" by Lettvin, et. al. One of the authors of that paper was Humberto Maturana. He and Francisco Varela worked together extensively to determine the role of the observer, and they believed that observers "create [preexisting systems] through the very act of observing them."
 |
| "A frog's visual system does not so much represent reality as construct it." (pg. 131) |
Again, perception was a key concept that I could connect to the discussion, because the theorists argue that the existence of reality is directly related to self-organized beings perceive reality (pg. 133). In addition to self-organization, which was defined as "living systems [operating] within the boundaries of an organization that closes in on itself and leaves the world on the outside (pg. 136)." Autopoiesis was another major concept tossed around in this chapter, which is defined as "the circularity of [a being's] organization that makes a living system a unit of interactions."
According to Maturana, a living system can be defined through autopoietic self-organization. There is a clear difference in this way of thinking as compared to the that of the first wave of cybernetics. The first wave of cybernetics is concerned with the liberal humanist "notion of possessive individualism, [which is] the idea that subjects are individuals first and foremost because they own themselves (pg. 145)," whereas autopioetic theory from the second wave of cybernetics states that "living systems are living because they instantiate organizational closure." It is interesting because before reading this book, I could never think of a machine as "living," but once I started reading about different concepts and theories about what it actually means to "be alive," my mind started to open.
Honestly, I feel like this course is opening my mind quite significantly in that regard. When I was an undergraduate, I majored in Wildlife Biology. In my animal behavior and communication classes, as well as in classes dealing with evolutionary biology, we were basically told that the basic purpose of the life is to survive and reproduce. Maturana and Varela's theory of autopoeisis bumps up against the theory of biological evolution, so it was a little difficult for me to swallow at first, but I found some interesting similarities as I read on, which I will discuss further when I move into the third wave of cybernetics.
The Third Wave of Cybernetics
The third wave of cybernetics is focused on the notion that "materiality is secondary to the logical structures it encodes." In other words, the third wave is concerned with the issue of "embodiment." "
"In contrast to the body, embodiment is contextual enmeshed within the specifics of place, time, physiology, and culture, which together compose enactment, ...whereas the body is an idealized form that gestures toward a Platonic reality."
Chapter Nine spoke in great detail about Artificial Life. Artificial Life is "the study of man-made systems that exhibit behaviors characteristic of natural living systems... It is concerned with the analysis of living organisms by attempting to synthesize life-like behaviors within computers and other artificial media (pg 232)." Artificial life is not to be confused with artificial intelligence. Artificial life "sees cognition as the operation of nervous systems," while artificial intelligence "envisions cognition as the operation of logic (pg 238)." Typically, artificial life "programs are considered to be simulations (pg 234)," and it can be "divided into three research fronts: wetware, hardware, and software (pg 225)."
Again, as a biogist, there was an interesting point that stuck out to me. On pg. 226, there was an explanation of how DNA can be compared to binary code. I found an interesting article called, "DNA seen through the eye of a coder -or- If you are a hammer, everything looks like a nail," which plays with the analogy of DNA as a code (or vice versa).
There are so many points that I did not cover in my post - I barely scratched the surface. I'm hoping to revisit more of the theories and theorists related to the posthuman as I work on the canonical text wiki page with Cheri. For now, I will close with a of video I found on YouTube that are related to cybernetics. It is kind of funny because of the German audio and post-apocalyptic soundstrack...
Hailes, N. Katherine. How We Became Post-Human: Virtual Bodies in Cybernetics, Literature, and Informatics. Chicago, Illinois: The University of Chicago Press, 1999. Print.
Saturday, February 25, 2012
Individual Tutorial & Reflection #2 - PHP
This week, I completed two different tutorials, so this reflection blog will contain two distinct sections.
PART I - Finishing the PHP Guide from PHP Learn It!
Last week, I completed 9 out of the 19 steps in the PHP Guide from PHP Learn It! Lean PHP by Examples. This week, I began with PHP Arrays.
PHP Arrays...
"An array is a mean[s] to store [a] collection of values in a single variable."
The two types of arrays dealt with in PHP are numeric arrays and associative arrays. Elements in numeric arrays are stored with a numeric ID key. "When we want to store elements in array with some meaningful association other than numbers, we use associative array."
Multidimensional arrays are used when we want to "associate multiple keys to an element."
PHP Loops...
In PHP, loops are used to repeat a code for as many times that you want without having to rewrite it. There are three types of loops used in PHP programming: foreach loop, for loop, and while loop.
"Foreach loop is most often used to print elements in a array...We can use foreach loop to print the keys and the values from a multidimensional array."
Example:
"A for loop is used when we want to execute a block of code for certain number of times."
"For loop has three statements.
PHP functions can also return a value like this:
PHP Comments...
"Comments are used to describe your code." The two ways to write comments are single line comments and multiple line comments. Single line comments are written with forward slashes "//", and multiple line comments start with "/*" and end with "*/". Because PHP codes can get complicated, it is important to write comments. Once you write a lot of code, you will need some way to remember what your code does so you can use it again later.
PHP E-mail...
In this section of the PHP guide, codes for the mail function were provided and explained. Examples of how to send both plain text and HTML emails were given.
PHP Date...
With the date function, there are two "arguments": format and timestamp. The format must always be specified so the time or date will display in the desired output, but the timestamp is optional. A complete list of day/time formats are available here at http://www.php.net.
PHP Cookies...
A "cookie is a small flat file which sits on user’s computer. Each time that user requests a page or goes to a webpage, all cookie information is sent too. This is used to identify who you are."
This is an explanation of the cookie function (creating a cookie), which I have copied directly from the guide:
PHP Sessions...
The last section of the guide explained PHP sessions, which are "used to store information which can be used through-out the application for the entire time the user is logged in or running the application." The guide walked me through how to start a session, store information in the session, retrieve stored information, and delete session information.
PART II - PHP 101: PHP For the Absolute Beginner
This week, I also spent time working on a tutorial I found on a website called Zend Developer Zone: Advancing the art of PHP. The tutorial was written by Vikram Vaswani and seemed to have positive reviews, according to the comment thread at the bottom of the tutorial's home page.
This particular tutorial involved quite a bit of reading, but it was extremely thorough and well-written. Now that I have been reading about PHP for the past several weeks, some of the information was review. I have to admit, it felt nice to find myself nodding my head while reading through the tutorial because I was actually recognizing some of the terms and concepts needed for having a basic understanding of PHP.
Part 1 of the tutorial gave a general overview of what PHP is and how it works. Again, this was review, and I was thrilled that it all made sense to me. Just like in the last tutorial I completed, this tutorial provided a definition for variables, since they are so important for PHP and any other programming language. There was also was an explanation of how the "=" sign is used to assign values to variables. The basic types of variables supported by PHP are Boolean, integer, floating point, and string. Finally, this part of the tutorial describes string operators and concatenation operators, which I had also learned about in the first tutorial I completed.
Part 2 of the tutorial was called "Calling All Operators." This part explained how PHP can "automatically receive user input from a Web form and convert it into PHP variables." I really liked how this part of the tutorial was laid out because he gave the php code, then he pointed out the most critical line of the code containing the php function, which he later provided the html script for in order to explain the function in great detail. After he was finished describing the basics of forms, he then talked about how to add "intelligence" to scripts by constructing conditional statements. (Side note: I thought "intelligence" was an interesting choice of word.)
Example
The next section moved from comparison operators on to logical operators.
I went ahead and tried the example code for the four logical operators: logical
PART I - Finishing the PHP Guide from PHP Learn It!
Last week, I completed 9 out of the 19 steps in the PHP Guide from PHP Learn It! Lean PHP by Examples. This week, I began with PHP Arrays.
PHP Arrays...
"An array is a mean[s] to store [a] collection of values in a single variable."
The two types of arrays dealt with in PHP are numeric arrays and associative arrays. Elements in numeric arrays are stored with a numeric ID key. "When we want to store elements in array with some meaningful association other than numbers, we use associative array."
Multidimensional arrays are used when we want to "associate multiple keys to an element."
PHP Loops...
In PHP, loops are used to repeat a code for as many times that you want without having to rewrite it. There are three types of loops used in PHP programming: foreach loop, for loop, and while loop.
"Foreach loop is most often used to print elements in a array...We can use foreach loop to print the keys and the values from a multidimensional array."
Example:
"A for loop is used when we want to execute a block of code for certain number of times."
"For loop has three statements.
- In the first statement, we initialize a counter variable to an number value.
- In the second statement, we set a condition (a max/min number value) until the counter is reached.
- In the third statement, we set a value by how much we want the counter variable to incremented by."
"The while loop is used to execute a block of code for certain number of times until the condition in the while evaluate to true."
A break statement can be used to "break the loop when a certain condition is true."
PHP Functions...
"A function is a group of instructions to perform a task....A function is a block of code with a name which can be used in our code whenever we need it."
"A typical function has three components to it
- Starts with the word function
- Has a function name followed by parentheses (). A function name can only start with a letter or a underscore.
- The code block in the function always goes inside curly brackets."
PHP functions can also return a value like this:
PHP Comments...
"Comments are used to describe your code." The two ways to write comments are single line comments and multiple line comments. Single line comments are written with forward slashes "//", and multiple line comments start with "/*" and end with "*/". Because PHP codes can get complicated, it is important to write comments. Once you write a lot of code, you will need some way to remember what your code does so you can use it again later.
PHP E-mail...
In this section of the PHP guide, codes for the mail function were provided and explained. Examples of how to send both plain text and HTML emails were given.
PHP Date...
With the date function, there are two "arguments": format and timestamp. The format must always be specified so the time or date will display in the desired output, but the timestamp is optional. A complete list of day/time formats are available here at http://www.php.net.
PHP Cookies...
A "cookie is a small flat file which sits on user’s computer. Each time that user requests a page or goes to a webpage, all cookie information is sent too. This is used to identify who you are."
This is an explanation of the cookie function (creating a cookie), which I have copied directly from the guide:
setcookie($name, $value, $expire, $path, $domain, $secure)
- $name - name of the cookie. Example: "username"
- $value- value of the cookie. Example: "john"
- $expire- time (in UNIX timestamp) when the cookie will expire. Example: time()+"3600". Cookie is set to expire after one hour.
- $path- path on the server where cookie will be available. For example, if the path is set to "/", the cookie will be available through out the whole site. If the cookie is set to say "/news/", the cookie will only be available under /news/ and all its sub-directories. If no path is given, cookie in created under the current directory.
- $domain- domain where cookie will be available. Instead of path you can use domain settings. For example, if the domian is set to ".yourdomian.com", the cookie will be available within the domain nd all its sub-domains, example news.yourdomain.com. If the cookie is set say "www.yourdomian.com" the cookie will be available under all www sub-domains, example " www.yourdomian.com/news"
- $secure - true if cookie is being set over a secure "https" server, false otherwise, Default value is false.
PHP Sessions...
The last section of the guide explained PHP sessions, which are "used to store information which can be used through-out the application for the entire time the user is logged in or running the application." The guide walked me through how to start a session, store information in the session, retrieve stored information, and delete session information.
PART II - PHP 101: PHP For the Absolute Beginner
This week, I also spent time working on a tutorial I found on a website called Zend Developer Zone: Advancing the art of PHP. The tutorial was written by Vikram Vaswani and seemed to have positive reviews, according to the comment thread at the bottom of the tutorial's home page.
This particular tutorial involved quite a bit of reading, but it was extremely thorough and well-written. Now that I have been reading about PHP for the past several weeks, some of the information was review. I have to admit, it felt nice to find myself nodding my head while reading through the tutorial because I was actually recognizing some of the terms and concepts needed for having a basic understanding of PHP.
Part 1 of the tutorial gave a general overview of what PHP is and how it works. Again, this was review, and I was thrilled that it all made sense to me. Just like in the last tutorial I completed, this tutorial provided a definition for variables, since they are so important for PHP and any other programming language. There was also was an explanation of how the "=" sign is used to assign values to variables. The basic types of variables supported by PHP are Boolean, integer, floating point, and string. Finally, this part of the tutorial describes string operators and concatenation operators, which I had also learned about in the first tutorial I completed.
Part 2 of the tutorial was called "Calling All Operators." This part explained how PHP can "automatically receive user input from a Web form and convert it into PHP variables." I really liked how this part of the tutorial was laid out because he gave the php code, then he pointed out the most critical line of the code containing the php function, which he later provided the html script for in order to explain the function in great detail. After he was finished describing the basics of forms, he then talked about how to add "intelligence" to scripts by constructing conditional statements. (Side note: I thought "intelligence" was an interesting choice of word.)
Example
The next section moved from comparison operators on to logical operators.
I went ahead and tried the example code for the four logical operators: logical
AND, logical OR, logical XOR and logical NOT.
The tutorial went on to explain conditional statements, if-else statements, and if-elseif-else statements. I will continue with this comprehensive tutorial next week - I really like the structure and the explanations are phenomenal yet easy to understand.Bonus:My friend Jay in the computer science department sent me one of his students, who is willing to help me brainstorm some ideas for my final project for this course. We will be meeting on Tuesday for lunch. I'm really looking forward to it! In the meantime, he gave me this code to play with...<?php
$array1 = array("scott", "laura", "php", "work");
//that's an array
//to access different items you start at 0 and count up
echo $array1[0]."<br/>";
//this will print the word "scott"
//notice how you access it through 0 not 1
echo $array1[2]."<br/>";
//this will print the work "php"
//the <br/> is html for line break
//notice how this is accessed through 2 and not 3
$array2 = array(array("me", "you"), array(3, 5));
//this is a nested array and allows you to have something that resembles a table
echo $array2[0][0]."<br/>";
//prints "me"
echo $array2[1][0]."<br/>";
//prints 3
?>... so I tried it out!
I was so happy to have learned about comments today, because being able to identify those within the code really helped me to understand the function of the script. I was also happy he showed me this code, because now I really see how you can retrieve information stored in an array.I'm really starting to understand PHP, and I'm looking forward to next week when I can continue the new tutorial and report on my meeting with Scott.Connecting Social Media with Indigenous Language Maintenance...
From the article called "Social Media Promotes Literacy Within Threatened Languages"....
"We started our website — http://www.ojibwe.net— in 2006," she says, with the goal to encourage proficiency in future generations, and to archive contributions from fluent elders. She expounds, "We save all the posts of fluent elders, and archive them at the Bentley, adding to the storehouse of information about this endangered language."
Their website posts audio files, songs, stories, spoken lessons and examples of the language. The social media sites are all accessible from the website in efforts to encourage the conversation. More than 9,000 people visited the site in 2011, and according to Ms. Noori, about 400 people in Michigan are now using the language.
Read more: http://technorati.com/social-media/article/social-media-promotes-literacy-within-threatened/#ixzz1nP3nRmqO
KEY CONCEPT: ARCHIVE
"We started our website — http://www.ojibwe.net— in 2006," she says, with the goal to encourage proficiency in future generations, and to archive contributions from fluent elders. She expounds, "We save all the posts of fluent elders, and archive them at the Bentley, adding to the storehouse of information about this endangered language."
Their website posts audio files, songs, stories, spoken lessons and examples of the language. The social media sites are all accessible from the website in efforts to encourage the conversation. More than 9,000 people visited the site in 2011, and according to Ms. Noori, about 400 people in Michigan are now using the language.
Read more: http://technorati.com/social-media/article/social-media-promotes-literacy-within-threatened/#ixzz1nP3nRmqO
KEY CONCEPT: ARCHIVE
Subscribe to:
Posts (Atom)