• Replies 23 replies
  • Subscribers 395 subscribers
  • Views 27108 views
  • Users 0 members are here
Options
Related

Better Studio SDK experience

Romulus Crisan (former member)

Hi,

We recently started to look at various options on how we can improve the Studio SDK learning experience. One of the first things we want to do is to move all the code samples and project templates to github which will allow you to browse the code without Visual Studio installed, contribute to an existing sample or create a new one and of course better explain what the sample is doing. This will happen in the next couple of weeks.

In parallel we have also started an internal discussion about ways to improve the current SDK documentation. Since the OpenExchange community is the main consumer of the SDK documentation I think is really important to have your view on this. Please share your view by answering the following questions:

1. Name some features that you would like most  and are not in the platform now?

2. Would you be interested to be able to contribute to the documentation ?

I'm looking forward for your replies.
Rate translation
×
Suggest better translation
×
Parents

  • I would find vb.net samples really useful - I can read and understand the C# samples but sometimes it is a lot of try and error until you get things going in vb.net.

    I would also with for an offline version of the SDK, like stated by some fellow coders below. That would be really helpful.

    From a features perspective, currently, I am missing editing of project templates via the API. You can create and configure a project, but then, if you want to store it as a template ... to no avail. So that would be really nice to have from a features perspective.

    Also, it would be very helpful, if there was a quick way to log on to the SDK via the web. Currently, you have to click yourself through a myriad of pages until you are there. That is cumbersome.

    Speaking of "cumbersome things" - have you ever tried publishing a new app using the upload page for OX? It seems to take forever until everything is filled out. At least the page is not crashing anymore as was the case earlier and you would lose everything you already entered. But still - the upload area has a lot of room for improvement if you ask me.

    Another one that has room for improvement is the browser support both of the upload page (not working on Safari for example and only working with some versions of IE and Firefox, I haven't tried Chrome, though) and the SDK itself. Please add support for more browsers.

    Apart from that - keep on with the good work! The APIs and SDKs are great and it is fun working with them (most of time;-)).

    Cheers

    Tom
  • in reply to Remy Blaettler

    Although everything has already been said, I would like to point out some of the features I would like to see with the next version:

    - Add further description and usage examples for some namespaces and functionality.

    - Offline access to the documentation of the SDK.

    - Not having to run executables from the Studio installation folder. This is really a constraint.

    Yes, we'd be willing to contribute to the documentation.

    Keep on with the good work!

    Cheers,

    Radivoj
Reply Children
  • in reply to rfajt

    I agree with everything said above:

    - Offline documentation

    - Logging in is cumbersome and it seems to time you out if you are not active on the page (I have to log back in again)?

    - Google indexing or something better than the search function we have now.

    I'm assuming some of the documentation is unfinished? For example:

    >see: StudioContext

    >Operations on DocumentView

    I cannot find this information.

    EDIT:

    Following up on my previous post, it seems there is no way to extend/control the built-in controls in Trados.

    For example, I would like to extend/control the display filter control to make custom display filters, but

    there seems no way to do this with the current public API. Also, looking at the "Document" class,

    you can "read" information from it, i.e. each property provides a "getter", but there are no "setter"s, so no way to manipulate it.
    Please let me know if there is something that I am missing.
  • in reply to Jesse Good

    Hi,

    my wishes are related to the MultiTerm SDK: it would be cool if the MT server would have a webservice-based API in addition to the COM one, and the MT API would provide access to all the features that are also available in MT desktop (e.g. manipulating multimedia objects: adding images to entries, reading them etc).

    Regards,

    Tamas
  • in reply to Tamas Meszaros

    I give my humble +1 on these:

    - Offline documentation: It would allow also to import the documentation in DASH (macosx) or VELOCITY (windows) - having to deal with multiple languages those utilities are a must have for any programmer, also it renders google indexing completely unnecessary.

    - Easier Login procedures (less click to reach the documentation, I think forums also would benefit from a reworked login procedure)

    - Powershell:, as i dug on on the helper files provided i found the SDK documentation useful without any need to adapt it. Of course the files provided in a forum post can'be considered a complete documentation ;-) I would write some documentation page on calling the sdk methods form the powershell, attaching the example files.

    - Overall the documentation is complete and clear, although a little schematic. I think having comments and some more examples would sometimes be an appreciated plus.

    Thanks for asking!

    Enrico