Jump to content

Codekit 2.1.3 (Mac Os X)


fripis
 Share

Recommended Posts

 
 
 
 
 
 
 
610.png
 
[B][SIZE=3][COLOR="#006400"]CodeKit 2.1.3[/COLOR][/SIZE][/B]
 
[B]Description[/B]
CodeKit helps you build websites faster and better.
Compile Everything: 
Process Less, Sass, Stylus, Jade, Haml, Slim, CoffeeScript, Javascript, and Compass files automatically each time you save. Easily set options for each language.
 
Live Browser Reloads: 
Instantly see changes in your browser, with animation and without hitting the refresh button or installing plugins. Great for tweaking layouts!
 
Combine and Minify: 
Reduce load times by mashing Javascript and CoffeeScript files together and then minifying with Uglify.js. It's so easy, you'll giggle like a schoolgirl. Seriously.
 
Optimize Images: 
Losslessly reduce JPEG and PNG file sizes with one click and see the savings. One less thing to do at deployment. (More compression options coming soon!)
 
JSHint and JSLint: 
Makes debugging scripts fun and easy. Instantly find that one hanging comma that kills IE, or enforce coding styles and best practices across teams.
 
Team Collaboration: 
Sync project settings across teams and computers in an open JSON format. Keep everyone on the same page or easily jumpstart new sites.
 
Easy Frameworks: 
Keep just one copy of a file on your drive and easily use it across many projects without worrying about file paths. No more copying files into every new site.
 
It Just Works: 
There's nothing to install or configure. No mucking around the command line. Just run the app and start working. It's that easy.
 
[B]What's New Version 2.1.3:[/B]
[Fixed] Excessive "Could Not Start HTTP Server" alerts no longer appear. When your network connection status changes (e.g. your Mac goes to sleep), the server now updates without restarting itself.
[Fixed] Android and Windows devices no longer infinitely refresh every 5 seconds.
[Not Fixed] Some of you use Android.
[Changed] The self-healing feature introduced in the last update has been removed....
   I tested the self-healing feature on a strong, fast WiFi network. If your WiFi is laggy (e.g. a public network), the self-healing routine would repeatedly try to reconnect to CodeKit because the HTML5 websocket protocol has no way to determine if a connection is truly dead or just laggy. In version 2.1.3+, if a page loses touch with CodeKit for 15+ seconds, it will display a banner telling you that the connection is unstable, but it will NOT attempt to automatically reconnect, since the connection may not be dead.
   Auto-refresh on remote devices really requires a solid, fast WiFi network to work well. If the network is bogged down with traffic or you're at the edge of the router's signal range, refreshes will probably be slow and/or unreliable.
 
 
[B]Requirements[/B]
OS X 10.8 or later
 
mx9.jpg
 
 
 
 
 
[SIZE=3][B]Download [/B][/SIZE]
 
https://www.oboom.com/73UJ0DA5
http://ul.to/c1ywfe69
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...