Thanks for the reply....
I think part of the problem is I haven't bitten the bullet and learned asp.net MVC yet...but even then I think there is a lot of hand coding one must do that could be incorporated into a template.
My goal is essentially this (for example):
I want to be able to write a UserDetails form (Name, Address, etc), then press the Save button and have that persisted to the database via an ajax call.
Now there are likely any number of ways to do this (of which I know precisely none). My suggestion was for a template implementing "a" methodology or pattern for doing this that works "good enough".
Some complications:
- I may not have all of the columns from the User table on the form, so it would be preferable to make my call passing in just the subset displayed on the form (obviously I have to pass in the primary key column values). Because of this, I think UI portion of these templates would have to generate into a temp folder, and one would have to then copy/paste/modify the snippets to support the specific UI implementation. The server side of the template output would not be manually modified, and could somehow handle a subset of values coming in.
- I would also like to have a decent client side two way binding system, that supports intellisense
Now, I don't know if this "should", or "has to" be done in an MVC framework, or if it can be implemented or called via webforms.
I don't know the correct answer to this by any means. I also don't know many of the complexities involved in properly implementing a rich domain model / data tier. But because of LLBLGen, I don't have to.
What I'm trying to say is that if a Ajaxy "framework", implemented through a set of LLB templates could be developed for the UI side, it would (to me at least) be as useful as the existing templates have been on the backend. I think I am looking for something somewhat similar to what one gets out of the box with Ruby on Rails (although I have only seen some sample videos of that, I am no expert).
Note: I hope it came through but if not, I will explicitly state here that I am not wanting to generate the entire UI. The ideal is the generation of:
- the server side interface
- client side stubs for loading the UI as well as persisting the UI back to the server side function. These stubs would manually be copied into a manually coded html form (the first iteration of which may have been generated)....I guess very similar to the existing LLB UI generation templates.
I'm sure there are some gotcha's involved in this, but hopefully I've gotten the general idea across?? Is something like this possible??