Go Back   Rhinocerus > Newsgroup > Newsgroup comp.lang.* 1 > Newsgroup comp.lang.clipper.visual-objects

Reply
 
Thread Tools Display Modes
  #31 (permalink)  
Old 02-24-2011, 08:32 PM
Nick Friend
Guest
 
Posts: n/a
Default Re: VOPS and SP4, open source ?


Oh dear Geoff, you really don't get it do you!

Your first post in this thread complained about a lack of development
work in VO. Now you say you need to do things like "... different
browser columns, new data fields, different validation rules... it all
means constant VO maintenance..." You need bug fixes in VO to do that?

Then you state categorically that it's much easier to add any new
functionality in C#.

I agree 100%.

So why are you so worried about a service pack for VO?

Nick
Reply With Quote
Alt Today
Advertising
 
and become member of Rhinocerus
Standard Sponsored Links

  #32 (permalink)  
Old 02-24-2011, 10:41 PM
Al Acker
Guest
 
Posts: n/a
Default Re: VOPS and SP4, open source ?

Geoff,

Sorry for the delay in getting back to you... had meetings all day. Not
sure where we left off...something about people voting with their credit
cards. Anyway, isn't that what people are doing in VOPS? i.e. If Brian
has one priority, it better be to do whatever the people in VOPS
want...right? So Brian has offered to do a SP4 for the VOPS guys. If he
ever makes it available for sale to non VOPS people is his choice and I
can't read his mind but I doubt having people complain about him will
increase their chances <g>.

Anyway, it's a moot point I guess cause as far as I know, the dev on SP4 has
started but no release date has been given. ( I may be wrong since I don't
ready every VOPS VO message)But if I had to take a wild guess, I'd bet
you're looking at VODC since that's when major things seem to be released.

Was reading your last post and you mention C#... that same functionality
avail in every NET language including Vulcan. I'm not buying the fact that
you think you can't do it in Vulcan cause there isn't Vulcan samples... If
someone can code in C#, they can very easily translate that to Vulcan code
on the fly.... heck I do it all the time when learning something new in .NET
and I'd bet most other Vulcan developers do it also. ( either use C#
examples or VB examples... which ever... but I always use the C# examples ).
Or if they have the real VS just compile the C and link it in...no?

Now for some coffee, I'm about 10 cups behind today <g>.

Al

"Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote in message
news:4d66ca20$0$77118$c30e37c6@exi-reader.telstra.net...
> I'm sorry?
>
> My apps are working fine but the client wanted to take advantage of AD
> groups to extend their security model into window and button security (who
> can add, edit, view etc). So how do you do this in VO? Well it is very
> hard. But in C# there is this beautiful set of classes that wrap the
> entire AD API so in just a few 100 lines of C# I have a nice library that
> gives me all sorts of functionality, right down to creating and
> manipulating groups and users. We wrapped that in COM and use it from VO.
>
> This is just one example - I have a dozen others - where things that were
> promised and not delivered for VO can be obtained in C# for a fraction of
> the effort and extended back to VO with COM. And no, it is NOT possible
> with Vulcan because there are no samples out there for this (things like
> AD classes). But C# I had my choice of 50 samples doing this sort of
> thing.
>
> So my apps are working fine but the client wants new, new, new. All the
> time.
>
> I hope you understand now.
>
> Geoff
>
>
>
> "Nick Friend" <nicktekhne@googlemail.com> wrote in message
> news:e3cd392a-6f26-4e0a-a9a7-aafcf2fb6d46@w6g2000vbo.googlegroups.com:
>
>
>> So your VO apps aren't working properly at the moment?
>>
>> Nick

>



Reply With Quote
  #33 (permalink)  
Old 03-01-2011, 02:10 PM
Apolonio Luis M.
Guest
 
Posts: n/a
Default Re: VOPS and SP4, open source ?

Hello,

Related to everything that has been commenting in this forum in the
last days, I decided to migrate my main application and new apps to
java web + mysql.

When I was looking for documentation about jQuery + java found this
link that maybe going to sweeten the lives of some of you:

http://www.weinfreund.de/struts2-jqu...e/index.action

Go to the auto complete section in the horizontal menu and be
surprised to see the list of languages available for the sample.


Best regards


Apolonio Luis
MEXICO
Reply With Quote
  #34 (permalink)  
Old 03-06-2011, 07:24 AM
Geoff Schaller
Guest
 
Posts: n/a
Default Re: VOPS and SP4, open source ?

Is this a fight to see who doesn't get it the most? <g>

> Your first post in this thread complained about a lack of development
> work in VO.


Yes. The promised HTML classes, Unicode, RP enhancements, repairs to the
GUI classes, FIXING THE BLOODY SPLIT WINDOW CLASSES, a whole bunch of
things. In fact Brian published a list of enhancements promised for VO
2.7 from Nuremberg at the last VO conference in that location. I still
want them.

> Now you say you need to do things like "... different
> browser columns, new data fields, different validation rules... it all
> means constant VO maintenance..."


No - you said you could not understand why I needed to work in VO at
all. You seem to think that a written app stays written and untouched.
Mine don't. Don't know anybody's whose does. Perhaps yours do. These are
some of the things we do on a daily basis for all our apps.

> You need bug fixes in VO to do that?


Of course. I'd like the repo not to crash. I'd like Source Control to
work properly. I'd like to not have to work around stupid control focus
management issues. I'd like a window editor that worked like all other
window editors. This is productivity. On balance there have been net
improvements each version so why should this stop?

> So why are you so worried about a service pack for VO?


Because I want all the things I just wrote about.
I guess you don't.

Geoff



Reply With Quote
  #35 (permalink)  
Old 03-06-2011, 07:32 AM
Geoff Schaller
Guest
 
Posts: n/a
Default Re: VOPS and SP4, open source ?

Al.

> cards. Anyway, isn't that what people are doing in VOPS?


No. I wish they were.

> If Brian has one priority, it better be to do whatever the people in VOPS
> want...right?


So how come almost none of the VO 2.7 promises ever made it to the
product? And still aren't there?

> So Brian has offered to do a SP4 for the VOPS guys.


Crikey... they've paid a fortune for it, got nothing last year and may
get a SP this year. And what's in it? No-one is saying. And what about
bug fixes to SP3? No-one is saying. And what to do about the new bugs
added to SP4? Do we then wait 2 years for SP5?

> Was reading your last post and you mention C#... that same functionality
> avail in every NET language including Vulcan. I'm not buying the fact that
> you think you can't do it in Vulcan cause there isn't Vulcan samples...


Right! So you've invented every line of code you've ever written and
never used a sample for anything? My suspicion then is that you don't
write much code and certainly not in Dot Net. There are tremendous sites
available with VB and C# code for a range of useful classes that would
take me days to figure out by myself. And why when I can just drop the
code straight into my repo and use it immediately.

> If someone can code in C#, they can very easily translate that to Vulcan code
> on the fly.... heck I do it all the time when learning something new in .NET


I guess you don't operate commercially and I also assume you haven't had
to do this very often... or with a 1000 lines of C# code. You see, I
don't have to go through the cost and time lag of conversion, I just use
it!

Geoff

Reply With Quote
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




All times are GMT. The time now is 07:40 AM.


Copyright ©2009

LinkBacks Enabled by vBSEO 3.3.0 RC2 © 2009, Crawlability, Inc.