Skip to content

Doc #243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 5, 2020
Merged

Doc #243

Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,12 @@

1. It's quick to write browser applications in **_EasyCoder_**. Website development is faster and sites are more reliable because they are more compact and easier to read.
1. **_EasyCoder_** scripts are smaller than the corresponding JavaScript and are easy to read by most people, not just by programmers. This matters later on when maintenance is needed and the original programmer may no longer be available.
1. **_EasyCoder_** has the ability to single-step its scripts, showing you its variables at each step, which makes it easier to see what's happening.
1. **_EasyCoder_** is well suited to the construction of single-page web designs of unlimited size. The memory space occupied by JavaScript remains roughly the same no matter how many scripts and data you load and unload using REST. There is no memory or performance hit as the size of the project grows, because unused modules remain on the server, ready for use, instead of taking up permanent browser space.
1. When things go wrong an error message pops up, showing you which line of the code you reached. The error message also gets written to the browser console.
1. The language has plain English commands to do things that are complex to do in JavaScript, such as handling REST dialogs, custom GUI elements and vector graphics. These are all written in JavaScript and supplied as seamless extensions in the form of plug-in modules.
1. Program data can be put into JSON files and either provided as a hidden block in your HTML or downloaded on demand using the REST commands. This allows you to keep your HTML as just structure and to write the content in from the script.
1. **_EasyCoder_** has a fully pluggable architecture. This allows any owner of JavaScript functionality to 'wrap' this in script commands and offer it as a plugin, allowing any site developer to use it without the need to learn JavaScript. Typical examples of such wrappers that are already provided are Google Maps and CKEditor, both of which present a concise API and functionality that's easily understood and easy to describe in plain English. Well-encapsulated products are ideal candidates for implementation as **_EasyCoder_** plug-ins.
1. **_EasyCoder_** has the ability to single-step its scripts, showing you its variables at each step, which makes it easier to see what's happening.
1. **_EasyCoder_** includes a REST server that permits scripts to access resources on demand from the server rather than having them embedded in the page. Resources include scripts, HTML components, CSS and general data, and all can be loaded and unloaded dynamically. Two versions of the REST server are provided, written in PHP and Python respectively.
1. **_EasyCoder_** is well suited to the construction of single-page web designs of unlimited size. The memory space occupied by JavaScript remains roughly the same no matter how many scripts and data you load and unload using REST. There is no memory or performance hit as the size of the project grows, because unused modules remain on the server, ready for use, instead of taking up permanent browser space.

To use **_EasyCoder_** all you need is to include its main JavaScript file in the _HEAD_ of your web page. It will call in any other JavaScript files it needs. An introductory example is given in the Introduction page of [our website](https://easycoder.github.io). You can alternatively build a standalone page where all the files are present on your own server, which avoids any possible risk of your site breaking when updates occur. We do our best to prevent this happening but it's impossible to cover all possibilities.

Expand Down