From c160933061f58a0f64a6037c1db8b79fb725b495 Mon Sep 17 00:00:00 2001 From: Yorhel Date: Sat, 26 Sep 2009 10:59:18 +0200 Subject: Converted VN relations to ENUM data type and made them translatable OK, these are actually two separate things: to make the relations translatable they didn't necessarily have to be stored as enum, and I could've also converted them to enum but not have it translatable. Nevertheless, it was easier to just do both at the same time. Also note how I used the string "$____vnrel_____$" as identifier in the relation graphs while I could have used something a lot shorter ("$$" would have been fine, for example). This is done so that graphviz can make some space for those relations - the long identifier gives a slightly more realistic representation of the actual length of the relation titles. --- static/f/forms.js | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'static/f') diff --git a/static/f/forms.js b/static/f/forms.js index ce9daab5..8c3e4e8b 100644 --- a/static/f/forms.js +++ b/static/f/forms.js @@ -199,7 +199,7 @@ function relLoad() { // fetch the relation types from the add new relation selectbox l = x('relation_new').getElementsByTagName('select')[0].options; for(i=0;i'+qq(relTypes[i])+''; t = document.createElement('td'); t.className = 'tc2'; @@ -289,10 +289,11 @@ function relSerialize() { var l = x('relation_tbl').getElementsByTagName('tr'); for(i=0;i