Off the map, and over the edge. A Rationale

The online exhibition appealed to me because it allowed me correlate information and image on something that I was both knowledgeable and passionate about. The topic of focus that I chose to pursue was the Sims community, and more specifically the “economy” that exists within the community.

I chose to pursue the sims as my central topic because of its prominent online following and prominent network, information is both accessible and easily correlated. The community is something that, although never directly involved in, I am also knowledgeable about beyond the basis of downloading and uploading content. Furthermore the monetization of creator content and the outright war that surrounds it is both a topical (within the community) and a fascinating concept that I felt was capable of being presented in the form of an online ‘library’ or ‘gallery.’

In terms of presentation the website appealed to me the most, over a blog or something of a similar format, because of html’s full creative capabilities. I felt that a website and the process of html would also allow me to explore this semester’s teachings without any restriction or constraint. It was also a the format I felt most appropriate for my work, due to the fact that a blog is a representation of personal opinion while I wanted to take a more omniscient and open sided approach to the topic.

Html and CSS acted as the main foundations and technical process in the construction of my project. Coding was completed by hand through the use of the text editor PS Pad , whilst graphics were created with Adobe Photoshop CS2. To me the general aesthetic of my website was important because aesthetic plays an incredibly large role within the sims community. Content is created to acquire a specific style in game, the appeal of creators largely lie in the aesthetic they present and the generally sim-based websites are largely graphic based.

The bare visual of the website, that is the black “L” shaped sidebar to footer, was creating with CSS styling. The html ‘Iframe’ or inline frame, also played a prominent part in the success of my layout. Basically the inline frame allows linked content to appear within a set box. If you observe my website, the main content box is an inline frame, there is also an inline frame placed within the sidebar.

Tutorials such as: this were referenced during the construction of my layout. They were mainly utilized as a reference to code or means of research into maximizing my own use of the code, such as finding an easier way to achieve a specific effect. A specific example of this is the ‘float’ element for creating separate ‘blocks’ and co-existent, as opposed to the use of a html table. Class and ID were also a prominant feature of my layout.

Another part of my technical process was interlinking the wider web, or network with my page through the use of APIS and yahoo pipes. Flickr (a slide show created with this resource) was specifically utilized to provide my website with a broader and unbiased or unedited “gallery” function. Feed Informer was also used with my process to manage feeds independently and put them into html code. It was important to establish a dynamic link into to the sims community to demonstrate both the use of the blog as a host for content and the nature of the internet network. I believed that this could best be established with a several of my favourite creators RSS feeds.

In a cultural context, online communities are a prominent part of the internet culture. The online community exists to support an interest or hobby, whether that be videogames, films, or a figure of popular culture. Within the context of the sims community, the game and its creative tools are just another method of self expression or art. The culture that surrounds the sims community is based on creative freedoms, which is ultimately not endorsed by paysites. The simmers thus have taken on an anti-paysite attitude. Paysites Must be Destroyed(PMBD) is the central hub for paysite protest to occur, it is at the very centre of the community “economy” because it ultimately attempts to abolish it.

My site is ultimately a tamer and more passive observation of the concept, little sites explore the issue of paysites and free sites with a overall view and without assuming a side. I responded to the cultural community ideal that “paysites” are bad through the use of a website to correlate my information. Websites, unlike the forum are not places of direct interaction. I found with the forum, direct interaction disallows one to establish an objective opinion on the matter. This is particularly dominate with PMBD who only promote the destruction of paysites (and thus believe all paysite content to be rubbish), and flame any member with a dissimilar point of view.

As I previously stated, the culture of the sims community is largely art based. Thus the design patterns that exist within it are largely aesthetic. One design pattern that I incorporated into my layout was the large, and colourful banner. Within the community a large banner is used in forums, blogs and sites as a means of promoting the content that the site contains. Banners are largely colourful (though that varies with the theme of the website, or content that the website offers) and assume a decent portion of the page. This can be observed both Here and Here.

I constructed my layout to also follow some of the universal web patterns in website design.

This included:
> The logo of the site linking back to the home page.
> The use of a banner as the header for the page.
> The side bar and side bar menu being situated on the left hand side of the page.
> A footer, and footer links.
> A copyright notice in the footer
> A main scrolling, content frame.

Overall and in conclusion, a community cannot exist without the network that links it. We are capable of gaining so much more through what the interconnectivity of the web, such as APIs. Our webbing experience is enhanced by such things, as they allow us to learn more with a single click. I have learnt that websites require patience, html requires even more and without the network, the sims would be a heck of a lot more boring to play.

Chocolate, did you say chocolate...? CHOCOLATEEEE, CHOCOLATTTTEEEEE

This is the closest thing that I can find to a CSS Frame tutorial. The more I look into this method of layout, the more perpetually complex it gets. We’ll see how far I get before I abandon it all for a blog.

I’m stress eating myself into oblivion right now. OM NOM NOM.

Edit: HOLY MOTHER OF GOD: This may be the answer: GOD LIKE TUTORIAL. It would mean abandoning the concept of CSS Frames, but the basic layout that they manage to build is incredibly nifty.

So, the realization has occurred to me that the topic of the Sims community is once again, too incredibly broad to cover for one assessment. Also, there’s that whole niggling limited time thing, you know, whatever.

We need to get into specifics. I have several possibilities in mind.

> The forums: the content they provide, and the people they harbor. Forum versus forum.

> A gallery of quality content. (That’s incredibly subjective, and also, plenty of these sites exist)

> Pay custom content versus free custom content, the pirates versus TSR.

>The sims and art, uses for the game outside of gaming. (The storytelling, photo, and video making aspect.)

>The sims economy. Paysites and the like. The Pay/Free war.

I’m not incredibly worried about the specifics of the content at this very moment, right now, sitting here, typing this. Mostly because I’m more concerned with actually constructing html structure in the first place. There’s no use in having content without somewhere to actually put it.

To frame or not to frame:

Back when I was young and naive, the iframe was, in my mind, the only possible method of constructing a website layout. So naturally I considered using the frames format for my layout in this assessment piece. I decided to conduct some research, not only for the code, but for the usability of frames, both their cons and pros in creating a layout. I found there were a lot of cons.

Essentially Frames have a habit of breaking everything, including your entire internet experience. They manage to shut down the functionality of the internet; urls, bookmarking, search engines, printing and accessibility. I think it’s rather redundant for me to relate exactly how, when THIS article does it so beautifully. Check it out because it also provides the alternative to using frames, which is the “CSS frame.” The CSS fame isn’t so much a frame as an imitation frame, it arranges content within organised and static modules without crashing and burning the usability of your website. Though with many great inventions, and as the article specifies, the CSS frame has its limitations. These limitations mainly regard the overflow function: overflow: auto. From what I understand this function allows a scroll bar to be added if the content overflows it’s designated “frame.” This is not supported by all browsers, and alternate style sheets, and printing based style sheets must be made to avoid this issue. means more work for the builder. The above article, which I’m sure you’ve discovered is the source of my power information, was written a while ago, its comments originate from the year 2004. {The internet is a freaking time machine I swear it.} I imagine that some of the limitations that have been addressed in this article have also been addressed by the big browser companies in the newer versions of their product. I guess then the major consideration, and thus limitation of using the CSS frame is the kids who refuse to update their out of date browsers, the kids who think they’re vintage but they’re not. But seeing as this is an assessment, and the kats who are marking it are fair hip- I imagine that they’re going to have more recent browser versions.
If I build it early, I test it early, and can thus reassess if the need arises. Knowing my luck it will.

My reasoning behind wanting to pursue the CSS frame is, quite frankly, the aesthetic appeals to me. It gives the illusion of professionalism and structure. The fact that I actually can group the CSS and call it something means that wider resources are available to assist me in the task of building, which is always fantastic for the HTML/CSS novice.

THIS is both the starting point of my CSS Frame research and a representation of the CSS Frame. I thought I would share to help others, as well as providing a visual aid for my aspired finished product.

Another discovery: W3schools maintains that the overflow function is supported by all major browsers.

An end note: As I get more involved in this project, my authorial voice becomes more “essay like.” I find this interesting.

Might I firstly say, I feel totally claustrophobic at my desk right now. Busy desks are quite counter-productive to the work mentality, I’ve discovered. Nonetheless I’ve gone as far as seating myself at my desk and downloading PS Pad, so that I can well and truly begin building HTML for assessment A. This is in fact progress, I am once step closer to completing this assessment, despite how small that step is, I feel proud, but luckily not so proud that I’m deluded into thinking I’ve done enough for today. For me this afternoon is going to be plagued by trial, error and constructing code. I must say, I’m actually looking forward to it.

Shocked? So is your humble narrator.

I’ve finally settled on my topic of interest, the topic that this website is going to revolve around, and that is the wonderful world of the sims community. Why? Well quite frankly it is one that so much information can be divulged on, it is one that few people, including many sims players, know exist. It is a place that thrives on drama and failure and neon colour. Ultimately I was bound to head in this direction, if not specifically the sims community than another beneath the web community umbrella, seeing as the majority of my webbing time revolves around lurking on forums, blogs, or networking sites. Initially I had tossed up the notion of fame or notoriety within the online community. The idea was too broad and too centralised within the art-based communities, seeing as that is where my experience lies. I also think it would be difficult to work this into an “exhibition” format, and too subjective to be the focus of a reference site. Similarly the idea of exploring the “art online” had too many subgenres to cover, so ultimately and more specifically I settled on the community surrounding the Maxis, EA phenomenon, The Sims.

Within the community there are many areas to report on; I hope to include some of the following: the creator, the content, the forums, the artistic purpose and the drama.

In terms of planning, this is where the conversation comes to a close. I’m hoping that in practice I will further develop the format of my exhibition and discover some neat tricks along the way.

Edit: I've been glancing at other blogs, and let me just say that some of them are fantastic, so much in fact that my measly little place on the web seems incredibly inferior.

HTML is, to be quite frank, something that I need to invest more time in exploring. In a previous post I mentioned that HTML and I used to be the best of friends, I have to remind myself that although HTML was in my life, my experiences with it didn’t leave me particularly equipped to pursue actual website construction. I blame the accessibility of it, although incredibly useful, if not fundamental to the web-based community, it makes people damned lazy. Some people can use HTML for a number of years without actually learning it, or really, what it does (as I’m sure I’ve mentioned before.)

My relationship with HTML, (I use HTML for a good time, then fail to return it’s phone calls) I imagine, is pushing procrastination. To be frank, when HTML and I get together, it’s a little awkward. Almost always we end up fighting. Though, this blog, amazingly acts as a nagging tool, reminding me that no matter how much HTML and I like to avoid each other; I really need it… to pass this course.

So cheers to you HTML, I hope we can put our differences beside us, and work together for a better future, as a team.

CSS is also one of my newer companions. Although we’ve only just recently met, I’m looking forward to working with it more, and getting over the initial CSS shock, in the coming week. A side thought, why is blog a term still ‘incorrect’ by Word’s standards, it’s a totally legitimate for something that’s getting the red squiggly line.

Onto the moodle topics, which was the main purpose for me writing this blog anyhow. I’ve already disclosed my many opinions on both HTML and CSS, but to summarize: it can be said that I get HTML and CSS to a certain extent, but mistakes are still made and the process is largely comprised of reference and trial and error.

Looking at the Semantic Link, I can see that Semantic Markup is an umbrella term for the umbrella tags, the ones that can be edited within CSS. Presentation based markup, I believe the example they use is the bold tag, is one that is not easily edited or accessed as it only pertains to the content within those tags on the HTML document, they cannot be changed and accessed by a style sheet. The link also stressed that semantic markup is much more organized than that of presentational based mark up. I imagine that this is because of the overriding nature of CSS sheets, making the actual core document less clunky and cluttered, and thus easier to read by the machines and search engines.

Cascading: layered, one builds on the other. They add up.


Semantic web: human level expressions. Semantic is what it looks like. Non semantic is what it is
(To be finished off)

I'm at a desk, I'm at a desk, don't you eva forget it

Reflecting on my last blog post, something became apparent. My past self lied to me. I told myself that writing this blog would be the first thing to happen this morning, after waking up. As I write this it is nearing ten to five in the afternoon. Something has become apparent, I have been procrastinating. The question is why? I believe that my attitude has shifted once more; blogging has become a negative thing in my head. This mostly is because I have little to report on, due to the little progress I have made on my assessment. I’m finding it difficult to exactly pin point what I’m trying to do.

Now that those facts are free and no longer wrenching at my subconscious (we’ve inadvertently discovered the true purpose of the personal blog, to vent), I will elaborate on last week’s findings.

Michael opened the lecture with a reminder; we are supposed to seriously apply ourselves to our blogs. Now, it’s not that I haven’t been applying myself, it’s rather that I haven’t been applying myself as seriously as I probably should. For this blog post I have obviously adopted a more serious authorial voice. This is actually what stress does to a person, renders them into a 50 year old company CEO. Now, I’ll begin this meeting with...

Mash ups and APIs.

API, or application programming interface, is something incredibly useful within the realms of website design. This was particular evident upon observing ‘Beyond Reasonable Drought’ and it’s use of the Flickr API. Although I’m not entirely savvy on the topic, I at least understand that APIs are a means of cooperation occurring between information and software. To further educate myself, I pursued some online research on the matter and discovered (correct me if I’m wrong,):

-APIs rely on XML or Javascript to function.
- Web based APIs allow mash ups to occur, which is a combination of web services.
- Allows web based communities to share data between applications.
-Data is easily accessible from multiple locations.

Wikipedia, (although condemned academically), had a wonderful list, that really solidifies the idea of an API put to use as it provides specific examples of websites that the general masses are familiar with.

Directly sourced from: Wikipedia
Use of API’s to share content:
1. Photos can be shared from sites like Flickr and Photobucket to social setwork sites like Facebook and MySpace.
2. Content can be embedded, e.g., embedding a presentation from SlideShare on a Linked-In profile.
3. Content can be dynamically posted. Sharing live comments made on Twitter to a Facebook account, for example, is enabled by Twitter and Facebook's APIs.
4. Video content can be embedded on sites which are served by another host.
5. User information can be shared from web communities to outside applications,
delivering new functionality to the web community that shares its user data via an open API. One of the best examples of this is the Facebook Application platform.

Basically API’s really improve the functionality of the internet. They make a user’s web experience more convenient in terms of gathering or relaying information, and overall enhance the internet experience.

From my understanding mash ups are usually a correlation of API’s. An example that I gained from the lecture was Neave TVor Everyblock. These sites are combining multiple API’s the present a wholistic collection of information. This was particularly evident with everyblock which combines government databases (for statistics) with mainstream news feeds and flickr. The result of these combinations is a rich catalogue of information concerning a location, streamed from several places on the internet. I’m just dissapointed that everyblock is only specific to the US.

One final lesson that I have learnt this week is one about the superficiality of a blog. The more interested the author is in blogging characteristic such as interesting authorial voice, humour (or lack there of) and quirk the more trivial the content will be. Excuse me now, why I go rescue my mad hatter poster from falling off my wall.

No, that was not some kind of innuendo.

Xanthe out.

PS. APIS = DYNAMIC. Courtesy of tutorial.

This week’s blog...

...Is a message to my future self.
Dear me,
Tomorrow, when you wake up, you are going to seriously consider your networked media assessment, and then you are going to write some html, and write a more comprehensive blog on your findings and contemplations.
Okay? Okay.
Sincerely
Your present self.