Documentation enrichment

Scriptcase 8 Suggestions
#1

Hi everybody,

My suggestions until now are about documentation.

  1. It would be useful if documentation present a link to related topics. For example, Talking about selecting the fields, it could present a link to a topic explaining how to refresh field list if table structure has changed.

  2. I need some explanation about the sc_mail_send macro. In Documentation appears the header of macro like this: sc_mail_send(smtp, usr, pw, from, to, subject, message, mens_type, copies, copies_type, port, connection_type, attachment), but in explained parameters last four are missing. Furthermore, it would be convenient to add an example with an attachement.

Scriptcase: great product! Congratulations guys.

Federico A. Lopez
El Salvador, Central America

#2

Re: Documentation enrichment

Yes, indeed a great product, but a documentation, that isn’t worth a floppy disc.
The translation is terrible and looks like a child has written it. Same problem to the Online-Support or more catastrophic on the telephone. Of course, English isn’t the mothertonque of everybody (also not mine), but when you intent to sell a product for 300 Us-Dollar on the global market, the well written, complete and up-to-date documentation is absolutly mandatory.

Hopefully, you realize it very soon, otherwise you won’t succeed with this.

Kind regars

Steffen R.

#3

Re: Documentation enrichment

I agree that it will help as the documentation gets better.

In addition having a forum like this where people can go to and get help, will also help a lot.

I have not had the time to really get into SC as much as I would like to, but assuming I can really do what I want to (timewise), I plan on doing training, etc on SC so that here in the US we have a good resource to help this product really sell well in my country anyway. I would like to set up a website and do training, mentoring, consulting, maybe even try to get people together for user group type meetings, though that will be tough until the product really sells here.

Alan

#4

Re: Documentation enrichment

When they release V5 which I hope is really soon, and start an Affiliate program, I will be onboard with really using the product for some high end websites I am working on.

I hope to eventually be a very good resource for SC info, etc in the USA.

We shall see…

Anyone in the US that wants to communicate or try to get together for conversations, etc, just let me know. We should be able to set something up.

I don’t really care if it’s just USA, but I only speak English, so I guess English speaking might be more correct, but of course, if we want to try to get together somehow, USA would be easiest.

Alan

#5

Re: Documentation enrichment

I Must agree too that a proper documentation is BADLY needed for a great product like this to really grow and succeed in the market.

I can extend my help for the documentation… :slight_smile:

But yeah, please a complete and well written documentation.

#6

Re: Documentation enrichment

Hi,
I recently bought 1 lincesnes and i am planning to buy few more licenses but i am dialoma to decide SC is right product for us

I would like to express my views…

  1. Script is a Great product with plenty of good features, which is easy to learn. But the Sample availble in the Website is only simple requirement. There is no detailed documentation of how to Customize, program macros & etc.,

  2. Poor Documentation -really make me depressed

  3. Support is not so good, and the reponse time is too long.

  4. I don’t know SC has a Tutorial or Book which talks about entire feature and function if yes i would like to buy

  5. There is no Search (Find options ) in source code. you may have to rember everthing and recall from the events and coding

  6. The Version 5 is expected to release, i don’t know when, It was told that those you purchased V4 in the month of oct-2009 will get V5 upgrade. But the SC support says, if the V5 is released before the support period otherwise no.

  7. In Future if we get few more liceses , it should work with older versions… Upgrade support is the big problem

  8. Code Ediior has lot of Bug , but support can’t help. It was told that the Intenent browser is not supoported.

  9. No option to uy support as a separate option…! Once 30 days is over…! No one can help…! Misareable situation…!

SCcript case has to address our problem.

Regards
Dhana

#7

Re: Documentation enrichment

I agree on the subject of this post. Documentation is very poor. Furthermore there’s no known product strategy and I have no clue what organization is behind scriptcase (except for the name of the company).

I wrote a letter containing these concerns a few weeks ago and send it to several departments at Netmake. I asked if they could give a response to my letter but so far I haven’t received any response.

It seems like they focus on the brasilian market only, and try to earn a few extra dollars by selling an english version of the product. The Portugese forum contains a few thousand posts, the english only about 350.

I like and use the product. As far as I know there’s no alternative php C.A.S.E. tool that offers as much as Scriptcase. Hopefully they change their strategy very soon.

#8

Re: Documentation enrichment

I hope they correct this as well. I understand from Sales that V5 docs will be improved. SC is a great product, they just need to correct this issue of bad docs.

As for the support, you can purchase additional support. Contact sales and they will send you a link. If they do not, then I will post the link I was provided for an additional 1 year support contract.

Regards,
Scott.

#9

Re: Documentation enrichment

Hi Scott,
They sell support alone…! Pls forward the link…!

regards
Dhana

#10

Re: Documentation enrichment

Any more news on when V5 is going to be released.
First I was told end of Sept, then end of Oct, so I really need to know a real date.
Alan

#11

Re: Documentation enrichment

I was told that it would be 1st week of November. I asked again at the end of last week and was told that they were working on the website, documentation and other items to get the product released. Hopefully this means very soon.

Regards,
Scott.

#12

Re: Documentation enrichment

Here is a link I was provided. You may want to email sales@scriptcase.com for other terms that may be available

https://www.regsoft.net/regsoft/vieworderpage.php3?state=enter&productid=74368

Regards,
Scott.

#13

Re: Documentation enrichment

Great …! I don’t find any option availble in ScriptCase website about this Support Option. I sent email to sales… Let me see

Thanks & Regards
Dhana

#14

Re: Documentation enrichment

@Scott,
I could really use V5 at this point. Just staring up my first real app and the Security portion sure would help.
I can’t wait much longer, so if it’s not within the next day or so, I will just have to use V4 and wait for V5 later.
Alan

#15

Re: Documentation enrichment

@asawyer13: I would suggest to build the application in V4 anyway. V5 will introduce new bugs and challenges, wait till they have released the first bugfix releases (service packs) for V5 to use it for production applications (I will).

on topic: is there any indication that the English documentation for V5 will be on an acceptable level?

#16

Re: Documentation enrichment

You’re no fun.
I do understand what you are suggesting.
I start today in V4.
I still consider myself pretty new to SC but I think it’s going to work for me.

#17

Re: Documentation enrichment

Let’s help each other with the issues we face during development, it’s the only resource we’ve got at this moment…

#18

Re: Documentation enrichment

We expect the V5 documentation good as well, But when they are going to release…?

#19

Re: Documentation enrichment

Dhana, on what information do you base your expectations of V5 documentation?

Do you have insight information from Netmake? If so, please paste it in this topic.

#20

Re: Documentation enrichment

I believe is it hopeful thinking that it cannot get any worse ;p

In talking with Sales and Support over the past few months, I believe our point has been made and it seems they have taken notice of their lack of documentation from comments I have received. Hopefully this is really the case. We will have to wait and see.

Regards,
Scott.