Snap!
| Краткое описание языка | |
|---|---|
| Компетенции в каких сферах формирует | Empowered Learner, Knowledge Constructor, Innovative Designer, Computational Thinker |
| Парадигмы программирования | |
| Возрастная категория | 14 |
| Назначение языка (Общее / Учебное) | Мини-язык для обучения |
| Visual_Text_Blocks | Блоки-Иконки |
| Измерение (2D/3D/Tangible) | 2D |
| Область знаний | |
| Открытость продукта | Открытый |
| Address | http://snap.berkeley.edu/ |
| Предки (Ancestors) | Scratch |
| Потомки (Descendants) | NetsBlox, SciSnap! |
| Активность в данный момент | Project is active |
| Доступны ремиксы? | Yes |
| Год создания | 2010 |
| Создатели | Brian Harvey, Jens Mönig |
| Поясняющее видео | |
| Используется для создания мобильных приложений? |
- Snap! упоминается в свойствах следующих страниц
- API, Arduino, Big O notation, CSV, Clock, Complex network analysis, Computer Science Logo Style, Computer Science with Snap! by Examples, Development of computational thinking based on collective interaction in MediaWiki and multi-agent approach, Dog chases cat and cat chases mouse, Egorovsn051, ElenaGrcaheva, Ergo Jr, Finch Robot, Flocking (model), Foo, GIS, GPT, Game design, Harvey, Heap, How to Keep Score in a Game, How to Move Sprites with the Arrow Keys, How to Move a Sprite in a Spiral, Hummingbird, JSON, K-means, Lieberman, Milena.aslamazova, Movement, Object Attraction, Patarakin, Pathfinding, Practice defining problems to solve by computing for data analysis, modeling or algorithmic thinking, Remix, Simply Scheme: Introducing Computer Science, Simulation models on the field of computational didactics, Sprite, Structure and Interpretation of Computer Programs, Switching Between Screens, Traffic jams, Using Clones for Particle Effects, Using Prototypical Objects to Implement Shared Behavior in Object Oriented Systems, Абстракция, Агентное моделирование, Активное эссе, Алгоритм, Алгоритмы и структуры данных (syllabus), Анализ данных, Анализ и интерпретация данных (syllabus)… следующие результаты
Snap! - потомок языка Scratch. В отличие от Scratch Snap! поддерживает лямбда-исчисление, объекты первого класса, процедуры, рекурсия и множество других возможностей. С версии 4.0 Snap! получил современное название и был переписан на JavaScript. Язык активно используется для обучения информатике (computer science) UC Berkeley учебный курс Beauty and Joy of Computing Curriculum
SNAP! is also a great way to program the Hummingbird Robotics Kit.
- Существует средство конвертации Scratch проектов в Snap! - https://snapinator.github.io/
- Вики о Snap! https://snapwiki.miraheze.org/wiki/Snap!
- Руководство - Snap! Manual - http://snapapps.github.io/edgy/app/edgy/help/SnapManual.pdf
В нашей вики digida.mgpu.ru можно использовать визуальные блоки Scratch для представления программ Snap!
when @greenFlag clicked ::control
say [I am very confused about Snap!] for (2) seconds:: looks
visit [https://snapwiki.miraheze.org/] ::sensing
for each ((item::reporter variables)::#dc4c14) in (list [blocks] [features] [and others] @delInput @addInput::#ea9473) {
think [hmm...] for (2) seconds::looks
say (join [I now know about ] (item) [.] @delInput @addInput:: operators
wait (0.5) seconds::control
}::#dc4c14
say [That clears some things up.] for (2) seconds::looks cap
Важно, что и сами проекты Snap! могут быть встроены в тексты вики страниц
(the [] block :: operators)
When reading the map example above, was it immediately obvious that each list item is plugged into the empty slot in the (() + (3)) block? Elementary school teachers all know that if an eight-year-old is presented with "x+3=7" and asked "what's x?" they are likely to get a blank stare, but if the same kid is shown "☐+3=7" and asked "what number goes in the square?" they are likely to answer "four."
Snap! uses that knowledge in the design of the notation for functions. When a grey-ringed function with input is called, call looks for an empty input slot inside the ring, and that's where the input value is inserted. This notation makes simple function calling obvious, in the Scratch spirit of trying to use the visual representation to make ideas obvious. The empty input slot mechanism is not good enough for the complicated cases, such as nesting a map call inside the function input to another map call. For those cases grey rings can be given explicit input names, just like a custom block: (((x::variables) + (3)) input names: (x::variables) @delInput @addInput :: grey ring).
