overture2112 Wrote:nest0r Wrote:In the future I can imagine having it all automated, and/or you can do stuff like: first derive a list of matures without the knowns and the knowns without the matures, and have the matures the darkest and the knowns medium dark, so the unknowns are lightest and you have a kind of gradient of your best to least knowns, if you want.
Yea, I should add an "export db as" button and we can make a few convertors for useful things. If you can document what exactly the xml needs to look like it should be easy enough.
nest0r Wrote:...To aru Majutsu no Index volume 1
I don't suppose you have a subs2srs deck for the show?
No I don't, though I love that show. (I removed that section from my comment just now since I think it would be redundant if you're already showing all the known morphemes for anything in Firefox, but I guess specific stuff could be useful if you're messing with custom pens in the extension.)
And export stuff would be awesome. If you have the extension you can export the .xml yourself and it'll have little variations depending on your colour settings, but here's what it looks like with everything default except the background changed to dark gray, and with 3 words added:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<vhdatabase.sqlite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<vocabulary>
<word>morpheme1</word>
<note/>
<htmlnote/>
<matchcase>0</matchcase>
<nothighlight>0</nothighlight>
<pen penname="">
<style>background: none repeat scroll 0% 0% darkgray ! important; border: medium none transparent ! important; color: black ! important; display: inline ! important; float: none ! important; font: inherit ! important; margin: 0px ! important; padding: 0px ! important; position: static ! important; text-decoration: inherit ! important; text-transform: inherit ! important; vertical-align: baseline ! important; visibility: inherit ! important;</style>
<leftboundary>0</leftboundary>
<rightboundary>0</rightboundary>
<findderivatives>0</findderivatives>
</pen>
</vocabulary>
<vocabulary><word>morpheme2</word>
<note/>
<htmlnote/>
<matchcase>0</matchcase>
<nothighlight>0</nothighlight>
<pen/>
</vocabulary>
<vocabulary><word>morpheme3</word>
<note/>
<htmlnote/>
<matchcase>0</matchcase>
<nothighlight>0</nothighlight>
<pen/>
</vocabulary>
</vhdatabase.sqlite>
So normally when you import an .xml, you can replace or append. But from the extension options it seems you can only adjust custom colours entry by entry, one at a time. So I figure you could adjust the colours and such in the .xml when you're adding the morphemes to the list (if manually). Not sure how it'd work if automatically exporting. Not that having different colours for different batches is essential, but it came to me that having both matures and known could be interesting to differentiate, since I'm always going on about gradients and 60/30/10, etc.
Edit: And this entry <vocabulary><word>。</word> would break it and make it say incorrect format till you removed that entry. (Not sure what else might break it. ‘!’ was okay, as was ‘,’ and 0-9/0-9. I had to remove those one by one, as well as other combinations of numbers, since the editor for the extension sucks like that and I didn't want all the numbers and commas, etc. on pages highlighted. In the future hopefully filtering/Morph Man can remove those, or maybe someone knows a good regex to remove them.)
Edited: 2011-08-26, 4:59 pm