Closed dregad closed 4 months ago
I have no clue where the highlighting is handled in the sidebar. Now there is an option to have one field to hold the full query (which was already there behind the scenes). When using this option, I can (currently) not support additional filters while scheduling. Most of the points I will handle in the very near future:)
I have no clue where the highlighting is handled in the sidebar.
On second thoughts I'm not sure the Core API actually allows this. Need to check.
Almost all changes are embedded in version 2.16 with the exception of:
Use a separate section to add new Definitions / Schedules and to list existing ones
I prefer this lay-out since you also see what is there before adding something
With this reasoning it would be more logical to have the Add section at the end of the list, which is not so different from what I'm suggesting (e.g. manage_prof_menu_page.php).
Anyway it's your plugin so do as you want, I'm just saying 😉
do think it is better to change to standard levels. So this will end up in the next version.
👍
Looks much nicer now, thanks !
Some more comments
Suggest using smaller Action buttons (btn-xs
class) as shown in screenshot below.
All available in verrsion 2.18 (thanks for helping out to get all in line).
Plugin is generally not conforming to MantisBT standard.
There a lot of things to say here and I don't have so much time to write it all up, but here are a few things to get you started
Configuration <==> Maintain Schedules
header which looks kind of weirdU
/A
) levels for restricted queries, why not simply use a standard Access Level threshold ?Is there really an added value to split a query into 6 distinct fields, instead of using a single, larger textarea ? It makes maintenance unnecessarily complex, as you can't just copy/paste the query from your favorite SQL tool.
Edit Query screen layout is kind of weird with label above textarea and help text on the left, I think it would be better to have more standard layout with label on left and input field on the right, with help text either below the label, or above / below the input field (lookt at Source Integration plugin config page for example).