Spring Roo
  1. Spring Roo
  2. ROO-421

Change shell prompt to provide current entity as a 'path'

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.0.RC3
    • Fix Version/s: 1.0.0.RC4
    • Component/s: @ ROO SHELL
    • Labels:
      None

      Description

      Interesting idea from a guy that attended my Roo demo today in Stockholm:
      change the Roo shell prompt to show you what the current entity is that you're working with, as you now have to memorize that when you start adding fields and such. The prompt could provide you with feedback on 'where you are', just like a normal shell prompt.

      I liked the idea, so I'm logging it as a Jira issue before I forget about it.

      1. roo-421.png
        22 kB
      2. roo-421a.png
        8 kB

        Activity

        Hide
        Ben Alex added a comment - - edited

        Added to SVN revision 461.

        Because I spend so many happy months of each year in Sweden, I decided to complete this enhancement request immediately.

        The prompt now shows you which package or type is going to be subject of the command. For example:

        com.wedding.Hello roo> q

        The additional information is displayed in a different color for ANSI-enabled shells. Joris, would you please verify this works OK with your Windows ANSI patch?

        I implemented this carefully so as to not impact STS' shell implementation (given its shell implementation extends AbstractShell).

        Show
        Ben Alex added a comment - - edited Added to SVN revision 461. Because I spend so many happy months of each year in Sweden, I decided to complete this enhancement request immediately. The prompt now shows you which package or type is going to be subject of the command. For example: com.wedding.Hello roo> q The additional information is displayed in a different color for ANSI-enabled shells. Joris, would you please verify this works OK with your Windows ANSI patch? I implemented this carefully so as to not impact STS' shell implementation (given its shell implementation extends AbstractShell).
        Hide
        Joris Kuipers added a comment -

        That's really quick! I've tested this successfully on Windows both with and without the ANSI addon installed. One possible improvement might be to use '' for the toplevel package, to keep the prompt length down to the required minimum. It's also a nice enforcement of the '' feature for users.

        Show
        Joris Kuipers added a comment - That's really quick! I've tested this successfully on Windows both with and without the ANSI addon installed. One possible improvement might be to use ' ' for the toplevel package, to keep the prompt length down to the required minimum. It's also a nice enforcement of the ' ' feature for users.
        Hide
        Joris Kuipers added a comment -

        Hmmm, JIRA interprets ~ specially. My last comment should read:
        One possible improvement might be to use '~' for the toplevel package, to keep the prompt length down to the required minimum. It's also a nice enforcement of the '~' feature for users.

        Show
        Joris Kuipers added a comment - Hmmm, JIRA interprets ~ specially. My last comment should read: One possible improvement might be to use '~' for the toplevel package, to keep the prompt length down to the required minimum. It's also a nice enforcement of the '~' feature for users.
        Hide
        Ben Alex added a comment -

        SVN revision 469 now implements the revised suggestion of using "~" in place of the topLevelPackage. This is shown in the roo-421a.png screen shot.

        Show
        Ben Alex added a comment - SVN revision 469 now implements the revised suggestion of using "~" in place of the topLevelPackage. This is shown in the roo-421a.png screen shot.

          People

          • Assignee:
            Ben Alex
            Reporter:
            Joris Kuipers
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: