Difference between revisions of "Ideas for Google Summer of Code/Visual interface to write structural transfer rules"

From Apertium
Jump to navigation Jump to search
Line 22: Line 22:
 
Check [http://code.google.com/p/blockly/ Blockly].
  
Check [http://code.google.com/p/blockly/ Blockly].
   
  +
Check [http://snap.berkeley.edu/]
−  
   
 
[[Category:Ideas for Google Summer of Code|Visual interface to write structural transfer rules]]
  
[[Category:Ideas for Google Summer of Code|Visual interface to write structural transfer rules]]

Revision as of 01:11, 18 August 2015

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

Frequently asked questions

  • none yet, ask us something! :)

See also

Check Appinventor.

Check Blockly.

Check [1]

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