Hi Bastien,
Op 24-8-2013 17:03, Bastien schreef:
I can't store the whole WLM database in my
instance, first because
it would cost me quite a lot (I pay for a redis database), secondly
because loading is stupid right now, it stores all monuments into a
javascript variable (see the HTML source).
Ok. How does this scale to the 1,3M
items we have in the database right now?
I'm sure the WLM international team has some money to get another
(bigger) VPS if needed.
I will work on this first and on i18n, thanks for
reminding me,
then ping the list with the updated version.
The website is built using Clojure, but help for i18n should be
easy enough for those who know how to clone a repository on github
and to send pull requests :)
It should be compatible with
http://translatewiki.net/
. In short: Use
message variables and store all the i18n messages in a separate file.
That way we can it's easy to get a lot of translations in a short time.
I'll publish the code on thursday at best, I
don't have enough spare
time before this, the biggest priority is to get the asynchronous
stuff working.
Isn't it already in git? Just the share the link :-)
What's wrong with using a dedicated domain name
from the beginning?
Switching from one domain name to another after WLM does not feel
convenient to me, from a user point of view -- is it for PR/marketing
concerns? Just trying to understand, thanks!
I just don't want to loose time
over it and keep things focused on
getting a map for WLM. The map subdomain is just easy to setup.
I definitely don't want to bike shed of the domain name.
Keep up the good work!
Maarten