Can't be portable with MavensMate

I wanted to try MavensMate.  Force.com IDE is like this comfort food you can't live without, but you started to wonder whether there's a better dish to keep you healthy.

So after thinking about it for quite some time, I finally got around to actually do it today.  I don't have a Mac, but MM should work for Windows too.  I downloaded Sublime Text and MavensMate, followed the instructions (solved some little issues along the way), and ... it didn't work.  "New Project" from the menu did absolutely nothing.  So I opened the console in Sublime and noticed the error message about needing mm_workspace information.  Eventually I found the issue - basically the portable version of Sublime Text does NOT work for MavensMate on Windows, because MM would be at a loss when it needs to find the settings file.  I couldn't figure out where the connection.py file is to modify as suggested on the Github issue page (maybe because I'm using the x64 version of ST3) so I just reinstalled Sublime with the regular Windows installer, and things started to work.

Overall the first step for adopting MavensMate was a bit more involved than I expected. It's a young tool - I told myself.

Skeleton code for Batchable/Schedulable classes

I wish Force.com IDE had a quick option to generate a skeleton class for Batchable classes.  It has one for test classes, so why not this one?  For now I just paste in my own skeleton code to save typing the same stuff every time.

global class BatchableSample implements Database.Batchable, Schedulable { global Database.Querylocator start(Database.BatchableContext context) { // TO-DO: construct the actual query return Database.getQuerylocator([Select Id From Account Where CreatedDate = TODAY]); } global void execute(Database.BatchableContext context, List scope) { } global void finish(Database.BatchableContext context) { }

// schedulable global void execute(SchedulableContext context) { } }

Why did Eclipse push 4.4.0RC3 to installations?

Don't fix it if it ain't broken.

I should have thought about that when I saw an Eclipse update (turns out to be 4.4.0RC3) coming up when looking for a Force.com IDE upgrade.  But I didn't.  I went ahead with the installation.  That's probably the old system admin version of me - always get the latest version!

Eclipse wouldn't launch, complaining about JVM 1.7 as required.  Fine, I installed Java 7.  It launched then, but I was greeted with a blank package explorer (after upgrading the workspace).  Looks like the new version doesn't work with Force.com v29.

My mistake for trusting it aside, why would Eclipse push out a RC version?  In the past I never had issues with Eclipse updates.

So stick with your original Luna - it worked fine for me.  Just be prepared to reject any update they might put out there.