![]() | |
#11
| |||||
| |||||
|
|
From Newsgroup: comp.databases.pick Gene, we're in sync. Preface all my responses here with "I hear ya bud". "Gene Buckle" wrote: The -1 issue is embarassing. It NEVER should have made it out of beta with such a fundamental flaw. I suspect the guy that wrote the code has either never written code in Pick BASIC or was very, very new to it. Or the code was written, tested, functional, and some subsequent update broke things. I won't make excuses, and have no idea how |

|
YMMV but I've been so turned off from contributing FOSS to this community that it's really depressing. It's the whole per-seat pricing mentality that makes it tough Tony. That and a whole lot of "what's in it for ME?!" attitude. Frankly, I don't care either way. If I deem it a worthy example of my work (and I get permission from my employer), I'll post it. If someone benefits from it, great. If not, no big deal. By "per-seat" I'm guessing you're referring to mv.NET. I certainly wasn't. Sure, I use and sell mv.NET but there are times when we don't want or need it. Right tools for the job and all that. No, I was seriously talking about FOSS and how projects like that notoriously fail in this market. Actually, I wasn't referring to mv.Net. I was referring to <insert per-seat |
|
(Just making conversation, no real point...) As usual it comes down to everyone taking, no one giving, and if you're lucky the "demand" comes in the form of a few people just telling you what's wrong with code rather than offering to send a cup of coffee for enhancements. I have no problem with FOSS in general and I have a bunch of them in the air - just trying to give back to the bazaar what I've consumed, so to speak. Combining all this, I'm just saying the effort to publish a wrapper lib for the D3CL as FOSS is a Lot of effort for a handful of people who probably won't care, and with Very little reward except for warm fuzzies. But it can never hurt to publish something you do and hope that someone helps you to make it better just by pointing out flaws that you might fall into with your own code. ![]() Well the effort is going to be made one way or the other. I can no more stop |
If someone benefits from the code I produce,
|
per-seat priced solutions. Me too. I think MVSP is kinda cool but I didn't want to get into it TOO far until I saw others using it. TL hasn't exactly trumpeted from the rooftops that MVSP even exists. Combine |
|
Coming back to mv.NET though, MVSP (.NET/Java) is now in line with UO.NET/UOJava, QMClient, and others. mv.NET uses those tools for basic connectivity while providing a superset of higher functionality. mv.NET (OK, take this as an [ad]) provides session pooling, code generation, Silverlight integration, and an ADO.NET interface. These |
#12
| ||||
| ||||
|
|
Take a look at the InsertCore() routine with ILSpy. Trust me, it's an embarassing mistake. ![]() |
|
TL hasn't exactly trumpeted from the rooftops that MVSP even exists. Combine that with a theoretically small number of shops that are both upgrading to v9 AND working with .Net applications and your potential audience ain't that big. |
|
I need to shove harder to get them to create a version that is compatible with Silverlight though - I could really leverage that to good advantage on my production floor processes. |
|
I don't get the whole ADO.Net thing - that's designed to work with SQL type data and (at least from where I sit) is fairly useless with MV datasets. I will admit that using DataTables are a better way to add data to a grid than the old AddItem() method of days gone by. |
#13
| ||||||
| ||||||
|
| I'm glad MVSP now exists. It's a good starting point for people who want to learn .NET or Java, for someone who just wants free and simple connectivity, or for people like us who might want to provide a free or low-cost utility without a $260 surcharge for a connectivity license. But for anything beyond the basics we just need something more. That's where mv.NET picks up. I'm sure that sounds like a sales pitch to people here, but as just another guy in the crowd, I'm just telling ya that this is where my decision process takes me. YMMV I've only got two issues with mv.Net. The first is that they charge a per-seat |
|
I need to shove harder to get them to create a version that is compatible with Silverlight though - I could really leverage that to good advantage on my production floor processes. I'll bet ya a Starbuck's mocha that you're not going to see Silverlight integration from them. You said yourself the market is almost too small just for uptake of the basic library. Not only is Silverlight connectivity much more sophisticated, requiring much more client/server development to make that work transparently, but the number of people who would want to use it so far is tiny. Heck, TL hasn't even implemented a basic mvItem class. Everything is string or object. They have a long way to go just on the basic lib before moving on to Silverlight - though I don't think this is the direction in which they want to go. You're probably correct. I'll likely end up just doing it myself if |
|
Again, not trying to sound like a surrogate here, but mv.NET has had Silverlight built-in for a while, and from my perspective only serious larger shops are even interested. Silverlight integration is free in mv.NET. Communications underpinnings, a XAML Wizard, and the business objects code generator are all in there. The price of the software hasn't changed in years and anyone who upgrades gets all of this at no extra code. Even as a freebie I don't see uptake from the traditional developer base. That surprises me. Silverlight makes for a great presentation layer and being |

|
both of these products are for .NET developers who don't know anything about Pick, but need to see DataTables, Records, Columns, and Stored Procedures. I have had clients who hire a .NET guy because it's too tough to hire a Pick guy who also does .NET. Rather than training |
|
them on Pick they just expose the DBMS in a way that makes sense to the .NET guy. So now they can do databinding and exchanges with relational systems without "foreign looking" code. I don't know a single Pick guy, including myself, who uses the ADO.NET hooks on a regular basis to get into the MV environment. But if someone asked me to write an interface, and provide source, for some non-Pickie who would later maintain my code - I'd use the ADO.NET mechanisms. |
|
Anyway, different strokes for different folks. What I enjoy is that these tools exist for us to discuss them - which is far better than the alternative of no tools and/or no one to have the discussion. |

#14
| ||||||||
| ||||||||
|
|
From Newsgroup: comp.databases.pick "Gene Buckle" wrote: I've only got two issues with mv.Net. The first is that they charge a per-seat fee for me to access data that I'm already paying someone else a per-seat fee to access. But "per-seat" with mv.NET is Way different from per-seat DBMS But it's _still_ per-seat. If I was doing Internet facing applications that |
|
But you're the only person I know who says that kind of performance is more important to you than overall cost and all of the other features I've mentioned. Because of the environment I'm working in, those "other features" really |
|
Further, you say you don't want pooling and you do need speed. But in many scenarios, not all, those factors counter one another. Pooling is used to improve performance for most new development scenarios that people consider these days. It's basic parallel processing vs serial. In _my_ situation, pooling is just a mother-may-i layer that adds nothing |
Are the developers you're talking to targeting|
You have to remember that this MV market is so small that all vendors need to consider unpopular license models just to stay in business. I lay this one right at the feet of the MV vendors themselves. The tool |
|
I don't expect it would be too difficult to shoe horn the existing MVSP code into a Silverlight compatible library. If you undertake that, please email me. I'm curious how you'd approach it. Essentially I think you'd need a faade/proxy class on the client which uses a web service to connect to a remote server. The server then does the actual processing. What's neat about this is that you might be able to get your data from a *nix server while the UI is served via ASP.NET from Windows. I don't know if that's a good idea in general but offloading the data access to another server, especially Linux, could have some performance benefits. Just a thought. The shortest path would be a Silverlight based implementation of the MVSP wire |
|
huge win in my book. Then again, I look at things through the filter of being an ERP geek. ![]() (BTW, that was supposed to be "no extra COST", not "no extra code".) Agreed. I think part of the problem is that Silverlight has undergone a slow evolution from v1 to v4 and only now are real gear-heads using it for RIA, line-of-business apps like we have in this market. In the MV world people equate Silverlight to Flash, think glitz, and turn the other way. Other people have gotten fed up with too many options, from ASP, to ASP.NET web forms, to ASP.NET MVC, and now Silverlight and it's radical client/server model. Add to that all the hullabaloo about plugins vs HTML5 and traditional Pick sentiments, and you get a hugely confused audience that is very reluctant to adopt anything anymore. I tend to look at Sliverlight as if it were basically a browser-hosted version |
|
I'm debating on how nuts it would be to build a version of MVSP in Delphi XE. THAT would scream. You can't beat a native compiler. ![]() I really need to publish my work on mvEsperanto. I think you would be VERY interested. ![]() Hehe. I bet it sounds better in the original mvKlingon. *laughs* |
|
Thanks for the discussion bud. I'm enjoying this one. (And wondering just how many people will actually read this far. HAHA) We probably should have offered a prize if they get this far. |
#15
| ||||||
| ||||||
|
|
Further, you say you don't want pooling and you do need speed. But in many scenarios, not all, those factors counter one another. Pooling is used to improve performance for most new development scenarios that people consider these days. It's basic parallel processing vs serial. In _my_ situation, pooling is just a mother-may-i layer that adds nothing but network latency. Are the developers you're talking to targetingthe browser or are they writing thick and "medium" clients? |

|
You have to remember that this MV market is so small that all vendors need to consider unpopular license models just to stay in business. I lay this one right at the feet of the MV vendors themselves. The tool vendors wouldn't have to use "unpopular" models if they were doing a hell of a lot more to promote the uptake of MV in general. They need to do more than go "MultiValue is better than SQL!" They need to shove that fact into peoples' faces all the time and never let up. Otherwise, they're going to be dead in another decade. I think the only one that has a chance is Ladybridge and that's because they're in a great position to help those that are left high & dry by the death of a primary vendor and are in dire need of a best-of-breed replacement. |
|
I don't expect it would be too difficult to shoe horn the existing MVSP code into a Silverlight compatible library. If you undertake that, please email me. I'm curious how you'd approach it. Essentially I think you'd need a faade/proxy class on |
|
the client which uses a web service to connect to a remote server. The server then does the actual processing. What's neat about this is that you might be able to get your data from a *nix server while the UI is served via ASP.NET from Windows. I don't know if that's a good idea in general but offloading the data access to another server, especially Linux, could have some performance benefits. Just a thought. The shortest path would be a Silverlight based implementation of the MVSP wire protocol itself. It would work well in an Intranet-only situation which is what I'd be working with. |
|
I tend to look at Sliverlight as if it were basically a browser-hosted version of WinForms. |
|
The NetAdvantage Silverlight controls makes it pretty painless. |
#16
| ||||||
| ||||||
|
|
From Newsgroup: comp.databases.pick "Gene Buckle" wrote: Further, you say you don't want pooling and you do need speed. But in many scenarios, not all, those factors counter one another. Pooling is used to improve performance for most new development scenarios that people consider these days. It's basic parallel processing vs serial. In _my_ situation, pooling is just a mother-may-i layer that adds nothing but network latency. Are the developers you're talking to targetingthe browser or are they writing thick and "medium" clients? I haven't had a single request for a thick or even medium-thick client for years. Everyone wants thin client. Of course that means chatty AJAX which can degrade some performance so I'm compelled to make up for it with some scripting. There's a constant dance in there to ensure the environment is performant, maintainable, and cross-browser capable. That's interesting. The only problem I've got with thin-client is that |
|
GUI/BUI users while keeping most internal people on the CUI. As described, the licensing costs for this are relatively painless, and sites gladly purchase a few more licenses than to migrating to Oracle or some other platform. After all of this rhetoric, that's really how I see this play out in almost all situations. Gene, you're just a rebel. ![]() Yep. I drive my AS/400-laden co-workers out of their minds sometimes.
|

|
However, while I agree that QM is a great platform, I'd submit that all of the MV providers are eager and capable of migrating competing systems. Best-of-breed once again depends on requirements. Personally, for small projects I like QM but for larger ones I'm inclined toward the larger providers, and the selection of which provider is dependent on my technical requirements. Do you thing QM is slower than the larger players (D3, Reality, etc)? |
|
I don't expect it would be too difficult to shoe horn the existing MVSP code into a Silverlight compatible library. If you undertake that, please email me. I'm curious how you'd approach it. Essentially I think you'd need a faade/proxy class on (Looks like Google or some other system in the middle doesn't speak french, that was "fac'ade/proxy class" with a non-english 'c'. ) I read news with tin and it bitches about any DBCS characters. You're likely |

|
The shortest path would be a Silverlight based implementation of the MVSP wire protocol itself. It would work well in an Intranet-only situation which is what I'd be working with. Hmm, I'd check with TL to see if they've tried MVSP in Silverlight. The modest requirements of that small library might not need more than what's available in that environment. If they say it won't work then you're talking about reverse- engineering the wire protocol. You really don't want to go there. Just create a proxy and wire it up yourself. It won't be that hard. It might even be fun to build an MVSP server daemon |

|
The NetAdvantage Silverlight controls makes it pretty painless. There ya go, an example of 'you get what you pay for'. MVSP is basic connectivity for free. If you want a "pretty painless" experience with something more sophisticated like Silverlight, you will either need to make or buy it. I don't mind buying it - I mind buying it again and again and again. |
![]() |
| Thread Tools | |
| Display Modes | |
| |