Posted by Rob Wed, 12 Sep 2007 13:19:33 GMT
We are happy to announce the release of Streamlined 0.9 final. This latest release includes numerous bug fixes and patches, and Streamlined is well on the way to 1.0 goodness.
Many thanks to all the contributors and users who are enjoying Streamlined and participating on the mailing list.
—
Release Notes (including detailed information and screen shots)
Posted by Jason Rudolph Thu, 23 Aug 2007 08:41:38 GMT
The Streamlined team is pleased to announce the availability of version 0.9 RC2 of the Streamlined framework. Some of the features you’ll find in this new release include
In addition to beefing up the docs and implementing the enhancements discussed above, the Streamlined team has knocked out numerous bugs and upped overall the quality of the framework as a whole.
From small usability tweaks (like rendering empty lists in a more aesthetically pleasing fashion) to ambitious features (like advanced filtering) to more rigorous tasks (such as increasing test coverage), this release marks an important milestone on the road to Streamlined 1.0. We hope you enjoy it!
The Streamlined team kindly thanks the users and patch contributors that have helped us reach this important milestone. Streamlined continues to ease our Rails development efforts day in and day out, and we hope you find it equally as useful and enjoyable.
—
Release Notes (including detailed information and screen shots)
Posted by Stu Fri, 27 Jul 2007 18:35:22 GMT
In the course of fixing a bug, I bit off of significant refactoring I have wanted to do for a while. Instead of saying this:
# old way class PoetUI < Streamlined::UI # declarative settings end
You can now say this:
# new way Streamlined.ui_for(Poet) do # declarative settings end
The new syntax is more testable, since it does not rely on singleton methods and inheritance. It also makes it much easier to break the default 1-1 relationship between models and ui instances. The old syntax is still supported, via a bit of method_missing trickery. But I am sure there are some breakages, and I would like to deprecate the old syntax over time. Kick the tires and let me know if you have any problems.
Posted by Luis Sat, 21 Jul 2007 01:13:01 GMT
Whenever I talk to someone about Streamlined, they usually ask about how they can customize the look. I’m going to cover how to change the look of the list / index view as of the state of the edge before the 0.9 release comes out.
You can do this by creating a UI class for your model by executing “rake streamlined:model MODEL=your_model_name”. This will create a ModelUI class in app/streamlined and affects the views for that model.
If you’ve tried Streamlined before, then you’ll know that when you’re viewing the list view for a model, then you’ll see a paginated table that contains all the instances of the model. Each row has one instance, along with three buttons: one to go to the show view of the instance, the second to go to the edit view of the instance and a third to delete the instance. Below the table, there’s a few more buttons with the most important one being the one to create a new model instance.
There’s already pretty good documentation on how to modify which columns show up, so I’m going to focus on the other options.
First, you can add custom headers and/or custom footers by adding the linesheader_partials :list => 'shared/my_custom_header'
footer_partials :list => 'shared/my_custom_footer'and then of course creating the header / footer partial and putting it in the place you specified. Second, you can turn off the delete button for each row. Perhaps you want to ensure that users delete from the show view or perhaps users should not delete instances of your model at all. Do this with
quick_delete_button falseThird, you can turn off the edit button for each row.
quick_edit_button falseFourth, if your model is read only, then you can turn off the new and edit buttons by adding the line
read_only trueNote that you can still delete, so you’ll have to specify quick_delete_button false like above if you want that. I’m not sure if that’s the right behavior. Any thoughts on that? Fifth, you can turn off all the buttons that link to show/edit/delete by adding the line
table_row_buttons falseSixth, you can turn off pagination via
pagination falseSeventh, you can turn off filtering via
table_filter falseEighth, you can add custom CSS styles via
style_classes :list => {:row => 'person_row'}
which means that each row will have a CSS class person_row which you can then specify in a stylesheet.
That’s it for customizing the list view declaratively. I’ll make sure all of this gets into the wiki. Please let me know if I missed anything. If there’s another way you’d like to customize the list view, please add a ticket in Trac or leave a comment here.
Posted by Stu Thu, 19 Jul 2007 23:38:48 GMT
The following lines have been removed from acts_as_streamlined for the upcoming 0.9 release:
if defined? AuthenticatedSystem include AuthenticatedSystem before_filter :login_required end
The team discussed it, and we (mostly) agreed that developer should choose to add AAA’s filter themselves—Streamlined shouldn’t automatically choose it for them.
If you are using Streamlined with AAA and you want to require login, you will need to add the before_filter to your own controllers.
Posted by Stu Thu, 19 Jul 2007 22:11:16 GMT
I have committed a fix for Trac 43 as svn 565. It seems that some code paths through Rails Connection.quote use sprintf internally, while others do not. So we now pass %% which either acts as an escape, or doesn’t.
Is passing the unnecessary % on to the database is innocuous? It feels dirty. Is this a bug in ActiveRecord?
Posted by jgehtland Thu, 19 Jul 2007 16:57:05 GMT
Due to a rash of Trac spam, we’ve had to turn off anonymous ability to modify pages or tickets on the Trac install. To do so, you simply have to create an account, which is easy and free and we don’t use your information for anything. Ever.
Sorry for the inconvenience, but it will help keep the Trac instance clean.
Posted by Stu Sat, 30 Jun 2007 08:52:16 GMT
Trac is now at trac.streamlinedframework.org. Please update your links, I will be turning off the old links on port 8079.Posted by Matthew Mon, 25 Jun 2007 09:48:00 GMT
We’re excited to announce a new feature in Edge that will make it much easier to use Streamlined’s default actions while still having control over what gets rendered afterwards. Render filters allow you to tack additional code onto the end of a default action.
Matthew demonstrated these filters in a very early form at the Streamlined tutorial at RailsConf last month. They have since become much more useful and flexible. By using these filters, we’ve been able to stop copying and pasting default actions into our controllers only to make a single small change. Now, we can make the small change declaratively without redefining the action.
For example, what if you prefer that Streamlined redirect back to the list view instead of the show view after updating a record? You would add this render filter to your controller:
render_filter :update, :success => Proc.new {
redirect_to :action => 'list'
}
What this says is that the Streamlined’s default update action should redirect back to the list action on success. (Render paths can also be defined for failure.)
The contents of the Proc are called in the context of the controller action itself, allowing you to redirect, assign new instance vars, etc. (Pretty much anything you can do inside a controller action.)
More examples and documentation can be found on the wiki.
Posted by jgehtland Fri, 15 Jun 2007 10:55:19 GMT
Here’s some new features we’ve added in Edge, which are all documented over on the Wiki as well:
:options_for_selectattribute.
class PersonUI < Streamlined::UI
style_classes :list => {:row => 'person_row'}
end
Each row in the list (in LIST context only) will be wrapped in the CSS style “person_row”.And plenty more. Keep an eye on the Wiki and the Trac Timeline for more.
Theme Credits: Phokus by John Serris