chargebops.blogg.se - Scriptcase macros

SCRIPTCASE MACROS INSTALL
SCRIPTCASE MACROS GENERATOR
SCRIPTCASE MACROS MANUAL
SCRIPTCASE MACROS PATCH
SCRIPTCASE MACROS FULL

Fix: users reported that the editor was not visible in some versions of Firefox.

Change alert messages to use the modal module.

Fix a problem that caused the field to select the event 'OnRecord/OnFinish' to be hidden when editing a 'Run' button.

SCRIPTCASE MACROS INSTALL

Change how the Install Id is synchronized with Firebase.

Fix an issue with Firefox which caused an warning message to show on developer console.

Performance improvement for the new editor to work with large content.

Fix an issue which caused a warning message (string.split) to show on developer console.

Fix an issue with the Save command for buttons of type "Run".

Fix an issue which sometimes caused macro documentation not to get the selected text.

New option to change settings for the new editor ("Preferences").

SCRIPTCASE MACROS GENERATOR

Lorem Ipsum generator - see more details.New features for the (new) code editor:.

SCRIPTCASE MACROS FULL

Add full compatibility with ScriptCase 9.

all outdated applications), and also save/restore a selection

New option "App Selection" which allows you to quickly select specific applications (e.g.

Fix an issue which prevented the option "Parameters(Fields)" to be shown when editing an ajax event (thank you Enrico!).

Fix an issue which sometimes caused the new editor not to load properly.

New option "Tab shortcuts" to switch between open tabs in ScriptCase, i.e., applications being edited (left ALT + number).

Extension is disabled for ScriptCase > v9.0.43.

Adjust the width of the extension's popup.

Improve the algorithm to identify the event which is being edited.

Extension is disabled for ScriptCase >= v9.0.43.

Extension is disabled for ScriptCase >= v9.

Adjust when checking ScriptCase's version.

This project is not affiliated with, sponsored by, or endorsed by Netmake Soluções em Informática.

SCRIPTCASE MACROS PATCH

When your new feature (or fix) is ready, submit a pull request and/or attach a patch to your issue. If you are working on a new feature, please create an issue for the feature you’re working on so that we can all avoid duplicating effort. Submit bug reports, ideas or new features.And because of that, this extension heavily depends on ScriptCase's code and structure (e.g., specifics JavaScript functions, the DOM structure, some elements with specific ID/class name). How does it work?īecause ScriptCase doesn't provide a public API, hacking into its JavaScript/HTML/CSS code was the (only) way to go. This browser extension was created to fulfill these gaps. If you often use ScriptCase to develop your applications, you've probably noticed that its development environment lacks some basic functionalities (e.g., no shortcut keys, not restoring last cursor position), while others could be improved (e.g., code editor, main menu sensitivity).Įven though some users have pointed out some of the problems on ScriptCase official forum, those improvements haven't been made yet. Other ScriptCase versions might work correctly, but were not tested.Īny problem with ScriptCase Tools in the above Scriptcases environment should be reported as a bug in our issue tracker or as a message to Why was ScriptCase Tools built? Wait for the confirmation popup and then click on the "Install" button.Download the compiled and signed file at.That is why there's not an official link in Firefox's webstore for ScriptCase Tools and it must be manually downloaded, which is very simple: And because ScriptCase Tools is an extension intented to be used with ScriptCase, which is a paid software, it was not accepted as a listed add-on. That means an extension can't be published (listed) in Firefox's "webstore" if it works together with a paid software, and although the add-on is digitally signed by Firefox's webstore, the file must be hosted by the owner/author. Require payment to use core add-on features (upfront or after trial) In this case, we need to ask you to switch your add-on to 'unlisted' (=selfhosted) as the add-on requires a payment for it to be useful. It took 19 days to receive a response for the first publishing attempt:ĭoes this add-on only work with paid software?

All extensions are manually reviewed by employers (or some volunteers), thus making the publishing process extremely slow: everytime an extension is submitted, whether the very first or a new version, it goes to the end of the reviewing queue. Review, signing, and distributing policies are different at Firefox's "webstore" (AMO).

Click " Load unpacked extension." and select the " source" folder inside the (unzipped) folder.

Ensure the checkbox labeled Developer mode is enabled.

SCRIPTCASE MACROS MANUAL

Manual Installation (latest/development version) Go to Chrome Web Store to install the release version. Installation Google Chrome Quick Installation A browser extension to make working with ScriptCase simpler and even more productive.