New library issues

Scriptcase 8 Bugs
#1

We’ve started to work out the use of the new library module. Until now we have been using the old model. Beneath are our findings which includes some issues we would like to have answered/fixed/solved. Perhaps we are doing some things wrong, I don’t know:

  1. We created a new public (we only have to options now, public and project)

  2. If you want to create a new file than we think you can do that only by uploading a file. Then you are able to edit it. IF you use ‘new file’ then this file is created but you can only rename the file or delete it. You cannot edit it?

  3. Uploading file: Je get a form with Portuguese text on a button to select a file.

  4. You cannot use scriptcase macro’s in the library. That makes it unusable.

5 While creating a new library and uploading the first file, the editor theme will be changed to ‘base 16 light’. Nice theme but some characters like quotes are pretty bad readable. You need to change these in default. If not then you have trouble everywhere in all editors. This only happens if you create a new library and upload a file and then try to edit it.

  1. You can read global values, but you cannot set them. Looks logical, because you can use parameters, but it’s not consistent. But to convert old libraries this is a bummer. Is this intended?

  2. In ‘public’ the library does not work. The library is not copied to the right spot when files are generated. It does with project. A know issue also reported on the forum.

Currently the new library module is unusable imho.

#2

  1. With the projects libraries you can create and edit files direclty in SC, if you write the filename including the extensions (tested with *.php and *.js files; haven’t tried anything else yet)

  2. I think its’ sort of by design: the ‘old’ part in “Scripts (Old Libraries)” seem to just indicate the former name, not that those are legacy or going away soon since SC Macros are usable only there.

#3

I assume that if a function is marked as ‘old’ and another is used as ‘new’ that the old function is deprecated. Therefore I think it’s important to have a consistent working. Currently that’s not the case and while the use of the new libraries are promoted the result is confusion.

#4

Albert, my interpretation is that thay are not marking that function as old. They are just renaming to Script the old Library function so that they can use Library as the name of the new and different function. Maybe they should have written something like:
“Scritpts (formerly known as Libraries)”.
But I could be wrong. It’s just my opinion.
And of course a single Library environment where SC macros could be used, would be better.