Streamlined now Postgres-enabled
Posted by jgehtland Sun, 27 Jan 2008 15:55:19 GMT
Streamlined is now proud to be 100% Postgres-compliant. If you are a Postgres user, Streamlined now does everything you want and has a full test suite to prove it.
Posted by jgehtland Sun, 27 Jan 2008 15:55:19 GMT
Streamlined is now proud to be 100% Postgres-compliant. If you are a Postgres user, Streamlined now does everything you want and has a full test suite to prove it.
Posted by Jason Rudolph Fri, 25 Jan 2008 21:27:44 GMT
If you’re up for livin’ on the edge, Streamlined has been enjoying sweet bliss with Rails 2.0.2 for a few weeks now.
Wanna try it out? Just grab the edge bits…
script/plugin install http://svn.streamlinedframework.org/edge/streamlined
...and you’re good to go.
As always, if you notice any issues, be sure to drop a ticket in Trac. In the mean time, we’re well on our way to a formal 1.0 release candidate in the near future. Stay tuned.
Posted by jgehtland Tue, 30 Jan 2007 23:59:20 GMT
One of our (very helpful) users asked the question on the mailing list: “You say 0.0.6 is Rails 1.2 compliant, but is it backward compliant with Rails 1.1.6?”
The simple answer is “no”. But the just slightly less simple answer is: here’s what to do about it.
Open /vendor/plugins/relevance_extensions/init.rb and comment out the line that reads:
Dependencies.load_paths.unshift("#{RAILS_ROOT}/app/streamlined")
Then, open up /vendor/plugins/relevance_extensions/lib/streamlined_controller.rb, and uncomment the two lines:
# require_dependencies :ui, Dir["#{RAILS_ROOT}/app/streamlined/*.rb"].collect {|f| f.gsub(".rb", "")}
# depend_on :ui, Dir["#{RAILS_ROOT}/app/streamlined/*.rb"].collect {|f| f.gsub(".rb", "")}
That’s it! The rest is all compliant in both releases.
Finally, if you are going to run it in Firefox 2.0, there is a bug in Prototype. You can monkeypatch it Add the following at line 865:
// patched as suggested in http://dev.rubyonrails.org/ticket/6579
for (var name in headers) {
if (typeof(headers[name]) != 'function') {
this.transport.setRequestHeader(name, headers[name]);
}
}
We’ve submitted that patch back to Prototype, and are waiting to hear if it gets adopted. Without this patch, everything still works fine in IE, Safari and Firefox 1.5 (and, yes, Opera). Only Firefox 2.0 seems to be affected.