Skip to main content

JayData–The cross-platform HTML5 data-management library for JavaScript

Last week, I wanted to call an oData service from my HTML5 metro app. First I was planning to use datajs until I discovered JayData which offers similar functionality to datajs and much more!
image
What’s JayData?
JayData is a standards-based, cross-platform Javascript library and a set of practices to access and manipulate data from various online and offline sources.
JayData provides JavaScript Language Query (JSLQ) as a tool to query local (in-browser and mobile) and remote data sources with a simple, unified query syntax: JavaScript itself. Much like Microsoft .NET developers can utilize LINQ to perform operations on data from different databases.
The aim of JayData library is to give a similar level of abstraction with the help of the $data.Expressions API and the JavaScript language itself.
JayData is cross-platform (runs on HTML5 desktop and mobile browsers, can be hosted in PhoneGap environment on iPhone, iPad and Android) and cross-layer as it works on client-side and server-side (Node.JS).
It provides support for
  • WebSQL
  • SQLite
  • IndexedDB
  • OData
  • Facebook
  • YQL
How to start using it(in ASP.NET)?
  • Create a new web application
  • Add the JayData nuget package.
  • A command line utility is copied into the web folder. With that you can create a JayData client context from any oData metadata document.
  • C:\NorthWindSample>JaySvcUtil.exe -m http://services.odata.org/Northwind/Northwind.svc/$metadata
    –n northwind -o northwind.js


  • A northwind.js file is generated.
  • Include this file into your web page together with jaydata.js and jQuery.
  • Now you can write some Javascript that uses this northwind odata service:
  •  
    <!DOCTYPE html>
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <title></title>
        <script type="text/javascript" src="/scripts/jquery-1.7.1.min.js"></script>
        <script type="text/javascript" src="/scripts/JayData.js"></script>
        <script type="text/javascript" src="northwind.js"></script>
        <script>
            var nwcontext = new northwind.NorthwindEntities({
                name: 'oData',
                oDataServiceHost: 'http://services.odata.org/Northwind/Northwind.svc'
            });
    
            function createItemLI(name, id, css) {
                var li = $('<li></li>').append(name).addClass(css).data('id', id);
                return li;
            }
    
            $(function () {
                nwcontext.Categories.toArray(function (categories) {
                    categories.forEach(function (category) {
                        $('#categories').append(
                            createItemLI(category.Category_Name, category.Category_ID, 'category'));
                    });
                });
            });
        </script>
    </head>
    <body>
        <ul id="categories">
        </ul>
    </body>
     
  • That’s all!

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...