Hi Tal, On Tue, May 20, 2014 at 11:55:10AM +0300, Tal Daniel wrote: > > It would be better to avoid JavaScript, and use the Dotiac::DTL > > / Django Template Language facilities, leaving the code logic on > > view.pm the list can be populated with a for loop. > > > > http://www.dotiac.com/cgi-bin/index.pl http://www.djangoproject.com/ > > The blog example: > > > > http://sourceforge.net/p/dotiac/code/HEAD/tree/trunk/Dotiac/examples/templates/blog.html > > > Ariel, I'd be glad to work better with Django templating, may I'll > give it a try and incorporate a {% foreach ... %} on a languages array > that I'll create. But I may need your assistance with the view.pm > code, to redirect to other pages [without Javascript?!].
I'm not sure if you can redirect without javascript on an HTML form, searching in google may help; anyway I was suggesting to move all that hard-coded list of languages out of the template; for example, you can create a CSV file with the data, process that file on view.pm, and feed the template with the data; that way, you only need to modify view.pm and the brand template once, and every time the language list changes, you only have to modify a CSV text file, which is easier to maintain and less error prone. You can see the live example on the foundation main site, where the content that seems dynamic is just generated at build time; the same approach could be used on the download pages, which are hard to maintain and a nightmare to translate; or even to generate the localized sites, all with same look and feels. (The main problem is that only Dave Fisher knows that stuff; if you are willing to learn, it will be very helpful for the project :) ). Regards -- Ariel Constenla-Haile La Plata, Argentina
signature.asc
Description: Digital signature
