Kendo UI grid rendering - kendo-grid

I have a scenario here, Consider there are two kendo ui grids(jquery), Grid1 and Grid2 both are of same schema. On adding data in the first grid ie Grid-1, should automatically reflect the grid-2. However the same data I am changing in the Grid-2 should not affect the Grid-1 unless I have made an explicit event to change the same. In my case it is working bi directionally not the way I want to be. I am using Kendo observable.

Related

Grid inside an Access form

I was looking through some Access templates, and bumped into the Task Database.
It uses a grid inside a form, but I can't understand what component it's using:
When I look in Design View I can only see a list of fields:
I guess this is pretty basic and sure it's covered in MSDN, but it seems I'm unable to find proper search keywords.
It's a Format Property of the Form.
In the Property Sheet, the property Default View must be set on Split Form.
You can choose whether the datasheet is on top or below the form by changing the property Split Form Orientation.
You can adjust the splitter to view the datasheet only and then hide the splitter handle by changing to No the property Split Form Splitter.

Hiding all columns while grid is loading in ExtJS

I am working with ExtJS 5 and am trying to hide the columns of an internally defined grid that extends Ext.Component. I will first explain the motivation behind this.
The thing is, while the grid is loading, the columns show up but then disappear after the loading. This leads to some inconsistency in the UI after the loading is done and the grid is finally rendered (a kind of glitch where columns disappear).
NOTE that by columns, I mean empty columns' titles while the grid is loading (the columns are only filled after the loading). Also, by grid loading, I mean the phase in which the grid data is not rendered, and only a spinner is shown on the grid content space.
The logic to show or hide two of the columns is included in the beforerender of a listeners:
beforerender: async function() {
// some async call to determine a global boolean flag for whether the two columns will be hidden or not; by default the two columns are showing
},
And for some reason, the rendering of the columns themselves, which depends on the global boolean flag set by the async call within the beforerender, does not fulfill the expected behavior of waiting for the async call to FINISH to have the proper global boolean flag in order to show or not.
Hence the inconsistency: the columns would show up at first while loading (and that's because the rendering of the columns does not wait for the boolean flag obtained asynchronously) but then the columns would be hidden (which is the intended behavior after determining the boolean flag).
After some digging around, I figured that a potential solution would be to hide the grid column titles themselves during the loading, so that the inconsistency is invisible (the user cannot see two columns that initially appear then disappear if they simply do not see the initial columns in the first place while loading).
Any suggestions or clues as to how to hide the columns while the grid is loading? I've looked around and saw that loadMask might be a potential path, but am not too sure as to how to implement this.
I believe this can be done pretty easily with through binding.
If the store is defined in your viewmodel, you can bind the loading property of the store to the hidden property of the grid column.
Here a fiddle that shows how to hide one column. The framework version is 6.5 but it shouldn't be too different on 5.X. If{gridStore.loading} bind does not work you can set a custom flag on your VM before and after store load. And bind the hidden property to that.
https://fiddle.sencha.com/#view/editor&fiddle/3f2j

Kendo tree in kendo grid - collapse issue

I am trying to get kendo tree in kendo grid.
I could able to achieve to get the data, but not the tree functionality.
below is the link for same
http://dojo.telerik.com/oDakE
can anyone help me why the expand and collapse is not working
have you tried kendoTreeList, it accepts a json sort of like a treeview but you assign a parent id to each node, and displays as a grid.

How to use the same ViewModel for different Pages (views)

I am searching for a way to use one ViewModel for two different Views (Pages). I know there is Multi-view support in Caliburn.Micro and I read a lot of it but I'm not sure if it is what I am looking for or how it works on Windows Phone.
Currently, I have one View ItemPage.xaml and one ViewModel ItemPageViewModel. I use this View/ViewModel to add a new Item and display an existing Item. Depending on the mode (add, show, ...) I need to show/hide or enable/disable some UI elements and display different AppBar buttons.
Instead of control these UI elements by binding to properties, I want to create two seperate Pages(Views) with the corrrect UI elements.
It would be nice to use the same ViewModel for both Pages to avoid repitive code. So is my use-case above possible with Caliburn.Micro for Windows Phone?

Setting (Bound) Model Object Properties from View in EmberJS...Programmatically?

QQ: How can I update an object's property to match the innerHtml of an element in a view when a button is clicked?
I am working on building a content editing interface using EmberJS and the HTML5 contenteditable attribute (via the Hallo editor). This means that valueBinding doesn't do the trick, since we're dealing with the actual page HTML, not input/textarea value attributes. I've built a similar app in Backbone, which lacks dynamic bindings but allows you to set the model object as a property of the view.
What's the best way to get this working with EmberJS? Should I set a property on the view to the entire model? Do I need to create some sort of innerHtml binding and view helper, modeled on valueBinding?
I've set up a fiddle with an example of what I'm trying to do (with basic jQuery handling of the contentEditable attribute, instead of hallo):
http://jsfiddle.net/W6gsW/2/
Thanks!
http://jsfiddle.net/ud3323/nXCvq/
I did change a few things with how you defined the bindings in App.docView to make things cleaner. My solution does feel a litte hackish, but it works with 1 line of code per property.