port, you may be disappointed to find that https et al won't work. The default install does not include support for ssl, which is a variant.sudo port uninstall curlMoreover, if you have multiple versions installed, you may have to uninstall the default - in my case 7.17.0_0 (don't forget the @ symbol)
sudo port uninstall curl @7.17.0_0Finally, reinstall with the ssl variant:
sudo port install curl +ssl
ID,TEXT,COSTIn Ruby there are a few ways to go about parsing this file. You can install a gem like
1,Gumball,0.05
2,Pack of Gum,0.50
3,Pepsi,1.00
fastercsv, but I prefer just to parse it directly. You can also just skip the first line and assume a standard layout of data, but this is a little error prone if anyone decides to add or remove columns. It's easy to build a header lookup from that first line, like so:h = line.split(',')
headermap = Hash[*h.zip((0...h.length).to_a).flatten]This splits up the string by commas into an array, then uses the array's "zip" method to pair each element with a number - from the range 0 to length-1, then flattening, giving us an array that looks like this:["ID",0,"TEXT",1,"COST",2]Then we pass in the array as an unbounded param list and use the Hash[] function to create a map like this:
{"COST"=>2,"ID"=>0,"TEXT"=>1}Pretty nifty for two line, eh? That way we can split up each row by comma, and access the array position by the header name, rather than a magic number:SEPERATOR = ','
data_ary = []
hm = nil
IO.foreach(filename) do |line|
unless hm
h = line.split(SEPERATOR)
hm = Hash[*h.zip((0...h.length).to_a).flatten]
else
d = line.split(SEPERATOR)
data_ary << {
:id => d[hm["ID"]].to_i,
:text => d[hm["TEXT"]].to_s.downcase,
:cost => d[hm["COST"]].to_f,
}
end
end
# An array of hashes
p data_ary #=> [{:id=>1, :text=>"Gumball", :cost=>0.05}, ... ]
require 'net/pop'
BASE_DIR = "/tmp/attachements"
Net::POP3.enable_ssl(OpenSSL::SSL::VERIFY_NONE)
Net::POP3.start('pop.gmail.com', Net::POP3.default_pop3s_port, 'email@gmail.com', 'passwd') do |pop|
if pop.mails.empty?
puts 'No mail.'
else
pop.each_mail do |email|
msg = email.pop
msg.scan(/content-type: application\/octet-stream;\s*name=(.*?)\s*content-transfer-encoding: base64(.+?)(---)?/m) do |v|
filename = $1.to_s
data = $2.to_s.strip.unpack('m*')
File.open("#{BASE_DIR}/#{filename}", File::CREAT|File::TRUNC|File::WRONLY) do |f|
f.write(data)
end
end
end
end
Hey guys! I'm having this problem and can't find an answerOnly to be responded to hours later:
please help!!! :(
[Some trace or dump]
Thanks;
Random Asshole
Random Asshole wrote:Do you not see the problem here? Irony aside, you're just plain being a dick. I have a rule. Let's call it - oh, I don't know - the Golden Rule: Treat others how you want to be treated. Remember that one? If not, learn it. Its reach extends beyond the elementary school playground.
>
> Hey guys! I'm having this problem and can't find an answer
> please help!!! :(
>
> [Some trace or dump]
>
> Thanks;
> Random Asshole
Ok, I figured it out and it works... ;)
<img src="/images/firefox.gif" />With:
<div id="ffimg" />Using CSS, we can create an object of similar height and width, setting the background image as the image we wish to see:
#ffimg {
width:211px;
height:92px;
background-image: url('/images/firefox.gif');
background-repeat: no-repeat;
background-position: 0px 0px;
}This is such an old trick you can find it painted on cave walls. A user will see the image in their browser as though it were inline via the img tag. Sure, you gain flexibility, but the way this ball lays we don't exactly gain any strokes. If we do this with 15 images, the browser still must make 15 requests to the server - but we are one step closer.
Our next task is to create an image that contains all images we want loaded onto the page. The SnipSnipe version is right here.#ffimg {
width:211px;
height:92px;
background-image: url('/images/big.gif');
background-repeat: no-repeat;
background-position: -208px 0px;
}This example shows a 211x92 pixel area of the big.gif image starting 208 pixels from the left side of the div (you must make them negative numbers since they shift left).acts_as_taggable entirely with acts_as_ferret. The benefit here is two fold: one, it reduces model complexity, which currently looks something like this (seriously):class Code < ActiveRecord::BaseMore importantly, two, it increases the flexibility of searches. I like the idea of giving the model semantic metadata, which I already do somewhat (tags pull double-duty as a desciptor of the snippet as well as specifies how the code is to be highlighted - code tagged 'xml' will be highlighted differently than code tagged 'java' - it currently won't let you choose both). I'd like to be able to choose multiple tags, like "maven", "java", "plugin" and let the system drill down for me. Currently you can only sort by one snippet at a time.
acts_as_taggable
acts_as_voteable
acts_as_commentable
acts_as_favorite
acts_as_ferret
end
