Hey Dario,
no. And I know this could sound bad, but is not the intention... so I'll try to explain why "no:"
1. it has a dependency on a framework we use on top of seaside (for all our apps) that helps us to do some scaffolding for the (sub) components we use in airflowing our sites, blogs and forums; that isn't opened at the moment so it would be complicated at this time
2. it's dependent on our persistence architecture (we store the translations in the application odb); which adds a second framework involved
3. our intention wasn't do something general, we dedicated like a day and a half on it (plus bits of debugging and upgrades)
I suggest you to: 1. do the best translator of the world or 2. spend the less time you can on it and move on
But consider this:
this app to edit translations wasn't a big deal but required something about a couple of days of full attention and I didn't find ways to evade that so I guess you should go for it and make yours (is very useful we use it very very often)
Hi, Sebastian
your solution sound well.
Do you have test it into GLASS ?
I read:
"The last thing we needed was a little web application that we can internally use to create translations and edit its .."
Do you have it for general seaside applications and for Pier CMS ?
I can view - work with your solutions ?
Thank,
Dario
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
