sandal

33 ms·

211.
by sandal 17y ago
While this book will help improve your Ruby (which will help improve your understanding of Rails) the two are not one in the same. RBP won't answer any direct questions about Rails for you.
212.
Ruby Best Practices book starting its open source release early.(blog.rubybestpractices.com)
34 points by sandal 17y ago|5 comments
213.
by sandal 17y ago
This would be a good discussion for the Prawn mailing list. Post there and I'll reply with some details (and the other devs will likely chime in as well). Just let us know what sort of feature set you want to implement, and we can point yo
214.
by sandal 17y ago
Whoa! Awesome. Prawn is "fast for Ruby" but still not fast when compared to lower level implementations. How is performance here? (If it's decent, I'll definitely need to steal some ideas :)
215.
by sandal 17y ago
I really consider it. Google Groups is a fucking nightmare.
216.
by sandal 17y ago
It never will. LaTeX is the right tool for layout, for now, at least. If someone wants to implement something like that on top of Prawn, awesome. But our goal isn't to be a layout tool, it's to provide all the low level tools necessary t
217.
by sandal 17y ago
You probably wouldn't have to do that. Check into something like resque: http://github.com/defunkt/resque (depends upon your needs, of course)
218.
by sandal 17y ago
Prawn does not write postscript, it writes PDF. Though possibly similar in appearance, two different beasts, for sure. And actually, we have support for reading arbitrary PDF on edge, expect a release in a few weeks :) http://github.com/y
219.
by sandal 17y ago
Ah, interesting. Yeah, I'm certainly aware of RMagick's memory issues, fortunately, haven't had a need for it.
220.
by sandal 17y ago
Some additional relevant links: # source, wikis, bug tracker http://github.com/sandal/prawn # mailing list http://groups.google.com/group/prawn-ruby # my twitter account (I announce all Prawn releases and other stuff there -- mixed in w
221.
by sandal 17y ago
Prawn should run perfectly in JRuby, and will be officially supported by its 1.0 release. Sneak it in a .jar :)
222.
by sandal 17y ago
Yeah, I guess it's easy enough to do on your own if you have RMagick handy. Good point.
223.
by sandal 17y ago
Itext is certainly more feature complete, but Prawn is pretty capable. It probably is more pleasant syntax-wise than iText, so for simple needs, Prawn might be better. iText is almost certainly significantly faster, but I haven't benchmark
224.
by sandal 17y ago
I think that our users might appreciate a magick-prawn extension that allows Prawn::Document#to_svg (or other formats). And also, thanks for donating!
225.
by sandal 17y ago
I'm the maintainer of Prawn, and yeah, it'd be nice to see this. Jamis Buck tried this with prawn-format, but after a while we dropped support for it because it fell behind our core library and started breaking (Jamis had since moved on t
226.
by sandal 17y ago
The best way to do this is FlyingSaucer via JRuby. https://xhtmlrenderer.dev.java.net/
227.
by sandal 17y ago
I can imagine seeing some sort of label maker where you can select n days, n weeks, from now and having it spit out a use-by date. Not high tech, but something you could sell with a convincing enough infomercial and a Billy Mays look-alike
228.
by sandal 17y ago
I was expecting stats on network activity and got pictures of equipment and beer. Did I miss something?
229.
by sandal 17y ago
Yep, and that's what most of the comments on the blog are saying, and I am coming around to agree with them. To put this in context, I am discussing new Ruby 1.9 language features in Ruby 1.9, and how tap can be used to do away with a 3rd
230.
by sandal 17y ago
That's not the case at all. I was asking how you do this with dict comprehensions: http://pastie.org/573042 I'm pretty sure the answer is "you don't", unless it requires setting a variable explicitly and returning it (same as in Ruby). S
231.
by sandal 17y ago
You clearly didn't bother to read beyond the 'dumb' example.
232.
by sandal 17y ago
I am not up on my python, but I'm definitely interested in knowing more. I looked at this: http://www.python.org/dev/peps/pep-0274/ List comprehensions are great, but they're typically used for iteration/map-like functionality, right? For
233.
by sandal 17y ago
You're not the only person. I'm the author of this post and I'm not even sure I like returning() :) I'm mostly pointing out the similarity for the sake of discussion, and as it seems to be playing out in the comments, using this approach i
234.
Code Blocks: Ruby's Swiss Army Knife(blog.rubybestpractices.com)
1 points by sandal 17y ago|0 comments
235.
by sandal 17y ago
Ah, Sean is one of our bloggers but he's been dormant since the start of the blog. Maybe I can nudge him to write up some content based on this talk, as it looks quite interesting. Thanks for sharing these links!
236.
An alternative to monkeypatching in Ruby(blog.rubybestpractices.com)
12 points by sandal 17y ago|2 comments
237.
by sandal 17y ago
email sent, thanks.
238.
by sandal 17y ago
I don't know how to edit titles on HN, otherwise I'd change it to "A Technique For ..." As for the rest of the ideas here, they're all good, and if you want to write up a post about them, I'd be happy to run it on RBP Blog. We'll be openin
239.
Techniques for Duck Typing Ruby's Core Objects(blog.rubybestpractices.com)
12 points by sandal 17y ago|4 comments
240.
Interview w. Brian Ford about the RubySpec project(blog.rubybestpractices.com)
1 points by sandal 17y ago|0 comments

More ›