Completed (in testing) Extend functionality so that it can be incorporated in other developer's applications

[Nathan Explosion]

Provide extensions to allow other developers to add translation functionality to their own applications.

[Nathan Explosion]

Here's an example: an integration into @Adriano Faria's Tutorials application in my dev environment.

 

 

 

 

 

[Nathan Explosion]

Completed - steps on how to integrate will be available once the resource has been released, and can be accessed via:

 

[Adriano Faria]

Nathan, about this:

selectThis = $('section').find('div.ipsType_richText').first();

Wouldn’t be easier if I add a new div in my template to be targeted?

I see you’re using the “content” field. What if we use that new div, I could add more stuff to it, right? For example, tutorials Description and Content, which are two different fields. Basically, everything inside the div woube translated. Wouldn’t it be better?

Edited September 16, 2023 by Adriano Faria

[Nathan Explosion]

Please - can you wait until you see the final release before suggesting changes? Don't assume that the JS in the front-end dictates what is actually translated

More will be revealed when I get the time to finish things off on it.

Also - the guide you read is NOT COMPLETE, and is only viewable to yourself, so I'd appreciate it if you didn't comment on it until it is available in a complete state.

[Nathan Explosion]

FYI - while this functionality is completed, I am going to hold off on releasing it for now.

I plan to have "(NE) Content Translator" released end of next week, and would like to concentrate on resolving any issues in the resources main functionality before worrying about bring others into the mix.

Additionally, as found during testing with some of Adriano Faria's resources, not all 3rd-party apps are going to be the same and I expect I'll have to assist others with getting their integrations done, which will take up time I am unlikely to have available before the end of this year.