Is there a Scriptcase v9 this year?
Yes Scriptcase V9 will be out by end of March this year.
Scriptcase 9 will come with important implementations for Business Intelligence contemplating new options for Charts, also news features for Sumaries, Reports and Dashboards. Additionally there are significant improvements in the Security Module and Calendar Application. The development environment is reformulated with a new interface at the same time increased performance including the most recent version of PHP 7, among other innovations we will include a new project diagram and ER diagrams, all this and much more that comes with new version.
Scriptcase 9 is already in final phase of development, predicted to be released in the end of March, 2017. The projects developed in versions 7 and 8/8.1 will be fully compatible with version 9. Renewals and new licenses purchased after January 2017 will be entitled to an extended upgrade, i.e. the date of your license upgrade will be of 12 months, counted only from version 9 release.
You can read more here
https://www.scriptcase.net/lp/scriptcase9/
Regards:)
I am looking forward to improvements they have for this: “strong generator for management reports”.
I hope it has a nice interface and is easy to use and fast.
I almost sure is not what you expect
I am optimistic
Let’s hope that Scriptcase Version 9 delivers!!
I hope that Scriptcase v9 has wonderful changes this year.
http://pass4surekey.com/exam/300-115.html
I strongly hope with you because the SC8 is a pool of bugs. SC8 applications have a worst code I have seen nowadays. I is incomparable for example with Adminer which is part of a generator code known as Database Builder. But the final code is stable working and relatively fast.
Which final code do you mean - SC or Adminer?
I agree with you about code generated is not well structured and a lot of code is repeated between apps, but one of the things of SC is not have to worry about code generated. SC apps are not designed to modify it outside SC. Think about it as a bundled obfuscation system
Adminer is the heaven (and opensource) and SC is the hell.
As Giu sed. I mean if you happily generate something then the code is stable, and not change in time. But the generated code is still deserve a little vomiting every time when you see it.
The generator look quite good but working with them is so hard. There is a lot of really stupid old bugs. It seems that the code was written yesterday with a couple of beginners. I started to working with SC before 40 days and every day I found something bad. [SIZE=16px]Today I again found three bugs and day is not over.[/SIZE] I am really getting angry.
I don’t understand this either. I have several projects developed with SC, and I offer my outsourcing services worldwide with customer from different countries, and I’m not angry, and trust me, I worked (and work) with big projects, and I have a lot of reasons to be angry
I admire you Giu you must be so patient.
See this: http://www.scriptcase.net/forum/forum/scriptcase-8/bugs-aa/74883-mystery-bugs-in-sc8-code-creator
I Have another unpublished unsolved personal list of bugs (more than 200 lines).
[SIZE=16px]Yesterday I found 6 bugs together. This is my personal record.[/SIZE]
I don’t understand this either.
- nothing forking without bug and some workaround
- if you change something against the example you got in the trouble
- if you touch SQL in app you got in the trouble
- if you make unusual query you a in trouble
- app creation is unstable you don’t know when some “Mystery happens”
- hard to mixing two or more multilanguages project together
- you can not rename the project
- you can not create change log in project (workaround blank app)
- documentation is for beginners
- manuals do not speak about architecture or about life cycle of application example
- there are not PHP debugger. I hardly integrated Tracy the best one I know. In other project is the easiest task.
- hard to find errors
- SC8 often generate damaged query itself in manner of beginners mistakes
- SC8 itself able to damage application without detecting it
- There are not too for repair / recovery damaged application
- you can change colors and shapes but not really the layout
- yes there are good and awesome things too but only at first glance and behind everything is some bugs waiting to kick you
- [B]and of course the carles altitude of NetMage is annoying too
- [/B]of course there are many many not significant annoying things
So I think SC is not for professionals (coding abble) and inconvenient for big complicated projects.
There is also a security issue which I did not mention. CAN BE A POOL OF BUGS SECURE ?
If I count quality it is clearly THE WORST tool I have ever bought in my all life.
Idea is superb but the way the NetMake do it is a disaster.
All this thing is more than annoying. So I must say that SC8 is an old crap.
I am waiting for SC9. I will compare it against my personal bug list.
If it will be a crap too probably I will start an open source project “Opens SC 101” on github (everybody is wellcome)
I Have another unpublished unsolved personal list of bugs (more than 200 lines).
Yesterday I found 6 bugs together. This is my personal record.
I don’t understand this either.
- nothing forking without bug and some workaround
I don’t undertstand this.
- if you change something against the example you got in the trouble
What change you mean.
- if you touch SQL in app you got in the trouble
Specific sample? You can change SQL on grids without problems (you have to revise obviously your fields again), and forms needs to be synced against database as obvious.
- if you make unusual query you a in trouble
Well, I don’t see this as a bug as is, I mean, SQL parser of apps sometimes don’t works exactly as you expect if SQL is complex, use a view instead.
- you can not rename the project
Yes, this is a pain, a workaround is to export and import the project with another name, but come on, you don’t have to constantly to rename your projects to see this as a showstopper.
- you can not create change log in project (workaround blank app)
Don’t understand this. If you talk about Security module generates standard SC apps with code. You can change/or create from zero what you want.
If you talk about what you changed, well, not many tools has this, and you have to use a CVS for this, but a CVS is not possible with SC.
- documentation is for beginners
Documentation is almost inexistent, old, and bad translated. Use only macros webhelp, and take care.
- manuals do not speak about architecture or about life cycle of application example
Events speaks by itself.
- there are not PHP debugger. I hardly integrated Tracy the best one I know. In other project is the easiest task.
Try with Tracy as an external lib and calling it from a function, You can’t integrate namespaces because should be declared at first of your file, and you don’t have access to this place. You have xdebug and you can use it too if you need it with a compatible editor.
- hard to find errors
But this is not SC fault IMHO. Errors are always difficult to find, on SC and in every IDE you work. Specific situations should be revised.
- SC8 often generate damaged query itself in manner of beginners mistakes
Did you reported (using the right way to report bugs) the specific situation and query?
- SC8 itself able to damage application without detecting it
How?
- There are not too for repair / recovery damaged application
What do you understand as damaged app?
- you can change colors and shapes but not really the layout
Right now layout is basic yet. Meanwhile you have Free form for grids, and in 9 free form for Control and Form apps AFAIR.
https://www.youtube.com/watch?v=tukCY_EusPc
- yes there are good and awesome things too but only at first glance and behind everything is some bugs waiting to kick you
With all my respect but is not as serious as you try to show it, if not, we can’t work in everyday with our projects in production.
Don’t take me wrong, again with all my respect, but I don’t see this kind of messages as constructive. Yes, there are bugs (any project is free of bugs), and little annoying things here and there, I agree totally without discussion, but with this type of messages seems like SC don’t works, and THIS IS NOT TRUE.
Check brazilian forums to see that there aren’t too many toxic posts, and a lot of developers has big projects. And as I answered in other thread, I’m SC developer too, I frustrate too. BTW, I have a calendar app in production not showing the exit button, and who knows why the hell, and working as expected in dev. After some time struggling my head, I decided to create a button with the same behaviour, and now I have to report this to NetMake to see what could be the cause, posting and raging in forums don’t solve anything for several reasons.
- SC Team don’t check the forums right now AFAIK. Forums are for community. I, Albert, and others requested a lot of time to SC be part of forums, they appear, and some time after disappears, Netmake is a small company and can’t have a persons checking forums (I guess)
- Sometimes bugs reported are not bugs as is, and they can’t check every post, and try every situation of every forumer, without providing a sample project.
http://www.scriptcase.net/forum/forum/scriptcase-8/bugs-aa/8063-how-to-post-bugs
http://www.scriptcase.net/forum/forum/scriptcase-8/bugs-aa/73021-how-to-report-a-problem
Just take into consideration this. The assumption that NetMake don’t cares, is absurd. They can manage better or worst the things (mostly worst than better), but they care. Anybody wants a project don’t working as expected.
So I think SC is not for professionals (coding abble) and inconvenient for big complicated projects.
I don’t know how to take this. What am I? a baker?
All this thing is more than annoying. So I must say that SC8 is an old crap.
I am waiting for SC9. I will compare it against my personal bug list.
If it will be a crap too probably I will start an open source project “Opens SC 101” on github (everybody is wellcome)
Sorry to say this but, don’t wait for 9, start now. Don’t expects to 9 to be a complete change. 9 Will release with bugs, as always, changes will come, but with time. 9 is not a SC rewrite, is a pretty layer over it with some new features, to sell new licenses (and I hope to be wrong, but I don’t expects it). Netmake concept of time is different of ours.
If you can fight with some workarounds, and how things are done in SC, you will be happy here, if not, you will be raging always. You are in time to leave if you think so.
I Have another unpublished unsolved personal list of bugs (more than 200 lines).
Yesterday I found 6 bugs together. This is my personal record.
I don’t understand this either.
- nothing forking without bug and some workaround
I don’t undertstand this.
Nearly every time I experience some bad things about SC I record some kind of log to myself. If I found something again I look in the logs and the situation is more clear.
There are some tags and discovery date. Comments is brief and sometimes hard to understand to others. You can see a part of it right in the next part of post.
- if you change something against the example you got in the trouble
For example from real life:
Yesterday I modified the “Security module” the group modes to my needs.
- In the module they used “login” as a primary key.
app_form_edit_users: - I changed it to integer auto increment (AI) and the trouble started.
- new record - N-N relation stop working because of this, no ID on write time, unable to force LAST ID
- no workaround exist, so I try to hide NN field in NEW
- change it in “Edit fields” corrupts the N-N relation and damage the app
- so I try workaround by “double select” field
- now it works with BUG the default value of doble select can be set only one time, ajax request have no effect
- I can’t to do it as I want
- I continue with other issue, I need to change field (autocomplet) based on change of another field (select | autocomplet) and pass another ID as select have.
- I have the forin ID in the row but there is only two parameters.
- OK, i found workaround to change the first ID created from two integer connected with gluee example: “4_40”
- I can extract both ID but the app stop working due to bad SQL generation by SC.
- First autocomplet can’t work with textual ID thanks to a beginers BUG in SC.
- I need to solve it in another complicated way
- one app and a too many obstacles
my personal bug log for this issue:
[SIZE=8px]-------------------------------------------
[BUG][Double select][18.02.2017]
- default value is set only first time, other (ajax) request have no effect.
- other field is changing
[BUG][TEXT AUTOCOMPLT][17.02.2017]
- when there used textual index the SC damages the query
(pdo-mysql): SELECT idrp,label
FROM sec_roles_members WHERE (role
= ‘1’) AND idrp = 9_9 - I try to add quotes
(pdo-mysql): SELECT idrp,label
FROM sec_roles_members WHERE (role
= ‘1’) AND idrp = ‘9_9’
[BUG][FORM][N-N relations][Synchronize table][17.02.2017]
- can not be changed the visibility in “Edit fields”
- when I change it in “Edit fields” to not show in new mode, then the SC transfrom the field to native SQL field
- so it corupt the applications
- consequently Synchronize table erase fields from N-N relations and custom fields
[BUG][FORM][TEXT AUTOCOMPLT][INSERT][17.02.2017]
- as a workaround I used ID in format INT:INT
- consequently SC8 corrupt the SQL query
- (pdo-mysql): SELECT idrp,
label
FROM sec_roles_members WHERE (role
= ‘1’) AND idrp = 5:5 - i changed the glue to ‘_’ again some problems appears
- Changing some how the SQL is a disaster
[BUG][FORM][TEXT AUTOCOMPLT][INSERT][17.02.2017]
- query: SELECT sc_concat(id,’:’,person_id) ,
label
FROM sec_roles_members whererole
= ‘[login_role]’ - transformend: (pdo-mysql): SELECT concat(id,’:’,person_id) ,
label
FROM sec_roles_members WHERE (role
= ‘1’) AND concat(id = 0
[BUG][FORM][INSERT][17.02.2017]
- sometimes the sc generate wrong sql query ???
- (pdo-mysql): INSERT INTO sec_logins (id_login, person_id, rid, role_id, login, pswd, email, activation_code, priv_admin, active, note, creator, editor, created, edited, ) VALUES (0, 0, 0, 2, ‘admin’, ‘0cc175b9c0f1b6a831c399e269772661’, ‘mbardiovsky@gmail.com’, ‘’, ‘’, ‘Y’, ‘’, 0, 0, null, null, ‘’)
- N-N relations relation field was put to SQL field, after synchro, the N-N field was deleted
[BAD-FEATURE][FORM][N-N relations][17.02.2017]
- event onAfterinsert is trigered before N-N relations and so it is unable to use it for AI tables
- no way to force LAST ID
- ‘LAST ID’ is mising in from SC framework, if it there we can chose that and it is OK
[BAD-FEATURE][FORM][17.02.2017]
- Dependencies - if changes the sql table name then not posible to change dependency rules
- erase and create
-------------------------------------------[/SIZE]
- if you touch SQL in app you got in the trouble
Specific sample? You can change SQL on grids without problems (you have to revise obviously your fields again), and forms needs to be synced against database as obvious.
Well, I don’t see this as a bug as is, I mean, SQL parser of apps sometimes don’t works exactly as you expect if SQL is complex, use a view instead.
I mean that
- if you change table in DB,
- if you change SQL field disappearing without warning or transferring the setting to another field
- if you change the table name impossible to change dependencies
- before mentioned SQL corruptions
- you can not rename the project
Yes, this is a pain, a workaround is to export and import the project with another name, but come on, you don’t have to constantly to rename your projects to see this as a showstopper.
Yes you a right but I consider the project rename as a basic functionality it its shows that is uncontrolled. Why I need to use workaround for a such basic things ?
- hard to find errors
But this is not SC fault IMHO. Errors are always difficult to find, on SC and in every IDE you work. Specific situations should be revised.
I mean
- nothing to say SC warnings and error messages without exact information
- absence of internal PHP debugger
But yes, it is overcomable
- you can change colors and shapes but not really the layout
Right now layout is basic yet. Meanwhile you have Free form for grids, and in 9 free form for Control and Form apps AFAIR.
https://www.youtube.com/watch?v=tukCY_EusPc
- by layout I mean positioning and total control of appearance
- if there a div boxes instead tables it would be better
- too many inline styles
- yes there are some insufficient possibilities
- you can not create change log in project (workaround blank app)
Don’t understand this. If you talk about Security module generates standard SC apps with code. You can change/or create from zero what you want.
If you talk about what you changed, well, not many tools has this, and you have to use a CVS for this, but a CVS is not possible with SC.
- nothing more than an text or md (mark down) file with name ‘changelog’ to preserve important info about the project and apps
But yes, it is overcomable
EXAMPLE:
Version 5.6.30 19 Jan 2017
EXIF:
Fixed bug #73737 (FPE when parsing a tag format). (CVE-2016-10158)
GD:
Fixed bug #73549 (Use after free when stream is passed to imagepng).
Fixed bug #73868 (DOS vulnerability in gdImageCreateFromGd2Ctx()). (CVE-2016-10167)
Fixed bug #73869 (Signed Integer Overflow gd_io.c). (CVE-2016-10168)
- SC8 itself able to damage application without detecting it
How?
I do not know why and how but it is the worst core bugs.
- There are not tool for repair / recovery damaged application
What do you understand as damaged app?
Don’t say me that you never experienced that. LOOK HERE
- SC8 often generate damaged query itself in manner of beginners mistakes
Did you reported (using the right way to report bugs) the specific situation and query?
No, not now. I had a bad experience with NM support. Reporting bugs is too time consuming and I got a strong feeling that nobody really cares about this things.
As an evidence indicates that there a lot of old and stupid bugs and things existing over more versions of SC.
- yes there are good and awesome things too but only at first glance and behind everything is some bugs waiting to kick you
Don’t take me wrong, again with all my respect, but I don’t see this kind of messages as constructive. Yes, there are bugs (any project is free of bugs), and little annoying things here and there, I agree totally without discussion, but with this type of messages seems like SC don’t works, and THIS IS NOT TRUE. …
I know that they are working on something for example on SC9, but what about the bugs ???
I meant this: see "For example from real life": (on the top of this post)
You see N-N relations is great thing but not working for insert new record with AI primary key.
Doble select is a good thing too but not working in FORM as should.
I really like SC8 for its wide functions and possibilities and the same way I hate it because of lot bugs.
So I think SC is not for professionals (coding abble) and inconvenient for big complicated projects.
I don’t know how to take this. What am I? a baker?
Sorry for offend you.
I mean it that if somebody is a PHP professionals and working in nowadays standards and with OOP used to work with some modern framework that it is a big disappointment.
I have a feeling that I went back to the past 10 years before now.
… to be continued
Wait, I bought an upgrade in november of 2016 because on their webpage v9 launch will be on January of 2017 and they offered the upgrade, later they extended the launch of v9 and started to say that v9 will be for buys starting on January of 2017? Am I mistaken or they fooled me?
What does that mean? I’ve renewed mine annually since I bought it - in November 2 or 3 years ago.
You should apply to upgrade, I think you don’t have to worry (I guess, I’m not Netmake employee)
meanwhile you have a valid subscription you apply to renewals. What offers normally say every new version, is, that if you renew, your renewal year period starts to count after the version to be released
There is one critical feature that I need for charts… The ability to identify the SCALE of the x-axis or y-axis. When the charts are generated, they default to 0,0 and the range may be too large for a chart to show data variations. For example: if you have a chart showing a series of times: 25.1, 25.6, 25.3, 24.9, 25.2 24.6 - when the 0,0 is used for the starting point of the graph, the resulting line is mostly flat… changing the scale of the axis would allow observing the fluctuation of data that is significant for the graph. PLEASE tell me this is going to be available!
http://www.scriptcase.net/lp/scriptcase9/ is still saying “[SIZE=12px]predicted to be released in the end of March, 2017[/SIZE].”
One more week to go
If there is going to be a delay (which is OK), please update the site so we all know.