I would like to collect your ideas on the following:
SharePoint 2010 (and 2007) does have a preview button... while you are editing a publishing page you can switch to the "Page" tab and hit the Preview button:
Clicking this button does some magic to save your data, and opens a new window where the preview page is displayed. Nice, but could be better. What I would like is live update on editing of field controls from the edit page on the preview page.
My thoughts on this is are as follows:
Field types have an ID. For rendering the field values on your preview page, subclass from the standard FieldValue control, and render a span with the same ID around the field value html. So if we have the text ABC in the content editable div of a RichTextFiled X, render the field value as ABC in the display output (for example using EditModePanels for Display and Edit)
Add key-stroke event handler on all fields for the edit mode page (using for example jQuery), on key press copy contents from edit browser window to preview browser window
Transfer can be done using http://www.sfpeter.com/2008/03/13/communication-between-browser-windows-with-jquery-my-new-plugin/.
Does this sound doable? Would be great to work dual monitor, edit on one monitor, preview page in its real rendering on the other monitor. Especially if the edit mode differs from the display mode.
Looking forward to your input!
I will answer my own question. It is not as easy as its sounds. Fields can use things like reusable content and render patterns. These features render at server side, and change the output. This would require postbacks, which renders the whole thing useless. Lets stay with the already available preview button.
Related
In Generic Inquiries, I've noticed that certain fields automatically have hyperlink functionality to open specific screens. I'm not sure what determines what screens these open (I'd imagine its based on whether its a key field for a maintenance table/DAC, etc.) - but I've also noticed that the manner in which it opens a screen is different for different fields / field types. Some open a popup with no menu, others open in the same screen space as the Generic Inquiry, and in doing so replace it in the browser.
My question is this: Is there a way to modify, in the GI setup, the manner in which it opens the screen so that it always opens as a replacement instead of a popup window?
If I remember correctly, with Acumatica ERP ver. 6.0 on the Generic Inquiries' Navigation tab there was added Window Mode drop-down to configure how the screen is opened from hyperlinks in a given GI:
I have created a webpage using Backbone.js and Marionette.js that mostly consists of a bootstrap accordion view that displays a list of items when the accordion header is clicked. Each item can also be clicked, which will show a hidden div of detailed information that pertains to that particular item.
I would like to make this site accessible to people who might not be using a mouse (Maybe they're visually impaired and using a screen reader? Maybe they just don't like clicking things? Either way.) I'm thinking that this would mean being able to press the Tab key to get to the accordion, pressing Space or Enter to open the accordion, Tabbing down (or down arrow key?) through the list items, and then using Space or Enter to show the selected item's hidden div.
I'm finding it difficult to find information on how to add a feature like this, since searches like "How to make an accessible website that can be used without a mouse" mostly turns up blogs on what a developer should do to add accessibility to a page, and not much on how to do it.
Currently, the page doesn't really respond to any keyboard buttons. Any tips or resources you could share would be extremely appreciated. I've been fiddling with ARIA role tags, but I'm either not doing it right or it's not the answer here.
You have to use tabindex
https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement.tabIndex
Screen readers automatically read whatever element is the activeElement
I'm sure I am missing something straightforward and simple, but in xpages, using a tabbed panel, who do I get all the tabs to print when the users prints the page?
You can use a Dojo tab container (part of the extension library) instead of the standard tabbed panel. With the Dojo tab container the content of all tabs is loaded at once (in opposite to the standard tabbed panel, as Tim said), so you could do some CSS magic to make all tabs visible when printing.
Tim recommends building a separate XPage for printing, and I second that. Organize the content of the tabs in custom controls, create a new XPage for example with the suffix "_print" and include the custom controls in it without the tabbed panel. Then create a button, link or whatever in the first XPage which simple opens an XPage with the same name plus "_print" in a new window.
In the "_print" Xpage you can use a "window.print" after the page loads to open the print dialog automatically.
This technique has the advantage that you can style the printing exactly as needed. You can even control which content to include when printing by using the visible/rendered property and compute to render controls only when the current page name does not include "_print".
I want to design own custom backstage view tab that has desing like standard tab FileNew.
How can I (and can I at all) use such tab elements like scrollable button set or large borderless button with text at bottom of one.
There are elements in the BackStage Tabs which are built-in and not available form the programming side. For example, all the individual controls on the Print Backstage Tab cannot be re-used by a developer. I'm afraid that we have the same problem with the File New Backstage. The previews are built-in. You can verify this if you look into the WordControls.xlsx file delivered with the Office 2010 Control-IDs download: There are no controls for the TabNew except for "GroupNewFormTemplates", "GroupNew2003Dialog" and "GroupNewFormPreview".
You can only re-use controls which are defined in the Ribbon Scheme, as Combobox, Edit Control, Button, and so on.
So to display your templates, you must use these default controls, or built something completely different.
I am designing a system in Share Point via Share Point Designer. We have a form in my Share Point site. Users have to fill some fields in the form and send it to the approval committee. We cannot upload anything to the servers. The design is site based. Our problems are:
1- I want to add small (?) icons for the descriptions of that field. When the user click on the (?) icon for "brief description" field a pop-up or another window will be opened and perhaps it will say:
Enter a description of the requested thing.
Be as specific as possible.
2- I want to change the font colors of the fields in the form. The share point brings them black as default. Such as I want to see the "Brief description:" and "Status:" as purple instead of black.
Brief description: .....
Status: .....
3- I want to add an agreement pop-up to the new form which will be open just after clicking "send" button in the form. The pop up will say: "Are you sure that you read the procedure" . The user has to click "Yes" to continue sending the form. Otherwise It will return to previous screen again.
Use jQuery. You can upload the scripts to a document library and do pretty much whatever you want to the html after it is rendered by SharePoint.
For making changes from a custom form, JSAPI may be useful. Alternatively you can hide a regular form and manipulate it with a popup.