Symphony.

The Symphony backend features three new pages that let you independently manage datasources, events & utilities. In Symphony 2.x they are all listed in a single page and sometimes I just need some time to realize where I can found my datasources, as “Components” doesn’t feel right to me at first glance.

I thought it was a good idea to include those changes in Symphony 2.2, thus I forked the project on github and commited a patch that replaces the “Components” page with “Datasources”, “Events” and “Utilities”. The code is based on Rowan Lewis’ Datasource Index with few additions. If you like the idea, maybe those changes could be merged into the integration branch.

Hoping to have done something appreciated, feel free to comment!

This will be solved in Symphony 3 so I’m not sure if it should be backported or not. It depends an the concept how to deal with the two core branches. In my opinion this could be solved by an extension which should be the way to go for 2.2.

I wrote an extension for that, but there are limits. For example: I couldn’t modify the href attribute of “View all Data souces/Events/Utilities”, which still pointed to blueprints/components. Of course this can be done with jQuery, but it looks like a ugly workaround to me. I suggested to merge it into the integration branch because it resembles the way Symphony 3 solves the problem.

If Symphony 2.2 is meant to be the last stable release before Symphony 3, then we must ensure to provide a product which is safe but also efficient to use. In fact, everybody will look at it for their public projects and new members will test it to understand if it’s the best choice for them.

Security is an important issue, but as a UI/usability guy I also care about workflow and productivity. It’s never early to make users more productive.

I agree with you that Symphony 2.2 shouldn’t add new features, but this change is not disruptive and aims at making the interface more effective. Together with new delegates and further small changes, this one in my opinion fits nicely as an interface improvement.

I agree with you that Symphony 2.2 shouldn’t add new features

It’s okay for 2.2 to have some feature additions so long as there is a clear upgrade path from previous versions in the 2.x branch.

I’m definitely adding a +1 to this feature request for 2.2, I think it would help make the platform look and feel a whole lot better and consistent across the pages.

The WGs have decided that since this can be achieved with an extension, it’ll be left out of 2.2 — development effort is needed on higher priority items.