View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|06485||Development||[All Projects] Expression Manager||public||2012-08-15 15:13||2012-11-26 22:25|
|Target Version||Fixed in Version|
|Summary||06485: Expression manager link doesn't seem quite right|
In the survey bar under the tools menu the link to the expression manager takes me to /index.php/admin/expressions which isn't survey specific and doesn't match the LimeSurvey GUI. In addition, clicking the Show Survey logic file link on this page leads to a PHP error since no survey ID is specified.
I propose that we link directly to index.php/admin/expressions/survey_logic_file/sid/SURVEYID since that's the only page that has useful survey-specific information. There's no reason for the unit tests to have accessible links pointing to the from the admin menu.
|Tags||No tags attached.|
Personally, I'd recommend putting the EM link on the main admin bar, and not make it survey specific (since it is not survey-specific).
If the team wants to refactor what it contains, that is also fine.
We certainly want easy access to the unit tests ourselves, but general users don't need that.
However, they should have access to:
Sounds fine to add a new main menu link to EM for a function list and unit test as long as it conforms to the UI unlike what we have now. I observed that there's already a link in the survey menu for generating the survey logic file, though it could use to have it's UI improved. In that case you would also want one for conditions conversion.
Here's my proposal
ajs, sounds fine - can you do it?
ajs, those are good ideas. I'd also recommend adding the following. I had these in my old system and they were very helpful for testing and debugging complex surveys:
(1) Design-time: add pop-up window that can stay active into which authors can type EM expressions and see the results. This would be similar to the Integration Unit Tests which show four columns: (a) raw string, (b) syntax-highlighted string, (c) results, (d) list of variables used (color coded to show whether there were any syntax errors).
All of those sound like good things to do, but I'm guess we'll want them to wait until 2.1+. I'll work on the basic stuff I listed above as soon as I finish my project.
Fix me! ;)
||Status||new => assigned|
||Assigned To||=> TMSWhite|
|2012-08-15 18:21||TMSWhite||Note Added: 20431|
|2012-08-17 15:17||TMSWhite||Assigned To||TMSWhite =>|
|2012-08-17 15:17||TMSWhite||Status||assigned => feedback|
||Note Added: 20540|
||Status||feedback => new|
|2012-08-20 13:10||c_schmitz||Note Added: 20547|
|2012-08-20 15:31||TMSWhite||Note Added: 20550|
||Note Added: 20553|
||Assigned To||=> user16774|
||Status||new => assigned|
|2012-10-02 14:58||c_schmitz||Project||Bug reports => Development|
|2012-11-26 22:25||c_schmitz||Note Added: 22564|