Fast Refresh

Posts   
 
    
Marcus avatar
Marcus
User
Posts: 747
Joined: 23-Apr-2004
# Posted on: 09-Sep-2004 10:12:01   

Frans,

I know we discussed this before when I complained about the fact that the catalog refresh on the designer was too cumbersome.

You correctly pointed out that the backup question, confirmation steps and re-connection to the database provided users with a safety net to protect the designer project from being updated by mistake. disappointed

BUT - Can you PLEASE include a feature in the next release to avoid all this?

I want to be able to refresh the catalog using CTRL-r or something, I don't want to be asked any confirmation, I don't want any re-connection, just refresh "right now".

You could turn this feature off by default in each new project so that only experienced users would have it turned on which would provide your safely net.

When I’m prototyping something or trying to get something to work, it will be refreshing tiny changes in the database multiple times and this feature would really benefit productivity…

Alt-tab from Visual Studio to LLBLGen Designer, CTRL-r to refresh and CTRL-g to re-generate no confirmations… Alt-tab back to Visual Studio… etc

OR BETTER STILL VS.NET integration!!!! simple_smile

What do you think?

Marcus

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 09-Sep-2004 11:11:43   

Marcus wrote:

Frans,

I know we discussed this before when I complained about the fact that the catalog refresh on the designer was too cumbersome.

You correctly pointed out that the backup question, confirmation steps and re-connection to the database provided users with a safety net to protect the designer project from being updated by mistake. disappointed

BUT - Can you PLEASE include a feature in the next release to avoid all this? \

So just backup and connect, refresh and be done?

I want to be able to refresh the catalog using CTRL-r or something, I don't want to be asked any confirmation, I don't want any re-connection, just refresh "right now".

You could turn this feature off by default in each new project so that only experienced users would have it turned on which would provide your safely net.

No backup file also?

When I’m prototyping something or trying to get something to work, it will be refreshing tiny changes in the database multiple times and this feature would really benefit productivity…

Alt-tab from Visual Studio to LLBLGen Designer, CTRL-r to refresh and CTRL-g to re-generate no confirmations… Alt-tab back to Visual Studio… etc

generation without questions is already there simple_smile set the correct generator config in the preferences, hit f7 and enter. simple_smile I'll add the cntrl-r thingy to the todo.

OR BETTER STILL VS.NET integration!!!! simple_smile

Seriously: would this be a big help really? I mean: the only thing you really want is project file management: an entity gets a new code file (or set of code files) and the project has to be updated, an entity is removed and its files have to be removed from the project file as well... Everything else, the integration would only clutter the UI, as vs.net's UI is very cluttered (some properties are in the properties window, others are in popup windows, again others are in a designer in the middle pane etc..) and integration would mean: real integration: the designer will be merged with vs.net completely.

This integration is horrible to program at the moment due to vs.net's COM structure...

Frans Bouma | Lead developer LLBLGen Pro
Marcus avatar
Marcus
User
Posts: 747
Joined: 23-Apr-2004
# Posted on: 09-Sep-2004 13:01:09   

Otis wrote:

So just backup and connect, refresh and be done?

Exactly smile

Otis wrote:

No backup file also?

Configurable?

Otis wrote:

generation without questions is already there simple_smile set the correct generator config in the preferences, hit f7 and enter. simple_smile I'll add the cntrl-r thingy to the todo.

Cool simple_smile

Otis wrote:

Seriously: would this be a big help really? I mean: the only thing you really want is project file management: an entity gets a new code file (or set of code files) and the project has to be updated, an entity is removed and its files have to be removed from the project file as well... Everything else, the integration would only clutter the UI, as vs.net's UI is very cluttered (some properties are in the properties window, others are in popup windows, again others are in a designer in the middle pane etc..) and integration would mean: real integration: the designer will be merged with vs.net completely.

I know what you mean... On the point of project refresh, is it just my imagination or have some things (such as automatic changed project re-loading) in VS.NET be added since I installed .NET 1.1 SP1 ?

I guess I just like the VS.NET environment and like the idea of having everything under the one roof.

Otis wrote:

This integration is horrible to program at the moment due to vs.net's COM structure...

Have MS made any improvement to this problem for VS.NET 2005, I've not heard anyone mention it... ?

Marcus

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 09-Sep-2004 14:53:06   

Marcus wrote:

Otis wrote:

No backup file also?

Configurable?

ok simple_smile

Otis wrote:

Seriously: would this be a big help really? I mean: the only thing you really want is project file management: an entity gets a new code file (or set of code files) and the project has to be updated, an entity is removed and its files have to be removed from the project file as well... Everything else, the integration would only clutter the UI, as vs.net's UI is very cluttered (some properties are in the properties window, others are in popup windows, again others are in a designer in the middle pane etc..) and integration would mean: real integration: the designer will be merged with vs.net completely.

I know what you mean... On the point of project refresh, is it just my imagination or have some things (such as automatic changed project re-loading) in VS.NET be added since I installed .NET 1.1 SP1 ?

No, it is there since LLBLGen Pro v1.0.2004.1 simple_smile

Otis wrote:

This integration is horrible to program at the moment due to vs.net's COM structure...

Have MS made any improvement to this problem for VS.NET 2005, I've not heard anyone mention it... ?

Not that I'm aware of. I haven't looked at the VSIP beta SDK yet, but they didn't change a lot of the framework of VS.NET, as they couldn't make a lot of dialogs resizable because they didn't want to change the framework...

Frans Bouma | Lead developer LLBLGen Pro
Cadmium avatar
Cadmium
User
Posts: 153
Joined: 19-Sep-2003
# Posted on: 30-Sep-2004 23:33:51   

It's sounds like you are working on this, but I just wanted to second the request exactly as suggested. I also think where it saves backup project files could be configurable as well, so maybe I could have all of them be created automatically in My Computer\LLBLGENBackups or whatever. simple_smile

Rob
User
Posts: 54
Joined: 17-Sep-2004
# Posted on: 20-Oct-2004 04:16:29   

Hi!

On the subject of refresh. When you rename a field in a table and refresh the catalog it does not appear as if it renames that field in the LLBLGen Entitiy. This means that I need to delete the entity and recreate it. Which in turn is a major pain since I then have to delete all my Typed Lists that are based on that entity and recreate them.

Please tell me that I have missed a piece of funtionality here. It is not really that uncommon to rename a field.

!Rob

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 20-Oct-2004 09:40:56   

Rob wrote:

Hi!

On the subject of refresh. When you rename a field in a table and refresh the catalog it does not appear as if it renames that field in the LLBLGen Entitiy. This means that I need to delete the entity and recreate it. Which in turn is a major pain since I then have to delete all my Typed Lists that are based on that entity and recreate them.

Please tell me that I have missed a piece of funtionality here. It is not really that uncommon to rename a field. !Rob

You can rename a field at several places. In the project explorer, select it and click with your rightmousebutton and select rename, or you can press F2. In the entity editor, you can also rename a field.

The field isn't renamed by default because it could break your code when that's done.

Frans Bouma | Lead developer LLBLGen Pro