Closed JRJurman closed 10 years ago
@kristenmills, @nicolasmccurdy, @ethanjurman... If I could get your :+1: on this, I think this is a much cleaner way to do this code, but I won't merge until you guys have given it a quick look through...
:thumbsup: The "around x movies" (especially w/o colorize) is a bit much information, that ultimately doesn't have much use being printed every other line (but besides that... most excellent)
@ethanjurman in the end, the example scripts are just for show... Besides, the script totally yells at you for not using colorize, so that's YOUR fault! :P
Or we should just look at the branch gem-nokogiri. I like that one.
@JRJurman It looks good to me!
@kristenmills :+1: I agree with all of this, and I do think the gem format would help organize things further. And gem-nokogiri
is just a merge of gem
and nokogiri
.
@nicolasmccurdy && @kristenmills I made it more gem-y, take a look, tell me what you think!
Add dependencies to the gemspec then i say :shipit:
colorize should be a dependency too
@kristenmills it's not actually used in the lib/, does that make it a dependency, if it's only in examples?
If that is the case, I might just nix the examples (or un-colorize them)
If the examples stay, it should be included in the dependencies. Just so the examples are runnable without any extra work. It could be a development dependency though.
There's no gem-ification, besides a few folder structure changes, but it's using nokogiri to pull in website data, and there's a formal Film.rb and List.rb which contain logic for pulling data from a given film and list, respectfully...
The examples have been modified to produce the same output with these new classes, using a hash of functions that are called in points in the class (I don't know if this is necessarily the ruby way to do this, but I think it worked out nicely).