Good morning friends PHPRunner .
After using this product for many years , I would suggest some features that I think could help improve their use.
Sorry if my English is not understood. I am speaking, however will do san use google to translate what I mean.
The screenshots are from another application, I use them as an illustration to show what I mean.
The progress of a version 7.0 is impressive, but could be better if you take into account these suggestions.
1 RUN STORED PROCEDURES : The ability to call or execute stored procedures , passing parameters. This option should be where you create views , reports . In form to display the results of the stored procedure must have the ability to set another form through which details the parameters that usuaruio get in, including the ability to validate these values entered by the user.
2 VIEWS / REPORTING TABLES MULTI : When you create a view / reports , PHPRunner necessarily compels you or believed to descend from a table . This restriction apparently because for key field validation . This subsequent effect on their ability to do searches , etc. . But generally are multitable views , so it would be necessary not to restrict it down to a table. Or better yet ask if created from a single table or multitable .
3 DYNAMICALLY GROUPED LIST FORM : In the form that displays the reports gives you the possibility to display them grouped , which is excellent.
It would be excellent list form also has the ability to group but dynamically. In the development stage, would set the fields and the order in which they grouped, and then at runtime can enable or disable fields (default under development) through which you want the data grouped together dynamically.
A small screenshot of how it could be. Here you just need to select options that allow the fields by which you want to group.
An example with dynamic grouped.
4 NEW FORM OF DISTRIBUTION LIST OF MASTER - SLAVE : Currently the organizational form of the listings master / slave is from top to bottom (vertical ). However, to improve visibility and user handling of this type of application it is suggested that there is further the possibility that the distribution of left to right (horizontal). The new distribution is far more intuitive to use for the user.
Below is a screenshot of what could be.
Another example with 03 levels.
One possibility distribution more could be next.
5 MDI FORMS : Currently you can only have a single form, which in turn contains with the help of ajax ( slave master case ) to others, but visually appears to just one. What this suggests is that there is a form main compartment, inside contains one or more forms, and that the developer can decide what to put in each of them. Even there the possibility of passing parameters from one form to another , which means that a form react based on the information provided in the other.
Below is a screenshot of what could be.
another example
6 VARIOUS DATABASE CONNECTIONS: Until the current version, you can only work with a single database connection, but in the practical development requires the application to access more than one database, including different type (eg mysql and sql server at the same time). This gives higher final application data can integrate different database engine.
7 ENCRYPTED PASSWORD : Currently you can encrypt the password or any specific field . In the case of passwords only for users that are logged by the application running, but that does not apply to users who are already registered .
In the hope that these suggestions are taken into consideration and hoping to be implemented in version 7.0.
Sincerely .
Pasquito .