Skip to main content



      Home
Home » Eclipse Projects » Babel » Why not an RCP application?
Why not an RCP application? [message #7437] Wed, 27 February 2008 02:05 Go to next message
Eclipse UserFriend
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 04:46 Go to previous messageGo to next message
Eclipse UserFriend
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 #7459 is a reply to message #7437] Wed, 27 February 2008 09:59 Go to previous messageGo to next message
Eclipse Webmaster is currently offline Eclipse WebmasterFriend
Messages: 607353
Registered: July 2009
Senior Member
Michael Keppler wrote:
> Why did you create a PHP application
> for the translation instead of a RCP client, which could be web-enabled
> using the RAP project?

The answer is simple: we had an initial code contribution for a
PHP/MySQL application. That gave us a big head start.


> My thought is that the current translation web tool is just not suited
> to translate lots of strings.
An RCP/Rap application would have the same problem if the features you
need aren't yet implemented. We can do this with web-based tooling too
-- file a bug!

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Babel&am p;component=Server&bug_file_loc=/babel/index.php

> 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.

Some of those enhancement have already been requested via Bugzilla.

Please be patient with us, as we've only started a couple of months ago
and we all have limited time to devote to the project. We're not at a
1.0 level yet, but we'll get there.

Denis


--

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 #7470 is a reply to message #7448] Wed, 27 February 2008 10:01 Go to previous messageGo to next message
Eclipse Webmaster is currently offline Eclipse WebmasterFriend
Messages: 607353
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 #7480 is a reply to message #7437] Wed, 27 February 2008 11:15 Go to previous messageGo to next message
Eclipse UserFriend
Michael,
It's a good idea and I agree with all your statements up to this one:

> you could give the people more features in shorter time,

One reason for building what we did is that the team who built it (Denis
& Gabe) are better at building server-side PHP tools than building
client-side RCP tools.

But don't let that stop you from contributing a client-side tool - I'm
sure that the existing team would be happy to help you by building the
web APIs you need.

- Bjorn
Re: Why not an RCP application? [message #7491 is a reply to message #7480] Sat, 01 March 2008 08:59 Go to previous messageGo to next message
Eclipse UserFriend
At least the Message/ResourceBundle Editor, Pascal contributed is a
Eclipse Plugin anyway.

I agree, over time a Server-Side Eclipse part for it similar to e.g. OHF
could be a good idea, if enough people are willing to contribute and use
it. Similar to the OHF server a couple of clients, RCP, Web (PHP or
Java/WTP) and even Mobile would be possible then.

Werner
Re: Why not an RCP application? [message #7502 is a reply to message #7491] Sat, 01 March 2008 09:04 Go to previous message
Eclipse UserFriend
btw, Compared to OHF, maybe "Babel Bridge" wouldn't be the best name.
A. too much similarity with e.g. Tower
B. I don't think Eclipse would like similar troubles with the Rolling
Stones, Apple once had with the Beatles ?;-)

> I agree, over time a Server-Side Eclipse part for it similar to e.g. OHF
> could be a good idea, if enough people are willing to contribute and use
> it. Similar to the OHF server a couple of clients, RCP, Web (PHP or
> Java/WTP) and even Mobile would be possible then.
>
Re: Why not an RCP application? [message #569688 is a reply to message #7437] Wed, 27 February 2008 04:46 Go to previous message
Eclipse UserFriend
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 #569712 is a reply to message #7437] Wed, 27 February 2008 09:59 Go to previous message
Eclipse Webmaster is currently offline Eclipse WebmasterFriend
Messages: 607353
Registered: July 2009
Senior Member
Michael Keppler wrote:
> Why did you create a PHP application
> for the translation instead of a RCP client, which could be web-enabled
> using the RAP project?

The answer is simple: we had an initial code contribution for a
PHP/MySQL application. That gave us a big head start.


> My thought is that the current translation web tool is just not suited
> to translate lots of strings.
An RCP/Rap application would have the same problem if the features you
need aren't yet implemented. We can do this with web-based tooling too
-- file a bug!

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Babel&am p;component=Server&bug_file_loc=/babel/index.php

> 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.

Some of those enhancement have already been requested via Bugzilla.

Please be patient with us, as we've only started a couple of months ago
and we all have limited time to devote to the project. We're not at a
1.0 level yet, but we'll get there.

Denis


--

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 #569735 is a reply to message #7448] Wed, 27 February 2008 10:01 Go to previous message
Eclipse Webmaster is currently offline Eclipse WebmasterFriend
Messages: 607353
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 #569761 is a reply to message #7437] Wed, 27 February 2008 11:15 Go to previous message
Eclipse UserFriend
Michael,
It's a good idea and I agree with all your statements up to this one:

> you could give the people more features in shorter time,

One reason for building what we did is that the team who built it (Denis
& Gabe) are better at building server-side PHP tools than building
client-side RCP tools.

But don't let that stop you from contributing a client-side tool - I'm
sure that the existing team would be happy to help you by building the
web APIs you need.

- Bjorn
Re: Why not an RCP application? [message #569779 is a reply to message #7480] Sat, 01 March 2008 08:59 Go to previous message
Eclipse UserFriend
At least the Message/ResourceBundle Editor, Pascal contributed is a
Eclipse Plugin anyway.

I agree, over time a Server-Side Eclipse part for it similar to e.g. OHF
could be a good idea, if enough people are willing to contribute and use
it. Similar to the OHF server a couple of clients, RCP, Web (PHP or
Java/WTP) and even Mobile would be possible then.

Werner
Re: Why not an RCP application? [message #569784 is a reply to message #7491] Sat, 01 March 2008 09:04 Go to previous message
Eclipse UserFriend
btw, Compared to OHF, maybe "Babel Bridge" wouldn't be the best name.
A. too much similarity with e.g. Tower
B. I don't think Eclipse would like similar troubles with the Rolling
Stones, Apple once had with the Beatles ?;-)

> I agree, over time a Server-Side Eclipse part for it similar to e.g. OHF
> could be a good idea, if enough people are willing to contribute and use
> it. Similar to the OHF server a couple of clients, RCP, Web (PHP or
> Java/WTP) and even Mobile would be possible then.
>
Previous Topic:Re: Join in and help translate the CDT to your language
Next Topic:News from the front
Goto Forum:
  


Current Time: Mon May 12 19:00:29 EDT 2025

Powered by FUDForum. Page generated in 0.05578 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top