I’ve taken a few moments to understand the underlying lookup window code.
To my surprise I’ve found out there is some sort of validation to check if it exists a form overriding svy_nav_fr_buttonbar_lookup_window.
Apparently it must be called svy_nav_fr_buttonbar_lookup_window_custom.
Can anyone take a few moments to explain me what are the requirements to use this functionality and how should it work??
Is this intended to be usable in svy_framework 6 or is it for the next version??
We are in the process of adding support for using your own custom forms in the framework.
So if you have a form in your solution that is called the same as a framework form, but with the postfix “_custom”, than the framework will use that form instead.
This will make it a lot easier to let the framework look the way you want it, without the pain of having to merge all your changes with newer versions of the framework.
In the latest version from our svn, this already works for the lookup form, but the idea is to add it for a lot more forms in the framework.
Obviously this is quite a big change on our end, so it is not certain yet when this will be ready.
Joas:
We are in the process of adding support for using your own custom forms in the framework.
So if you have a form in your solution that is called the same as a framework form, but with the postfix “_custom”, than the framework will use that form instead.
This will make it a lot easier to let the framework look the way you want it, without the pain of having to merge all your changes with newer versions of the framework.
In the latest version from our svn, this already works for the lookup form, but the idea is to add it for a lot more forms in the framework.
Obviously this is quite a big change on our end, so it is not certain yet when this will be ready.
Can I add my support/request for this!
Most specifically, can you/will you be adding the following forms to your ‘custom’ list?
basically the main bits around the framework that our clients see, as some of my clients want certain aspects of these changed to work better for their needs
Thanks
Joas:
Yes, those forms are on the list.
The idea is to do it for all visible forms, so basically all forms starting with “svy_nav_fr_”.
Fantastic!
Is there any chance this will be ready before the end of the year as I have a project that might go live then that I would really like to use this functionality for??
Thanks