ENV['SPROUT_HOME'] Not defined about project-sprouts

[lukebayes]

Sorry for the mixup - you set this value in your .bashrc, .bash_profile or System Registry. The value should point at the outer directory where the Sprouts github repo was cloned. On my system, this points to: ~/Projects/Sprouts, when contains "bundles, sprout, etc"...

This variable is used by features to avoid loading dependent sprout 'gems' while in development.

[lancejpollard]

nice, is there a way to automate that in the rakefile?

[lancejpollard]

http://github.com/defunkt/rip/blob/master/lib/rip/setup.rb

That's is pretty cool, I'm going to do something like that, see how it works for the env vars. What do you think?

Best,
Lance

[lancejpollard]

The last thing I need to learn is how to prompt the user at the terminal..., open files and listen for CMD-W/CMD-S to continue the process, sleeping, multiple threads... lots of stuff :)

Do you per chance know how to capture the CMD-W input when a user closes a textfile window?

• Lance

[lukebayes]

Hey Lance... Thanks for pushing through this stuff, I have been meaning to clean that process up - just haven't made the time. Basically, I added the mocha dependency recently with the idea that I'd refactor cross-gem dependencies out of all those packages.

As far as the ENV goes, I've generally just used the ||= operator. It'll basically allow you to assign with a default value, or use what was provided elsewhere with something like:

ENV['SPROUT_HOME'] ||= File.dirname(FILE) + '/../../'

I probably forgot to put that in a place or two.

As far as prompting the user and collecting input, it's the 'gets' command and it's pretty straightforward. Here's an example:

input = $stdin.gets
break if input.nil?
msg = input.chomp!
puts "message: #{msg}"

Capturing when a user closes a text editor seems kind of hard. I imagine there's a way to do it, but it would probably cause more heartache than it's worth. What are you up to with that idea?

The RIP link is a little confusing. I'm not exactly clear about what you're referring to in that file.

[lancejpollard]

Thanks for your help Luke, I'm going to work on that prompt stuff.

For the text editor thing, it would be nice if it just opened the ~/.bash_profile with SPROUT_... parsed in but commented out, and it said "Please enter the locations of your Flex SDKs". Just trying to make it so users don't have to know too much to get going :).

I can open the text editor like this:

system("vi #{@profile}") unless
   system("edit #{@profile}") unless
      system("mate #{@profile}")
stdout.flush
$stdin.gets.chomp

...but to continue the process you have to manually press enter in the terminal. I just thought it would be neat to know how to do that, like how svn/git commit messages work. Maybe just doing something like stepping through a bunch of prompts would be easier.

The RIP link was just about parsing the ENV variables into the .bash file. It looked interesting.

I've been working on Bundler all night and it needs a lot of work to work with sprouts, though it looks like a very interesting project. It copies all of the repositories to your application, which isn't what sprouts needs. As for RIP, it seems a bit confusing or maybe just a little advanced for my needs, plus it doesn't work on linux which might be an issue considering I deploy everything on Slicehost.

As for sprouts, I just got it so I can run "rake install:flex4sdk" or "rake install:sprout", and it'll locally install the gem from the git clone directory to wherever your gems are stored. Works well enough, and I added 'environment: SPROUT_FLEX_4_SDK' to the yaml block for the remote_file_target, so it uses my flex sdk.

Using something like bundler would be great, I'm going to look more into that.

Have a good week man,
Lance