#72 I18N: property files,\" externalize strings\"

[Anonymous]

Would it be possible with a little more support for
I18N in Spindle? Specifically, I miss the following:

- Possibility to "Jump" through the context menu to the
property
files in a component/page.

- Possibility to collapse the 5-6 files with same
basename which makes
up a component to one single line in the navigator.

- A wizard which makes it possible to exchange any
occurence of
"string" to <span key="userSelectedKey">string</span>
in the
template.

Overall, as of Spindle 0.0.30 (my version), I get the
impression that
bringing things like these (I'm sure there is more...)
into the feature discussion is a Good Thing.

[Geoffrey Longman]

Logged In: YES
user_id=387057

first one - is a possiblity
second one - sorry I don't have that kind of control over the
package explorer or the navigator

third one - is a possibility

I'm hoping that the new Eclipse web tools project will take off
and a lot of the slog code I write will go away as I start to
use thiers. I'm concentrating on filling in the basics first - for
example there's no syntax completion in for <page> or
<library> tag attributes

[Geoffrey Longman]

Logged In: YES
user_id=387057

I've been thinking about this one. A popular request on the
Tapestry list is to make it easy to change the way that
Tapestry locates properties files. And, one of the action items
for Tapestry 3.1 is to enable this effortlessly via Hivemind.

So, any solution I make now will probably be moot by the end
of the summer. I'd hate to put a great amount of effort into a
solution that wouldn't work when Tapestry 3.1 comes out.

Adopting a "wait and see" stance.

[Geoffrey Longman]

Logged In: YES
user_id=387057

deferred to Spindle 3.1

[Kevin Menard]

Logged In: YES
user_id=131417

In addition to this, I'd like to see the list of keys
available in the default properties file when pressing ctl +
space when setting the value for "key". This way, one
wouldn't have to keep switching windows to recall key names,
typos can be avoided, etc.

[Kevin Menard]

Logged In: YES
user_id=131417

Just thinking outloud a bit here, but for automatically
externalizing strings, I see two ways of doing it. One,
hook into eclipse's "Externalize Strings" feature. Two,
offer a quick fix if the key specified is not in the default
properties file. The quick fix then could add the key and
make the value everything between the set of span tags, for
example.