pgr,
I am the developer that CustomMachine referred to.
We are currently at version 7.7.9 and have made extensive customizations to that version.
You have said " It isn’t complicated to get the filters panel to show all the time, instead of having to click to open" but that is not everything that is required to get the user interface back to the functionality that our users are comfortable with.
Our users are comfortable with the Search view panel displayed above the List view and we have many custom fields that they need to use as filters. Opportunities, for example, has 36 filter fields (4 across by 9 down) and the users are familiar with frequently-used filter locations on the page.
In the current version, we see that these filters would be presented in a scrolling list which is displayed by clicking the filter/funnel on the List view. This would require that the users click the funnel and then scroll through the lengthy, single-field wide list possibly numerous times to set all of the filters for their desired List view.
So as I see it, the modifications required (for every module we use which are all of the standard ones plus 10 more custom modules) would be to reformat the Search view back to 4 wide instead on 1 wide and modify it so it displays and stays at the top of the List View page.
As I am just trying to understand the extent of changes required right now, I do not yet have an instance of the latest version currently configured but I have looked at some files changed in Github. Could you discuss in general terms the changes necessary to a single module in order to get this working?
For example (based on experience with versions 7.7.9 and prior), I would anticipate needing to modify the metadata/searchdefs.php files for each module to set templateMeta maxColumns to 4 to keep my 4-wide search filter list. But I see that templateMeta is no longer in the Github searchdefs.php files, so I am concerned that it is no longer utilized in the latest version. If, prior to upgrade, I created custom versions of all metadata/searchdefs.php files with templateMeta would templateMeta 4-wide functionality still work?
And I assume (this is the area that I am not very familiar with), custom changes would be required to each module’s ListViewSmarty.php or would the changes be made in the common include/ListView/ListViewSmarty.php. I see extensive changes to this file in Github. I see many new flags were created. It would be very handy if setting these a particular way would achieve my desired result. But perhaps that is too much to wish for
For each module…Would custom TPL changes be required as well? Changes to view.list.php?
Thanks in advance for your assistance. By the way, I personally do like the new interface. I think that it is much cleaner and allows better display of the List View.
Dianna