Paul Wilson has released V1 of his UI Mapper...

http://www.uimapper.net/

I've not really checked it out...anyone here taken a look and tried it with some LLBLGen code?

MattWoberts wrote:

Paul Wilson has released V1 of his UI Mapper...

http://www.uimapper.net/

I've not really checked it out...anyone here taken a look and tried it with some LLBLGen code?

I downloaded the demo, Paul gave me a license some time ago, so I can download teh full version but I haven't tried it yet. I couldn't find any documentation in the download so I gave up pretty quickly. The demo win exe app ran extremely slow on my Xeon 3Ghz dell monster, which made me think a bit if the execution of the idea has a few problems here and there.

The idea is ok, though will be obsolete with the new winforms controls which let you specify controls in a table style way on a form in .NET 2.0.

Paul mailed me if I wanted to implement the interface he defined. The interface was not really that useful, as it missed a lot of things LLBLGen Pro supports, for example multiple PK fields. I mailed that back to him but I haven't received a reply yet.

In general I'm not really convinced if a ui-mapper is necessary, I mean: it more or less performs the same things as the currency manager in .NET and with that you can use standard controls.

Note to Paul: Sheesh, one screenshot would be helpful.

Seems like an interesting idea, at least for asp.net apps (which is pretty much all I do now). Anything that could help me standardize and minimise the number of admin forms I have to make for each project

Otis wrote:

In general I'm not really convinced if a ui-mapper is necessary, I mean: it more or less performs the same things as the currency manager in .NET and with that you can use standard controls.

I'm curious what technique or solution would you reccomend for the current version of .Net?

swallace wrote:

Note to Paul: Sheesh, one screenshot would be helpful.

True, a live demo would also have been nice.

Cadmium wrote:

True, a live demo would also have been nice.

Did you try the Demos tab at the top?

Cadmium wrote:

Otis wrote:

In general I'm not really convinced if a ui-mapper is necessary, I mean: it more or less performs the same things as the currency manager in .NET and with that you can use standard controls.

I'm curious what technique or solution would you reccomend for the current version of .Net?

Winforms have the currency manager and default databinding. In asp.net you have one-way databinding, but I think that's because it is really one way. I don't see an additional benefit for this, especially because you have to use special controls.

I'll agree with ya Otie.. I prefer not to use software that restricts what I can do even if it's purpose isn't for overly technical tasks. The learning curve, practicality, and scalability of the software pushes me away.

netclectic wrote:

Cadmium wrote:

True, a live demo would also have been nice.

Did you try the Demos tab at the top?

Guess not

On a slightly related note, has anyone seen this? http://slashdot.org/articles/05/03/02/1449240.shtml?tid=152

Haven't seen any demos, but it sounds an awful lot like what UIMapper does.... only without .NET so it doesn't do us much good. I believe it can be integrated with .NET projects somehow though.

Again, it's one of those things I find interesting but not enough to read any further.

alexdresko wrote:

On a slightly related note, has anyone seen this? http://slashdot.org/articles/05/03/02/1449240.shtml?tid=152

Haven't seen any demos, but it sounds an awful lot like what UIMapper does.... only without .NET so it doesn't do us much good. I believe it can be integrated with .NET projects somehow though.

Again, it's one of those things I find interesting but not enough to read any further.

No Adam and Eve are what XAML + Databinding does for .NET .

You can define dialogs in a simple language and bind a model to it by defining the controller in a simple language too. It's pretty nifty, as C++ / Win32 doesn't have this stuff build in. It's also cross platform and culture independent, so you can easily create multi-language forms with the same definitions.