Example page:
http://infotools.ru/products/BRIZ/EX...CsharpGPTL.htm

Interestingly Your opinion on technology and style.

Regards,
Grigory

GVP wrote:
I'm not familiar with BRIZ, but the end result looks similar to the way
it would be done with mv.net. jrcs and the other dotnet object
libraries for connecting to MV products.

The only comment in general I would have is that I would personally
have suggested using vb.net rather than c# for the demo. vb being a
Basic derivative is slightly easier to read for somebody who is
familiar to databasic. c# looks funny to those who aren't used to
reading it or are familiar with java/c..

Regards
Simon

Simon wrote:
....
Simple example of the program on VB.NET for D3 and OpenQM:
http://infotools.ru/products/BRIZ/EX...harpGPTLVB.htm

This technology exists more than 6 years and is successfully used.

Grigory

Hi Steve,

Connection should be done once, at the start of program. Shown only
four from hundred methods: ExecTCL, ReadFromPick, OpenPickFile and
GetActiveList. For example it is possible to execute any PB subroutine
(interactive and asynchronous). Interactive means that Client and
Server can exchange by data when subroutine executing.
I think, that serious program should have not Data object binded to
GUI. Esspecially MV.

Regards,
Grigory

"GVP" wrote:
Steve, this thing about binding data to controls is one of those "less
filling, tastes great" arguments that will never go anywhere. I'm not
a personal fan of data binding because it violates MVC but it does
have it's place. Grigory has a point - In some circles data binding
is more for newbies, hobbyists, and prototypes. Though it seems to
have some undying credible support in other circles as well. I think
the decision comes down to this: if your client won't fire you for
using it then it's probably OK for this one gig. A couple of my
clients would disown me for suggesting it.

mv.NET is really a suite comprised of three libraries, one of which is
the Binding Objects library dedicated to exactly what you're talking
about. This makes "codeless" programming very easy. The upcoming
release of mv.NET v3.0 includes Atlas integration to make Ajax
development completely transparent, and with data binding to
components the coding for data access will be minimal as well.

For those who prefer "English" - The next mv.NET has drag-n-drop Ajax,
so you don't need to manually code everything in order to get
field-level validation all the way back to the database from a
browser.
Hey wait a minute, that's exactly what DesignBais is!

BlueFinity who provides mv.NET started with Atlas early on and they
helped to guide its development by pointing out ways that it can be
used which Microsoft hadn't yet envisioned. Yippie for MV-induced
innovation! It will take some research for people to really grok how
to get the most out of these tools, but it should be worth it.

Related to all of this, I have an article that will be posted to my
blog in just a couple days called "Wizard vs Manual Coding of Data
Components". I'm sure you'll be interested and your comments will be
most welcome.

Regards
Tony
http:// removethisNebula-RnD.com/blog/category/tech/mv/mvnet/