How does one turn a collection of Sections on an Orbeon form into page tabs. Its similar to the wizard view, except the tabs run across the top of the page and they don't assume a page workflow.
The intent would be to use Forms Builder to implement a UI in a web application, vs being a regular data collection capture form.
As of this writing, showing the "tabs" at the top of the page, rather the left side, isn't supported out-of-the-box, and this is tracked as request for enhancement 3033.
As a side note, I have seen people do this, I imagine with CSS, but suspect it isn't just a matter of adding a few rules, and requires some work.
Related
Complete nooby to web development (used C# and F# for desktop apps in the past).
I was playin around with Blazor server side (no more Javascript - yea!) and wanted to know, is there a way to save a page's DOM using Blazor, so that when you follow a link and navigate back, the DOM does not have to be reconstructed for the original page?
Currently using OnInitializedAsync in .razor page to construct original page - it gets called again when the nav back is taken.
Does this even make sense to do? It seems to me that in many web sites using different techonology, a nav back does not re-construct the page, the DOM is saved somewhere and the browser merely 're-paints' using previously constructed tree. Or is this also a complete misunderstanding?
So I'm working on a dashboard like app that has 8 different widgets that come up in the same page (index). All 8 pages talk to SQL server and might load slow at one point or another.
I'm looking for the best method to load the page first thing and display each widget as soon as the data is available, and not wait for all 8 widgets to be ready before i see anything but a blank page.
The current method uses includes and ajax but is not ideal and causes other problems.
JDash looks good but is quite too complex for my needs.
Using ajax to fetch dashboard item will be the best option.
You can try with calling the same function to the ajax success event with the next dashboard item.
I am new to Microsoft Dynamics. I managed to create new solution and know how to add web resource to particular page like Contacts. Also, I have added few buttons to Ribbon control with their actions.
Now my problem is, I want to add a button either to ribbon control or anywhere in page, which I can access in complete CRM (like I can do in Master Page of asp.net), and which will help me open my web resource.
For example, if I click on Charts bar, web resource should be visible, otherwise it should be hidden.
My question may be lame, because I am very new to CRM Dynamics, kindly suggest my way is correct or I need to take some different approach?
If I understand it correctly you're looking for a way to add a button to multiple screens without need to modify each of them separately. (To avoid the pain when modifying all the ribbons or all the forms.)
In that case I'd suggest creating a separate JS web resource with code that adds a button with desired functionality, styling etc. And use Form Libraries Manager from XrmToolbox to bulk add the resource to all the forms.
I have a search page published in a cms that locates database driven pages hosted in but not managed by the cms.
The search form consists of a number of different buttons and dropdowns. It works with a postback.
In the results listing, there are links to the resulting pages.
Is it possible (without changing from postback to a GET form) to make the back button work in IE such that I can click one of the result items and then get back to the result listing?
Currently when I click back I get the "Web page has expired".
Is it possible to do something smart with headers or redirects? I want to be able to history back to the search result in IE 8 and 9.
No, you will need to follow a POST-REDIRECT-GET pattern instead.
See:
http://en.wikipedia.org/wiki/Post/Redirect/Get
http://blog.simonlovely.com/archive/2008/11/26/post-redirect-get-pattern-in-mvc.aspx (shameless plug for implementing in MS MVC framework)
I'm about to build a web application(not web presentation) which will load its content through AJAX (jQuery) into a specific div. There will be a menu above the div and when a user clicks on an item from the menu, the appropriate page will be loaded into the main div.
I'd like to know if there are any cons and pros of choosing this pattern for a web application.
So far I'm avare that the browser back button and history/url will be gone.
Two possible downsides are that it could make it difficult for users to bookmark content on your site and difficult for search engines to differentiate pages on your site.
You should probably provide more information on your reasons for taking this approach. You might have good reasons or it might be a case of using a technology (AJAX) because it is cool to use.
If you want to give the users the impression of fast responsiveness, then yes AJAX load your pages, but still have a different url for each page. This will take more code but it will solve both issues that I mentioned.
http://yourdomain.com/home.aspx //loads its own content via AJAX
http://yourdomain.com/contact.aspx //loads its own content via AJAX
etc
This is really only appropriate if you have a lot of content, or where the content involves time-consuming calculations, such as on a financial site. In most cases, it would be less trouble to just load your pages normally or break you content into paged chunks.
The main con of this approach this will make your site very difficult for search engines to crawl. They don't read Javascript, so your content won't get seen or indexed by them. Try to do progressive enhancement so that they (and any users who don't use Javascript, e.g. screen-readers) don't get left behind.
On the other hand, you can keep browser history functionality. This can be done using the URL hash, e.g. http://www.example.com/#home vs http://www.example.com/#about-us. The nicest way to do this is to get Ben Alman's hashchange plugin and then use the hashchange event:
$(window).hashchange(function(){
var location = window.location.hash;
//do your processing here based on the contents of location
});
This will allow your users to use the history function and the bookmarking function of their browsers. See the documentation on his site for more information.