My goal is to embed the dataset explore screen where the user can build charts as an iframe in a web application; the idea would be that the user cannot see the menu bar on the top such that they cannot navigate away from the dataset within this iframe because it would result in the scope of the iframe being different from the scope of the application around it if they change datasets. I found the answer on a different thread was to use the standalone=true query parameter, but using that setting on a dataset explore page it simply shows you the chart (which is empty until the user adds some dimensions and measures to the query). Embedding a dashboard seems to work as expected.
Try appending ?standalone=1 to the URL. You can find more details about in the superset documentation:
https://superset.apache.org/docs/creating-charts-dashboards/creating-your-first-dashboard/
You might find this article helpful too: https://www.tetranyde.com/blog/embedding-superset
Related
Is there a way to publish the amount of views/edits of a page in/on the page itself in xWiki?
I've used parts of this article to create an accessible form to see usages of different spaces. But I would also like to publish the views/edits on the pages itself.
Thanks in advance!
Richard
I would suggest you use an UIExtension point (see https://extensions.xwiki.org/xwiki/bin/view/Extension/UIExtension%20Module and the tutorial https://www.xwiki.org/xwiki/bin/view/Documentation/DevGuide/Tutorials/UIXTutorial/) from the list of available ones (https://www.xwiki.org/xwiki/bin/view/Documentation/DevGuide/ExtensionPoint/) to add the extra information to be displayed on each page.
I guess the most suitable UIXP would be the Content Footer one (https://www.xwiki.org/xwiki/bin/view/Documentation/DevGuide/ExtensionPoint/ContentFooterUIX/).
Inside the UIX you add, you can do a simple query to fetch the view/edit values from the statistics module (either with the API, if it exists) or with a HQL query, like in the example you've mentioned.
I am working on designing webpage UI where some experimental data is stored. This data could be inaccurate sometimes so I'm providing a button at the bottom of the page which redirects the user to the new issue webpage in GitLab. Look at the sample below.
And this button will take the user to somewhere like this:
The URL behind the button is simply
<full-path-to-some-gitlab-repo>/issues/new?issue[title]=Issue%20with%20experiment%20%201
which was taken from GitLab official documentation.
As you can see here, there's an option to automatically fill the Title section directly from URL but I couldn't figure out how to do the same for Labels. Is there any way to do it this way?
For internal requirements, there must be a label automatically selected and the users can't be relied on to select it by themselves. For each webpage, a new label is assigned which makes it possible to extract all the issues related to that webpage later just by extracting all issues with that label. This might not be an optimal way to do this so if you have any other suggestions, please put them in comments. Thanks.
This does not seem yet supported, regarding pre-filling labels on issues.
That was requested in issue 63392, but without solution for now.
I would like to build a custom index page for ActiveAdmin.
I don't mean the records shown in the index or the list of columns to display -- I mean a custom view as described here:
https://github.com/activeadmin/activeadmin/blob/master/docs/3-index-pages/custom-index.md
A Google and SO search does not turn up any code samples. I have looked at the Active Admin code itself -- but also wanted to see some examples.
Ideally, I would be able to reuse the filter and scope and table components that the index provides -- I simply want to move things around quite a bit and add a custom component or two.
Anyone have any pointers or examples?
activeadmin has nice wiki page here https://github.com/activeadmin/activeadmin/wiki/Plugins
there u can find at least several implementation of custom index components
for instance
https://github.com/bys-control/activeadmin-index_as_calendar
https://github.com/zorab47/active_admin-sortable_tree
And of course take a look at sources
https://github.com/activeadmin/activeadmin/blob/master/lib/active_admin/views/index_as_grid.rb
https://github.com/activeadmin/activeadmin/blob/master/lib/active_admin/views/index_as_table.rb
https://github.com/activeadmin/activeadmin/blob/master/lib/active_admin/views/index_as_blog.rb
https://github.com/activeadmin/activeadmin/blob/master/lib/active_admin/views/index_as_block.rb
You can try to inherit from one of them and add your own missed parts, depends on your needs
I am kind of new to SharePoint. I am learning it on the go and learned about the concept of pagelayout and publishing features on the site. But I am not really 100% sure what is the difference between a WebPartPage, SitePage and PublishingPage. I kind of know what all these pages be used for, but what I not get is: why do they need to separate all these pages?
I think we can just get a publishing page and have all the feature there including webpart and everything else (with our choice of PageLayout). However I dont see a way to use a pagelayout on a particular SitePage.
Is there any particular reasons for using either one of them? Even though it seems like one of them can serve as all of them?
You should use page layout when ever you know the page structure. For example you are running an online news paper. You want to show the news to the users into three columns. First column is for menu, second column is for news content and third column is for advertisements. Now in your daily usage this layout is common. So you can use this page layout for entering the news. After creating the page layout you can make it as a default to your pages. Page layout is nothing but the structure of a page simply!!
A webpart page does not have a field for content directly on the page like a SitePage has. A Publishing Page is like a SitePage, but requires extra fields for dealing with the publishing extra features.
Using a single layout for all three risks being confused as to why one page does not work the same as another when it has the same layout (the difference would be the underlying features are different.).
I will make a comparison with cars. There are three type of cars, each is better suitable for a certain purpose: tractors for farming, buses for public transport, light cars for private transport. You could use a tractor for all the purposes above but it's not ideal.
"One of them can serve as all of them". This is not true in their current implementation. I'll give you one example: prefer Web part pages against Publishing pages to better control content added by contributors in an intranet. There are many other examples.
I created a form to display a specific report instead of a view. iwant the form to locate into the directory folder in which views located. for eg I have a view at 1. Reports\a. Quarterly Reports, I want the reports be to located at 1. Reports\b. No of Request per Country(this is the form). So that when I view the reports they are only in one location. Is this possible?
Ken has good points about the design of the solution. If you need more direct assistance, then I can offer the following solution.
As you're now using a variety of design elements. You need to unify it using a frameset and an outline. Framesets in Notes are the generally the same as their web counterpart. The great thing with Notes is that you can easily add this to your current design.
I would recommend the following order of tasks.
Create the outline. Instructions here
Create the frameset and connect the outline to it. Instructions here.
Set the database launch properties so the frameset loads up when people open the database. Instructions here.
Even though the links point to Lotus Notes version 6, the functionality is still applicable in version 7 and 8. The only other point I would make is that when you click on an outline element it needs to know where the target location to display the data. You define this on the frames in the framesets. Just look at the menu option "Frames" and select "Frame properties" or "Frameset properties" respectively.
You can use a Notes Outline to manage this. Set one up for your database, if you haven't already, and use it as your left-hand navigation in your frameset. If you aren't sure what I'm talking about, try creating a new database based on the Document Library template and take a look at the design. It'll have a frameset, and on the left frame it'll have a Notes Outline.
Once you have your database setup like that, you can control what the user sees in that outline by creating hierarchical outline entries. You can link views, pages, and forms to your outline entries and that way you can have your 1. Reports\a. Quarterly Reports view showing next to your 1. Reports\b.No of Request Per Country form (report).
Even better, you can use different names. Since an Outline manages its order, you don't need to name your entries 1., 2., etc to get them to show in a certain order. You can name them whatever you like and rearrange them in the Outline design screen.