[Qt-interest] Plugins vs Dynamic dialogs

[Constantin Makshin]

I think the second approach should be OK because it's more flexible and, probably, easier to debug — you can add/update/remove forms in run-time without need to develop complex plug-in system, there's no need to worry about memory-related errors ([de]allocation, pointers, leaks, etc.), etc..

Write common and performance-critical functions in C++ and implement data-entry forms using .ui and/or scripts.

On Wednesday 14 July 2010 09:42:38 Harry Sfougaris wrote:
> I am about to begin a development on an application which will mainly function as database front-end, with many data-entry forms (ranging from simple to complex, each adhering to specific business rules).
> 
> I am not sure what would be best in such a scenario: 
> - grouping the forms into modules and creating a plugin for each module where all design and behavior is hardcoded, or 
> - implementing the forms as standalone .ui files and loading them with QUiLoader as needed (I will most likely need to have an accompanying script with each .ui file to customize it's behavior).
> 
> Does anyone have some experience/recommendations they can share?