<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>ArcticSoft Blog</title>
	<link>http://blog.arcticsoft.net</link>
	<description>Official Blog of ArcticSoft</description>
	<pubDate>Fri, 05 Sep 2008 17:48:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>
	<language>en</language>
			<item>
		<title>jQuery and AJAX Requests</title>
		<link>http://blog.arcticsoft.net/2008/09/04/jquery-and-ajax-requests/</link>
		<comments>http://blog.arcticsoft.net/2008/09/04/jquery-and-ajax-requests/#comments</comments>
		<pubDate>Thu, 04 Sep 2008 17:44:04 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Web Development</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2008/09/04/jquery-and-ajax-requests/</guid>
		<description><![CDATA[Ive written ajax request the long handed way using the long hand way of a XMLHttpRequest. It can be tedious and frustrating. Don&#8217;t get me wrong, it works great but building this functionality can take a long time, just to avoid a page refresh.
This is where jQuery comes in handy. In a few lines of [...]]]></description>
			<content:encoded><![CDATA[<p>Ive written ajax request the long handed way using the long hand way of a XMLHttpRequest. It can be tedious and frustrating. Don&#8217;t get me wrong, it works great but building this functionality can take a long time, just to avoid a page refresh.</p>
<p>This is where <a title="JQuery" href="http://jquery.com">jQuery</a> comes in handy. In a few lines of javascript you can create quick ajax requests. This is how its done:</p>
<p>1. Download the jQuery library and include this file in your head tag like so.</p>
<blockquote><p>&lt;script type=&#8221;text/javascript&#8221; src=&#8221;path-to-file/jquery.js&#8221;>&lt;/script></p></blockquote>
<p>2. Create a php file that will be called and return value to the DOM. This can be a simple file that echos &#8216;Hello World&#8217;.</p>
<p>3. Create a page element that receives the markup. Here would be an example:</p>
<blockquote><p>&lt;div id=&#8221;loadedContent&#8221;>&lt;/div></p></blockquote>
<p>4. Now that you have a php file that returns content, and a page element that can recieve the content you can now create the javascript/jQuery to make the ajax request and input the results into the DOM. </p>
<blockquote><p>&lt;script type=&#8221;text/javascript&#8221;><br />
$(document).ready(function () {<br />
$.post(&#8221;hello-world.php&#8221;, function(data){<br />
$(&#8221;#loadedContent&#8221;).html(data);<br />
});<br />
});<br />
&lt;/script></p></blockquote>
<p>That&#8217;s it! On the page load it should request the page. You can go further by using simple click events and send simple name/value pairs using the same request. jQuery is simple and easy to use. If you have any questions please leave a comment.</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2008/09/04/jquery-and-ajax-requests/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Google Chrome</title>
		<link>http://blog.arcticsoft.net/2008/09/03/google-chrome/</link>
		<comments>http://blog.arcticsoft.net/2008/09/03/google-chrome/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 21:42:33 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Browsers</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2008/09/03/google-chrome/</guid>
		<description><![CDATA[After downloading and installing chrome, here are my first thoughts.
1. Its fast, but when many tabs are open with flash it slows down a lot.
2. Its simple design turns me off. Dont get me wrong I love simple design, but when I feel like more functionality is lost it crosses the line. I&#8217;m used to [...]]]></description>
			<content:encoded><![CDATA[<p><img hspace="10" align="left" id="image27" alt="Chrome Browser" src="http://blog.arcticsoft.net/wp-content/chrome.jpg" />After downloading and installing chrome, here are my first thoughts.</p>
<p>1. Its fast, but when many tabs are open with flash it slows down a lot.</p>
<p>2. Its simple design turns me off. Dont get me wrong I love simple design, but when I feel like more functionality is lost it crosses the line. I&#8217;m used to Firefox with custom add-ons such as firebug and such. I have the feeling that more browsing tools are being taken away.</p>
<p>3. I have the feeling in the back of my mind that Google is using the browser to monitor browsing habits just like many think is happening with Analytics. This may not be true, but one has to wonder if rankings may depend on how often a site is visited using Chrome. I&#8217;m not saying this is how they will rank sites in the future, but could be a factor.</p>
<p>Those were my first thoughts on the beta of Chrome. It has potential using the webkit engine if it was more customizable and I didn&#8217;t feel like half of my browsing experience was taken away.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2008/09/03/google-chrome/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Business Open!</title>
		<link>http://blog.arcticsoft.net/2008/08/27/business-open/</link>
		<comments>http://blog.arcticsoft.net/2008/08/27/business-open/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 19:20:22 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Uncategorized</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2008/08/27/business-open/</guid>
		<description><![CDATA[A friend of mine just opened a business in Fairbanks Alaska. He opened an Anytime Fitness franchise. Congratulations Nathan! Here is a commercial for the opening. Click Here to see the commercial!

]]></description>
			<content:encoded><![CDATA[<p>A friend of mine just opened a business in Fairbanks Alaska. He opened an Anytime Fitness franchise. Congratulations Nathan! Here is a commercial for the opening. <a href="http://wernerswonderland.blogspot.com/2008/08/anytime-fitness.html">Click Here to see the commercial!</a>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2008/08/27/business-open/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Essential Medical (Medical Passport v1.2.0)</title>
		<link>http://blog.arcticsoft.net/2008/08/19/essential-medical-medical-passport-v120/</link>
		<comments>http://blog.arcticsoft.net/2008/08/19/essential-medical-medical-passport-v120/#comments</comments>
		<pubDate>Wed, 20 Aug 2008 01:24:03 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Application Development</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2008/08/19/essential-medical-medical-passport-v120/</guid>
		<description><![CDATA[Just released! I just finished developing a new version of the Medical Passport. This new version adds charting to the Passport formally called Electronic Medical Record. So in short, if you are away from home, and something happens, a new doctor can create a chart that is stored on your medical drive. Then when you [...]]]></description>
			<content:encoded><![CDATA[<p>Just released! I just finished developing a new version of the Medical Passport. This new version adds charting to the Passport formally called Electronic Medical Record. So in short, if you are away from home, and something happens, a new doctor can create a chart that is stored on your medical drive. Then when you get back to your doctor, he/she can see exactly what another doctor has done or given you. I am continuing to develop for Essential Medical and there are some new and exciting things coming up that should be a great asset for the medical community. See the features of the EMR <a title="Electronic Medical Record" href="http://ess-med.com/emr.php">HERE</a>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2008/08/19/essential-medical-medical-passport-v120/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Affiliate Sites</title>
		<link>http://blog.arcticsoft.net/2008/06/24/affiliate-sites/</link>
		<comments>http://blog.arcticsoft.net/2008/06/24/affiliate-sites/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 18:16:12 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Uncategorized</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2008/06/24/affiliate-sites/</guid>
		<description><![CDATA[I must repent for not posting lately. I have been busy with development and site redesigns. Also I went to Alaska for vacation.
I have had an interest in affiliate sites for the last few years and its looking more appealing all the time. I have seen great success from others in this area and have [...]]]></description>
			<content:encoded><![CDATA[<p>I must repent for not posting lately. I have been busy with development and site redesigns. Also I went to Alaska for vacation.<img hspace="8" height="128" width="192" align="left" alt="collegestudent.jpg" id="image24" src="http://blog.arcticsoft.net/wp-content/collegestudent.jpg" /><br />
I have had an interest in affiliate sites for the last few years and its looking more appealing all the time. I have seen great success from others in this area and have about a half dozen idea floating in my mind for doing this. I will most likely try both sides as an affiliate and a host of a program for a few different sites. One site i will be offering a program for is <a href="http://www.ess-med.com">Essential Medical</a>. This will work similar to the distributor section just online. For every refering site that sales either a download or drive Essential Medical will pay $5.</p>
<p>Also on the other end of things, I am looking to be an affiliate for a few differnt sites and will be setting up specific blogs and sites just for this purpose. I will document my findings as I progress.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2008/06/24/affiliate-sites/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Top 12 Design Mistakes (Part Two)</title>
		<link>http://blog.arcticsoft.net/2007/12/07/top-12-design-mistakes-part-two/</link>
		<comments>http://blog.arcticsoft.net/2007/12/07/top-12-design-mistakes-part-two/#comments</comments>
		<pubDate>Fri, 07 Dec 2007 21:14:27 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Web Design</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2007/12/07/top-12-design-mistakes-part-two/</guid>
		<description><![CDATA[Here is the rest of the list.
1. Watch your load speeds. As a lot of people are on      dial up, load speeds are an issue. No one wants to wait along time to have      a page load. More and more are moving to faster connection [...]]]></description>
			<content:encoded><![CDATA[<p>Here is the rest of the list.</p>
<p>1. Watch your load speeds. As a lot of people are on      dial up, load speeds are an issue. No one wants to wait along time to have      a page load. More and more are moving to faster connection speeds, but      still a large percentage of people are still on slower speeds. While      adding images or even thinking about video, remember load speeds.</p>
<p>2. Do not play music on your home page automatically.      This has been mentioned by many books and design sites, yet still      designers do it. For one most find it annoying when it starts, and two it      can alienate people from your site because in various likes in music. I      you must have music for example, a band site, give the user an option to      turn it off, or have volume controls.</p>
<p>3. Easy to use navigation. This one is pretty important.      Users want to know where they are and how to easily get to where they want      to get. Make the site map of your site easy to read, and make the      structure easy to follow. Also the navigation bar should be easy to read      and consistent throughout your site or application.</p>
<p>4. Colors of text vs. background should be pleasing.      There are always those sites that use red text over bright blue or      something similar. Then you try to read the first line of text and go      cross-eyed. Black texts on a white background is preferred, but if you      need to use different colors, make sure the text is easily read, and does      not strain the eyes.</p>
<p>5. Content. Write content for your site that is      appropriate. Do not try to combine 3 businesses into one site as users      will get confused as to what they are looking at. For example, if your      site is about skiing in Aspen,      do not try to run an online poker page from the same site. Domains and      hosting is cheap enough to separate your business ventures.</p>
<p>6. Spelling goes a long way. Make sure you run your      content through a spell-checker. I find even large corporate sites have      very easy to fix spelling errors. Simple spelling errors put off users. If      you can not spell right, it shows that a user cannot trust you with a      product or service either.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2007/12/07/top-12-design-mistakes-part-two/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Top 12 Design Mistakes (Part One)</title>
		<link>http://blog.arcticsoft.net/2007/10/31/top-12-design-mistakes-part-one/</link>
		<comments>http://blog.arcticsoft.net/2007/10/31/top-12-design-mistakes-part-one/#comments</comments>
		<pubDate>Wed, 31 Oct 2007 19:54:04 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Web Design</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2007/10/31/top-12-design-mistakes-part-one/</guid>
		<description><![CDATA[I am making a list of mistakes in web design. I know, there has been tons of these lists on other sites. But this list is different, it also takes into account newer technologies that have been used over the last few years. So here we go:
1. Write for web not print. In the text [...]]]></description>
			<content:encoded><![CDATA[<p>I am making a list of mistakes in web design. I know, there has been tons of these lists on other sites. But this list is different, it also takes into account newer technologies that have been used over the last few years. So here we go:</p>
<p>1. Write for web not print. In the text of your sites make short easy to read paragraphs. You are, most of the time, writing to explain a product or service, not write a novel. If the first thing a user comes up against is a wall of text, more than likely they will leave.</p>
<p>2. Write articles on the web on one page. This is a common complaint I have heard lately from people. I have never done it but have seen many people split articles into many pages for no real reason. Make pages contain information people are looking for without looking for a next button. They would rather continue scrolling than click to 5 different pages for the same article.</p>
<p>3.With the big hype of AJAX, don’t overdo it. Make sure you have a purpose for using it. Google maps have a valid reason for updating maps, but to go to a site filled with cheesy dropdowns and auto completes for no known reason is bad design.</p>
<p>4. Do not overuse animations such as Flash. These technologies serve specific purposes. Flash is great for interactive elements in a site such as video or animation, but search engines do not know what content is in a .swf file so cannot index it. Plus people do not like splash screens, they want the website.</p>
<p>5. Do not use popups on your site. With the huge push on internet security, users mostly view popups as spyware or annoying ads. If you must use popups, make your user aware by spelling it out on your site that you use them. This will make them more aware that you use them and that they should expect content from your site to be displayed using them.</p>
<p>6. When linking, do not use the target of _blank. Most users are still using non-tabbed browsers. Users can find this obtrusive and feel like your site is opening windows for them.</p>
<p>That is just a few tips on design, I&#8217;ll give you six more in a few days. Stay tuned.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2007/10/31/top-12-design-mistakes-part-one/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Mac Mini, the first Apple</title>
		<link>http://blog.arcticsoft.net/2007/08/30/mac-mini-the-first-apple/</link>
		<comments>http://blog.arcticsoft.net/2007/08/30/mac-mini-the-first-apple/#comments</comments>
		<pubDate>Thu, 30 Aug 2007 21:41:32 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Misc</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2007/08/30/mac-mini-the-first-apple/</guid>
		<description><![CDATA[I never thought I would say this, but I am now a proud owner of a Mac computer. As Macs have been gaining more market share and the need to do testing on a mac is coming up shortly, I went out and purchased the mini.
Now I have used a mac a few times in [...]]]></description>
			<content:encoded><![CDATA[<p><img width="232" hspace="10" height="154" align="left" id="image19" alt="macmini.jpg" src="http://blog.arcticsoft.net/wp-content/macmini.jpg" />I never thought I would say this, but I am now a proud owner of a Mac computer. As Macs have been gaining more market share and the need to do testing on a mac is coming up shortly, I went out and purchased the mini.</p>
<p>Now I have used a mac a few times in the past, but not any of the new ones. When I got it setup in the office I was very surprised on how well it performed for such a small package.</p>
<p>I also loaded a bunch of photos into iPhoto, its is very easy to add photos and remove what you don&#8217;t want and enhance what you do.</p>
<p>Also the new iWeb is nice for layouts. I have yet to find the time to get PHP 5.2.X installed to do some development as well. Who knows, it might become a development machine.</p>
<p>Just a few drawbacks I have seen so far. 1. The mini has only one DVI port, so without headache, dual monitors is out of the question. and 2. iWeb&#8217;s gallerys require a .mac account. I have found plugins that allow your own hosting, but it is a pain to use. Plus for all the bashing Apple does on PC&#8217;s about being so creative, why cant I be creative on my own web space?</p>
<p>That&#8217;s just a quick review on a new mac user after having it for a day or two.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2007/08/30/mac-mini-the-first-apple/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>The Typical Design Client</title>
		<link>http://blog.arcticsoft.net/2007/06/22/the-typical-design-client/</link>
		<comments>http://blog.arcticsoft.net/2007/06/22/the-typical-design-client/#comments</comments>
		<pubDate>Fri, 22 Jun 2007 17:52:25 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>Web Design</category>
	<category>Web Development</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2007/06/22/the-typical-design-client/</guid>
		<description><![CDATA[Like most other software developers and web designers we have trouble with some clients. I really feel the problem to this is a client does not understand the work and effort that goes into a site or software package. If a client saw what was involved in the Software Development Life Cycle and designing a [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 11pt; font-family: Verdana">Like most other software developers and web designers we have trouble with some clients. I really feel the problem to this is a client does not understand the work and effort that goes into a site or software package. If a client saw what was involved in the Software Development Life Cycle and designing a functional database or design they may think about things a little differently. </span></p>
<p><span style="font-size: 11pt; font-family: Verdana" /></p>
<p><span style="font-size: 11pt; font-family: Verdana">Clients should think of software or a site like a house (<a href="http://www.scottmanning.com/archives/000455.php"><font color="#800080">Read this for a good laugh</font></a>). Once a foundation is down, any drastic changes are costly. With a house, if you decide to add a room half way through, you have to get plans re-approved for loads and building codes, drastic changed need done, and the extra labor in building the extra piece. The same is true with development. If you have a database and software halfway through being built, and a client requests a change in structure, there can be many effects in database integrity, other pages or forms affected, and the extra work to build. </span></p>
<p><span style="font-size: 11pt; font-family: Verdana">This shows that even small changes to software can affect many aspects. Without fail, this also pushes out deadlines and increases costs as a lot of work needs to be done to make the so called &#8220;easy change&#8221;. </span><span style="font-size: 11pt; font-family: Verdana" /><span style="font-size: 11pt; font-family: Verdana"> </span><span style="font-size: 11pt; font-family: Verdana"> </span><span style="font-size: 11pt; font-family: Verdana"><span style="font-size: 11pt; font-family: Verdana">Please keep these in mind when working with a developer or designer. They will be happy, it will cost you less, and the chance of the project getting done on time will increase.</span></span><span style="font-size: 11pt; font-family: Verdana"> </span><span style="font-size: 11pt; font-family: Verdana"></p>
<p /></span>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2007/06/22/the-typical-design-client/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Too Much AJAX, is it good for SEO?</title>
		<link>http://blog.arcticsoft.net/2007/05/17/too-much-ajax-is-it-good-for-seo/</link>
		<comments>http://blog.arcticsoft.net/2007/05/17/too-much-ajax-is-it-good-for-seo/#comments</comments>
		<pubDate>Thu, 17 May 2007 21:19:16 +0000</pubDate>
		<dc:creator>jpratt</dc:creator>
		
	<category>SEO</category>
	<category>Web Development</category>
		<guid isPermaLink="false">http://blog.arcticsoft.net/2007/05/17/too-much-ajax-is-it-good-for-seo/</guid>
		<description><![CDATA[Well I did it, just upgraded to Adobe Web Premium Edition. First I would like to say I love it. It is actually based on web standards and not IE6 which I am grateful for. But one thing I feel got &#8220;too easy&#8221;, that’s AJAX. I like the way Dreamweaver using Spry to build AJAX into [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 11pt; font-family: Verdana">Well I did it, just upgraded to Adobe Web Premium Edition. First I would like to say I love it. It is actually based on web standards and not IE6 which I am grateful for. But one thing I feel got &#8220;too easy&#8221;, that’s AJAX. </span><span style="font-size: 11pt; font-family: Verdana"><span style="font-size: 11pt; font-family: Verdana">I like the way Dreamweaver using Spry to build AJAX into your site, but there is one problem, one word JavaScript. Search Engines have been known to have problems with links and content generated by JavaScript. Don’t get me wrong, I love JavaScript, it’s a great client side scripting language, but with Spry I really feel it will be overused. </span></p>
<p></span><span style="font-size: 11pt; font-family: Verdana">Now that it is easy to build these &#8220;widgets&#8221; what stops someone from building all their content onto one page fed by an xml file? Not much except ignorance by which search engines will index the content. </span><span style="font-size: 11pt; font-family: Verdana"> </span><span style="font-size: 11pt; font-family: Verdana">I feel a lot of web designers clients are going to get hosed with regards to engine traffic once a very creative and non-technical designer get a hold of this tool. That’s ok, if everyone starts using this it will just get easier for others that understand SEO to rank well. This is like the Flash epidemic. </span><span style="font-size: 11pt; font-family: Verdana"></p>
<p /></span>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://blog.arcticsoft.net/2007/05/17/too-much-ajax-is-it-good-for-seo/feed/</wfw:commentRSS>
		</item>
	</channel>
</rss>
