On a hunch, I do the same thing- add to SCC, cancel... and the information appears.  Not the most intuitive, but it works.

I have to admit the Zeus SCC is a bit confusing and it can probably do with some improvements.

There is no option for automatic check out on edit, but as that has been requested a few times I guess it might need such an option. Something for a future version.

To add some clarity this is how it should work here is a quick overview.

Initial SCC Setup
Zeus will work with any SCC version control so the first thing that needs to be done is for that to be setup.

That is done at the editor level using the Options, Editor Options menu, Source Control panel where you select and enable the source control.

Binding a Workspace to SCC
To use the source control the projects inside the workspace need to be bound to the source control.

The binding details are stored in the Workspace, Source Control, Options menu.

There you will find the Project Name, Aux Path and Local Path, an option to enable source control and a Run Setup Utility button.

Since you imported a Visual Studio solution that already contained version control bindings, that process should have already filled in these details.

When there are no binding details it is best use the Run Setup Utility as that will let you browse the source control looking for a suitable project.

Looking at the source control error message you posted I can see the AUX Path is empty which is why the connection the to source control failed.

However, those binding details should have been available as they should have come in when the project was imported?

It looks like this may well be some sort of incorrect state bug and by this I mean, because the project was newly imported it was not quite in the correct state.

By doing your work around that fixed up the issue buy fixing up the state of the project, but I suspect if you had closed and reopened the project that too would have probably worked?

I add a file to the project in the workspace, and it's not added to the project in Visual Studio

Yes, Zeus will never touch any Visual Studio files.

However, if you had added the project inside Visual Studio, there is an option to update the Workspace inside of Zeus and the workspace is automatically updated the next time it is opened.

It probably should also do that check for update whenever it is re-activated. Another something for a future version.

I ran into a problem with ctags when there were icons included in the project.

I'll look into this.

As you suggest, it looks like xtags/ctags might have run into trouble processing the icon file.

That message box dates a long time to when the user had to manually configure the PATH and as that is no longer required I suspect the dialog can be removed.

it wasn't perfect.

Zeus is certainly not perfect and there are always things that can be done to make it better.

The next version will no longer have that xtags message, so that in itself will be a small but nice improvement

Thank you for the very nice and thorough review, wraith808 .

And thanks to Jussi for taking the time to comment in this thread .

Do you have any insight on how Zeus Edit compares to UEStudio?

Ok, yet another editor which looks quite alot like Textmate (OSX) to me (well, alot of editors looks like each other so this is irrelevant point anyway)... what are main benefits in this editor compared to Sublime Editor (http://www.sublimetext.com/) which is gaining heavily popularity among coders.

They look like totally different approaches

I'd agree with this assessment.

I've not used Sublime or TextMate but from what I read they use more of a plug-in approach to configuration. To add a feature you download and install a plug-in.

Zeus does not use that approach, but instead provides an editor that can be configured by the user. As such it uses an approach more similar to editors like Vim, EMACS, SlickEdit etc.

As to which approach is best, that is another discussion

Zeus has always be designed as an alternative to Visual Studio and as such it has many Visual Studio like features (i.e. project/workspace, project make, compile, class browser, source control integration etc). In that sense Zeus is more of an IDE than an editor.

Now I suspect Sublime might offer those IDE like features via plug-in (I don't know) but as your review shows, Zeus has those features pretty much out of the box.

Edit.

Downloaded Zeus Lite. Installation. Open file --> error.
Uninstall.

That was singularly unhelpful.  What kind of error?  What OS?

And to let you know why I think it was unhelpful especially to post if you weren't going to engage is that it's quite difficult to get developers willing to engage in such a way and offer discounts/giveaways these days, because the chance of negative publicity and interactions is very real.  We want to put forth DC as a place where developers can engage and be assured that their contributions will be received respectfully.  Please keep that in mind when posting.

Does this still count as a mini review?

Guess it depends on your definition of mini.  I've seen some as long... it's not all *that* long.  I've also seem some terminally brief.  So I guess that remains an exercise for the reader.

I understand what you're saying, and your frustration.  But I guess my point is that if you're not willing to work with the developer, either here or by contacting the developer, then posting such comments is only a negative statement and doesn't really *help* the situation, and makes developers less likely to engage with us.  Especially when the developer has been as up front and engaging as they have in this case.  And makes it harder to bring you this type of offer in the future.  Not to soft shoe anything, but just to be aware of the tone of your posts and how they affect the board and the view of the board as a whole.  Just food for thought.