Figured out a polynomial to make the lines scale intuitively (oddly enough they need to start thick, get thinner, then get thicker again as you go from zoomed right out to zoomed right in). I have colours working for feature categories (although the actual colours will almost inevitably get changed). Still haven't worked on point display yet. I've also figured out how to detect the features under a click, so it'll be easy to decide which one deserves the click based on the extent and type of their geometry. Coming along nicely.
December 10, 2014
At request of MF, added a News item to the primary navigation bar and a News section containing one page to the site structure. It is to contain ongoing updates from work on the discovery of the Erebus. Currently I've rebuilt only the home intro page and the news page itself. If they agree to the implementation, then I'll rebuild the entire site with that navigation item.
This ticket has been in process for nearly two years, and was finally resolved at the last Council FTF meeting; I developed an implementation plan on the wiki, which Council commented on, and this morning I implemented the changes according to the plan. Checked everything in the resulting Jenkins build, and made a couple of tweaks to an example. All seems to be well. if so, and if the resulting schemas do what we want them to, we can adopt this in MoEML and elsewhere following the next TEI release.
The fourth review for volume 22 has now been encoded. I'm up to date with incoming stuff.
As a first effort, added a choose condition around each output string in the navigation and more info xslt files to support French as well as English output pages. Works. Will investigate using a system of language files with key-value look-ups and a function that passes the language desired and the key and returns the value as a more elegant and extensible solution.
December 9, 2014
I've written the math bits to convert SVG coords to feature geometry arrays, and it's working for MultiLineStrings and for Polygons; it appears to be fine for Points, but the one Point example I have isn't displaying yet. I have places appearing and disappearing based on clicks in the GUI, and I've got one block of sample code working to change the thickness of strokes based on the resolution.
If I can solve the point problem, then deal with the issue of multiple features for a single location (which is a question of creating an array of Features, and then testing the typeof the FeaturePtr to see if it's an Array or not before doing anything with it), I should be able to start working on a more principled and well-organized version in which we allow for different colours for different categories, etc. And I can also start working on detecting clicks and showing popups.
Making good use of console.log and the Firebug console; that really helps a lot.
Incorporated files with typos corrected from Judy; stripped out all instances of placeholder texts in french translator and french proofer elements in English documents; checked all french files to ensure value of translation_language element is French (16 had to be corrected). Rebuilt entire site, now includes a number of French documents.
Will have to modify the XSLT so that the navigational elements for French are in French, not English.
Also wrote to translators to make sure that everything is in order for them regarding Mystery Quest files and waiting for website page files.
Did some at the weekend, and a couple more this morning. All done.
I've now encoded the two reviews that were waiting (the second one from NVD and one from SB). The first review from NVD has already had some corrections from her, and it has keywords; if the editors are happy with it, it could be published. The other two need to be proofed by the authors and by editors, and they also need keywords.
December 8, 2014
On late duty, and wanted to get something difficult finished.