I'm currently building a web form using APEX that is losely modelled after a "wizard" style. That is, I have forward and back buttons for most pages, etc, etc.
The problem I have is that it seems all my buttons need to be part of a region and that region needs to located in a pre-determined section of the page.
I would prefer to be able to place my buttons where I want them rather than include them into a specific region. I just want them at the bottom of the page.
At the very least, I need to get a region to ignore all my theming so that it can be "invisible" so that only the buttons are showing.
Can anyone point me in the right direction?
See this example I just created on apex.oracle.com. The buttons are in a separate region that has no template associated with it.
In fact, it would be better to create a new region template for the buttons region, with no decoration applied. This would give you more control over the location and spacing of the buttons. At its simplest this template could be defined as:
<div id="#REGION_STATIC_ID#" class="myButtonTemplate">
#BODY#
</div>
(The ID is optional, but I like all my tags to have IDs so I can reference them in Javascript and CSS if required.)
Related
Our team is working in ServiceNow and trying to make some aesthetic changes to the ootb Form widget. We've cloned that widget and are trying to give the Form Sections a different background and some larger/bolder font. Since the Form layout is buried in some template code in the system, the only way for us to change the look and feel is to manipulate the DOM in our cloned widget. We've read that the best way to do this is to use the Link Function tab, but we are unsure how to begin. After inspecting our console, it looks like we want to manipulate the parent div of a tag. What is the syntax so that we can target that specific div?
We've tried different variations of this without any success:
angular.element('legend').parent().addClass('newDiv');
Depending on how big changes you want to make are, I would just try and add CSS using the page CSS. I don't know how familiar you are with ServiceNow, but if you ctrl + right-click the widget in the portal, click 'Page in designer', and then the 'Page' button with a gear on it in the top right corner, then you can add page specific CSS there. I've used this a lot, and it also saves you from cloning the widget.
I'm hoping to get some direction on the following scenario. I have some UI/UX design experience but not much in working with SharePoint 2013 branding. What I need to accomplish is the following:
Custom "tab" style navigation in the left hand and top of the page. These would look like folder tabs along the top, and on the left hand side they would only be rounded on the right corner. I understand that I need to edit the CSS but not sure how best to accomplish this considering some of our page requirements. We want to have the tabs along the top and left but each department's "page" is a different color theme.
Example of tabs required
Do I edit the Master Page CSS to get the rounded tabs look and then that is applied to each page, but that page keeps its color selection or do I have to do a CSS page for each page? For example, a department uses the color palette selection to assign their colors but the Master Page takes care of the tabs modification or do I have to do a Master Page for each department's page?
ANY direction would be a big help. I just need to deploy this as simply as possible but not sure how. -Thanks!
I created several regions and I added several blocks within these regions.
I created a Node and it's being displayed within the "content" block.
I need to know how to display a Node in a different block ("Sidebar", "Top bar" etc.).
I watched several screencasts about Views, Content-Type etc.
I couldn't find a way to solve this problem.
I know it seems ridiculous, but I've been working on other frameworks (Yii, Joomla, Wordpress ...) and it was very straightforward.
Any help is appreciated.
Best Regards, Wissam
You usually have to use a block to place content in a specific region. Content, Sidebar, and Top Bar are considered regions. Blocks can be managed from the admin/structure/block screen. You can either create a block right from that screen, or create a block view in Views and it will appear in that list. Then you can move it to whichever region you'd like.
There are blocks in drupal like Main Menu, Navigation, Management Etc,
They all appear as a solid text in huge letters, but I want to turn them into links and to act as an actual menu.
Is there any extension that does it, or I would have to code it my self?
I'm a newbie in drupal but I don't want to re-invent the wheels, if it's already provided somewhere.
Edit:
Well, the titles of the block are the solid text indeed, I want to turn them into link, or at least hide them, these letters are so huge and out of place. And if I set label to '' it displays the default word, like 'Navigation'...
Enter <none> as the title to hide the block title. Blocks are not made to be pages so there's no point linking to them. Consider a view if you want more complex functions from blocks.
I am developing a public website which is the front end to information about medical conditions.
After the user does a search (questionnaire based) they are presented with the results which are categorised in to sections and sub-sections.
Information items can be assigned to both sections and sub-sections.
At the moment sections are represented by tabs across the top and the screen and sub-sections by links in a sidebar. The links in the sidebar change depending on which section is selected.
The problem is the section names are quite long (several words) and as a result the combined length of the tabs is too wide for a standard screen resolution (1024 x 768). Therefore they wrap and break the page layout. We will also have to add additional tabs in the future.
With this problem in mind and the fact our target audience is quite wide, this is a public medical website, what options are there for presenting this kind of information in a way which is accessible and easy to navigate for an average user.
How long are the subsection names? Will they fit in the space for tabs? You’re likely to get better user performance if you put the section links on the side bar menu and the subsection links in the tabs, rather than the other way around. See http://www.usability.gov/pubs/040106news.html.
The other alternative is to put everything on the side bar menu. Subsection links can appear indented under their section links. You can also consider putting the subsection links in a column of their own to the right of the section column. This makes the section menu stable, but takes a lot of horizontal space that’s perhaps better used for content. In either case, proper attention to visual design will show the current section, subsection, and the link between them.
There shouldn’t be a problem with accessibility as long as you’re using links to navigate to each section/subsection (perhaps generated programmatically for each page based on a database relating links to pages).
Just brainstorming some ideas:
Use combo boxes to allow the user to select the (sub)sections, then display the appropriate information items.
Create separate pages for each section-level and provide a bread-crumb control to show the user where he / she is in the page hierarchy.
Create some sort of fold-out menus that automatically hide when the user reads an information item.
In another question on SO, I came across a link to Quince, perhaps you can find some inspiration there as well.
You could try:
An iPod-style menu (in which subsections are hidden pages that fly in from the right): http://www.filamentgroup.com/lab/jquery_ipod_style_and_flyout_menus/
Or as Daan has said:
Cascading drop-down boxes: http://www.asp.net/AJAX/AjaxControlToolkit/Samples/CascadingDropDown/CascadingDropDown.aspx
The downside with both of these (over a traditional tree view) is that the subsections aren't visible until you choose a section. If your users don't know the name of the subsection they're after, then either of these will be a good fit.
If, on the other hand, they do know the name of the subsection they're after, it's probably better to give them an auto-complete textbox so they can type a few characters and go directly to it.