Webhost4life was my first hosting provider, I joined their service at November 2009.
Although their support was… not very technical, and REALLY slow on response time, I was able to solve most problems I had by myself.
In the middle of January, they announced that their moving to a new and improved platform, and they even had this fancy “transition kiosk” that was suppose to find and resolve all potential migration problems automatically.
I’ve put together a small site that allows you to preview the custom AtomSite themes I’ve done.
Furthermore, you can rate, download and comment the themes at the site, would love some feedback if you liked any theme.
http://atomsitethemes.erikzaadi.com
You’ll notice a gray thing on the left :
This is the compact mode of the theme switcher. If you click on the show button you’ll see:
This is where you can choose a theme to preview.
[This post is a follow up to the workaround for AtomSite 1.3]
I’ve updated the Windows Live Workaround to the new release of AtomSite (1.4).
Thanks to some hierarchical changes made in the new release, deploying the workaround is much easier.
The workaround is built as a plug-in, so you can apply it to any AtomSite deployment without the need for compiling source code.
Simply unzip the binaries zip file below to your AtomSite root, then access http://yourblogAddress/WLWWorkaround
[UPDATE - Available for version 1.4 as well, see post here]
In continuous to an old series about migrating from Blogger to AtomSite, I came up with a workaround/solution that allows you to connect Windows Liver Writer to the AtomSite blog.
I’ve been asked a couple of times to supply the solution, so I thought I’d publish it here for more easy access:
Read the included README file for specific instructions..
If you want an easier access to the workaround than clicking in the address mentioned in the README, you can add the following to your service.config, I added it `AdminSettingsEntireSite"=>“settingsRight”
For the impatient, check out the demo | source..
Creating desktop applications in Air with html and JavaScript is a joy for any web oriented developer. You get the same environment to work in, jQuery included, and the ability to create desktop based applications fast. The only thing problem you encounter is the switch in concept of updating the desktop application with a new version. It’s no longer as easy as updating the site, you need to get the user to download the update..
For the last year and a half I’ve been heavily exposed to a lot of open source software.
It started out with a small conversation mentioning jQuery (Thanks Tim!), and since then I’ve been amazed by the open source community.
The great thing about open source is that you can pay back to the people that created software that you like (Yes, the price is also nice, of course).
I’ve been using jQAPI by Sebastian Senf (@mustardamus), which is an alternative (and in my personal opinion better) documentation for the jQuery API framework.
Google Closure Compiler is an amazing tool. Besides having the best compression rate (and being the official choice of jQuery), it really alters the way you write javascript.
When using the Advanced Optimization option, it forces you to write more concise code, exposing only what really matters to the global namespace.
There’s a lot more the be said in that matter, but that’s material for a future post about how Google Closure Compiler changed the way I write jQuery plugins.
Fixed a bug (calculating the base href for embedding css when not using port 80, see issue).
Added a small feature, the entire element is cloned, ensuring that all attributes are added to the element in the generated print page (see feature request ).
Links:
Download | Download (Minified) | Documentation | Issues (Report a bug) | Official jQuery Plugin Page
By the way, all of my jQuery plugins have been tested with jQuery 1.4.1..
For those of you who can’t install asp.net mvc 2 rc2, here are the vsdoc files for jQuery 1.4.1 :
http://demos.erikzaadi.com/js/jquery-1.4.1-vsdoc.js
http://demos.erikzaadi.com/js/jquery-1.4.1.min-vsdoc.js
The release also includes the vsdoc files for the jQuery validate plugin:
http://demos.erikzaadi.com/js/jquery.validate-vsdoc.js
http://demos.erikzaadi.com/js/jquery-1.4.1.min-vsdoc.js
Enjoy,
Erik
Most companies with somewhat restricted firewall rules typically enables only web traffic using port 80 or 443 (for SSL).
Git is communicating with Github using port 22 (or the default 9418), which in my own case was blocked after a while.
To keep “gittin” from work there are some options.
Work with pure http access (port 80) git clone http://github.com/username/repository.git
This will only give you read only access and is rather slow