Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

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

    Originally posted by claudiobosticco View Post
    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.

    Leave a comment:


  • claudiobosticco
    replied
    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

    Leave a comment:


  • claudiobosticco
    replied
    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.


    Originally posted by Isomorphic View Post
    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?
    Originally posted by claudiobosticco View Post
    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?

    Leave a comment:


  • Isomorphic
    replied
    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

    Leave a comment:


  • Isomorphic
    replied
    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

    Leave a comment:


  • claudiobosticco
    replied
    Hello, could you please comment on this?

    Leave a comment:


  • claudiobosticco
    replied
    Originally posted by Isomorphic View Post
    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:

    Code:
    <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()):

    Code:
    <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?

    Originally posted by Isomorphic View Post
    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?

    Leave a comment:


  • Isomorphic
    replied
    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!

    Leave a comment:


  • claudiobosticco
    replied
    Originally posted by claudiobosticco View Post
    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.

    Leave a comment:


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

    Leave a comment:


  • Isomorphic
    replied
    Hey Claudio, just wanted to say - thanks for that feedback! That really makes the team feel good, and it's part of what motivates us to produce great stuff.

    Just wait til you see the next level of what we have in store! We think you'll love it!

    Leave a comment:


  • claudiobosticco
    replied
    I also noted a new feature to record Tours/Tutorials...The years pass by but your work continues to amaze me :)

    Leave a comment:


  • claudiobosticco
    replied
    Originally posted by Isomorphic View Post
    hi Claudio,

    We've added around 40 new framework i18n attributes for all hard-coded strings in the Tour subsystem, and you'll find them already in the language packs with AI translations as of tomorrow's builds, dated May 29 and later.

    Another 60 or so i18n attributes unrelated to Tours were picked up and translated at the same time, including the max grouping messages you mentioned in another thread.

    We're taking a look at the warning you see and will update here shortly.
    Thank you very much.
    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

    Leave a comment:


  • Isomorphic
    replied
    hi Claudio,

    We've added around 40 new framework i18n attributes for all hard-coded strings in the Tour subsystem, and you'll find them already in the language packs with AI translations as of tomorrow's builds, dated May 29 and later.

    Another 60 or so i18n attributes unrelated to Tours were picked up and translated at the same time, including the max grouping messages you mentioned in another thread.

    We're taking a look at the warning you see and will update here shortly.

    Leave a comment:


  • claudiobosticco
    replied
    Another question about the Tour/Process: is it possible to internationalize it? I mean with an approach similar to that used for DataSources expressed in XML.

    Leave a comment:

Working...
X