| Smart Remote Explorer (SRE) |
|
| Download |
| Lite FREE |
SRE Client v.2.0.110 - Lite
600 KB |
SRE Server v.2.0.110 - Lite
600 KB |
Pro
less than 50 users: $101
greater than 50 users: $251 |
SRE Client v.2.0.110 - Pro
600 KB |
SRE Client v.2.0.110 - Pro
600 KB |
|
The 2nd version of the SRE is now available. This new version of the SRE now is able to stand on it's own. It does not require any additional software to be installed on the server or the client outside of Java (java.com)*. This new version has been built from the ground and has it's own server and client engines. This enable the SRE servers and clients to be installed on a Windows and a Linux machine.
With it's own file system, the SRE client can now be run from any device, including a Flash drive. This means users can install and run the SRE client from a Flash drive on any machine. No longer does a user have to install the SRE client on each machine they want to use. They can take the SRE client with them via a Flash drive.
Application Overview
The SRE application (formerly the SBRE) is a version control system. It is an application which will allow you to manage modification of documents, code and files being edited by teams (or an individual) which have members located in disperse locations.
The SRE application is purely Java-based, which will make it easier to take the application to multiple platforms easily from a development standpoint, including Windows, Linux, and MAC OS X. However, since the application was coded in Java it will require a larger download and will require a machine with larger memory (RAM). It is recommended you use the SRE application on a machine that has at least 96MB of RAM.
Getting Started: SRE Client
If you already have an SRE server setup, you can just download and use the client by following the steps below. If you do not have an SRE server already setup, proceed to the "Get Started: SRE Server" section to setup the SRE server first.
1. Download and unzip the sre_client_2_0_110_lite.exe
2. Run RunSre2Cln.bat
Make sure the command prompt is:
SRE:[Cln:2.0.110]>
3. Use command:
CREATE LCS lcs
And command prompt becomes:
SRE:[Cln:2.0.110][Idle/Idle][lcs][\root]>
4. Use command:
CREATE SERVER <YourServer> 216.160.186.200 <YourLogin> -password <YourPassword>
Make sure that new server has been created using command DIR
---------------------
Type Key Name
---------------------
server 2 <YourServer>
5. Connect to the server <YourServer>
CONNECT <YourServer>
The server: SmartBond has been connected successfully
6. Login to the server SmartBond
LOGIN <YourServer>
7. Refresh projects tree from repository
REFRESH <YourServer>
The operation could take awhile if your server's repository is large
8. Use commands CD, DIR to make sure that the projects tree has been created into LCS.
Congratulation you are in SRE world !!!
Getting Started: SRE Server
If you do not already have already have an SRE server setup, you will need to setup an SRE server first. The SRE server is the engine that manage the central repository. You can setup an SRE server by following the steps below.
1. Download and unzip the sre_server_2_0_110_lite.exe
2. Run RunSre2Ser.bat
Make sure the commmand prompt is:
SRE:[Ser:2.0.110][Started][\root]>
3. Use command:
CD rps - to get into 'rps' directory.
SRE:[Ser:2.0.110][Started][\root\rps]>
CD .. - to get into parent directory
SRE:[Ser:2.0.110][Started][\root]>
4. Use command:
IMPORT PROJECT <YourPrj> rps
The project: 'YourPrj' has been imported to: 'rps' successfully
5. Use command:
DIR or LS to make sure that the 'YourPrj' does exists in 'rps'.
6. Use command:
WATCH to observe user's activity:
SRE:[Ser:2.0.110][Started][\root\rps]>WATCH
The WATCH mode is ON.
7. Connect to the server from SRE client and make sure that the server does response.
Repository Operations, Features, User Interface and License
Q: Atomic Commits: Support for atomic commits means that if an operation on the repository is interrupted in the middle, the repository will not be left in an inconsistant state. Are the check-in operations atomic? Are the check-in operations atomic, or can interrupting an operation leave the repository in an intermediate state?
A: Yes, the SRE commits are atomic
Q: Files and Directories Moves or Renames: Does the system support moving a file or directory to a different location while still retaining the history of the file?
A: No, commands RENAME, COPY, and MOVE are not implemented at this time. They are slated to be implemented in a future version of the SRE.
Q: File and Directories Copies: Does the version control system supports copying files or directories to a different location at the repository level, while retaining the history?
A: As with the previous question, no, commands RENAME, COPY, and MOVE are not implemented at this time. They are slated to be implemented in a future version of the SRE.
Q: Remove Repository Replication: Does the system support cloning a remote repository to get a functionally equivalent copy in the local system? That should be done without any special access to the remote server except for normal repository access.
A: Yes, the SRE has a COPY RPS command to handle this.
Q: Propating Changes to Parent Repositories: Can the system propagate changes from one repository to another?
A: Yes, the SRE handles repository mirroring. This is done via the command: OPEN RPS RpsName [ RpsMirrorName]
Q: Repository Permissions: Is it possible to define permissions on access to different parts of a remote repository? Or is access open for all?
A: Yes, the SRE supports permissions on folder, project, and file basis. As well, admins may set persmissions on a per user basis.
Q: Changesets' Support: Does the repository supports changesets? Changesets are a way to group a number of modifications that are relevant to each other in one atomic package, that can be cancelled or propagated as needed.
A: No, changes are file specific in the SRE.
Q: Tracking Line-wise File History: Does the version control system has an option to track the history of the file line-by-line? I.e: for each line show at which revision it was most recently changed, and by whom?
A: Not directly, but it's possible to compare any two versions using a visual differ.
Q: Ability to Work only on One Directory of the Repository: Can the version control system checkout only one directory of the repository? Or restrict the check-ins to only one directory?
A: Yes, the SRE supports check in/out on a project, directory, and file basis.
Q: Tracking Uncommited Changes: Does the software has an ability to track the changes in the working copy that were not yet commited to the repository?
A: Yes, the SRE supports tracking uncommitted changes. The SEARCH command has option -NeedCheckIn.
Q: Per-File Commit Messages: Does the system has a way to assign a per-file commit message to the changeset, as well as a per-changeset message?
A: Yes, it is possible to have a per-file commit comment.
Q: Documentation: How well is the system documented? How easy it is to get started using it?
A: Relatively poor, but improving. There are tutorials, and HELP commands.
Q: Ease of Deployment: How easy it is to deploy the software? What are the depenedencies and how can they be satisfied?
A: Good. You do not need any additional software beside the Java Virutal Machine (VM), which is usually installed by default on many Windows, Mac, and Linux machines.
Q: Command Set: What is the command set? How compatible it is with the commands of CVS (the current open-source defacto standard)?
A: Many commands are compatible with CVS. However, there are many other commands that the SRE has which CVS does not have.
Q: Networking Support: How well is the networking integration in the system? How compliant it with existing protocols and infra-structure.
A: Good (single TCP/IP socket). The SRE was built from the ground up to handle remote users.
Q: Portability: How portable is the version-control system to various operating systems, computer architectures, and other types of systems?
A: Good. Runs on all platforms supported by Java.
Q: Web Interface: Does the system have a WWW-based interface that can be used to browse the tree and the various revisions of the files, perform arbitrary diffs, etc?
A: No. The Web interface will be implemented soon.
Q: Availability of Graphical User-Interfaces: What is the availability of graphical user-interfaces for the system? How many GUI clients are present for it?
A: No. The GUI interface will be implemented soon.
Q: License: What are the licensing terms for the software?
A: The SRE "Lite" version is FREE. The SRE "PRO' version is proprietary, short text key. 30-day full-featured trial.
Price
The LITE version of the SRE is FREE for both the server and the client. The LITE version is limited to 25 users and a 10 GB RPS (server repository) file.
The PRO version of the SRE is for a fee. Below is the pricing structure for the PRO version of the SRE.
< 50 users : $101
> 50 users : $251
With the PRO version there are no restrictions on the size of the RPS file. As well, the PRO version has the following features enabled which the LITE version does not:
- SET PERMISSIONS
- SET ADMIN
- CREATE GROUP
- CREATE SHARE
- EDIT SHARE
- RENAME SHARE
- DELETE SHARE
The PRO version comes with 1 year of free technical support and code updates. After that 1 year technical support code updates are $50 per year. Technical support is provided via email.
Feedback
Feedback on the SRE application should be sent via email to sre@smartbond.net
* The previous version of the SRE (ver 1) required Apache, Tomcat and MySQL to be installed on the server.
|
