Home » Eclipse Projects » Babel » Babel PTT
|
| Re: Babel PTT [message #26607 is a reply to message #26461] |
Mon, 13 April 2009 15:42   |
Eclipse User |
|
|
|
Originally posted by: brianf.sybase.com
I too am interested in knowing how exactly to use the Babel PTT to satisfy
the localization should-do for DTP for the Galileo simultaneous release.
We're already good as far as getting everything into Babel (map files and so
on), but I can't find anything on the wiki or newsgroups or doing a Google
search to figure out what exactly is necessary to use the Babel PTT.
Any suggestions would be very helpful.
--Fitz
DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
"V
|
|
|
| Re: Babel PTT [message #26724 is a reply to message #26607] |
Mon, 13 April 2009 19:10 |
 Eclipse Webmaster
Messages: 607343
Registered: July 2009 |
Senior Member |
|
|
While I am not the best person to answer this, I managed to dig out this
mailing list posting. It may be a good start:
http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00448.html
Denis
Brian Fitzpatrick wrote:
> I too am interested in knowing how exactly to use the Babel PTT to satisfy
> the localization should-do for DTP for the Galileo simultaneous release.
> We're already good as far as getting everything into Babel (map files and so
> on), but I can't find anything on the wiki or newsgroups or doing a Google
> search to figure out what exactly is necessary to use the Babel PTT.
>
> Any suggestions would be very helpful.
>
> --Fitz
>
> DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
>
> "Víctor Roldán Betancort" <vroldan@opencanarias.com> wrote in message
> news:gri31v$pki$1@build.eclipse.org...
>> Hi everyone,
>>
>> as a member of the CDO component, we are trying to fulfill our
>> localization needs for the Galileo release. I'll try to expose here what
>> I've understood.
>>
>> (Please correct me if wrong) The steps to properly prepare our project for
>> babel are:
>>
>> 1. Externalize all Strings that are subject to be shown in the UI from our
>> plugins (in our case, I expect only UI and Exceptions are subject to be
>> shown). Use JDT and PDE tooling to externalize strings.
>>
>> 2. Create a babel map. If I understand it correctly, this is kind of a
>> file that exposes which externalized Strings can be translated by the
>> Babel community. I saw this is done through a webapp. The first thing I
>> see is our project does not appear, which I understand since we are not
>> top level project under modeling, but rather under modeling.emf. How can
>> we add our component to this list? Is there anything we should do?
>>
>> 4. Perform PTT to see everything is fine?
>>
>> How is exactly the Pseudo Translation Test performed? I believe I should
>> download the PTT plugin and then configure eclipse.ini to use it? Which is
>> the flag I should use? If I understood correctly:
>>
>> a. Hard-coded strings don't have prefix
>> b. Externalized Strings have prefix. If the string has the prefix, what
>> does it exactly mean?
>>
>> Question: where is the index file that maps prefix to file containing the
>> string?
>>
>> Thanks in advance :D
>>
>> Víctor.
>
>
|
|
|
| Re: Babel PTT [message #26762 is a reply to message #26724] |
Tue, 14 April 2009 08:30 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Denis,
thanks for pointing out this. I actually read this mail before posting
here, since I believe it does not answer the questions I've posted. Just
wanted to have everything clear before "babelizing" the CDO project :P
Cheers,
Víctor.
Denis Roy escribió:
> While I am not the best person to answer this, I managed to dig out this
> mailing list posting. It may be a good start:
>
> http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00448.html
>
>
> Denis
>
> Brian Fitzpatrick wrote:
>> I too am interested in knowing how exactly to use the Babel PTT to
>> satisfy the localization should-do for DTP for the Galileo
>> simultaneous release. We're already good as far as getting everything
>> into Babel (map files and so on), but I can't find anything on the
>> wiki or newsgroups or doing a Google search to figure out what exactly
>> is necessary to use the Babel PTT.
>>
>> Any suggestions would be very helpful.
>>
>> --Fitz
>>
>> DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
>>
>> "Víctor Roldán Betancort" <vroldan@opencanarias.com> wrote in message
>> news:gri31v$pki$1@build.eclipse.org...
>>> Hi everyone,
>>>
>>> as a member of the CDO component, we are trying to fulfill our
>>> localization needs for the Galileo release. I'll try to expose here
>>> what I've understood.
>>>
>>> (Please correct me if wrong) The steps to properly prepare our
>>> project for babel are:
>>>
>>> 1. Externalize all Strings that are subject to be shown in the UI
>>> from our plugins (in our case, I expect only UI and Exceptions are
>>> subject to be shown). Use JDT and PDE tooling to externalize strings.
>>>
>>> 2. Create a babel map. If I understand it correctly, this is kind of
>>> a file that exposes which externalized Strings can be translated by
>>> the Babel community. I saw this is done through a webapp. The first
>>> thing I see is our project does not appear, which I understand since
>>> we are not top level project under modeling, but rather under
>>> modeling.emf. How can we add our component to this list? Is there
>>> anything we should do?
>>>
>>> 4. Perform PTT to see everything is fine?
>>>
>>> How is exactly the Pseudo Translation Test performed? I believe I
>>> should download the PTT plugin and then configure eclipse.ini to use
>>> it? Which is the flag I should use? If I understood correctly:
>>>
>>> a. Hard-coded strings don't have prefix
>>> b. Externalized Strings have prefix. If the string has the prefix,
>>> what does it exactly mean?
>>>
>>> Question: where is the index file that maps prefix to file containing
>>> the string?
>>>
>>> Thanks in advance :D
>>>
>>> Víctor.
>>
>>
|
|
|
| Re: Babel PTT [message #26798 is a reply to message #26762] |
Tue, 14 April 2009 15:45 |
Kit Lo
Messages: 137
Registered: July 2009 |
Senior Member |
|
|
VÃctor, let me try to answer your questions.
1. Externalize all Strings that are subject to be shown in the UI from our
plugins (in our case, I expect only UI and Exceptions are subject to be
shown). Use JDT and PDE tooling to externalize strings.
Answer: correct
2. Create a babel map. If I understand it correctly, this is kind of a
file that exposes which externalized Strings can be translated by the
Babel community. I saw this is done through a webapp. The first thing I
see is our project does not appear, which I understand since we are not
top level project under modeling, but rather under modeling.emf. How can
we add our component to this list? Is there anything we should do?
Answer: We pull the information from a data bridge to Eclipse Bugzilla. If
you don't see your project, please open a bug against Babel/Server.
4. Perform PTT to see everything is fine?
How is exactly the Pseudo Translation Test performed? I believe I should
download the PTT plugin and then configure eclipse.ini to use it? Which is
the flag I should use? If I understood correctly:
a. Hard-coded strings don't have prefix
b. Externalized Strings have prefix. If the string has the prefix, what
does it exactly mean?
Question: where is the index file that maps prefix to file containing the
string?
Answer: There are 2 ways to get the pseudo translation language packs,
either through the Babel update site, or the downlable zips. See
http://www.eclipse.org/babel/downloads.php for more info. After installing
the language packs, start Eclipse with -nl en_AA. After that, just run
your project normally. You will see most of the strings with a special
prefix like "eclipse123456:". If a string does not have a prefix, it
usually means the string is hard-coded in the code. The added length of
the prefix will help you test truncation problems. For example, if a
button is not coded correctly, the new label "eclipse123456:OK" will be
truncated. The prefix can also tell you which project does the string come
from. The index number can be used to locate the exact key in the
properties that it's coming from. The index file can be found in the
pesudo translation feature for the project. This is the path for the
Eclipse index file for example:
eclipse\features\org.eclipse.babel.nls_eclipse_en_AA_3.5.0.v 20090406043401\BabelPseudoTranslationsIndex-eclipse.html
|
|
|
| Re: Babel PTT [message #26838 is a reply to message #26798] |
Tue, 14 April 2009 17:16 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Kit,
thanks you very much for your answer, things are more clear to me now. I
just submitted the bug to include CDO in Babel Map definition webapp
(see #272181). The pseudo test is also more clear now, I'll start
externalizing strings ASAP!
Cheers!
ViK
Kit Lo escribió:
> VÃctor, let me try to answer your questions.
>
> 1. Externalize all Strings that are subject to be shown in the UI from
> our plugins (in our case, I expect only UI and Exceptions are subject to
> be shown). Use JDT and PDE tooling to externalize strings.
>
> Answer: correct
>
> 2. Create a babel map. If I understand it correctly, this is kind of a
> file that exposes which externalized Strings can be translated by the
> Babel community. I saw this is done through a webapp. The first thing I
> see is our project does not appear, which I understand since we are not
> top level project under modeling, but rather under modeling.emf. How can
> we add our component to this list? Is there anything we should do?
>
> Answer: We pull the information from a data bridge to Eclipse Bugzilla.
> If you don't see your project, please open a bug against Babel/Server.
>
> 4. Perform PTT to see everything is fine?
>
> How is exactly the Pseudo Translation Test performed? I believe I should
> download the PTT plugin and then configure eclipse.ini to use it? Which
> is the flag I should use? If I understood correctly:
>
> a. Hard-coded strings don't have prefix
> b. Externalized Strings have prefix. If the string has the prefix, what
> does it exactly mean?
>
> Question: where is the index file that maps prefix to file containing
> the string?
>
> Answer: There are 2 ways to get the pseudo translation language packs,
> either through the Babel update site, or the downlable zips. See
> http://www.eclipse.org/babel/downloads.php for more info. After
> installing the language packs, start Eclipse with -nl en_AA. After that,
> just run your project normally. You will see most of the strings with a
> special prefix like "eclipse123456:". If a string does not have a
> prefix, it usually means the string is hard-coded in the code. The added
> length of the prefix will help you test truncation problems. For
> example, if a button is not coded correctly, the new label
> "eclipse123456:OK" will be truncated. The prefix can also tell you which
> project does the string come from. The index number can be used to
> locate the exact key in the properties that it's coming from. The index
> file can be found in the pesudo translation feature for the project.
> This is the path for the Eclipse index file for example:
> eclipse\features\org.eclipse.babel.nls_eclipse_en_AA_3.5.0.v 20090406043401\BabelPseudoTranslationsIndex-eclipse.html
>
>
|
|
|
| Re: Babel PTT [message #26996 is a reply to message #26798] |
Wed, 15 April 2009 16:02 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Kit,
I just finished doing some part of the string externalization work, and
two questions has popped up in my mind, I hope you could answer:
- Does the used externalization mechanism matter for Babel? I mean, does
Babel require Messages class to extend NLS, or does it work as well with
the ResourceBundle way? We we were concerned about this issue because we
want CDO to run in standalone as well, and NLS seems to come from some
OSGi bundle...
- How can I launch an eclipse runtime instance with certain locale? I
managed to activate the pseudo locale in the first eclipse instance, but
when one I need to be with this local is the second. I've tried to use
arguments -nl ${target.nl:en_AA} and also with -nl en_AA in the launch
configurations, but none work. Does the pseudo transaction fragment need
to be installed in the second instance in some way for this to work? I
realized that fragments cannot be selected in the launch configuration
plugin list (they are just not listed there)
Cheers,
ViK.
|
|
| | | | | | | |
| Re: Babel PTT [message #27771 is a reply to message #27266] |
Mon, 27 April 2009 09:03 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Kit,
I'm afraid I still don't see those fragments in the plugin tab in my
launch configuration. The do appear as installed, according to my
"Installation details" dialog, and both the OSGi console and PDE Plugin
Registry corroborate it. But for reason unknown to me, the don't appear
in the launch configuration. In fact, I can't recognize the fragment
icon the plugin list, so I fear there is no single fragment in that list.
Is there anything special that should be done here?
I'm using these same eclipse installation as you, the same zips.
I must admit this is quite confusing. Fragments seem to be installed
according to the different views and other facilities. Could it be a
platform bug?
Thanks for your feedback, Kit.
Víctor.
Kit Lo escribió:
> 1) I installed the following zips:
> - eclipse-SDK-3.5M6-win32.zip
> - emf-runtime-2.5.0M6.zip
> 2) Launch Eclispe
> 3) Click on "Debug>Debug Configurations..." toolbar button
> 4) Create a new configuration for Eclipse Application
> 5) On the "Arguments" tab, I change the program arguments to:
> -os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl en_AA
> 6) On the "Plug-ins" tab, I can see a list of the code plug-ins and
> NL plug-ins (but grayed out)
> 7) I select "plug-ins selected below only"
> 8) I did run into a problem launching this configuration the first time,
> therefore, I deselect the following plug-ins
> - org.eclipse.core.net.win32.x86.nl_en_AA
> - org.eclipse.equinox.launcher.win32.win32.x86.nl_en_AA
> (I will open a separate bug and investigate this)
> 9) Then, I just click on the "Debug" button, the second instance of Eclipse
> is launched
>
> Is you setup different from mine? Please try this.
>
|
|
| | | | |
| Re: Babel PTT [message #578170 is a reply to message #26607] |
Mon, 13 April 2009 19:10 |
Eclipse Webmaster
Messages: 607343
Registered: July 2009 |
Senior Member |
|
|
While I am not the best person to answer this, I managed to dig out this
mailing list posting. It may be a good start:
http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00448.html
Denis
Brian Fitzpatrick wrote:
> I too am interested in knowing how exactly to use the Babel PTT to satisfy
> the localization should-do for DTP for the Galileo simultaneous release.
> We're already good as far as getting everything into Babel (map files and so
> on), but I can't find anything on the wiki or newsgroups or doing a Google
> search to figure out what exactly is necessary to use the Babel PTT.
>
> Any suggestions would be very helpful.
>
> --Fitz
>
> DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
>
> "Víctor Roldán Betancort" <vroldan@opencanarias.com> wrote in message
> news:gri31v$pki$1@build.eclipse.org...
>> Hi everyone,
>>
>> as a member of the CDO component, we are trying to fulfill our
>> localization needs for the Galileo release. I'll try to expose here what
>> I've understood.
>>
>> (Please correct me if wrong) The steps to properly prepare our project for
>> babel are:
>>
>> 1. Externalize all Strings that are subject to be shown in the UI from our
>> plugins (in our case, I expect only UI and Exceptions are subject to be
>> shown). Use JDT and PDE tooling to externalize strings.
>>
>> 2. Create a babel map. If I understand it correctly, this is kind of a
>> file that exposes which externalized Strings can be translated by the
>> Babel community. I saw this is done through a webapp. The first thing I
>> see is our project does not appear, which I understand since we are not
>> top level project under modeling, but rather under modeling.emf. How can
>> we add our component to this list? Is there anything we should do?
>>
>> 4. Perform PTT to see everything is fine?
>>
>> How is exactly the Pseudo Translation Test performed? I believe I should
>> download the PTT plugin and then configure eclipse.ini to use it? Which is
>> the flag I should use? If I understood correctly:
>>
>> a. Hard-coded strings don't have prefix
>> b. Externalized Strings have prefix. If the string has the prefix, what
>> does it exactly mean?
>>
>> Question: where is the index file that maps prefix to file containing the
>> string?
>>
>> Thanks in advance :D
>>
>> Víctor.
>
>
|
|
|
| Re: Babel PTT [message #578190 is a reply to message #26724] |
Tue, 14 April 2009 08:30 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Denis,
thanks for pointing out this. I actually read this mail before posting
here, since I believe it does not answer the questions I've posted. Just
wanted to have everything clear before "babelizing" the CDO project :P
Cheers,
Víctor.
Denis Roy escribió:
> While I am not the best person to answer this, I managed to dig out this
> mailing list posting. It may be a good start:
>
> http://dev.eclipse.org/mhonarc/lists/babel-dev/msg00448.html
>
>
> Denis
>
> Brian Fitzpatrick wrote:
>> I too am interested in knowing how exactly to use the Babel PTT to
>> satisfy the localization should-do for DTP for the Galileo
>> simultaneous release. We're already good as far as getting everything
>> into Babel (map files and so on), but I can't find anything on the
>> wiki or newsgroups or doing a Google search to figure out what exactly
>> is necessary to use the Babel PTT.
>>
>> Any suggestions would be very helpful.
>>
>> --Fitz
>>
>> DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
>>
>> "Víctor Roldán Betancort" <vroldan@opencanarias.com> wrote in message
>> news:gri31v$pki$1@build.eclipse.org...
>>> Hi everyone,
>>>
>>> as a member of the CDO component, we are trying to fulfill our
>>> localization needs for the Galileo release. I'll try to expose here
>>> what I've understood.
>>>
>>> (Please correct me if wrong) The steps to properly prepare our
>>> project for babel are:
>>>
>>> 1. Externalize all Strings that are subject to be shown in the UI
>>> from our plugins (in our case, I expect only UI and Exceptions are
>>> subject to be shown). Use JDT and PDE tooling to externalize strings.
>>>
>>> 2. Create a babel map. If I understand it correctly, this is kind of
>>> a file that exposes which externalized Strings can be translated by
>>> the Babel community. I saw this is done through a webapp. The first
>>> thing I see is our project does not appear, which I understand since
>>> we are not top level project under modeling, but rather under
>>> modeling.emf. How can we add our component to this list? Is there
>>> anything we should do?
>>>
>>> 4. Perform PTT to see everything is fine?
>>>
>>> How is exactly the Pseudo Translation Test performed? I believe I
>>> should download the PTT plugin and then configure eclipse.ini to use
>>> it? Which is the flag I should use? If I understood correctly:
>>>
>>> a. Hard-coded strings don't have prefix
>>> b. Externalized Strings have prefix. If the string has the prefix,
>>> what does it exactly mean?
>>>
>>> Question: where is the index file that maps prefix to file containing
>>> the string?
>>>
>>> Thanks in advance :D
>>>
>>> Víctor.
>>
>>
|
|
|
| Re: Babel PTT [message #578202 is a reply to message #26762] |
Tue, 14 April 2009 15:45 |
Kit Lo
Messages: 137
Registered: July 2009 |
Senior Member |
|
|
VÃctor, let me try to answer your questions.
1. Externalize all Strings that are subject to be shown in the UI from our
plugins (in our case, I expect only UI and Exceptions are subject to be
shown). Use JDT and PDE tooling to externalize strings.
Answer: correct
2. Create a babel map. If I understand it correctly, this is kind of a
file that exposes which externalized Strings can be translated by the
Babel community. I saw this is done through a webapp. The first thing I
see is our project does not appear, which I understand since we are not
top level project under modeling, but rather under modeling.emf. How can
we add our component to this list? Is there anything we should do?
Answer: We pull the information from a data bridge to Eclipse Bugzilla. If
you don't see your project, please open a bug against Babel/Server.
4. Perform PTT to see everything is fine?
How is exactly the Pseudo Translation Test performed? I believe I should
download the PTT plugin and then configure eclipse.ini to use it? Which is
the flag I should use? If I understood correctly:
a. Hard-coded strings don't have prefix
b. Externalized Strings have prefix. If the string has the prefix, what
does it exactly mean?
Question: where is the index file that maps prefix to file containing the
string?
Answer: There are 2 ways to get the pseudo translation language packs,
either through the Babel update site, or the downlable zips. See
http://www.eclipse.org/babel/downloads.php for more info. After installing
the language packs, start Eclipse with -nl en_AA. After that, just run
your project normally. You will see most of the strings with a special
prefix like "eclipse123456:". If a string does not have a prefix, it
usually means the string is hard-coded in the code. The added length of
the prefix will help you test truncation problems. For example, if a
button is not coded correctly, the new label "eclipse123456:OK" will be
truncated. The prefix can also tell you which project does the string come
from. The index number can be used to locate the exact key in the
properties that it's coming from. The index file can be found in the
pesudo translation feature for the project. This is the path for the
Eclipse index file for example:
eclipse\features\org.eclipse.babel.nls_eclipse_en_AA_3.5.0.v 20090406043401\BabelPseudoTranslationsIndex-eclipse.html
|
|
|
| Re: Babel PTT [message #578213 is a reply to message #26798] |
Tue, 14 April 2009 17:16 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Kit,
thanks you very much for your answer, things are more clear to me now. I
just submitted the bug to include CDO in Babel Map definition webapp
(see #272181). The pseudo test is also more clear now, I'll start
externalizing strings ASAP!
Cheers!
ViK
Kit Lo escribió:
> VÃctor, let me try to answer your questions.
>
> 1. Externalize all Strings that are subject to be shown in the UI from
> our plugins (in our case, I expect only UI and Exceptions are subject to
> be shown). Use JDT and PDE tooling to externalize strings.
>
> Answer: correct
>
> 2. Create a babel map. If I understand it correctly, this is kind of a
> file that exposes which externalized Strings can be translated by the
> Babel community. I saw this is done through a webapp. The first thing I
> see is our project does not appear, which I understand since we are not
> top level project under modeling, but rather under modeling.emf. How can
> we add our component to this list? Is there anything we should do?
>
> Answer: We pull the information from a data bridge to Eclipse Bugzilla.
> If you don't see your project, please open a bug against Babel/Server.
>
> 4. Perform PTT to see everything is fine?
>
> How is exactly the Pseudo Translation Test performed? I believe I should
> download the PTT plugin and then configure eclipse.ini to use it? Which
> is the flag I should use? If I understood correctly:
>
> a. Hard-coded strings don't have prefix
> b. Externalized Strings have prefix. If the string has the prefix, what
> does it exactly mean?
>
> Question: where is the index file that maps prefix to file containing
> the string?
>
> Answer: There are 2 ways to get the pseudo translation language packs,
> either through the Babel update site, or the downlable zips. See
> http://www.eclipse.org/babel/downloads.php for more info. After
> installing the language packs, start Eclipse with -nl en_AA. After that,
> just run your project normally. You will see most of the strings with a
> special prefix like "eclipse123456:". If a string does not have a
> prefix, it usually means the string is hard-coded in the code. The added
> length of the prefix will help you test truncation problems. For
> example, if a button is not coded correctly, the new label
> "eclipse123456:OK" will be truncated. The prefix can also tell you which
> project does the string come from. The index number can be used to
> locate the exact key in the properties that it's coming from. The index
> file can be found in the pesudo translation feature for the project.
> This is the path for the Eclipse index file for example:
> eclipse\features\org.eclipse.babel.nls_eclipse_en_AA_3.5.0.v 20090406043401\BabelPseudoTranslationsIndex-eclipse.html
>
>
|
|
|
| Re: Babel PTT [message #578289 is a reply to message #26798] |
Wed, 15 April 2009 16:02 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Hi Kit,
I just finished doing some part of the string externalization work, and
two questions has popped up in my mind, I hope you could answer:
- Does the used externalization mechanism matter for Babel? I mean, does
Babel require Messages class to extend NLS, or does it work as well with
the ResourceBundle way? We we were concerned about this issue because we
want CDO to run in standalone as well, and NLS seems to come from some
OSGi bundle...
- How can I launch an eclipse runtime instance with certain locale? I
managed to activate the pseudo locale in the first eclipse instance, but
when one I need to be with this local is the second. I've tried to use
arguments -nl ${target.nl:en_AA} and also with -nl en_AA in the launch
configurations, but none work. Does the pseudo transaction fragment need
to be installed in the second instance in some way for this to work? I
realized that fragments cannot be selected in the launch configuration
plugin list (they are just not listed there)
Cheers,
ViK.
|
|
| | | | | | | |
| Re: Babel PTT [message #578521 is a reply to message #27266] |
Mon, 27 April 2009 09:03 |
Victor Roldan Betancort
Messages: 524
Registered: July 2009 |
Senior Member |
|
|
Kit,
I'm afraid I still don't see those fragments in the plugin tab in my
launch configuration. The do appear as installed, according to my
"Installation details" dialog, and both the OSGi console and PDE Plugin
Registry corroborate it. But for reason unknown to me, the don't appear
in the launch configuration. In fact, I can't recognize the fragment
icon the plugin list, so I fear there is no single fragment in that list.
Is there anything special that should be done here?
I'm using these same eclipse installation as you, the same zips.
I must admit this is quite confusing. Fragments seem to be installed
according to the different views and other facilities. Could it be a
platform bug?
Thanks for your feedback, Kit.
Víctor.
Kit Lo escribió:
> 1) I installed the following zips:
> - eclipse-SDK-3.5M6-win32.zip
> - emf-runtime-2.5.0M6.zip
> 2) Launch Eclispe
> 3) Click on "Debug>Debug Configurations..." toolbar button
> 4) Create a new configuration for Eclipse Application
> 5) On the "Arguments" tab, I change the program arguments to:
> -os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl en_AA
> 6) On the "Plug-ins" tab, I can see a list of the code plug-ins and
> NL plug-ins (but grayed out)
> 7) I select "plug-ins selected below only"
> 8) I did run into a problem launching this configuration the first time,
> therefore, I deselect the following plug-ins
> - org.eclipse.core.net.win32.x86.nl_en_AA
> - org.eclipse.equinox.launcher.win32.win32.x86.nl_en_AA
> (I will open a separate bug and investigate this)
> 9) Then, I just click on the "Debug" button, the second instance of Eclipse
> is launched
>
> Is you setup different from mine? Please try this.
>
|
|
| | | |
Goto Forum:
Current Time: Wed Feb 05 18:54:18 GMT 2025
Powered by FUDForum. Page generated in 0.07820 seconds |
] 
Search
Help
Register
Login
Home
