Create a "Standalone mode" staff client shortcut in the Windows installer

[Dan Scott]

This is a wishlist item.

Occasionally, network issues force the client to hang waiting on a response from a dead server and make it hard for staff to launch standalone mode, as the button on the full client won't respond.

Recent versions of Evergreen include additional command-line options for launching the staff client in standalone (offline) mode. However, many users are not comfortable with the command line.

Therefore, the desire is to teach the Windows installer to include a shortcut that launches the staff client into standalone mode.

[Dan Scott (denials)]

Hi, we use "In Progress" to indicate that a committer is testing a proposed branch or patch, so I'm setting this back to the previous status until such time as the bug has been tagged "pullrequest" and a committer starts looking at it.

[Pranjal Prabhash (pranjal-prabhash)]

In the file windowssetup.nsi, we have to add the following lines:

After line 106: CreateShortCut "$SMPROGRAMS\$ICONS_GROUP\Evergreen Staff Client (Standalone).lnk" "$INSTDIR\evergreen.exe" "-ILSoffline" "$INSTDIR\evergreen.ico"

After line 270: Delete "$SMPROGRAMS\$ICONS_GROUP\Evergreen Staff Client (Standalone).lnk"

[Jason Etheridge (phasefx)]

On Fri, Apr 6, 2012 at 12:40 PM, Pranjal Prabhash
<email address hidden> wrote:
> In the file windowssetup.nsi, we have to add the following lines:

Pranjal, you should give diff (and patch) a try. Ideally, you'd give
us a link to a git branch, but a patch file produced by diff is better
than asking us to hand-edit a file (though for one-off contributions
we probably wouldn't mind, so don't let that scare other would-be
contributors--I think we're just hoping for more from GSoC students).

-- Jason

[Jason Etheridge (phasefx)]

Also, we still don't want the ticket to be In Progress yet. Once you're happy with the patch you're providing us, you should add a "pullrequest" tag to the ticket. Someone handling the request will change the status to In Progress.

[Pranjal Prabhash (pranjal-prabhash)]

Please find attached my patch for this bug.

[Pranjal Prabhash (pranjal-prabhash)]

New patch fixing a minor error. Tested on a windows 7 machine.

[Michael Peters (mrpeters)]

To make for easier testing by the devs, I've pushed a branch for you, this time Pranjal.

user/mrpeters-isl/standalone_mode_shortcut
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=06612422b979b6686542c1e7c2c520a7826b9fef

For future reference, a push to the evergreen-ils.org Git server is preferable to Github, patch files, etc., as it makes it easier for folks to test, signoff, and commit your submission.

Some great information on getting started with that is available at http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git

As for commit messages, at a minimum, the commit message should consist of a subject line (i.e., the first line of the commit message), then a blank line, then an optional description of the patch, followed by one or more signoffs. The subject line should be brief, ideally no more than 60-70 characters, and should include a bug number from LaunchPad if relevant. Here is an example of a minimum commit message:

LP#24544: fix the quuxifier
Signed-off-by: Jane Hacker <email address hidden>

If you need any help getting started with submitting code this way in the future, please feel free to reach out to me (or any of the other devs) via email, or the Evergreen IRC chat. (#evergreen on Freenode.net).

Thank you, again, for your work in solving this bug!

[Michael Peters (mrpeters)]

Sorry, I supplied the wrong hash above. It's actually:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=001858551e9e49e89caf941d82bd0f52936aa64f

[Pranjal Prabhash (pranjal-prabhash)]

Hello Michael,

Sorry for this very late reply, I had my exams. I will surely keep that in mind, and Thank you for your help. I am working on another bug and will do as you said.

--Pranjal

[Ben Shum (bshum)]

Picked to master for 2.5m1. Thanks Pranjal and Mike!