TLN

You can now use Google search to find SVG doc­u­ments. SVG is an open, XML-based for­mat for vec­tor graph­ics with sup­port for inter­ac­tive ele­ments.
Goole indexes SVG con­tent whether it is in a stand­alone file or embed­ded directly in HTML. The web is big, so it may take some time before Google can crawl and index most SVG files, but as of today you may start see­ing them in your search results. If you want to see it your­self, try search­ing for sitemap site:fastsvg.com or HideShow site:svg-whiz.com
If you host SVG files and you wish to exclude them from Google’s search results, you can use the “X-Robots-Tag: noin­dex” direc­tive in the HTTP header.

Sprout­Core is an HTML5 appli­ca­tion frame­work for build­ing respon­sive, desktop-caliber apps in any mod­ern web browser, with­out plu­g­ins. This is a cheat sheet i put together for myself in the first instance of all the com­mands for gen­er­at­ing sc components.

Down­load the PDF here

HTTP Client .. A Mac OS X Leop­ard devel­oper tool for debug­ging HTTP ser­vices by graph­i­cally cre­at­ing & inspect­ing com­plex HTTP messages.

Fea­tures:

• HTTP meth­ods: GET, POST, PUT, DELETE, TRACE, OPTIONS, HEAD, CONNECT
• HTTP Basic Authen­ti­ca­tion (with Key­chain integration)
• Cus­tom HTTP request head­ers with pre­pop­u­lated names and val­ues (date for­mat strings and most pop­u­lar User-Agent strings)
• Sup­ports send­ing request bod­ies with POST or PUT
• Fol­low or ignore redirects
• Optional syn­tax high­light­ing (change­able in Preferences)
• Optional text wrap (change­able in Preferences)
• Each HTTP Client win­dow is a doc­u­ment that can be saved as a .http­client file and reopened later

Here and here. The price has been con­firmed at around$20,000,000 dol­lars which is not dab for the orig­i­nal $250,000 injected into it. A lot of Motorola’s recent suc­cess has been through Android devices and so we can expect Cap­puc­cino to come up with a set of touch com­mands soon.

280 North already have Atlas which helps to speed up the devel­op­ment process by act­ing like X-Codes inter­face builder.

The mobile devel­op­ment scene seems to be mov­ing apace with a range of hard­ware devices and a match­ing and dizzy­ing range of devel­op­ment plat­forms. When i say mobil devel­op­ment i am really talk­ing about iPhone, and Android and WebKit devices. Now although this can be con­sid­ered a small part of the mar­ket it seems to me to be the most inno­v­a­tive and the one that is dri­ving devel­op­ments, ini­tia­tives and pub­lic interest.

Devel­op­ment seems to be falling into a num­ber of camps.

Objective-C for native on the iPhone/Pad/Pod

Java and java tools for native on Android Phones

HTML/CSS/JavaScript Frame­works for any WebKit based.

From the early rather rough days some of these offer­ings are get­ting very solid and some are also weigh­ing with devel­op­ment front-ends to ease the pain of devel­op­ment and dare i say lock you in to their framework?

I have pre­vi­ously cov­ered some of the frame­works and will be doing an update in the near futre to do a full catch up.

Any­way two of the frame­works that i missed past time round, because they didn’t really cater for mobile devel­op­ment were Cap­puc­cino and Sprout­core. Cap­puc­cino still has no direct mobile offer­ing, i.e. touch capa­bil­ity, but Sprout­core now has.

First a bit about Sprout­core. It is a frame­work for writ­ing HTML 5 sites and JavaScript and pro­vides all the libraries and infra­struc­ture to do this. The thing that helped Sprout­core a great deal was that Apple used it to build the MobileMe plat­from and are reputed to have adopted it for much of it’s web build­ing. It is also use in iWork as well.

This is all very well but doesn’t let you build mobile apps with a touch inter­face. How­ever in April of this year Sprout­core Touch was announced. You can go to Hed­wig to see sam­ples of the ges­tures available.

Finally they announced Green­house as the tool to build the inter­faces for Sproutcore.

This is a reset stylesheet which unlike Meyer’s or YUI’s not only removes the default styling of HTML ele­ments, but also rebuilds the new generic rules for the typog­ra­phy, head­ings, para­graphs, lists, forms, tables etc. It’s light-weight, flex­i­ble and browser-friendly. Free, trendy, cool new etc.

You can get it from here

Wher­ever pos­si­ble i develop on a Mac. I’m not an Apple fan­boy as such but there are cer­tain aspects of the hard­ware and the soft­ware plat­form that i like and gen­er­ally the whole devel­op­ment process on the OSX plat­form is smoother and eas­ier than when­ever i try Windows.

Hav­ing said that it will then tend to be that i am biased towards appli­ca­tions that run well on the Mac as well as offer­ing the func­tion­al­ity required to develop software.

I started my com­put­ing career on HP’s with a share­ware edi­tor called Edi­tor and a full screen one called QEdit and TECO on the DEC Tops 20 OS. At a later stage after mov­ing to the PC and Win­dows plat­form i tried a num­ber of edi­tors, BRIEF which was quite cool for it’s day and is still going strong. How­ever when i got to web devel­op­ment and was an MS user i either used Visual Stu­dio or Home­Site. VS need no expan­sion but Home­Site was inter­est­ing as an HTML ori­ented devel­op­ment tool but let you get at the code and didn’t muck with the code like Front­Page (shud­der) and was not as clut­tered as even the early incar­na­tions of Visual Stu­dio were.

When i moved to the Mac i couldn’t take Home­Site with me as it was a Win­dows only tool so after a bit of hack­ing around i started to use Eclipse as it was sim­i­lar to Home­site in it layout.

I stayed with Eclipse which became more use­ful as the PHP plu­g­ins were devel­oped but as i got more used to the Mac the less i liked Eclipse as being Java based it was never quite Mac like. At one point i had a brief foray into Zend Stu­dio, about 2007, but at that point it was not Mac like enough and had Ctrl+key as opposed to cmd+key which as a key­board short­cut user was as annoy­ing as hell. Ok maybe there were key­bind­ings i could have altered but i am a bit lazy that way.

Some time later i bought a copy of Text­Mate as i had seen this touted as “THE” Mac Edi­tor and the Ruby boys were flock­ing to it as well. This i found to be, like a lot of Mac soft­ware, the right level of com­pro­mise between usabil­ity, lack of overkill (see Visual Stu­dio) and because it is native Cocoa sheer speed on the Mac. It’s other advan­tage is the opene­ness that allows bun­dles to be writ­ten which add func­tion­al­ity but don’t overwhelm.

Very recently i used Net­Beans again. I had looked at it in the early days at the same time i was using Eclipse but then it was com­pletely Java. How­ever now it not only has PHP sup­port but also Zend and Sym­phony sup­port. THis means it will do code com­ple­tion etc.

How­ever it is Java and there­fore tends to run like a dog on the Mac (or is that just me?) and the inter­face is back to the messy, busy win­dows type style.

I think ther­fore that Text­Mate is going to stay as my edi­tor of choice for the fore­see­able future.

.….. some­one who reads in bed. Me!

All you need to know .……

CouchDB on a postit