![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| ||||
| ||||
|
|
Luke: Hell yea! :-) |
|
Besides, the product is given away by RDUS and, in fact, they could easily have done what these good people have done. RDUS only uses it at all because people want to be able to type "HELP LOCATE" at tcl. :-) |
|
This is just another example of why it's difficult to use/develop on an MV product. Documentation is in multiple forms with different stuff in each different documentation package. :-( |
|
"Luke Webber" <luke (AT) webber (DOT) com.au> wrote in message news:43bf15ba$1_1 (AT) news (DOT) melbourne.pipenetworks.com... Scott Ballinger wrote: Is there a link to that html version of the pick reference manual http://www.rainingdata.com/support/t.../apprm006.html anywhere on RD's website? Also, there is Sierra Bravo's D3 ref site: http://www.d3ref.com Hmmm, cheeky. Taking Jon Sisk's / Raining Data's help text and converting it to HTML. Helpful, but is it quite kosher? Luke |
#12
| |||
| |||
|
|
Scott Ballinger wrote: Is there a link to that html version of the pick reference manual http://www.rainingdata.com/support/t.../apprm006.html anywhere on RD's website? Also, there is Sierra Bravo's D3 ref site: http://www.d3ref.com Hmmm, cheeky. Taking Jon Sisk's / Raining Data's help text and converting it to HTML. Helpful, but is it quite kosher? Luke |
#13
| |||
| |||
|
|
Luke Webber wrote: Scott Ballinger wrote: Is there a link to that html version of the pick reference manual http://www.rainingdata.com/support/t.../apprm006.html anywhere on RD's website? Also, there is Sierra Bravo's D3 ref site: http://www.d3ref.com Hmmm, cheeky. Taking Jon Sisk's / Raining Data's help text and converting it to HTML. Helpful, but is it quite kosher? (No real points here, just yakkin) Jon didn't think so. RD was surprised when they found out it was done too, but later approved it as long as the RD copyrights were in plain view. That sort of ticks me off too because I was trying for a few years to get them to approve a similar community documentation project which I've been talking about among MV colleagues for some years now. I have full respect for Sierra Bravo but the way this d3ref.com thing was done was a mistake IMO. That data is sorely out of date and I don't believe there is any collaboration with RD to bring it up to date. I'm sure when the new Ref account is made available by RD the SB site will be updated. In the mean time it's just another source for the same old stuff. |
|
What never ceases to amaze me is how impressed people are with what was done. A friend of mine did a VB4 front-end to EPick over 10 years go, but we sort of laughed it off as one of those things no one would use - it was just too easy. A web interface to AP Ref is also just too easy to do - the only thing stopping it was approval from RD. This GUI stuff isn't rocket science even though lots of Pick people think it is. All it takes is someone to say they think it should be done - and maybe someone to cough up some chump change to make it happen. |
#14
| |||
| |||
|
|
... Let third parties host your doco, and how do you keep it up to date? Not that up to date doco is one of RDTA's current interests, or so it seems. |
|
What never ceases to amaze me is how impressed people are with what was done. A friend of mine did a VB4 front-end to EPick over 10 years go, but we sort of laughed it off as one of those things no one would use - it was just too easy. A web interface to AP Ref is also just too easy to do - the only thing stopping it was approval from RD. This GUI stuff isn't rocket science even though lots of Pick people think it is. All it takes is someone to say they think it should be done - and maybe someone to cough up some chump change to make it happen. Absolutely. In fact, Jon tells me that he had in mind to produce something like this (HTML or hypertext) from the start. But I guess Dick wasn't interested. It's a real shame, IMO, that Dick used this to push his Update processor, because it could have been done a lot better with just a little BASIC code instead. But yes, the conversion to HTML is utterly trivial, and there is no good reason why it should have been left to a third party. In fact, you could use OSS tools to convert the Help database to just about any format - HTML, PDF, what-have-you. Then you'd just maintain the text in one place, which beats the current setup (books online, PDF and online help). Luke |
#15
| |||
| |||
|
| Originally Posted by Luke Webber Tony Gravagno wrote: Precisely why I said in another post that I wouldn't have given permission if I'd been in RDTA's place. Let third parties host your doco, and how do you keep it up to date? Not that up to date doco is one of RDTA's current interests, or so it seems. Absolutely. In fact, Jon tells me that he had in mind to produce something like this (HTML or hypertext) from the start. But I guess Dick wasn't interested. It's a real shame, IMO, that Dick used this to push his Update processor, because it could have been done a lot better with just a little BASIC code instead. But yes, the conversion to HTML is utterly trivial, and there is no good reason why it should have been left to a third party. In fact, you could use OSS tools to convert the Help database to just about any format - HTML, PDF, what-have-you. Then you'd just maintain the text in one place, which beats the current setup (books online, PDF and online help). Luke |
#16
| |||
| |||
|
#17
| |||
| |||
|
|
Playing with the D3/NT 7.5 Beta, documentation is MUUUUCH improved - something to look forward to. heck, it even documents the "ED" option from Basic debugger that I found by accident last week - wish I had known about THAT - yeah, I KNOW it is in REF .... obviously I need to spend moore time RTFM) |

![]() |
| Thread Tools | |
| Display Modes | |
| |