Is NetMake going to address the list of bugs that were posted on this forum? Simply deleting the posts without addressing the Bugs themselves in any fashion is serious malpractice.
Same feelings here, deleting posts just because it shows the failure of Netmake in fixing their bugs is really bad indicator and reflect a dark image of the future of great product like Scriptcase, I am one of those who using Scriptcase for years and i will left it soon because of Netmake behaviors.
The only reason that i am using Scriptcase now is that i am running some projects and i have to make them alive until i re-build them again in alternative RAD.
It’s actually not up to me to answer a question like this, but on the FB page SC had a formal reaction regarding this. Was trying to copy it here but the thread was deleted there so I can’t. But in short, they admit that issues sometimes have a long history, but they are aware and promise that they are working hard to fix any issues, in fact they will not release a major version but only short follow-ups so that they are not overwhelmed by issues on every new release. Personally I know they have a mantis in place, unfortunately it’s Portuguese. A long discussion.
hi iiiax
Also I will abandon SC, but like you I have projects done to which I have to do maintenance.
What RAD have you tried? Which do you think you’re interested in?
I would like to stay in a RAD that uses php / mysql-mariadb to break down the learning curve.
Hello
Enrico
I am really sorry that this is how our move was received. I am the responsible for the recent mass post deletion in the forum. It was not meant to hide bugs or anything alike, but to purge the posts from a user called @Jena_Matusen that has been using another person’s identity to post here. The posts could not remain in our pages once we received the information about the real person from who the Jena stole the identity. I hope you understand why I can’t provide any more details about this.
The posts itself were soft-deleted and moderators have access to them. A lot of bug fixes came from this forum and we are willing to keep up with that. I, for one, can confirm that we are slow to fix some bugs, but it is more due to a complex and unneficient reporting and releasing process than to our unwillingness to do so. We are putting some major efforts in changing those processes in order to provide more agile and reliable bug management.
I’ll also be fixing this topic for a while, so people will be able to read and understand why some posts are gone and what they can expect about it. I’m sorry I didn’t provide any official statement about this before.
Alright! Some movement in the right direction. That was what I was hoping to see.
Thanks Henriqueb, for your honesty and perseverance.
Dear @Henriqueb
Really this is the first time that i see Netmake doing something positive in the right direction, Thank you so much
Thanks for the update.
Besides the fact that Jena Matusen was a fake account with a stolen identity, I must say that I did not find it appropriate for this person to hijack the forum. It is okay to post about a bug or trouble that one may have. However, I definitely do not find it acceptable for someone to keep posting sensational posts in huge coloured fonts with headings in capital – and so many that it continually drowns out other posts on the first page of the forum. It gives a negatively biased and untrue picture of ScriptCase to existing and potential new users. Also, it deter others from having positive exchanges about making applications using ScriptCase. In my book, such behaviour alone warrants exclusion from a forum. Try to do the same on one of the other RAD tool suppliers’ forums and see how far you get before you find yourself banned and / or censored.
I welcome your initiative to get better control of the bugs and look forward to hear more about it. Besides any internal system you may have, you could consider a simple, public facing bug-info system (e.g. build in ScriptCase) where on couuld read info about bugs as well as work arounds. Most RAD tool vendors carry luggage of less critical bugs with them from version to version – nothing new or surprising there :-). However, being able to read about bugs, critical and less important, as well as how to work around or avoid them, gives a good impression of control and openness. Such a system could have access limited to users with active licenses.
In general it would be great with regular news from ScriptCase, e.g. a (bi)weekly update of how you are doing and your plans. I think it would go a long way to build a positive impression of ScriptCase.
Thank you so much for updating us. It would be very nice to see a list of the bugs and the order they are being addressed. I would like to see the security issues worked on first to make all the applications more secure.
To help Netmake with bugs, please document all the steps you have taken
1.Screenshot of error
2. Screenshot or example of code not working
3. Please be prepared to answer additional questions Netmake may ask.
4. Test for same conditions in multiple browsers
5. Please be prepared to send Netmake the app or for them to remote into your system.
Please send all this info to Henriqueb, this will make tracking down the bug easier. Henriqueb seems to be our point of contact to get these bugs looked at by the proper people and to get them on the bug list to be fixed if they are confirmed as a bug.
Everyone we have a point of contact and lets use it to get bugs and issues resolved.
Thank You,
Dr Tim