Ideas for Google Summer of Code/Visual interface to write structural transfer rules

From Apertium

< Ideas for Google Summer of Code

Jump to navigation Jump to search

Contents

1 Tasks
2 Coding challenge
3 Frequently asked questions
4 See also

Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, but clumsy and may be hard to write. The idea is to design a visual programming language of the style of like Scratch, where jigsaw-puzzle-style pieces corresponding to statements and control structures fit only if the syntax is right.

Tasks

Write a graphical user interface to write structural transfer rules (one that reads in (a subset of) the current XML-based language, allows for a graphical, intuitive editing of the rules, and writes compilable .t1x, .t2x or .t3x files)

Coding challenge

Install Apertium (see Installation)
Go through the new language pair HOWTO

Frequently asked questions

none yet, ask us something! :)

See also

Check Appinventor.

Check Blockly.

Check Snap

Retrieved from "https://wiki.apertium.org/w/index.php?title=Ideas_for_Google_Summer_of_Code/Visual_interface_to_write_structural_transfer_rules&oldid=54002"

Ideas for Google Summer of Code