[Isomorphic]

The XML format of Tour is just converted to the JavaScript format before being run. So the only thing you can possibly be missing are things associated with that transform, like using server-based i18n, as you pointed out. Also, you could use XML-centric tools to validate the format, but these days, the JSON-based tools are better.

[claudiobosticco]

Hi, I wanted one more comment on the differences between the JS and XML modes for Tours.

Basically, if I use XML and therefore internationalize the messages the same way I do for XML dataSources, it works, but I have to load the files statically (that is, I can’t use isc.Tour.loadTour(), and there is no equivalent of the dataSourceLoader for Tours).

At this point I would prefer to use the JavaScript version of Tours, but I wanted confirmation that there are no limitations compared to the XML version.

[claudiobosticco]

Hello, thanks, I got it working, but I need to specify the bundle in the <fmt:message> tag (while in the datasources I only use <fmt:bundle basename="...). I'll try to understand If I could use the more compact notation I use in the datasources.

Regarding the JS version, are there any limitations for Tours?
I ask because with the <fmt> tag I lose the ability to load the Tours dynamically, whereas in JavaScript I could continue doing so.

[Isomorphic]

We set up a test based on the Showcase Tour sample, https://smartclient.com/smartclient/...id=productTour. We then modified the following line in the productTour.proc.xml file to add the <fmt:message> tag:

<instructions>Welcome to the SmartClient Showcase!  We'll show you how to use it.  <fmt:message key="instructions1"/></instructions>

Then we created a productTour.properties file immediately under WEB-INF/classes and defined an "instructions1" property:

instructions1: Extra instructions in English

This does work - the <fmt:message> tag is replaced in that Welcome message with "Extra instructions in English". So we think this is fundamentally working. If it is not working for you, please can you provide more information about the exact steps you have taken

[Isomorphic]

Hi Claudio
Sorry for the long silence on this. We did some preliminary work here and thought we had things working but clearly that's not what you're finding.
A proper in-depth investigation has been queued up for a while behind some other priorities. Our dev team anticipates getting into this over the next few work days so should have more information for you soon.

Regards

Isomorphic Software

[claudiobosticco]

Hello, aside from the issue with the <fmt> tags, could you please provide your thoughts on this question from post #11:

Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?

I’m considering switching to the JS version if there aren’t any drawbacks.

[claudiobosticco]

SmartClient Version: v13.1p_2024-12-19/Enterprise Deployment (built 2024-12-19)

Hello, any news about this issue? I still see the <fmt> tag in the js-translated Tour, with the approach described in post #11

[claudiobosticco]

SmartClient Version: v13.1p_2024-12-01/Enterprise Deployment (built 2024-12-01)

Hello, it doesn't seem to work for me, I still see the <fmt> tags in the js-translated Tour.

If you instead define them in JavaScript, then you use the usual client-side approaches.

Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?

Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?

could you also please comment on this?

[Isomorphic]

Hi Claudio
Sorry for the long pause on this.
We've made a change to have the server pick up the appropriate messages from the resource bundle file and substitute them in for tour *.proc.xml files.
Please try the next nightly build (Nov 27 or above) in the 13.1 / 14.0 branch to see this in action.

Let us know if it doesn't work for you

Regards
Isomorphic Software

[Isomorphic]

Hi Claudio
We see the problem, and our development team are working on it. We'll be following up when we have more information for you

Regards
Isomorphic Software

[claudiobosticco]

Hello, could you please comment on this?

[claudiobosticco]

claudiobosticco sorry we missed that question. If the Tour is defined in XML, you should be able to use the same i18n mechanisms that apply to DataSource .ds.xml files and screens (.ui.xml files).

Hello, I've actually tried like this:

<Tour ID="firstTour" showProgress="true" xmlns:fmt="WEB-INF/">
    <fmt:bundle basename="i18nMessages" encoding="utf-8"/>
    <steps>
        <TourStep ID="welcome">
            <title><fmt:message key="welcome"/></title>
....

and then I've tried to load it like this (as I don't think it could work with Tour.loadTour()):

<script type="text/javascript" charset="UTF-8">
    <isomorphic:XML>
    <jsp:include page="/WEB-INF/ds/profileMenuTour.proc.xml"/>
    <jsp:include page="/WEB-INF/ds/aSampleDS.ds.xml"/>
    </isomorphic:XML>

and, while I see the same key correctly used in the js version of the ds, in the js version of the Tour I see the <fmt> tag in the title. Am I missing something?

If you instead define them in JavaScript, then you use the usual client-side approaches.

Thanks for the suggestion, I actually hadn't thought of that, but it will definitely work. However, does this have any implications on the features, or is it fully equivalent?

[Isomorphic]

claudiobosticco sorry we missed that question. If the Tour is defined in XML, you should be able to use the same i18n mechanisms that apply to DataSource .ds.xml files and screens (.ui.xml files).

If you instead define them in JavaScript, then you use the usual client-side approaches.

MQDeveloper - we have a prototype of a Tour-recording system. If you are interested in Feature Sponsorship to make it an officially supported feature, start here!

[claudiobosticco]

Actually in post #3 I meant also to ask if it's possible to internationalize what I write in the <instructions> tags and in the title attributes in my tour.proc.xml file, as I tried an approach similar to that used for dataSources but it didn't work

Hello, just bumping this up to know if I should actually make a version of my tutorial for each locale or if I'm missing some other option.

[MQDeveloper]

Can you tell me where I can find the feature to record tours?