Details
-
Type:
New Feature
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.1 Final
-
Fix Version/s: 1.2 Beta
-
Component/s: None
-
Labels:None
-
Environment:mobile
Description
Once the basic component is setup, addition support could be added for auto adjusting either width of height to the size of the current window. This insures that when an orientation change takes place the panel will resize accordingly. But the first cut only needs to support overflow:scroll.
I originally called the component panelScroller and Judy, scrollPane. I think we should go with scrollPanel to better line up with other components.
Issue Links
- is duplicated by
-
MOBI-313
create splitPane component to replace composite component panelScroller and to be used for other layout type attributes
-
- Resolved
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Steve Maryka [ steve.maryka ] | Judy Guglielmin [ judy.guglielmin ] |
rather than have a scrolling component, it might be best to have a "scrollable" attribute which can be applied to both pagePanel and contentPane components (or any further layout components).
Using device detection, we can either
a) apply the applicable styling to the div's to allow the pane to scroll if supported (iOS5, Android...not sure about Blackberry, IE?)
b) load the appropriate script for those that don't support css capability of scrolling within div's.
or
c) always use script in order to disable other touch events while scrolling.
| Affects Version/s | EE 1.1 [ 10339 ] | |
| Affects Version/s | 1.1 Beta [ 10320 ] |
This is a new feature so should be deferred after 1.1 Final.
| Fix Version/s | EE 1.1 [ 10339 ] |
Not sure if this is still a valid jira, but I have reassigned it to 1.2 Beta.
see jira for splitPane component
| Fix Version/s | 1.2 Beta [ 10344 ] | |
| Fix Version/s | EE 1.1 [ 10339 ] | |
| Affects Version/s | 1.1 Final [ 10343 ] | |
| Affects Version/s | EE 1.1 [ 10339 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
Not sure if this is still a valid jira, but I have reassigned it to 1.2 Beta.
I don't like the idea of specify a view layout by menu, or column1, column2, row 1, row2 etc. This means different thing to different people. The menu might go just below the header or on the right side, there really aren't any rules. A scroll panel can bet setup with some very simple css to meet N permutations.
One could build a taptu or Pulse application interfaces as follows:
<pagePanel>
{bean.feeds}<facet name="body" >
<outputList>
<repeat value="#
var="feed" >
{feed.title}<outputListItem group="true">#
</outputListItem>
{feed.contents}<outputListItem>
<panelScroller autoHeight="false" style="height:120px;width:100%">
<repeat value="#
var="content" >
{content.link}<outputLink value="#
>
{cotnent.image}<graphicImage value="#
/>
</ouputLink>
</repeat>
</panelScroller>
</outputListItem>
</repeat>
<mobi:outputList>
</facet>
</pagePanel>
Here is simpler example of how I would put a menu bar on the right hand side of the screen:
<pagePanel>
<facet name="header" >Dyanmic view Example</facet>
<facet name="body" >
<!-- menu on the right hand side -->
<panelScroller style="width:70%">
<include src="/WEB-INF/content/splash.xhtml" />
</panelScroller>
<panelScroller style="width:30%">
<include src="/WEB-INF/content/menu.xhtml" />
</panelScroller>
</facet>
</pagePanel>
If I wanted a third column it would simply be
<pagePanel>
<facet name="header" >Dyanmic view Example</facet>
<facet name="body" >
<!-- menu on the right hand side -->
<panelScroller style="width:3%">
<include src="/WEB-INF/content/splash.xhtml" />
</panelScroller>
<panelScroller style="width:33%">
<include src="/WEB-INF/content/menu_2.xhtml" />
</panelScroller>
<panelScroller style="width:33%">
<include src="/WEB-INF/content/menu.xhtml" />
</panelScroller>
</facet>
</pagePanel>