Scriptbuilder dead?

[Wolf Voigt, ParkInter.Com]

Hi, by watching the NG I come to the impression, a lot of SB-user are not
satisfied with this program.

I downloaded the NOF-SB trial version and installed ... the Microsoft
Reader!

What is that meaning?

The program is that buggy that NOF stopped the delivery?

If this is so, I would appreciate to have a note about this, before I spend
my time to download 11 MB and install a unwanted program (and uninstall it).

On the other hand, thanks to NOF for saving my time to test this program.

--
Greetings,

Wolf Voigt
ParkInter.Com, Stony Plain
Alberta, CA
(780) 963-3086

[B.J. Brogan]

Its dead all right, yet they still have it listed on their home page
as a viable product (a bad smell to this!) I bought this "thing" as a
replacement for a previous product (I forget the name,) that had also
been discontinued or bought out - a total ripoff, it has never worked
well. At least I didn't get suckered into "upgrading" to version 3.

You might want to try Sapien Technologies PrimalScript at
http://www.sapien.com. It works, and is being actively supported and
enhanced, including (beta) additions to support M$ .Net SDK.

I have lost what little confidence I may otherwise have had in ANY of
NetObjects' products, and am going to tell as many people as possible
EXACTLY what I think about this company, especially how reliable and
honest I think they are.

BJ
Calgary

[wta...@cais.com]

Last week I downloaded the Trial version of NetObjects Scriptbuilder
3.0. The file was labeled NOSB30_TRIAL.EXE and it installed fine,
and I've found the tool to be quite sufficient for the project I'm
working on. I do realize that there are some bugs in it. For example,
when displaying the contents of a Script Component file "testfile.scc"
that I created, the "Script Component Pad" displays duplicate listings
for the same object method in the "Interface" Window. The method should
only be listed once.Also, the Script Component Pad Source Code Editor
does not support global search and replacement of code, which can make
implementing revisions to the code cumbersome. But for me, utilizing
Scriptbuilder 3.0 for my project was definitely not a waste of time.
When I started using the tool, I was not really sure how to go about
redesigning my previously developed JavaScript code to fit an "object-
oriented" methodology. Scriptbuilder 3.0, with its installed base of
simple examples, was very helpful in this regard.
I had been planning on paying for the product, as after 30 days
the "Trial" version becomes unusable on the platform on which it had
been installed. I was not aware however, until reading your posting,
that the company had engendered such ill will in its customer base.

--- Bill Angel
CSC, Inc.
Springfield, Virginia

In article <1l7jsscjv3de31e0l...@4ax.com>,

B.J. Brogan <broganR...@cadvision.com> wrote:
> Its dead all right, yet they still have it listed on their home page
> as a viable product (a bad smell to this!) I bought this "thing" as a
> replacement for a previous product (I forget the name,) that had also
> been discontinued or bought out - a total ripoff, it has never worked
> well. At least I didn't get suckered into "upgrading" to version 3.
>

>....
....

> I have lost what little confidence I may otherwise have had in ANY of
> NetObjects' products, and am going to tell as many people as possible
> EXACTLY what I think about this company, especially how reliable and
> honest I think they are.
>
> BJ
> Calgary
>

Sent via Deja.com http://www.deja.com/
Before you buy.