As a side note, I managed to drop it into an existing ActiveResource-using app with this code:
module HashAccessor
def method_missing(method)
value = self[method] || self[method.to_s]
raise NoMethodError.new unless value
value
end
end
Hash.send :include, HashAccessor
module ActiveResource
class Base
def self.find(from=nil, params={})
resource = from == :all ? self.collection_name : self.element_name
values = QAR::Resource.new(self.site.to_s, resource).find(from, params)
end
end
end
Qt's a pretty general toolkit for C++ applications – a pretty huge chunk of it has nothing to do with GUI programming (and what, for instance, the KDE desktop and associated tools are built on):
It's a kickass toolkit (and my toolkit of choice) for cross-platform desktop apps. Just keep in mind that it's GPL licensed for free apps and that the commercial license is expensive for a one-man shop.
As somebody who has dealt with ActiveResource in a production environment, thank-you!
My company noticed an absolutely whopping performance boost when we dropped XML in favor of JSON for a transport format, fwiw. Ruby has quite possibly the slowest XML parsing libraries on the block (even when you wrap libxml), and we avoid parsing XML at all costs now.
