Our Developer Q&A will begin in less than 2 hours, so feel free to start posting your questions now! At 9 a.m. PST, these developers will be joining us right here on this forum thread:
Would be great to hear a release date for 9.1 particularly as it will solve a number of issues we have including the "Google Chrome issue" and active directory group syncing.
Current date is given as Q3 2015, but I'm guessing that, as this is an open Q&A for 9.1 and not just for us a beta testers, it's got to be days away
Those of us in Scotland are about to head home after a days work, so if those of you in Seattle are up early then a reply before 9am Seattle time would be great!
Few questions in advance then:
- What CI system is used at Tableau (Travis, Jenkins, etc)?
- What are the basic commit rules, what tests are integrated into the build?
- How do you test server specific functions in Desktop builds? Like do you have some fancy server mocking library or builds using internal test server farms?
- How would you test your Web Data Connectors? Simulator is nice, but that one is clearly not for connector regression/unit tests. Do you have any libraries for WDC unit tests (like ones which can be used from headless browsers)?
- (When) do you plan to sunset wgserver? It seems most of the features went to vizportal but you still have the legacy ruby code in production. How does this polyglot-dual-portal approach impact the development life-cycle?
- How painful is to debug JNI calls from web applications? Do you have any internally developed process to reduce the complexity of mixed and different kind of byte codes?
you can skip questions if that helps and thanks as always
Is there any Plan of developing a Drag and Drop Way of builiding a Web Data Connector for an end user ?
How does the Permission Works ? Will all the user be able to access the URL ?
Is there any plans to make a way to change column width in webedit in a similar way to Desktop-like functionality?
Did you see this KB article on the Chrome M45 issue? http://kb.tableau.com/articles/issue/error-uncaught-syntaxerror-unexpected-identifier-viewing-workbook-in-chrome?lang=en…
There is a quick patch there. We are also working with the Chromium community to resolve the issue.
We're glad you're excited! Stay tuned
Yes that's ok, but 9.1 doesn't have the issue, so as we're working on regression testing a 8.2 to 9.0 upgrade anyway we may as well regression test an 8.2 to 9.1 upgrade but only when 9.1 is live and out of beta.
If the server administration blessed the WDC by importing it with Tabadmin, then yes, any user with access to the server will have access to the WDC (if they know the URL).
Hey Vishwa, thanks for the idea! We don't have any immediate plans to provide a drag and drop interface for end user to create Web Data Connectors but it's a great idea.
Would you mind posting this on the ideas forum? That way other users can upvote the idea and push for us to add it.
I don't know of plans for drag-and-drop WDC development. You might try using the Kimono example connector I wrote (Web Data Connector for Kimono). Kimono lets you define a "screen scraping" API to a web site using the mouse. Once you do that, you can use the Kimono WDC to connect to your Kimono-hosted API. (Warning: I wrote that connector as a personal hack. I don't guarantee bug-free.)
More on security: if the WDC connects to a secure site, the connector should ask the user for their credentials. You could embed username/password in the connector, but that probably wouldn't be wise.
Tamás: thanks for all the questions. can you give us some more context for questions #1 & #2?
#3) we do end to end testing and use internal test framework
#4) a lot of the WDC testing is done using our internal test tools we use for testing other data connections for Tableau Desktop. We also use Jasmine to test the Simulator. No unit tests for our samples (maybe we should?)
#5) you’re right: wgserver is still shipped to support the REST and XML APIs. these are actively being ported over to vizportal and, once complete, we should be able to remove wgserver from the product. most of the wgserver UI and logic (besides the REST APIs) is turned off so we’re not spending dev time on it
#6) we have a common pass-thru that goes from our Java to C++ layer...and we don't modify this pass-thru very often so luckily this isn't very painful for us
We are actively looking to bring more functionality to web authoring. I spend a lot of my day thinking about that. We are always eager to learn what our users would find most useful. I didn't see a post on the ideas forum yet (sorry if I missed it). This would be a great idea to add.