GUI CL prompting issues. What are the plans (even with TurnOver)?

[craigs@xxxxxxxxx]

I have some issues with GUI CL prompting mainly with forcing apostrophes.
I have to really watch the result of the prompt.  I know this is still in
the works but I wanted to let you know some issues in case you weren't
aware.
Is there a fix in the makings for not forcing apostrophes when prompting
the CHGVAR keyword when it is an expression in CL?  For example, "CHGVAR
VAR(&X) VALUE(&X + 1)" after prompt shows "CHGVAR VAR(&X) VALUE('&X + 1')".
Same with *CAT or "CHGVAR VAR(&XA) VALUE(%SST(&YA 1 3))" show up with
('...').
Any mods in the works for allowing changing of tags and comments on the
prompt?  What about prompting within a prompt?
I can live with this but I was wondering what the plan was for GUI CL
prompting and what fixes were planned.  I was also wondering how TurnOver
plans to integrate the library list with the GUI CL prompt instead of using
the default on the logged on userid.  Is the focus of GUI CL prompting
actually going to be on the Lpex editor?

Thanks,
Craig Strong