Home » Eclipse Projects » Babel » Why not an RCP application?
Why not an RCP application? [message #7437] |
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
|
|
|
Re: Why not an RCP application? [message #7448 is a reply to message #7437] |
Wed, 27 February 2008 09:46 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Hi,
I also thought about this :-) but more seriously I'd like to see a
WebService-API provided by Babel this way translation tools could be
written more easily.
I'm not a PHP Guru but providing a WS-API ontop of Java Projects is a
piece of cake if you strucutured your application appropiately.
Tom
Michael Keppler schrieb:
> 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
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
| |
Re: Why not an RCP application? [message #7470 is a reply to message #7448] |
Wed, 27 February 2008 15:01 |
Eclipse Webmaster Messages: 607343 Registered: July 2009 |
Senior Member |
|
|
Tom Schindl wrote:
> Hi,
>
> I also thought about this :-) but more seriously I'd like to see a
> WebService-API provided by Babel this way translation tools could be
> written more easily.
You know the drill -- please file a bug :-)
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Babel&am p;component=Server
D.
>
> I'm not a PHP Guru but providing a WS-API ontop of Java Projects is a
> piece of cake if you strucutured your application appropiately.
>
> Tom
>
> Michael Keppler schrieb:
>> 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
>
>
--
Eclipse WebMaster - webmaster@eclipse.org
Questions? Consult the WebMaster FAQ at
http://wiki.eclipse.org/index.php/Webmaster_FAQ
View my status at http://wiki.eclipse.org/index.php/WebMaster
|
|
| | | |
Re: Why not an RCP application? [message #569688 is a reply to message #7437] |
Wed, 27 February 2008 09:46 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Hi,
I also thought about this :-) but more seriously I'd like to see a
WebService-API provided by Babel this way translation tools could be
written more easily.
I'm not a PHP Guru but providing a WS-API ontop of Java Projects is a
piece of cake if you strucutured your application appropiately.
Tom
Michael Keppler schrieb:
> 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
--
B e s t S o l u t i o n . at
------------------------------------------------------------ --------
Tom Schindl JFace-Committer
------------------------------------------------------------ --------
|
|
| |
Re: Why not an RCP application? [message #569735 is a reply to message #7448] |
Wed, 27 February 2008 15:01 |
Eclipse Webmaster Messages: 607343 Registered: July 2009 |
Senior Member |
|
|
Tom Schindl wrote:
> Hi,
>
> I also thought about this :-) but more seriously I'd like to see a
> WebService-API provided by Babel this way translation tools could be
> written more easily.
You know the drill -- please file a bug :-)
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Babel&am p;component=Server
D.
>
> I'm not a PHP Guru but providing a WS-API ontop of Java Projects is a
> piece of cake if you strucutured your application appropiately.
>
> Tom
>
> Michael Keppler schrieb:
>> 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
>
>
--
Eclipse WebMaster - webmaster@eclipse.org
Questions? Consult the WebMaster FAQ at
http://wiki.eclipse.org/index.php/Webmaster_FAQ
View my status at http://wiki.eclipse.org/index.php/WebMaster
|
|
| | | |
Goto Forum:
Current Time: Mon Sep 23 13:06:07 GMT 2024
Powered by FUDForum. Page generated in 0.04399 seconds
|