Bloggink » webrelated http://joggink.com Blog of Joggink, home of Jochen Vandendriessche Fri, 27 Jan 2012 10:03:33 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 The social cms http://joggink.com/2011/04/the-social-cms/ http://joggink.com/2011/04/the-social-cms/#comments Sun, 10 Apr 2011 12:04:58 +0000 joggink http://blog.joggink.com/?p=375 Continue reading →]]> Think about your favorite CMS and how it handles digital asset management. It gives you the ability to upload pictures, videos, audio files and every other possible document format that exists, right?

Imagine that the asset management didn’t store your uploads on your hosting’s disk space? Imagine you could link it to the social services that are out there?

Images could be uploaded to flickr or picasa, videos to vimeo or youtube, audio files to soundcloud, presentations to slideshare, … The only real problem would be other file formats, but if you have a dropbox account you can easily get a public download link for them.

Advantages:

  • if you ever have to move your site to a different website you don’t have to change most of the URLs (e.g moving wordpress to a different domain)
  • your files are available via a CDN, so they won’t slow down your page load.
  • less disk space usage on your hosting
  • these social services make sure your media plays nice, e.g. video files get converted to FLV’s and have an HTML5 fallback, same for audio files, images on flickr can be queried to return an image of your requested dimensions, etc…

Disadvantages:

  • If your social service discontinues you’re pretty much screwed
  • if your social service changes their API it would break your CMS’ asset management

This is just an idea that I have been playing with for quite some time, I don’t know if it is doable or even smart to do but I’ve always been intrigued by the possibilities. It could be that I’ve forgotten some pros/cons or that I missed something crucial, if so, please let me know.

]]> http://joggink.com/2011/04/the-social-cms/feed/ 5 Git clients, an overview http://joggink.com/2011/04/git-clients-an-overview/ http://joggink.com/2011/04/git-clients-an-overview/#comments Sun, 10 Apr 2011 00:12:31 +0000 joggink http://blog.joggink.com/?p=367 Continue reading →]]> I’ve always been intrigued by the number of SVN apps there are , like the beautiful versions app, and the lack of descent GIT clients. Last year I’ve seen some upcoming GIT clients websites all claiming they were building the best GIT client ever. I’ve tried to make a nice list of GIT clients:

  • Gity (Mac, open source)
  • Gitti (Mac, currently in beta, download available)
  • SmartGit (Mac/windows/linux, free for non-commercial use / 55 euro license)
  • Gitbox (Mac, free for max. 3 repositories / available in app store)
  • GitX (Mac, open source)
  • Tower (Mac, 30 day trial available)
  • Sourcetree (Mac, also for mercurial, trial available)
  • Gitnub (Mac, opensource)
  • Sprout (Mac, available in app store)

I’ve bought Tower with a github promo code. Partially  because of the clean interface but definitely because it plays nice with Textmate and because I can create a new git repository on my beanstalk app account.

It could be that I missed some git clients, so feel free to let me know.

]]> http://joggink.com/2011/04/git-clients-an-overview/feed/ 2