Hi,
On the roadmap page there is a "Dock Manager Component" listed, but I don't see any information on this anywhere.
Anyone have more information or an ETA on this?
Thanks
Christopher
Hi, I'm trying to use a SplitView within a layout in a mobile application. I'm using MVVM.
I've defined the splitview in the html body, outside of any layouts or other views. The application starts by loading a basic layout and view It then navigates to different views based on data entered.
Can I use my main layout as the layout for the splitview in addition to the starting view, and other standard (non-split) views?
Does the splitview need to contain its own layout for each pane?
I can't directly navigate to "v_bill_splitview" as the page appears blank. I need to go through another basic view which navigates to the splitview when a tabstrip link is clicked - once the splitview layout is displayed, the content is still blank.
Any thoughts / guidance? Thanks.
Example structure:
<body>
<!-- Loader Layout -->
<div data-role="layout" id="l_layout" data-id="l_layout" style="display:none;">
<section data-role="content"></section>
</div>
<!-- View Loader -->
<div id="v_loader" data-role="view" data-layout="l_layout" data-show="onShow" style="visibility:visible">
<div class="center">
<p>
<object data="logo.svg" type="image/svg+xml">
<img src="logo.png"/>
</object>
</p>
<p>
Loading...
</p>
</div>
</div>
<!-- Main Layout -->
<div data-role="layout" id="l_main" data-id="l_main" style="display:none">
<header data-role="header">
<div data-role="navbar">
<a data-role="button" data-click="l_main_homeOnClick" data-align="left">
<img src="logo.png" style="height: 1.8em; width: 1.8em;"/>
</a>
<span data-role="view-title"></span>
</div>
<div style="text-align: center;">
<img src="../img/logo.png" style="max-height:25px; text-align:center"/>
</div>
</header>
<section data-role="content"></section>
</div>
<!-- View Search Criteria -->
<div data-role="view"
id="v_search"
data-id="v_search"
data-layout="l_main"
data-model="app.models.search_criteria"
data-title="title"
style="display:none">
<ul data-role="listview">
<li>
<label>Test
<input type="text" class="km-text"/>
</label>
</li>
<li>
<label>Test2
<input type="text" class="km-text"/>
</label>
</li>
</ul>
<hr/>
<ul data-role="listview" data-bind="source: dataSources.types" data-template="tpl_types"></ul>
<br/>
<div class="container-fluid">
<div class="row">
<div class="col-xs-12">
<a data-role="button"
data-bind="events: { click: events.searchClick }"
data-icon="search">
Search
</a>
</div>
</div>
</div>
</div>
<div data-role="splitview"
id="v_bill_splitview"
data-id="v_bill_splitview"
style="display:none"
data-layout="l_bill"
data-style="vertical">
<!--data-portrait-width="200"-->
<div data-role="pane" style="-webkit-box-flex: 4" id="main-pane" data-layout="l_bill2">
<!--<div data-role="layout" data-id="l_bill2">
<div data-role="header">
<div data-role="navbar">
<a id="side-pane-button" data-role="button" data-align="left" data-click="expandSidePane">Side</a>
<span data-role="view-title"></span>
<a data-role="button" data-align="right" href="#bar">Bar</a>
</div>
</div>
</div>-->
<div data-role="layout" data-id="l_bill2">
<header data-role="header">
<div data-role="navbar">
<a data-role="backbutton" data-align="left">Back</a>
<a data-role="button" data-click="l_main_homeOnClick" data-align="left">
<img src="track_trace_logo.png" style="height: 2em; width: 2em;"/>
</a>
<span class="l_bill_title">Freight Bill 2</span>
</div>
</header>
</div>
<div data-role="view" data-title="Main Pane">
Main pane Initial view
</div>
<div data-role="view" data-title="Main Pane Bar View" id="main-bar" data-show="collapseSidePane">
Main pane Bar view
</div>
</div>
<div data-role="pane" data-initial="#view1">
<div data-role="view" id="view1" data-id="view1" data-title="Side Pane">
<h3>view1</h3>
<a data-role="button" data-target="main-pane" href="#main-bar">Bar (Main pane)</a>
</div>
</div>
</div>
Hi there,
I've tailored the splitview demo on the Kendo UI demo site.
Prior to the splitview view displaying, I have an initial view asking for some information including what default category the user is interested in.
I'm looking for a solution where I can automatically navigate the user to their selected category. I.e. #side-inbox?CategoryID=15
This is effectively mimicking the user navigating to the split view and clicking on category 15. I will still give them a facility to go "back" so they can look at the contents of other categories.
I've done the easy bit of navigating to the splitview using app.navigate("#splitview"); but I'm struggling to fire the default category.
See extract of categories view on left side of the splitview:
<div data-role="view" data-title="Categories" id="side-root" data-use-native-scrolling="true">
<ul data-role="listview" data-style="inset" data-source="splitViewCategories" data-template="categoriesTemplate">
</ul>
</div>
<script id="categoriesTemplate" type="text/x-kendo-template">
<a href="\#side-inbox?CategoryID=#: CategoryID#" data-icon="mostviewed"><span class="daysfont">#: CategoryName #</span></a>
</script>
Appreciate any help,
Thanks
Hi,
I have tried to use collapsible inside a splitview but it was failed. Is it possible to do?
Thank you.
I've been developing a phonegap application using Kendo and overall the result has been pretty good. I've been focusing on just phone screen size, but now I'm adapting it to tablet, meaning that on some cases where there's a listview that goes to a details view, I'd like to use a SplitView to make a better use of the screen size on a tablet device.
I've developed all my screens as remote views, each one in its separate html file and each one is bound to its own viewmodel.
That being said, now I'd like to reuse my existing views in a splitview layout, but it hasn't been as easy as I thought it would be (or I haven't found the correct documentation/examples). All examples I've seen are very basic and just use a couple of views, all defined in the same file.
In a real world application, that's most likely not the case and you'll have quite a few screens that you can navigate to and that you cannot have all of them in the same file if multiple developers are working on the same app.
Issues I've found so far:
I've stopped developing the split view at the moment as I've found myself writing a lot of hacky code to bypass this limitations.
This could actually be a showstopper for using your framework in my application.
Are the issues I mentioned solvable? Am I missing something?