attoX is the extension system for atto, which allows features to be added to the language through JavaScript .attox.js files.

Extensions can be loaded with extload url, and unloaded with extunload url. An extension's commands can be then accessed with name.command, where name is the extension name, and command is the command for that extension. The extension's name can be assigned to the user by entering extload url, name, which can also be used to load multiple instances of the same extension.

Example usage of attoX:

10 extload "http"
20 extload "json"
30 input "Enter your name: ", name$
40 http.get "https://api.agify.io?name="; name$, data$
50 json.parse data$, "age", age%
60 print "Your age is probably "; age%; "..."
70 print "Don't quote me on that, though!"

Here's a few extensions that either already exist for attoX (in this PR), we are working on, or we'd like to add:

• [x] HTTP GET/POST (eg. http.get "https://atto.devicefuture.org", data$, status)
• [x] JSON parsing (eg. json.parse `{"data": {"number": 123, "string": "hello"}}`, "data.string", data$)
• [x] WebRTC/broadcasting communications
• [ ] Weather API (we could use something like OpenWeatherMap)
• [ ] Raspberry Pi/Arduino GPIO interfacing
• [ ] micro:bit interfacing
• [ ] LEGO Mindstorms NXT/EV3 robotics interfacing

Over the coming days, we plan to move atto to a new home, where we will continue to develop atto and build new projects that are part of the atto ecosystem. We're calling our new home DeviceFuture, since we believe that atto plays a part in the future of creating open, accessible software and hardware that anyone can get their hands on and start using to learn about the world of digital technology!

atto will still be maintained by the same people, and we've got some awesome features planned for the future of atto. In order to do this, we're creating the DeviceFuture organisation to develop a unified brand consisting of atto and its related projects.

We will soon be moving atto over to the @devicefuture GitHub organisation where we will then resume fixing bugs, adding features and making atto cooler with every release. This will mean that atto will experience downtime for a short period while we perform this migration. We expect the downtime to last up to a few hours, but if all goes well, you shouldn't notice a thing.

We will move atto to a new domain (atto.devicefuture.org) and to a new GitHub path (devicefuture/atto). GitHub will automatically redirect the old path (James-Livesey/atto) to the new one for those who have made bookmarks of the repo. We will also redirect the jamesl.me/atto path to our new domain, along with all of atto's subpages and custom links. That way, you (hopefully) won't have to manually update all your bookmarks and links to atto!

We're looking forward to the (device)future of atto, and can't wait to work on new projects that we're sure you'll love! Feel free to leave any questions about this migration on this issue, and I'll do my best to answer them ASAP. 😀

-James

Atto has problems with some Unicode characters (like emoji).

Example program:

10 PRINT "Καλημέρα 😄"

test.atto.txt

The problem is that when accessing chars like text[9], the emoji is returned in two parts (positions 9 & 10). A workaround is to do:

var chars = Array.from(text);

Then chars[9] will return "😄".

Applying this change to term.js:print() and canvas.js:drawText() seems to be enough to make the above program run correctly. The program listing still has problems though, because of the hid.js:render function.

Implement a simple dark mode theme.

• Auto-detection happens once on startup using a media query
• Changed the absolute minimum amount of code

Further possible enhancements:

• Move all color definitions to the new theme.js
• Export default background and default foreground colors from theme.js
• (Maybe) replace media query with toggle button and use localStorage to remember choice

Note: Feel free to make any changes you like or even reject the PR. I just went ahead and implemented it for my use case as I saw best. Thanks for atto!

This PR implements turtle graphics commands, namely show, hide, forward, backward, left, right, penup, pendown and angle. Relevant reference documentation for turtle graphics is also available in this PR.

Consider this program:

 10 PRINT "OK"
 20 GOTO 1

This reports an error ("cannot goto a nonexistant line"), but I think it should fall-through. Reporting an invalid line is probably the correct choice with:

 10 PRINT "BLAH"
 20 GOTO 3000
 2000 PRINT "BLAH"

I guess here the expectation is that GOTO should go to the named line, and if it isn't present the next one that is there. But be limited by the upper-bound of lines that was used.

This includes commands such as list, edit, import, export etc. which can't be used inside programs; only the shell. A new styling for the <kbd> element was also added so that keyboard shortcuts for these commands can be displayed too.

We should be able to write just if booleanCondition instead of having to write if booleanCondition=1, much like with other programming languages. This may require a much-needed overhaul to some of the boolean logic operator behaviour and operator evaluation in general.

We also should have true and false constants, which could be evaluated to 1 and 0 respectively. Then, if conditions can check if an expression's value is nonzero as a means of checking if the value is true.

Fixes #21. This pull request adds emoji support, allowing users to insert multi-codepoint characters. It also modifies the syntax highlighting system and canvas rendering system to do so.

Emojis are scaled by a scale factor of 0.65 to ensure that they do not leave rendering artifacts when rendering on top of an old representation of a cell (a dirty cell).

Based on the comments on Issue #15 https://github.com/James-Livesey/atto/issues/15 I proposed the changes for the gosub example. On the other hand, a typo on the repeat example foes not allow to run it

the sample code: 10 diameter=5 20 gosub 100 30 print area 40 diameter=12 50 gosub 100 60 print area 70 end 100 print "The area of a circle of diameter "; diameter; " is: "; 110 area = pi*(diameter/2)^2 120 return run The area of a circle of diameter 5 is 19.6349540849 The area of a circle of diameter 12 is 113.0973355292 Mismatched statement closing mark at line 70

Adds an error when no error should be the expected

In this other example (forget about the logic ) Nothing to return to at line 160 Ready shows up

10 cls 20 number_marks = 0 30 while number_marks < 100 40 if number_marks mod 2 = 1 50 ratius=10 60 gosub 140 70 else 80 ratius=5 90 gosub 140 100 break 110 number_marks = number_marks + 1 120 loop 130 end 140 move 250, 200 150 draw ratius, ratius + number_marks 160 return

There's only two courses in the help guide so far. It would be great to have more courses on some of the other aspects of atto, too!

One example of a course to write is how to make subroutines using gosub/return.

This adds the getkey command that opens the door to games! I was surprised this isn't already built-in (although I did find the undocumented key variable).

Accompanying getkey is readkey, which is the same but will not block if there is no key waiting.