| Why not an RCP application? [message #569650] |
Wed, 27 February 2008 07:05  |
 Michael Keppler
Messages: 164
Registered: July 2009 |
Senior Member |
|
|
Hello,
I looked through the mailing list archive but did not find an
explanation for the approach choosen by the Babel project, so please
shed some light on this question: Why did you create a PHP application
for the translation instead of a RCP client, which could be web-enabled
using the RAP project?
My thought is that the current translation web tool is just not suited
to translate lots of strings. It misses essential features like lists
for common translations, cross checking different translations, it can
not be resized to fullscreen and has no keyboard shortcuts. All those
and more things can be done much easier with a RCP app (which could even
reuse the RessourceBundle editor from Sourceforge). The web client would
then just be the same RCP application, but using the Eclipse Rich Ajax
platform
( http://www.eclipse.org/projects/project_summary.php?projecti d=technology.rap).
That way the translator implementation would be easier (than by
scripting), you could give the people more features in shorter time,
leading to better translations (hopefully) and using RAP would also be
good old "eat your own dogfood" style. :)
So has this never been considered or is there some other technical
aspect or project goal which I'm completely missing?
Ciao, Michael
|
|
|
|
Powered by
FUDForum. Page generated in 0.01830 seconds
] 
Search
Help
Register
Login
Home
