How does the Google Analytics connector add the hierarchical options tree to select which dataset to use? Is it a custom control?
We have the same need right now, where we want the user to choose multiple items, with database->Node->Item tree of over 20000 items. Ideally we would also like to search for elements.
In tableau, you implement a html page with js backing, so you can put any controls you want in this section, but the Data Studio seems to have just it's own subset.
Any hints would be greatly appreciated, as this is a blocker in using the Studio.
For Data Studio Community Connectors, dynamic or hierarchical config is not supported yet. For now, you can either provide a flat list or a type in option.
If you require searchable options and hierarchical configs, please put in feature requests / vote for them in the issue tracker.
Edit: Updated link.
Related
Within the console on a feed layout, we can add tools to the page such as the inline article tool. The feed view setting options with the page layout edit suggest (i.e. help text says "select the tools to make available in the center column of the page") that more than one tool can be created using code and added to the page layout (i.e. within the feed directly below the publisher actions but above the feed items). There is even a multi-select control to move the tools from available to selected, but...
I cannot find any documentation that discusses how to create the tools or how to make them available within the setup menu. Can you provide any insight to if this is possible and if so how to do it?
See example screens below...
thanks
jf
Please chk it - https://resources.docs.salesforce.com/200/10/en-us/sfdc/pdf/salesforce_case_interaction_setup_cheatsheet.pdf
Hope it helps.
I have been searching for the past 6 hours and I still couldnt figure out yet on how to create licenses that can be used for image uploads in Mediawiki. This is what I understand so far:
1) Add the list of licenses into the Mediawiki:Licenses page. (for this I copied the licenses used in Mediawiki site)
2) Next I then need to create the templates for each licenses. To do that, follow the red template links that appear below the license selection drop down menu on special:upload when you select a license from it and put info boxes in each of those respective template pages.
Step 2 is where I am having trouble with. For example, I copied the Licenses used in MediaWiki site. When I tried to add the Template:PD for public domain images, I copied the template from Mediawiki.org/Template:PD to my site. When I do that,this template is dependent on 3 or 4 other templates that needs to be created, like Mbox template, etc..etc... When I create those, those templates are dependant on even more templates that are yet to be created. Like this its a big massive tree of templates that needs to be created. For the past hour, I have been going through each red links trying to create those template one by one (basically copying it from Mediawiki site) and it seems to be an never ending task. So far I've created these templates:
Template:Mbox
Template:Namespace_detect
Template:Documentation
Template:Template_sandbox_notice
Template:Documentation/start_box2
Template:Documentation/start box
Template:Documentation/docspace
Template:Documentation/template page
Template:Documentation/end_box2
Template:Ombox
Template:Documentation/end box
Template:Fmbox
etc..etc..
Its not even half way by the looks of it. Now this is what I dont know:
1) Am I on the right track? Is this how I do it or am I doing it wrong?
2) How many templates needs to be created like this? Seems like 100s to me...
3) Is there a simpler way to do this?
4) How do I create the license lists for image uploads so the user can choose it from the list? I want a simpler one than what is used in Wikipedia.
Any guidance please.... This license list seems to be more harder than installing the Mediawiki itself!! I just dont understand why some default listings are already provided with the install. Please help...
I was finally able to complete creating the licenses for my site. The method I was doing before was stupid and completely wrong. Thanks to Mir for pointing me out in the right direction. Here is the steps on how I ended up creating licenses for my Mediawiki.
HOW TO CREATE LICENSES: - Tutorial
In order to create licenses you need to do the following steps:
1) First figure out what licenses you want to list in your wiki. Its best to look at some samples to get an idea. Here are a few samples you can have a look at:
Licenses Samples:
MediaWiki Licenses: https://www.mediawiki.org/wiki/MediaWiki:Licenses
Wikipedia Licenses: http://en.wikipedia.org/wiki/MediaWiki:Licenses
https://en.bitcoin.it/wiki/MediaWiki:Licenses
http://qed.princeton.edu/main/MediaWiki:Licenses
2) Next step is to create the list of licenses in Mediawiki:Licenses page. The format used for this is like this: "template name|descriptive label." Once you add the list, the Drop-down list is displayed on Special:Upload.
3) Once you create the license list, when you view it in the Special:upload page by selecting that license, you will see a red link to that template. follow the red template links that appear below the license selection drop down menu on special:upload when you select a license from it and put info boxes in each of those respective template pages. Eg, if one of your license choices is "* Unknown | I don't know" then you want something informative in [[template:unknown]], see template:unknown.
4) Create a template for that license. Here you can have a look at some of the license templates used in wikipedia or other sites and create your own template like that. You can add div tag to add border styles, background colours, padding, etc.. the way you want it. You can also add images for the common licenses like Creative Commons, Public domain, etc.. and most of these images are usually available in default Mediawiki install itself.
5) Once the templates are created, those license templates will be loaded when the license is selected in the Special:Upload page.
Thats it!
In the future when you create new license templates, its better to copy an existing template, look at wikipedia for the sample and just change the license text and image for that new license you are about to add. Its that easy. In the end remeber to add that new license to the Mediawiki:Licenses page.
Hope this makes sense to other newbies like me... :)
There is a category on MediaWiki.org called License templates containing 30 or so templates. You can use the Special:Export page on MediaWiki.org to export this entire category into an XML file. Be sure to tick the box that says "Include templates".
Then, on your wiki, use the Special:Import page (as admin user) to import these templates into your wiki.
More info at https://freephile.org/wiki/Licensing#Licensing_of_Wiki_content
Just want to expand on Neel's answer above.
When you add your list of licenses to the MediaWiki:Licenses page, it's important to include the Bullet List markup.
* Your own work
** cc-by-sa-4.0|Own work, Creative Commons Attribution-Share Alike 4.0
** cc-by-sa-4.0,3.0,2.5,2.0,1.0|Own work, multi-license with CC-BY-SA-4.0 and older
If you do not include the asterisks at the beginning of the line, they will not appear as options in the Licensing drop-down on the Upload page.
More detail in MediaWiki's wiki.
Also, another good source for information on licenses is the Creative Commons site.
I'm using umbraco 4.7.1 and the Repetable Custom Content Pacakge. My questions are:
I see questions that are saying that this package is not compatible with umbraco 4.7.1, but it is working fine for me... is the package compatible with umbraco 4.7.1 ?
When should I choose repetable custom content over creating nodes of a certain datatype ? Which option is better for performance ?
Is it possible to index/include repetable fields in examine search ?
Thanks.
Repetable Custom Content
Repeatable custom content is very useful if the number of fields you have is small and they are logically part of the content node you are editing. By this I mean a collection of content that is part of the page you are editing. An example of which may be a list of links with a description, name etc.
Child nodes make most sense if the content is related but not necessarily part of the same page. Or if the content in question has lots of data. The trade off with child nodes is that they are slightly slower to add.
Another benefit of child nodes is that they are selectable and sharable amongst nodes easily. For instance a content panel that can be shared amongst pages.
There is no right or wrong way to use either nodes or repeatable content, however the main thing to consider is the ease of editing experience. As from a developer perspective it doesn't make much difference.
In terms of compatibility if you know that the package is working in a version of Umbraco that is not listed as compatible on the Package page on our.umbraco.org, then you can click the Report Compatibility link to indicate which version of Umbraco you have tested it with. This will ensure that the information is up to date.
I want to know if we can create reports using EXTJS.
Thnx a lot
If you simply mean that you want to format reporting data received from the server into visual charts or graphs (or tabular / grid format) the answer is yes. Look at the Ext.chart package in the documentation. Other than that, you'd have to provide some details on what you're trying to do.
EDIT: I'm still not 100% clear on what you're asking, but if you already have working grids and you want to display the same data in a different format for reporting, this is certainly possible. However, you would not use the grid directly, you would use the underlying Ext.data.Store and bind it to some other component that can output your report. The most obvious solution that comes to mind would be using a View (previously DataView) to bind your existing store to a custom XTemplate that would generate your report view.
No. You can't create reports with EXTJS. There are tools appropriate for reporting. All of them, server side.
Hope it helps.
You can use a CSS with "media='print'" like this:
< link rel="stylesheet" type="text/css" href="css/print.css" media="print">
This CSS will be used by the browser only when the user are trying to print the page. Then, you can change the entire style of the page to look like a report.
This is a server side job. Here is what I use for generating tabular reports which are based on Grid data: http://xmlgraphics.apache.org/fop/
Also, you can generate a very nice, fully functional Excel spreadsheet from tabular data: http://msdn2.microsoft.com/en-us/lib...ffice.10).aspx
I can't find an example of a silverlight 2 tree control that is bound to a database table. I have a table with ID and ParentID columns and I use it to populate a tree control in windows forms. I want to do the same with a silverlight tree control but I can't find any examples on how to do this. Most of the samples have the nodes hard coded. I don't need any advice on how to wcf the data table, I know that part really well. Thanks in advance.
I have not worked with the tree control myself, but I did a quick google, and found the following site Populating Silverlight TreeView from WCF Service with LINQ to SQL
It does however make use of custom classes to store the data and then makes use of LINQ to SQL to extract data from your data tables to manually construct the tree view.
Hope this helps