What happened to Slydr 2.6 ?

I submitted Slydr 2.6 Friday the 6th Jan as i though i’d better update NoDo users with latest changes. I branched current Mango code base and made changes to revert the code to NoDo compatible code. I didn’t realise it but i left Mango version of Silverlight Toolkit and 2.6 didn’t pass certification as the app crashes when you navigate to Settings page. This is what consumes the Silverlight toolkit based controls.

So what did i do ? Well to start with I pushed 3.2 (which is update to 3.1 Mango version and contains some bug fixes) and its currently in testing. I have also downloaded NoDo sdk to get my hands on NoDo Emulator so i can thoroughly test 2.6 when i push it for certificaiton in coming week.

Apart from that Cool Cam is close to completion. I have the photo viewer working correctly and all i need to do is get effects application code working correctly. I plan to finish it tonight and then hopefully i will polish it a bit (for example displaying a count down when using timer mode). Then comes the annoying part of localisation. I am keeping the text very simple and so i hope localisation is easy / more accurate.

Last week i also published entire word lists i have generated. I have uploaded 50k zip, entire zip and log file which details file count / word count etc etc.

New word lists

I finally got around to uploading the new word lists. These are more precise as the code now checks for more than one subtitle and only picks one set rather than everything. In addition to existing languages lists, i also uploaded lists for Indonesian, Serbian (both latin and my conversion to Cyrillic), Macedonian, Malay, Albanian and Simplified Chinese.

I hope the lists are useful.

Recent work

I finally started working on Sat Nav app last night.. Not having maps is getting tiring specially for testing.. i guess i will have to download at least a big chunk of maps and set up my own map service so that i can keep testing – its getting very very annoying.

Apart from that i have been reworking on my second favourite topic.. Frequencylists. One of the chaps asked me a couple of questions and i must say good questions… the word count, the file count etc etc. In fact if it wasn’t for him i personally wouldn’t have bothered with this whole – how true is the corpus. I remember talking to a greek user about a greek list on similar lines however this time it was english and i could deal with it easily 🙂
He cleverly pointed out that on opensubtitles.org each movie at times had multiple subtitles and i check my repository and that was true… i reworked the algorithm to pick up only one set. Before i left for home, i kicked off the code and the frequency lists should all be built by now.

I might just upload the whole lot instead of only sharing 50k. People can deal with large lists 🙂

Besides all this, i finally fixed my dishwasher. It was a leak in water reflow system ? took the gasket off, cleaned it nicely… bit of rust, cleaned that and put it all back togather. My tests showed that second time around i did a pukka job. Well done me 🙂 Guess i can concentrate on coding fully now.

Traditional and Simplified Chinese pronounciation dictionaries done

Just took first big step for supporting for chinese language both traditional and simplified. Pronounciation dictionaries are ready.

I am for now supporting only pronounciation dictionaries and first version has over 29k words / phrases only not 50k words like other dictionaries.

More will be done based on feedback received. Time for keyboard layout and addition to slydr project tomorrow.

Slydr will support entry of whole word / pronouciantion or first char of each pronouniation for predictive part and whole word / pronouciantion for sliding mechanism for now. Might have to rework some logic for first char match for sliding mechanism.

Slydr (aka Sliding Keyboard) 2.0 submitted to marketplace

I have just finished 2.0 changes.

This version has been hard work. A lot of rewriting since my goal was to add more layouts and language support. Total languages / layouts support are
◦Catalan (Català) – Spanish keyboard layout
◦Czech (Český)
◦German (Deutsch)
◦Dutch (Nederlands)
◦Dutch (Belgium)
◦Spanish (Español)
◦Finnish (Soumi)
◦Français (France)
◦Français (Canada)
◦Français (Switzerland)
◦Greek (Ελληνικά)
◦Italian (Italiano)
◦Norwegian (Norsk)
◦Hungarian (Magyar)
◦Polish (Polski)
◦Português (Portugal)
◦Português (Brasil)
◦Russian (русский)
◦Swedish (Svenska)
◦Turkish (Türkçe)
◦Ukrainian (українська)

I would like to take this to thank http://www.opensubtitles.com for their work on extensive subtitles and making them easy to consume for other purposes 🙂

I would also like to thank Francis Tyers for being so approachable and building me a Catalan word list in matter of minutes. Thank you very much Francis Tyers.

Do you think i should publish my word list related work on wikitionary ? I did get the idea from them after all !!!

I am not going to have my laptop for next 3 weeks so i think changes will be slower.
For now, i will only bug fix current app.

My next goal is Mango integration. Submission starts this month and i want to implement contacts feature asap. I might consider adding other e.g. Slovak, Romanian, Bulgarian, Croation, Slovenian and Afrikaans ???

How could i forget Greek

In yesterday’s rant i forgot to add Greek to the list of languages.
Of course Greek will be there. It was good so see the whole greek alphabet without thinking of Math or finance for a change 🙂

I am progressing well with 2.0. I think i am going to rename it to Slydr (not keeping keyboard in the name any more). I should be finishing the updated layout code hopefully today and should testing it later on today or tomorrow.

I have also fixed a few things in Greek / Turkish / Russian and Ukrainian word lists.
Word search for double char words like too or good etc should be simpler (just trace over t o / g o d) no messing about with hovering or tracing a neighbouring char.

Another 8 days to go

The joys of coding a numerous 🙂

for starters its all the praise you get from users 😛

I am resisting desire to make release before adding support for Nordic / Russian / Ukarainian.
the thing that makes it hard is that standard Querty keyboard has 10 letters in a row max. Nordic / Russian / Ukarainian has 11 letters per row. While means i need to rework a lot of character detection code 😦

why why why… just when life was getting easier 🙂

The total support languages for 2.0 will be
English, French, German, Spanish, Catala, Italian, Portuguese, Bralizian Portuguese, Polish, Hungarian, Czech, Dutch, Danish, Finnish, Norwegian, Swedish, Russian, Ukarainian and Turkish. (word lists are ready for these languages… yay – hope i got them right)

After adding these, i need to fix a bug in automatic space addition. If i still have energy, I will try to add Slovakian.

I have another 8 days of laptop use before i lose it for 3 weeks. I might do some work from my desktop – which recently got all the dev tools but i have a hectic schedule of fixing my garden while the girls are away. All i gotta do is take some paving slabs off from half the garden, put new ones in the first half and landscape the rest of it. DIY paving here i come

Done with word lists, back to Sliding Keyboard

I am done with word lists for now. Made last set of changes yesterday evening and run the list builder… took a couple of hours but its all done with all 50 languages i had data for. Not going to add support for all. I am looking to add supprt for Nordic languages and possibly russian in next version. Possibly fix a few some issues.

Got some encouraging feedback for 1.9
The app works much better after the 1.9 update. It’s finally worth using.
Update made this app great. Just have to get used to it. Picked words correctly when I slid past what I wanted.
Update: With v1.9 this has improved no end! Very usable. Few small niggles but developer has done everything people have requested of him. So I still expect rapid improvement. Now 4 stars. Have bought it, can’t say more than that really.

Got some feature request from last user (in first round of feedback) and i’m going to try and add it in v2.

Also what about Slydr. I tried it with German version – Deutsch Slydr (only released 1 version before integrating it into the same code base) and never released French Slydr

Frequency Word List is driving me mad

Why is nothing ever easy.
I managed to get Frequency List Builder up and running in no time. It can work pretty fast and gives me decent output.

What do i find ?? the input has errors.. of course that is bound to happen. So what do i do ? well i change my code to work around common bugs. ‘il is actually ‘ll and mr. is same as mr etc etc.

so what happens next.. i test it and its all beautiful. Except i have no idea the structure of words in non English languages. Damn!!!!!

The xml wiki dumps are just a pile of xml / html mess. I’ll probably have to write more code to strip the unwanted data before i start looking for real data.