Comments
Sort by recent activity
Thanks for the comments.
We're certainly looking to tweak what actions are available on the toolbar, and select all and deselect all is one of the most critical. The final solution for this, didn't make it into the Beta unfortunately.
With regards to filtering, the filter side panel is a lot more comprehensive than the old toolbars. In part we had to go down this route given the huge increase in the number of object types and the difficulty in trying to recognise them by icon alone. With such obscure object types, an icon is pretty meaningless, so we had to make space for a text label too - a toolbar in this situation would be less useful and would make things look more daunting than they needed to. :-)
Of course, what this doesn't allow is the filtering of a complete difference type, e.g. all equal objects. This is actually by design, since now that a project remembers your options, if you had previously chosen not to show objects only in one database, you might not realise that the next time you ran that project. We felt that it was always important to get an overview of the differences at a global level, just to ensure that you spot that odd occasion when something isn't as it's supposed to be...
Hope that in part explains things, and thanks for your help !
:-)
Dom / comments
Thanks for the comments.
We're certainly looking to tweak what actions are available on the toolbar, and select all and deselect all is one of the most critical. The final solution for this, didn'...
We take all comments made here seriously. We are, afterall, trying to make the best product we can. [image]
We're reviewing Interactive help tomorrow and I'll make sure your points are raised.
:-)
Dom / comments
We take all comments made here seriously. We are, afterall, trying to make the best product we can.
We're reviewing Interactive help tomorrow and I'll make sure your points are raised.
:-)
Dom
Admittedly there are less groups for something like a stored procedure, but it would still split out things like permissions. [image]
Dom / comments
Admittedly there are less groups for something like a stored procedure, but it would still split out things like permissions.
Dom
I'll see if anything can be done about the problem you mention Thomas. I had a quick look and can replicate what you noticed.
Vanram, the View TSQL in groups option is useful when you want to quickly find out where the differences in an object's T-SQL are. So, when viewing in groups, TSQL relating to columns will be collected togethr in one group, T-SQl relating to constraints and indexes will be in another, etc. etc.
With all the groups collapsed, you can home in on what's different more quickly, as the difference status is displayed in the grouping bar.
This was actually a feature in version 3 and 4, but because of the way we displayed it, it was easily overlooked.
Hope that helps and thanks for your interest in the Beta ! [image]
Dom / comments
I'll see if anything can be done about the problem you mention Thomas. I had a quick look and can replicate what you noticed.
Vanram, the View TSQL in groups option is useful when you want to qui...
We're making a few changes to this area. Apologies, but this didn't get looked at before the Beta release.
:-)
Dom / comments
We're making a few changes to this area. Apologies, but this didn't get looked at before the Beta release.
:-)
Dom
Glad you're enjoying it so far !
We had a long hard think about projects as most people we visited weren't using them at all, and there were a number of reasons.
We started by making them as undemanding as possible, i.e. there's no need to give them meaningful names, interact with the file system or annoyingly get prompted to save them just when you've finished with what you were doing.
It also works the other way around... our old projects forced you to think up a good naming convention and then relied on your excellent name for you to be able to recognise that you've got the thje right project. Not always easy and enough of an obstacle to stop a lot of people bothering in the first place.
:-)
Dom / comments
Glad you're enjoying it so far !
We had a long hard think about projects as most people we visited weren't using them at all, and there were a number of reasons.
We started by making them as undema...
Thanks all for the comments.
We went through a few iterations of this, and by all accounts, it's still not as good as we would like.
What we were aiming for is that the central column is the clearest indicator that a difference exists. If you scan your eyes down the middle, anything that's equal is pretty much subdued, so when a difference does crop up, it should be more noticeable than the previous version. In the old version, looking down the central column could be a bit bewildering and you could often miss a difference becasue the strong black of an equals sign was very dominant. Essentially, you have less screen to look at to spot the differences.
There are times when the coloured lines on either side actually detract from being able to spot differences. If you get a messy mix of lines that differ, it can all break down, looking more confusing than adding order.
However, with all that said, it sounds like it still needs some work, so I'll see what I can do.
With regards font swapping, I can't promise anything, but I'll certainly put it on the list of things to shove in front of a developer when they least suspect it.
Dom / comments
Thanks all for the comments.
We went through a few iterations of this, and by all accounts, it's still not as good as we would like.
What we were aiming for is that the central column is the cleare...
Hi Robert,
The "Don't wait on this screen" checkbox has since been renamed, it now says "Close message box on completion"
The idea behind it is that it gives the user an opportunity to not have the progress dialog disappear when it's finished.
In user testing we found that people were sometimes unsure what had just occured when they initially ran a comparison. Some thought it had actually performed a synchronization, instead of just the comparison, so the first time it runs, we wanted the user to be in no doubt that only a comparison had occured. Over time, this reassurance isn't necessary, so it's nice to be able to turn it off, and have the message box disappear as soon as it has completed.
Hope that explains it !
Dom / comments
Hi Robert,
The "Don't wait on this screen" checkbox has since been renamed, it now says "Close message box on completion"
The idea behind it is that it gives the user an opportunity to not have the...
I know that our original colours were as subdued as we could make them whilst still being distinct enough to tell apart. Half the trouble though, was that this meant that we had some parts of the UI themed and others not, which made for some potentially eye watering combinations.
If I can catch a developer off guard, and ply them with the odd beverage, I'll see if they'll consent to your colourisation plea. But be warned, they can be a steely bunch and it may take many months of beverage persuasion for them to yield.
With regards to the scrollbars in the group, context is also maintained by looking at the central column and the object name columns either side. So taken in isolation, each line tells you whether it's equal, in both but different, or only in one of the databases without the need to see the grouping bar it belongs under.
Another slight disadvantage is that if each of the bars remain on screen, then we take away valuable screen space for displaying the objects themselves. In this instance, having a global scrollbar actually saves us a bit of space.
Glad you like the font resizing, I'll see if a font change option is something that we can squeeze into a future release.
:-)
Dom / comments
I know that our original colours were as subdued as we could make them whilst still being distinct enough to tell apart. Half the trouble though, was that this meant that we had some parts of the ...
Hi Brian,
Thanks for your feedback.
We did initially have the four grouping bars each in their own colour - much as your edited screenshot shows. But after early usability testing, we found that more people were put off by the excess of colour, rather than seeing it as a way to help them quickly drill down to the section they're interested in. In the end, we settled on a more subtle approach using icons, which in testing, seemed to work equally as well.
We'll have a ponder over the other suggestions...
:-)
Dom / comments
Hi Brian,
Thanks for your feedback.
We did initially have the four grouping bars each in their own colour - much as your edited screenshot shows. But after early usability testing, we found that m...