Task #12213 (closed)
Opened 10 years ago
Closed 7 years ago
RFE: Generic Insight on Windows can't be started
Reported by: | rleigh | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Unscheduled |
Component: | Insight | Version: | 5.0.1 |
Keywords: | n.a. | Cc: | jburel, jamoore, spli, khgillen |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
The generic zip file contains shell scripts to start OMERO (editor, importer, insight). These work on Linux and MacOS X. However, it does not include .bat versions of these scripts, so it's not possible to run any of the programs directly on Windows--there's nothing to click on to start them when using e.g. explorer.
Change History (4)
comment:1 Changed 10 years ago by jamoore
- Cc jburel jamoore spli khgillen added
- Owner jburel deleted
comment:2 Changed 10 years ago by rleigh
Why would we want to rename it to *nix? There's nothing unix-specific about it other than the shell scripts, which are purely a convienience. It could be trivially made to work on all platforms. This was initially triggered by the exe4j windows zip being bust for 64-bit systems, but there's no reason one shouldn't be able to use this on Windows, it costs us almost nothing and provides more flexibility.
comment:3 Changed 10 years ago by jamoore
- Priority changed from minor to major
- Summary changed from Bug: Generic Insight on Windows can't be started to RFE: Generic Insight on Windows can't be started
I'm probably confusing the "*nix" conversation with that of the server zips. The cost, though, is writing and maintaining the script. As you've explained it, I think this is more of an RFE. Happy if someone steps up to write it.
comment:4 Changed 7 years ago by jburel
- Resolution set to wontfix
- Status changed from new to closed
Roger, if we rename the generic zip to *nix is there any reason a bat needs to be added to it? Is the use case that the native versions don't work in some instances?