Subscribe to GameFromScratch on YouTube Support GameFromScratch on Patreon

22. March 2012

 

 

Adobe has recently made Photoshop CS 6 available as beta, which will last until CS6 is PSCS6released.  In order to activate, you need to have an Adobe ID ( freely available ) within 7 days of installing.  The Mac installer is now 64bit only and weighs in at just under 1GB, while the Windows install is closer to 1.7GB.

 

 

 

The biggest new features in Abobe’s own words are:

 

  • Content-Aware Patch — Patch images with greater control using the newest member of the Content-Aware family of technologies. Choose the sample area you want to use to create your patch, and then watch Content-Aware Patch magically blend pixels for a stunning result.
  • Blazingly fast performance and a modern UI — Experience unprecedented performance with the Mercury Graphics Engine, which gives you near-instant results when you edit with key tools such as Liquify, Puppet Warp, and Crop.* Plus, a refined, fresh, and elegant Photoshop interface features dark background options that make your images pop.
  • New and re-engineered design tools — Create superior designs fast. Get consistent formatting with type styles, create and apply custom strokes and dashed lines to shapes, quickly search layers, and much more.

 

 

The content aware tools are easily the biggest new feature, and look pretty impressive as demonstrated in this video:



Another good video showing off the new features is Russel Brown's 6 favorite new features:

 

 



Lynda.com have also made a number of tutorials freely available for CS6.


So, if you are interested in Photoshop CS6, or just want a free copy for a limited time, head on over to labs.adobe.com and give it a download.

News, Art

21. March 2012

 

 

As my journey with Appcelerator continues, I’ve run into another annoyance, and the fix wasn’t immediately obvious.  Titanium Studio ships with an Android 2.2 image pre-configured, although I am trying to develop for Ice Cream Sandwich ( Android 4 ).  The problem is, every time I launch my application, it would ignore the running emulator ( launched using AVD Manager ) and launch it’s own. This is really irritating, as the Android emulator takes forever to load.  ( About a minute for 2.2, and well over 5-10 minutes for ICS, on an i7 machine with 12GB of RAM! ) to say nothing of the fact their emulator image is for a phone, not a tablet.

 

 

It seemed no matter what I did, it would still load a new instance of the emulator, regardless to if I had one running already.  The answer isn’t as intuitive as you would think.  My first thought was it would be under Debug Configurations, which can be accessed by right clicking tiapp.xml in your project, choosing Debug As –> Debug Configurations…  which brings up the screen below:

 

 

image

 

 

 

Ah, this looks promising, change Android API level to Android 4.0, click Apply then debug.   Still loads the pre-configured 2.2 emulator. Sad smile  Ok, so that wasn’t it.

 

 

In the end, it comes down to how you build your project.  In Project or Package Explorer, double click tiapp.xml to bring the property editor up.  Search for the “Deployment Targets” section, then click the configure link, like this:

 

 

image

 

 

In the dialog that pops up, there is a selection for “Default Android SDK:”.  This is the value you need to change:

 

image

 

 

Now I click debug and behold!  Ice Cream Sandwich goodness!

 

image

 

 

 

Well… that was intuitive.  Not really something you can blame Appcelerator for, nor Titanium Studio ( although again Eclipse/Google Android tools make things far too complicated! ) in the end.  That said, if I could debug on a physical device, I wouldn’t have to deal with the terrible Android emulator in the first place!

 

 

Anyways, finally after a few days of messing about with configuration and install issues, finally, time for some coding!

General

21. March 2012

 

 

Hey, I’m on time this time! Well, almost…

 

 

This weeks cool thing is in an area where there aren’t too many options, audio capture and manipulation tools.  On the “pro” side, the dominant player is probably Pro-Tools, which is in a word expensive.  With pricing starting at 700$ and going up from there, it is out of the reach of many peoples budget.  Truth of the matter is, it’s probably overkill for most people too.

 

 

In the mid range you have other, slightly cheaper options such as Adobe's SoundBooth or if you are the Mac type, Apple’s Logic Pro.  Both of these apps sell for about 200$.  If you’ve noticed one thing about me though, it’s I like free stuff, I really like free stuff.

 

 

Thankfully there is a free option, and it’s pretty damned good.  This weeks CTofW is Audacity.  In addition to being a rather clever pun, it is also a “free, open source, cross-platform software for recording and editing sounds.  It is available on Windows, Linux and Mac. 

 

 

Audacity in action editing a Wav file:

image

 

 

As is pretty typical of open-source projects, it’s a bit on the ugly side, although compared to it’s open-source peers, it is the belle of the ball.  However, unlike most open sourced projects, it’s incredibly well documented.  In addition to the included documentation, there are actually a few published books including Getting Started with Audacity 1.3 and The book of Audacity.  It’s a good thing too, even though Audacity is pretty simple to get started with, it’s an amazingly deep program.  The short form description for their site goes as follows:

 

You can use Audacity to:

  • Record live audio.
  • Convert tapes and records into digital recordings or CDs.
  • Edit Ogg Vorbis, MP3, WAV or AIFF sound files.
  • Cut, copy, splice or mix sounds together.
  • Change the speed or pitch of a recording.
  • And more!

 

 

 

Instead of going into depth here about what this program can do, I’ll refer you to their feature list.  And I promise you, that list just scratches the surface.

 

 

So, if you are looking for a audio capture and manipulation application and are doing things on a budget, you really can’t do better than Audacity.  Seeing as it’s free and only a 20MB download, what have you got to lose?

Cool Thing of the Week

20. March 2012

 

 

As you might have noticed from my previous post I am currently evaluating Appcelerator and I have to say, the early frustrations are far too common.  In the future I may do a full review, if I don’t give up on it completely.  For now though, let me share a few of the issues I’ve run into, beyond the one described in the previous post.

 

 

Failed to find Javac.

I got an error the first time I tried to compile my code, stating that it failed to find javac. So I opened a command prompt, CD to %JAVA_HOME% and there it is.  WTF?  Some Googling later and I discover it doesn’t support file paths with spaces!  Seriously?  What, is this 1994?  Moved Java to c:\jdk and problem went away.  Seriously, when was the last time you ran into an app that didn’t support spaces?

 

 

Blackberry Support

A big part of why I chose Appcelerator in the first place is support for iOS, Android AND Blackberry, as I have all three tablets in my house.  I go to make a Mobile application in Appcelerator and Blackberry is grayed out.  I click through to a “Get SDK” link, download 500mb of Blackberry stuff, restart Appcelerator Studio and… Blackberry is still grayed out.  Turns out this is a “pro only” feature…  and that’s only discovered by reading a forum post, their own documentation says nothing of the sort!  Disappointing, not only that it’s a premium feature, but because they didn’t indicate this anywhere, the UI suggests otherwise, causing me to waste a couple hours of my life.

 

 

Android device support

So, native blackberry support isnt a huge deal, now that you can bundle Android apps as Blackberry Playbook apps, so I continue on targeting just Android.  I configure and setup the Android SDK, create a demo app, launch it on by Transformer, all good so far.  So I set a breakpoint, hit debug and…….. the emulator launches.  If you’ve done any Android development, you know using this emulator is somewhere between an 8 and 9 out of 10 on the “Things that hurt” scale.  It is sloooooooooooooooow.  But get this, Appcelerator can’t debug on device, emulator only.   This.  Sucks.  Hard.

 

 

 

 

So, let’s just say, after two days I am extremely unimpressed, and I haven’t even got around to coding yet!

 

 

Anyone out there have prior experience with Appcelerator?  Am I just hitting all the bad stuff up front, or is this what I should expect as the norm?

General

17. March 2012

 

 

 

So I have decided to give Appcelerator Titanium a shot for a cross platform mobile project I am working on.  If you are previously unaware of Appcelerator, it is basically a cross platform framework where you program in Javascript and can natively target a number of mobile devices including Android, iOS or in this case Blackberry.  That said, the IDE is based on Eclipse, so that means I am going to develop a number of new pains in my backside.   Lo and behold, I wasn’t wrong.

 

 

Installed the app, went to make a project and BLAMMO, hit the first wall.  Apparently you need to install the Android and Blackberry SDKs.  This of itself is no big shock, the problem arises when you try to install the Blackberry Java SDK which as you can see, you can either download as a pre-configured Eclipse install, or you have to use the Eclipse Updater.  As my Eclipse install is Titanium itself, I obviously have to go the updater route.  Fortunately, Appcelerator already has the Blackberry updater site configured, but then I hit the wall.

 

 

 

You select Help->Install New Software… select the Blackberry Update Site, then select the Blackberry Plugin, like so:

 

image

 

 

Of course, this is Eclipse we are talking about, so of course it isn’t going to work, throwing up the following error:

 

Cannot complete the install because one or more required items could not be found.
  Software being installed: BlackBerry Java Plug-in (core) 1.5.0.201112201607 (net.rim.EclipseJDE.feature.group 1.5.0.201112201607)
  Missing requirement: BlackBerry Java Plug-in (core) 1.5.0.201112201607 (net.rim.EclipseJDE.feature.group 1.5.0.201112201607) requires 'org.eclipse.jdt.debug.ui 0.0.0' but it could not be found

 

 

Oh joy.  Off to Google I go!  Sadly, I didn’t find an answer, but a few minutes later I puzzled it out myself.  If you are using Titanium Studio and run into dependency errors like this, there are a few things you need to change to fix it.

 

 

In the Available Software dialog, click the “Available Software Sites” link:

 

image

 

 

Check the box beside Eclipse Update site like below:

 

image

 

 

This will give you access to all the various Eclipse updates.  Finally back on the updates screen, you want to verify that the “Contact all update sites during install” checkbox is checked:

 

image

 

 

 

With this change, the Blackberry SDK install will be able to resolve it’s dependencies and complete the install.

 

 

 

 

It’s a small thing, but if you are just starting out with Eclipse, this is the kinda showstopper garbage that make me hate recommending this tool.

General

Month List

Popular Comments

Setting up Java, Android SDK, GWT plus Eclipse or IntelliJ to work with LibGDX–Video Tutorials
Subscribe to GameFromScratch on YouTube Support GameFromScratch on Patreon


12. November 2014

 

The title pretty much says it all.  The installation process to get a fully working Java, Android and GWT development environment up and running can be a bit tricky at times.  These three videos walk through the entire process, from downloading and installing a Java JDK, then the Android SDK and GWT then finally creating your first LibGDX project.  The second video then looks at working with IntelliJ IDEA with LIbGDX, the third video shows the same thing for Eclipse.  Each of these videos walks through loading a project, then running a Desktop, Android then HTML5 project.  Each of the videos is hosted on YouTube and is available in 1080p.  Click the link above the video below to open it directly in YouTube.

 

Part 1: Configuring a Java Development Environment for LibGDX and Android Development

 

 

Part 2: Using IntelliJ IDEA with LibGDX

 

 

Part 3: Using Eclipse with LibGDX

 

Programming , ,

blog comments powered by Disqus

Month List

Popular Comments