154 reputation
4
bio website
location
age
visits member for 2 years, 3 months
seen Apr 4 at 10:52

Aug
15
accepted Tips for a “New Project” dialog
Aug
15
comment Tips for a “New Project” dialog
This looks promising. I will try it.
Aug
15
accepted What should the default display in a middle column of a frameset be?
Aug
15
asked Tips for a “New Project” dialog
Jun
7
awarded  Editor
Mar
22
asked What should the default display in a middle column of a frameset be?
Jan
22
accepted About the creation and management of items
Jan
22
comment About the creation and management of items
I like this approach, I will go for it. Thank you!
Jan
22
asked About the creation and management of items
Sep
28
comment Tree for database objects and other elements
Yes, you're right, that is the final purpose of it. This tool is more or less is supposed to be to be managed by 1 person tool, since in our experience the database deployment is (should be) managed usually by a small team/1 person, in order to not to get a very chaotic and hectic process. And the purpose of this tool is just to get rid of all the hundreds of small SQL scripts that usually go along with a database deployment, and instead have everything in one place with a GUI and in just a few clicks you have your DB deployed in various places. This way there is more control over the process.
Sep
28
awarded  Student
Sep
28
awarded  Scholar
Sep
28
accepted Tree for database objects and other elements
Sep
28
awarded  Supporter
Sep
28
comment Tree for database objects and other elements
Hi, thanks for reply, it is useful :) Now some explanation: the "previous" versions should be all visible because after a deployment (of v1.0) (this is what the tool does... deploys databases) the user might consider that v1.0 is done, so he might release to v2.0. But if after some time they discover a bug in v1.0 they will need to modify v1.0 (thus obtaining v1.1) and deploy the changes to all the locations the v1.0 was deployed. They might not want to deploy v2.0 since it might contain too much irrelevant changes. This is why all the versions should be visible, even if idle.
Jul
6
comment Tree for database objects and other elements
@JonW: I am trying to determine which is less confusing for the users: To have a lot of items (all of them, tables, views, diagrams, code, ...) shown duplicated in the tree or to have less item duplication (only for those that are effected by versioning: Table, view, ...) and a common gathering place for the other items (Diagram, Code, Documentation), but in that case to have an extra selection somewhere else to achieve the correct functionality for the latter.
Jul
6
asked Tree for database objects and other elements