Infragistics Community

SQLSaturday #216 Krasnodar Event Recap

[Infragistics] Mihail Mateev — Sun, 19 May 2013 10:45:28 GMT

Infragistics Inc. was a gold sponsor of BI conference SQLSaturday # 216 Krasnodar. Company was also presented at SQLSaturday Krasnodar by me by me as a speaker.
The event was held on Saturday, May 18th 2013 at Business Center "Caucasus" in Krasnodar.

The event was organized from PASS and supported from the Krasnodar SQL user group, Microsoft Russia, Infragistics Inc, Red Gate Software and other companies.

It was an very well organized event involving many good SQL, BI and. Net professionals from Russia, Ukraine and Bulgaria. Special Thanks to Andrey Korshikov, the Russian PASS community lead and RM, who did everything to be this conference successful.

There was 9 presentations in 2 tracks: Development, BI, DBA, Azure and other areas. Event schedule is available here.

Infragistics participation in the event:

There was 2 technical presentations from Infragistics Inc.:

Spatial Data with SQL Server Reporting Services : Speaker – Mihail Mateev

Windows Azure SQL Reporting for App developers : Speaker – Mihail Mateev

At the conference I presented the products of Infragistics Inc on behalf of the company as a sponsor

There was also an interest in the Infragistics solutions, related to Data Visualization and Business Solutions. Infragistics presentations included samples solutions with WPF and ASP.Net MVC implemented with Infragistics components (NetAdvantage and Ignite UI). At the conference were showcased and the mobile Infragistics applications - SharePlus and ReportPlus

Presentations could be downloaded here:

Follow news from Infragistics for more information about new Infragistics events.

As always, you can follow us on Twitter @mihailmateev and @Infragistics and stay in touch on Facebook, Google+ andLinkedIn!

Infragistics Friends Group Presentation:Introduction to Geoflow for Excel - Event Recap

[Infragistics] Mihail Mateev — Sun, 19 May 2013 07:59:09 GMT

Infragistics Friends group, BI & .NET Geeks (Bulgarian PASS Chapter) with the help of Infragistics Inc. organized a presentation about Introduction to Geoflow for Excel. From 14th of January 2013 our group is an official PASS Chapter in Bulgaria under the name BI &. NET Geeks and we try to provide more BI and data visualization related content.

The event was held on Wednesday, May 15th at Infragistics Bulgaria Office, 110B, Simeonovsko Shosse Bul., Sofia, Bulgaria.

Geoflow is a 3D data visualization tool for Excel that provides a powerful method for people to look at information in new ways enabling discoveries in data that might never be seen in traditional 2D tables and charts. It 3D visual exploration with the ability to make direct comparisons of values and identify outliers by seeing data displayed in 2D charts at the same time.

Speaker was Ivan Donev .

Ivan Donev is a certified Microsoft IT Professional in Business intelligence, Database development and database administration since 2010 and dealing with different SQL Server projects and environments since 2007. He is also a certified trainer, active blogger and leader of www.mssqlinsider.com.

Presentation was focused on the modern trends in BI : better spatial data visualization and easier analysis, demonstrated via the new Beta of Geoflow for Excel.

Ivan Donev is presenting

Enjoy the great Geoflow spatial analysis.

As always, you can follow us on Twitter @mihailmateev and @Infragistics and stay in touch on Facebook,Google+andLinkedIn!

Showing the XamDialogWindow from a ViewModel in Silverlight and WPF

Brian Lagunas — Sun, 19 May 2013 05:09:00 GMT

The Problem

If you have used the Infragistics xamDialogWindow control in your WPF or Silverlight application, I can probably guess your biggest complaint with the control. I know what mine is! Currently, the XamDialogWindow has to be part of the visual tree in order for you to use it in your View. What do I mean by that? It means that you have to predefine your XamDialogWindow above the top most element in your View, being sure to add any Grid.RowSpan and Grid.ColumnSpan properties, so that it will be properly displayed when you show the dialog to the user by using the WindowState property or calling the Show method. If that still isn’t clear, let the code do the talking.

This is what I have to do:

<Grid x:Name="LayoutRoot" Background="White">
    <ig:XamDialogWindow x:Name="_xamDialogWindow" StartupPosition="Center" WindowState="Hidden">
        <StackPanel Margin="25" Orientation="Horizontal">
            <Button Width="75" Margin="4" Content="OK" />
            <Button Width="75" Margin="4" Content="Cancel" />
        StackPanel>
    ig:XamDialogWindow>
    <Button Content="Show xamDialogWindow" VerticalAlignment="Center" HorizontalAlignment="Center"
            Click="Button_Click"/>
Grid>

private void Button_Click(object sender, RoutedEventArgs e)
{
    _xamDialogWindow.Show();
}

Remember, the xamDialogWindow has to be part of the visual tree, so first I have to declare all instances of the xamDialogWindow that your View will need in XAML. Once you have declared your xamDialogWindow instances, you must then provide some type of mechanism to display the dialog to your user. In this example we add a simple button with an event handler. Now, you could create some reusable derived dialogs that will allow you to encapsulate any dialog logic and help you reuse the dialog throughout your application, but you will still need to add it the visual tree of your View somehow. This is not what I want to do. I want it simple. Very simple.

This is what I want to do:

XamDialogWindow dialog = new XamDialogWindow();
dialog.StartupPosition = StartupPosition.Center;
dialog.Show();

I want to be able to simply create a xamDialogWindow instance and have it displayed to the user whenever I call the XamDialogWindow.Show method. It shouldn’t matter if I am in the code-behind (which I hope you aren’t), or from within my ViewModel (which you still shouldn’t be). I’ll explain all that later. It should be simple.

If you use the ChildWindow control in Silverlight, then you know exactly what I am talking about. A common scenario is that you create a derived ChildWindow and then you can show it anywhere you feel like it form within your code. Well, that is what we are going to do with the xamDialogWindow.

The Solution – Silverlight

In order to achieve our desired result, we need to create a derived version of the xamDialogWindow. Let’s start with a new Silverlight application, and then add a new user control to the project. Yes you heard me correctly, I said SILVERLIGHT! This is what my derived dialog looks like.

<ig:XamDialogWindow x:Class="XamDialogWindowWithCode.Dialog"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:ig="http://schemas.infragistics.com/xaml">
    
    <Grid x:Name="LayoutRoot" Background="White">
        <StackPanel Margin="25" Orientation="Horizontal">
            <Button Width="75" Margin="4" Content="OK" />
            <Button Width="75" Margin="4" Content="Cancel" />
        StackPanel>
    Grid>
    
ig:XamDialogWindow>

It’s nothing complicated. Just a couple of buttons. Now, you may be asking yourself, how are we going to get around this limitation of the control. Simple! We are going to place it inside a popup. Let’s add some code to the code-behind to see what I mean.

public partial class Dialog : XamDialogWindow
{
    Popup _hostPopup;

    public Dialog()
    {
        InitializeComponent();
        WindowStateChanged += Dialog_WindowStateChanged;

        _hostPopup = new Popup();
        _hostPopup.Child = this;
    }

    void Dialog_WindowStateChanged(object sender, WindowStateChangedEventArgs e)
    {
        if (e.NewWindowState == Infragistics.Controls.Interactions.WindowState.Hidden)
            _hostPopup.IsOpen = false;
    }

    public new void Show()
    {
        base.Show();

        _hostPopup.IsOpen = true;
    }
}

All we did was programmatically create a Popup, set it’s content to the derived Dialog control, the control displaying the popup by creating a new Show method and making sure we close the Popup when the WindowState changes to Hidden. Not so complicated now is it? Now let’s look at how we can create an instance of the control in code and display it to our user by calling the Show method.

private void Button_Click(object sender, RoutedEventArgs e)
{
    Dialog dialog = new Dialog();
    dialog.Show();
}

That’s it. So what about a ViewModel? Alright, in case you still don’t believe me that it will work in code no matter where you are at, let’s check out a ViewModel approach.

public class ViewModel
{
    public ICommand ShowDialogCommand { get; private set; }

    public ViewModel()
    {
        ShowDialogCommand = new ShowDialogCommand();
    }
}

public class ShowDialogCommand : ICommand
{
    public bool CanExecute(object parameter)
    {
        return true;
    }

    public event EventHandler CanExecuteChanged;

    public void Execute(object parameter)
    {
        Dialog dialog = new Dialog();
        dialog.Show();
    }
}

<Grid x:Name="LayoutRoot" Background="White">
    <Button Content="Show xamDialogWindow" VerticalAlignment="Center" HorizontalAlignment="Center"
            Command="{Binding ShowDialogCommand}"/>
Grid>

We just created a simple ViewModel, a simple Command (since we aren’t using a DelagateCommand or a Relay Command), and then updated the View’s DataContext and set our Button’s binding. Nothing complicated, yet we still get the same result when we click the button.

Oh, and don’t worry, it will still work as Modal as well. Just so you know, the gray is the Modal background.

Now this particular sample was done in Silverlight, but the same approach can be taken in WPF.

Solution – WPF

This was really easy to implement for Silverlight, but to get the same type of functionality in WPF, it will take a little extra work to get the Popup to behave like you want it to. First let’s add a new WPF Application project to our Visual Studio Solution and immediately open up the Project Properties. Now change the default namespace to match that of the Silverlight namespace. Next, go to the Build tab and add a “Conditional compilation symbol” named WPF. This will allow us to share all of our code across both WPF and Silverlight.

Now, let’s add both the Dialog.xaml/cs and the ViewModel.cs files from our Silverlight project to our WPF project as a file link. Right click the WPF project and selected “Add Existing Item”. Navigate to the Silverlight files and add the files as a link by selecting the drop down arrow in the add button and selecting the “Add as Link” option.

Now we will need to modify our Dialog.cs file to accommodate our WPF specifics. First off, in Silverlight we don’t have to worry about multiple Windows like we do in WPF. We also don’t have to worry about the moving of a Window or the resizing of a Window in Silverlight like we do in WPF. The goal of the WPF version is to keep the Dialog within the bounds of the Window, but still be able to show the Dialog from code. Also, if it’s Modal, we want to cover up the entire Window including the minimize, maximize, and close buttons. We want it to be truly modal. We will also need to handle the resizing of a parent Window and the movement of the Window. Seems WPF introduces a lot of hurdles we must jump over, but it’s nothing we can’t handle. I made some modifications to the Dialog.cs file. Let’s look at the file, then talk about it.

    public partial class Dialog : XamDialogWindow
    {
        Popup _hostPopup;

#if WPF
        Window _parentWindow;
#endif

        public Dialog()
        {
            InitializeComponent();
            WindowStateChanged += Dialog_WindowStateChanged;

            _hostPopup = new Popup();
            _hostPopup.Child = this;
        }

        void Dialog_WindowStateChanged(object sender, WindowStateChangedEventArgs e)
        {
            if (e.NewWindowState == Infragistics.Controls.Interactions.WindowState.Hidden)
            {
#if WPF
                if (_parentWindow != null)
                {
                    //unhook our event handlers to prevent memory leaks
                    _parentWindow.LocationChanged -= ParentWindow_LocationChanged;
                    _parentWindow.SizeChanged -= ParentWindow_SizeChanged;
                }
#endif
                _hostPopup.IsOpen = false;

            }
        }

        public new void Show()
        {
            base.Show();

#if WPF
            _hostPopup.AllowsTransparency = true;

            foreach (Window window in App.Current.Windows)
            {
                if (window.IsActive) //I want to show the popup over the current active window
                {
                    _parentWindow = window;

                    _hostPopup.PlacementTarget = _parentWindow;
                    _hostPopup.Placement = PlacementMode.Relative;

                    _hostPopup.HorizontalOffset = -7.5; //account for window padding
                    _hostPopup.VerticalOffset = -30.5; //account for window title bar

                    CalculatePopupSize();

                    _parentWindow.LocationChanged += ParentWindow_LocationChanged;
                    _parentWindow.SizeChanged += ParentWindow_SizeChanged;

                    break;
                }
            }
#endif
            _hostPopup.IsOpen = true;

        }

#if WPF
        void CalculatePopupSize()
        {
            _hostPopup.Width = _parentWindow.Width;
            _hostPopup.Height = _parentWindow.Height;
        }

        void ParentWindow_SizeChanged(object sender, SizeChangedEventArgs e)
        {
            CalculatePopupSize();
        }

        void ParentWindow_LocationChanged(object sender, System.EventArgs e)
        {
            //this forces the popup to re-evaluate it's positioning
            _hostPopup.Placement = PlacementMode.Custom;
            _hostPopup.Placement = PlacementMode.Relative;
        }
#endif

    }

The first thing you are going to notice it the addition of an #if WPF … #endif regions. What this does is allows us to add WPF specific code to the WPF project without effecting the Silverlight application code. Basically we say that anything inside the #if WPF region is to be compiled into the WPF project only and Silverlight will ignore it completely when you compile the Silverlight project. Pretty col huh?

Now you will see the declaration of a private variable called _parentWindow because this is WPF and a WPF application can have many windows. We have to know which Window is the parent of the Dialog. Next we add code to the Dialog.Show method. This code looks for the active Window, then sets the _parentWindow variable because we will need it later. Next we set the host Popup.PlacementTarget to the active window, and set the Popup.Placement to Relative which will place the popup in the 0,0 location of the parent window content area. Problem is that we want it to cover the ENTIRE window in the case of a Modal popup. So we need to set the horizontal and vertical offsets to account for the Window title bar and border space. Next, we need to calculate the size of the popup to be the same as the parent active window.

Next, there are two scenarios we need to handle. One is when the parent window is dragged to a new location. By default, Popups do not reposition themselves automatically when the parent is moved. So, we hook into the LocationChanges event and toggles the _hostPopup.Placement property. This will force the Popup to re-evaluate it’s position. We also add a handler to the Window.SizeChanged event so when the user resizes the Window, our popup will be resized accordingly. Lastly, we need to make sure that we unhook our event handlers from the parent window when we close the Dialog.

Now, we can show our Dialog in a non-modal mode with the ability to move the dialog around within the bounds of the window.

Or, we can show the Dialog in a modal mode blocking all interaction with the contents of the windows including the minimize, maximize, an the close buttons.

Taking it a Step Further

Now that you know how to show your custom dialog from just using code, let’s talk about how you SHOULD be using this new found power. First off, don’t create and show your Dialog from your View’s code-behind file. Why, because you should be using the MVVM pattern when developing your XAML application, and we all know that anything in the code behind is strongly discouraged.

Now that we are all on the same page, and you are using the MVVM pattern to develop your Views, let’s discuss how you should call your Dialog from your ViewModel. Unlike in this very simple demo where I am showing the Dialog from within my ViewModel, TRY NOT to do this. A dialog is a View concern. In MVVM, your ViewModel should have no knowledge of View specific implementations, including showing a dialog window. How SHOULD you do it? Well, you should be using a Dialog Service. What is a Dialog Service? A Dialog Service is a class that your ViewModel will know about, preferably only through an interface, that will abstract or hide the implementation of showing the Dialog you just created.

Unfortunately, I will not be covering a Dialog Service in this post. Fortunately I will be writing a post on a Dialog Service soon. It will discuss different approaches as well as handling callbacks in your ViewModel when the dialog closes so that you can handle the dialog result or other required tasks of the completed dialog.

Until then, feel free to download the source code and play around. Contact me on my blog, connect with me on Twitter (@brianlagunas), or leave a comment below for any questions you may have.

Codrops - HTML5 Resource of the Day

Brent Schooley — Fri, 17 May 2013 16:24:56 GMT

Today’s resource is a quick one. I’m on the road speaking at Stir Trek so I don’t have a whole lot of time to comment on the resource. With that being the case I wanted to pick something that could stand up on its own merits without much explanation. And with that, I give you: Codrops and the Collective.

Codrops

From their website: “Codrops is a web design and development blog that publishes articles and tutorials about the latest web trends, techniques and new possibilities.” In other words, this is just another great place to gain high quality knowledge. Here’s a sampling of some of the tutorials you will find there:

Collective

The Collective is another one of these weekly article roundups that are very popular right now. It is one that I read just about every week because their curation is solid. They really do find the coolest and best articles in the web development and design world. The latest issue is Collective #63. Check it out today!

Summary

Codrops is a wonderful resource for learning really cool new things in the web development and design world. The Collective helps in your quest to never miss a great article on these topics. I’d highly recommend checking out what Codrops has to offer. While you’re checking out new things, don’t forget to try Ignite UI!

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

iOS Using Bluetooth to talk to other iOS Devices

Stephen Zaharuk — Fri, 17 May 2013 15:06:00 GMT

So here's the scenario. You're writing an app, and you realize that it would be really cool if the stuff your app creates could be shared with other people. Sure you can go down the typical root of sharing through e-mail, dropbox, iMessage, etc.. However, your app is a collaborative tool, and the person who you want to share with, sits right across from you. It seems kind of silly to send your file to some server somewhere and bounce it back to them. Well, today i'm going to show you...(read more)

How to Integrate Ignite UI Pivot Grid in ASP.Net MVC Applications

[Infragistics] Mihail Mateev — Fri, 17 May 2013 08:26:49 GMT

Ignite UI Pivot Grid is a WEB client (HTML5/jQuery/jQuery.UI based ) implementation of the very successful Infragistics Pivot Grid (xamPivotGrid) , well known from XAML platforms like WPF and Silverlight. Pivot Grid is a component that provides the same functionalities like Pivot Table and developers could embed this control in their applications and get pivot table functionalities out of the box.

Introduction

A pivot table is a program tool that allows you to reorganize and summarize selected columns and rows of data in a spreadsheet or database table to obtain a desired report. A pivot table doesn't actually change the spreadsheet or database itself.

The term pivot table is a generic phrase used by multiple vendors. In the United States, Microsoft Corporation has trademarked the specific form PivotTable. Pivot tables can be seen as a simplification of the more complete and complex OLAP concepts.

On-Line Analytical Processing (OLAP) is a category of software technology that enables analysts, managers and executives to gain insight into data through fast, consistent, interactive access to a wide variety of possible views of information that has been transformed from raw data to reflect the real dimensionality of the enterprise as understood by the user.
OLAP functionality is characterized by dynamic, multi-dimensional analysis of consolidated enterprise data supporting end user analytical and navigational activities including:

calculations and modeling applied across dimensions, through hierarchies and/or across members
trend analysis over sequential time periods
slicing subsets for on-screen viewing
drill-down to deeper levels of consolidation
reach-through to underlying detail data
rotation to new dimensional comparisons in the viewing area

Microsoft SQL Server Analysis Services (SSAS) delivers online analytical processing (OLAP) and data mining functionality for business intelligence applications. Analysis Services supports OLAP by letting you design, create, and manage multidimensional structures that contain data aggregated from other data sources, such as relational databases.

XMLA

XML for Analysis (XMLA) is a SOAP-based XML protocol, designed specifically for universal data access to any standard multidimensional data source that can be accessed over an HTTP connection. Analysis Services uses XMLA as its only protocol when communicating with client applications.

As a developer, you can use XMLA to integrate a client application with Analysis Services. Developers can use XMLA to integrate a client application with Analysis Services, without any dependencies on the .NET Framework or COM interfaces. Applications require XMLA and an HTTP connection to Analysis Services.

In this study we will not talk about how to set XMLA http access for SQL Server Analytics Services (SASS).

You could learn how to set up an SQL server that provides analysis services and XMLA HTTP Access from the great article “How to set up XMLA HTTP Access for SQL Server Analysis Service 2008 and access the Adventure Works 2008 from an Infragistics PivotGrid application”.

XMLA and Ignite UI Pivot Grid

Pivot Grid to use XMLA via Infragistics Data Source (igDataSource) using serverUrl option

There are two main options:

Direct XMLA provider via SQL Server HTTP Access
Remote XMLA provider (using XMLA via controller / WEB service)

Often requirements could be to use a different format to transfer data between WEB service and WEB client (for example JSON, which is very popular last years)

In this study we will demonstrate direct and remote XMLA access and also how can implement service with a different format (JSON)

Sample Demo

Sample demo is an ASP.Net MVC 4 project, generated with Visual Studio 2012

We have 2 projects in the solution:

1. WEB client – ASP.Net MVC 4

2. ASMX service (used for JSON serialization of the XMLA data)

In the WEB client (ASP.Net MVC 4 ) application there are :

3. PivotGridController (contains controllers implementations for all views (direct and remote XMLA, remote JSON)

4. Views :

DirectXmla (Direct XMLA implementation)
Index (Remote JSON via XMLA )
RemoteXmlaProvider (Remote XMLA implementation)

5. OlabWebService (ASMX service, used for JSON serialization )

6. WEB config (you need to allow Cross-origin resource sharing for ASMX service)

Demo project structure

Web Service

Landing page layout

From the landing page there are added three links that calls controllers / respectively return views for the each case that the sample covers:

Remote JSON provider
Remote XMLA provider
Direct XMLA

Direct XMLA Access

The Controller (In this case controller just returns a view)

   1: public ActionResult DirectXmla()   2: {   3:     return View();   4: }

Data source definition.

Here the Url points to the address for SQL Server HTTP Access for OLAP

   1: dataSource = new $.ig.OlapXmlaDataSource({   2:     serverUrl: 'http://sampledata.infragistics.com/olap/msmdpump.dll',   3:     catalog: 'Adventure Works DW Standard Edition',   4:     cube: 'Adventure Works',   5:     rows: '[Date].[Calendar]',   6:     columns: '[Product].[Product Categories]',   7:     measures: '[Measures].[Internet Order Count]'   8: });

Ignite UI PivotGrid definition – direct XMLA (igPivotGrid just uses data source – there are no specific settings)

   1: $directGrid.igPivotGrid({   2:     dataSource: dataSource,   3:     width: "915px",   4:     height: "450px",   5:     hideFiltersDropArea: true,   6:     disableColumnsDropArea: true,   7:     disableRowsDropArea: true,   8:     disableMeasuresDropArea: true,   9:     tupleMemberExpanding: function (evt, ui) {  10:         toggleTupleMember(true, $directGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  11:     },  12:     tupleMemberCollapsing: function (evt, ui) {  13:         toggleTupleMember(false, $directGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  14:     }  15: });

Direct XMLA View (Razor)

Below you could see the whole view code.

   1:     2: @{   3:     Layout = null;   4: }   5: <!DOCTYPE html>   6:     7: <html>   8: <head>   9:     <title></title>  10:    11:     <!-- Ignite UI Required Combined CSS Files -->  12:     <link href="@Url.Content("~/igniteui/css/themes/infragistics/infragistics.theme.css")" rel="stylesheet" />  13:     <link href="@Url.Content("~/igniteui/css/structure/infragistics.css")" rel="stylesheet" />  14:    15:     @Scripts.Render("~/bundles/jquery")  16:     @Scripts.Render("~/bundles/jqueryui")  17:    18:     <!-- Ignite UI Required Combined JavaScript Files -->  19:     <script src="@Url.Content("~/igniteui/js/infragistics.core.js")"></script>   1:     2:     <script src="@Url.Content("~/igniteui/js/infragistics.lob.js")">   1: </script>   2:     3: </head>   4: <body>   5:     6:     <script type="text/javascript">   7:         $.support.cors = true;   8:         $(function () {   9:             var dataSource,  10:                 remoteDataSource,  11:                 remoteSize = { u: 0, d: 0 },  12:                 directSize = { u: 0, d: 0 },  13:                 $directGrid = $("#directPivotGrid"),  14:                 //$remoteGrid = $("#remotePivotGrid"),  15:                 toggleTupleMember = function (expand, pivotGrid, axisName, tupleIndex, memberIndex) {  16:                     var friendlyAxisName = axisName == "Axis0" ? "columnAxis" : "rowAxis";  17:                     if (expand) {  18:                         pivotGrid.igPivotGrid("expandTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  19:                     }  20:                     else {  21:                         pivotGrid.igPivotGrid("collapseTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  22:                     }  23:                 };  24:    25:    26:             $(document).ajaxComplete(function (event, request, settings) {  27:                 if (settings.url.match("http://localhost:14889/OlapWebService.asmx/GetAdventureWorks")) {  28:                     remoteSize.u += settings.data.length;  29:                     remoteSize.d += request.responseText.length;  30:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  31:                 }  32:                 else if (settings.url.match("(.*/)?remote-xmla-provider-endpoint(.*)")) {  33:                     remoteSize.u += settings.data.length;  34:                     remoteSize.d += request.responseText.length;  35:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  36:                 }  37:                 else if (settings.url === "http://sampledata.infragistics.com/olap/msmdpump.dll") {  38:                     directSize.u += settings.data.length;  39:                     directSize.d += request.responseText.length;  40:                     $("#transferSize").text("Uploaded: " + (directSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (directSize.d / 1024).toFixed(2) + " KB").show();  41:                 }  42:             });  43:    44:    45:    46:             dataSource = new $.ig.OlapXmlaDataSource({  47:                 serverUrl: 'http://sampledata.infragistics.com/olap/msmdpump.dll',  48:                 catalog: 'Adventure Works DW Standard Edition',  49:                 cube: 'Adventure Works',  50:                 rows: '[Date].[Calendar]',  51:                 columns: '[Product].[Product Categories]',  52:                 measures: '[Measures].[Internet Order Count]'  53:             });  54:    55:    56:             $directGrid.igPivotGrid({  57:                 dataSource: dataSource,  58:                 width: "915px",  59:                 height: "450px",  60:                 hideFiltersDropArea: true,  61:                 disableColumnsDropArea: true,  62:                 disableRowsDropArea: true,  63:                 disableMeasuresDropArea: true,  64:                 tupleMemberExpanding: function (evt, ui) {  65:                     toggleTupleMember(true, $directGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  66:                 },  67:                 tupleMemberCollapsing: function (evt, ui) {  68:                     toggleTupleMember(false, $directGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  69:                 }  70:             });  71:         });  72:     </script>  20:    21:     <h5>Direct XMLA Access</h5>  22:     <h5 id="transferSize">Uploaded: 0KB, Downloaded: 0 KB</h5>  23:    24:    25:     <div id="directPivotGrid"></div>  26: </body>  27: </html>

Remote XMLA Provider

Controller implementation. In this case you need to add a specific attribute “remote-xmla-provider-endpoint” for your action in the controller. XmlaDataSourceModel is a class implemented in Ignite UI .Net libraries and you need to use it as a context for your view. To initialize the model you need to add a server Url for OLAP HTTP access.

   1: [XmlaDataSourceAction]   2:  [ActionName("remote-xmla-provider-endpoint")]   3:  public ActionResult RemoteXmlaProviderEndpoint()   4:  {   5:      return View(new XmlaDataSourceModel { ServerUrl = "http://sampledata.infragistics.com/olap/msmdpump.dll" });   6:  }

Remote DataSource. In this case for serverUrl you need to use the action in the MVC controller: '@Url.Action("remote-xmla-provider-endpoint")'

   1: remoteDataSource = new $.ig.OlapXmlaDataSource({   2:      isRemote: true,   3:      serverUrl: '@Url.Action("remote-xmla-provider-endpoint")',   4:      catalog: 'Adventure Works DW Standard Edition',   5:      cube: 'Adventure Works',   6:      rows: '[Date].[Calendar]',   7:      columns: '[Product].[Product Categories]',   8:      measures: '[Measures].[Internet Order Count]'   9:  });

Pivot Grid implementation (there is nothing specific – all differences are in igDataSource).

   1: $remoteGrid.igPivotGrid({   2:     dataSource: remoteDataSource,   3:     width: "915px",   4:     height: "450px",   5:     hideFiltersDropArea: true,   6:     disableColumnsDropArea: true,   7:     disableRowsDropArea: true,   8:     disableMeasuresDropArea: true,   9:     tupleMemberExpanding: function (evt, ui) {  10:         toggleTupleMember(true, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  11:     },  12:     tupleMemberCollapsing: function (evt, ui) {  13:         toggleTupleMember(false, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  14:     }  15: });

Remote XMLA View (Razor)

You could see the code of the whole view below.

   1: @{   2:     Layout = null;   3: }   4: <!DOCTYPE html>   5:     6: <html>   7: <head>   8:     <title></title>   9:    10:     <!-- Ignite UI Required Combined CSS Files -->  11:     <link href="@Url.Content("~/igniteui/css/themes/infragistics/infragistics.theme.css")" rel="stylesheet" />  12:     <link href="@Url.Content("~/igniteui/css/structure/infragistics.css")" rel="stylesheet" />  13:    14:     @Scripts.Render("~/bundles/jquery")  15:     @Scripts.Render("~/bundles/jqueryui")  16:    17:     <!-- Ignite UI Required Combined JavaScript Files -->  18:     <script src="@Url.Content("~/igniteui/js/infragistics.core.js")"></script>   1:     2:     <script src="@Url.Content("~/igniteui/js/infragistics.lob.js")">   1: </script>   2:     3: </head>   4: <body>   5:     6:     <script type="text/javascript">   7:         $.support.cors = true;   8:         $(function () {   9:             var dataSource,  10:                 remoteDataSource,  11:                 remoteSize = { u: 0, d: 0 },  12:                 directSize = { u: 0, d: 0 },  13:                 $remoteGrid = $("#remotePivotGrid"),  14:                 toggleTupleMember = function (expand, pivotGrid, axisName, tupleIndex, memberIndex) {  15:                     var friendlyAxisName = axisName == "Axis0" ? "columnAxis" : "rowAxis";  16:                     if (expand) {  17:                         pivotGrid.igPivotGrid("expandTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  18:                     }  19:                     else {  20:                         pivotGrid.igPivotGrid("collapseTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  21:                     }  22:                 };  23:    24:    25:             $(document).ajaxComplete(function (event, request, settings) {  26:                 if (settings.url.match("http://localhost:14889/OlapWebService.asmx/GetAdventureWorks")) {  27:                     remoteSize.u += settings.data.length;  28:                     remoteSize.d += request.responseText.length;  29:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  30:                 }  31:                 else if (settings.url.match("(.*/)?remote-xmla-provider-endpoint(.*)")) {  32:                     remoteSize.u += settings.data.length;  33:                     remoteSize.d += request.responseText.length;  34:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  35:                 }  36:                 else if (settings.url === "http://sampledata.infragistics.com/olap/msmdpump.dll") {  37:                     directSize.u += settings.data.length;  38:                     directSize.d += request.responseText.length;  39:                     $("#transferSize").text("Uploaded: " + (directSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (directSize.d / 1024).toFixed(2) + " KB").show();  40:                 }  41:             });  42:    43:    44:             remoteDataSource = new $.ig.OlapXmlaDataSource({  45:                 isRemote: true,  46:                 serverUrl: '@Url.Action("remote-xmla-provider-endpoint")',  47:                 catalog: 'Adventure Works DW Standard Edition',  48:                 cube: 'Adventure Works',  49:                 rows: '[Date].[Calendar]',  50:                 columns: '[Product].[Product Categories]',  51:                 measures: '[Measures].[Internet Order Count]'  52:             });  53:    54:             $remoteGrid.igPivotGrid({  55:                 dataSource: remoteDataSource,  56:                 width: "915px",  57:                 height: "450px",  58:                 hideFiltersDropArea: true,  59:                 disableColumnsDropArea: true,  60:                 disableRowsDropArea: true,  61:                 disableMeasuresDropArea: true,  62:                 tupleMemberExpanding: function (evt, ui) {  63:                     toggleTupleMember(true, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  64:                 },  65:                 tupleMemberCollapsing: function (evt, ui) {  66:                     toggleTupleMember(false, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  67:                 }  68:             });  69:         });  70:     </script>  19:    20:     <h5>Remote XMLA Access</h5>  21:     <h5 id="transferSize">Uploaded: 0KB, Downloaded: 0 KB</h5>  22:    23:    24:     <div id="remotePivotGrid"></div>  25: </body>  26: </html>

Remote JSON (using WEB service *.asmx)

The Controller

When you have own serialization controller just returns the view

   1: public ActionResult Index()   2: {   3:     return View();   4: }

Remote JSON WEB service (ASMX service)

In your implementation you need to create XmlaDataSourceModel and XmlaDataSourceManager that should be used to create a query.

Result is serialized as JSON – You can use for the your web method an attribute [ScriptMethod(ResponseFormat = ResponseFormat.Json)].

   1: /// <summary>   2: /// Summary description for OlapWebService   3: /// </summary>   4: [ScriptService]    5: [WebService(Namespace = "http://tempuri.org/")]   6: [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]   7: [System.ComponentModel.ToolboxItem(false)]   8: public class OlapWebService : System.Web.Services.WebService   9: {  10:    11:     [WebMethod]  12:     [ScriptMethod(ResponseFormat = ResponseFormat.Json)]  13:     public string GetAdventureWorks()  14:     {  15:         const string serverUrl = "http://sampledata.infragistics.com/olap/msmdpump.dll";  16:    17:         var model = new XmlaDataSourceModel { ServerUrl = serverUrl };  18:         var mng = new XmlaDataSourceManager();  19:         string result = mng.DoQuery(model, this.Context.Request);  20:    21:         return result;  22:     }  23: }

Remote JSON view implementation

Remote Data Source using JSON (you need to use for serverUrl the Url of the your web method in the asmx service)

   1: remoteDataSource = new $.ig.OlapXmlaDataSource({   2:     isRemote: true,   3:     serverUrl: 'http://localhost:14889/OlapWebService.asmx/GetAdventureWorks',   4:     catalog: 'Adventure Works DW Standard Edition',   5:     cube: 'Adventure Works',   6:     rows: '[Date].[Calendar]',   7:     columns: '[Product].[Product Categories]',   8:     measures: '[Measures].[Internet Order Count]'   9: });

Ignite UI Pivot Grid implementation (it is the same like in Direct XAML and Remote XMLA implementations)

   1: $remoteGrid.igPivotGrid({   2:     dataSource: remoteDataSource,   3:     width: "915px",   4:     height: "450px",   5:     hideFiltersDropArea: true,   6:     disableColumnsDropArea: true,   7:     disableRowsDropArea: true,   8:     disableMeasuresDropArea: true,   9:     tupleMemberExpanding: function (evt, ui) {  10:         toggleTupleMember(true, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  11:     },  12:     tupleMemberCollapsing: function (evt, ui) {  13:         toggleTupleMember(false, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  14:     }  15: });

The whole Remote JSON View (Razor)

The whole view is available here:

   1: @{   2:     Layout = null;   3: }   4: <!DOCTYPE html>   5:     6: <html>   7: <head>   8:     <title></title>   9:    10:     <!-- Ignite UI Required Combined CSS Files -->  11:     <link href="@Url.Content("~/igniteui/css/themes/infragistics/infragistics.theme.css")" rel="stylesheet" />  12:     <link href="@Url.Content("~/igniteui/css/structure/infragistics.css")" rel="stylesheet" />  13:    14:     @Scripts.Render("~/bundles/jquery")  15:     @Scripts.Render("~/bundles/jqueryui")  16:    17:     <!-- Ignite UI Required Combined JavaScript Files -->  18:     <script src="@Url.Content("~/igniteui/js/infragistics.core.js")"></script>   1:     2:     <script src="@Url.Content("~/igniteui/js/infragistics.lob.js")">   1: </script>   2:     3: </head>   4: <body>   5:     6:     <script type="text/javascript">   7:         $.support.cors = true;   8:         $(function () {   9:             var dataSource,  10:                 remoteDataSource,  11:                 remoteSize = { u: 0, d: 0 },  12:                 directSize = { u: 0, d: 0 },  13:                 $directGrid = $("#directPivotGrid"),  14:                 $remoteGrid = $("#remotePivotGrid"),  15:                 toggleTupleMember = function (expand, pivotGrid, axisName, tupleIndex, memberIndex) {  16:                     var friendlyAxisName = axisName == "Axis0" ? "columnAxis" : "rowAxis";  17:                     if (expand) {  18:                         pivotGrid.igPivotGrid("expandTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  19:                     }  20:                     else {  21:                         pivotGrid.igPivotGrid("collapseTupleMember", friendlyAxisName, tupleIndex, memberIndex, true);  22:                     }  23:                 };  24:    25:    26:             $(document).ajaxComplete(function (event, request, settings) {  27:                 if (settings.url.match("http://localhost:14889/OlapWebService.asmx/GetAdventureWorks")) {  28:                     remoteSize.u += settings.data.length;  29:                     remoteSize.d += request.responseText.length;  30:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  31:                 }  32:                 else if (settings.url.match("(.*/)?remote-xmla-provider-endpoint(.*)")) {  33:                     remoteSize.u += settings.data.length;  34:                     remoteSize.d += request.responseText.length;  35:                     $("#transferSize").text("Uploaded: " + (remoteSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (remoteSize.d / 1024).toFixed(2) + " KB").show();  36:                 }  37:                 else if (settings.url === "http://sampledata.infragistics.com/olap/msmdpump.dll") {  38:                     directSize.u += settings.data.length;  39:                     directSize.d += request.responseText.length;  40:                     $("#transferSize").text("Uploaded: " + (directSize.u / 1024).toFixed(2) + " KB, Downloaded: " + (directSize.d / 1024).toFixed(2) + " KB").show();  41:                 }  42:             });  43:    44:    45:             remoteDataSource = new $.ig.OlapXmlaDataSource({  46:                 isRemote: true,  47:                 serverUrl: 'http://localhost:14889/OlapWebService.asmx/GetAdventureWorks',  48:                 catalog: 'Adventure Works DW Standard Edition',  49:                 cube: 'Adventure Works',  50:                 rows: '[Date].[Calendar]',  51:                 columns: '[Product].[Product Categories]',  52:                 measures: '[Measures].[Internet Order Count]'  53:             });  54:    55:             $remoteGrid.igPivotGrid({  56:                 dataSource: remoteDataSource,  57:                 width: "915px",  58:                 height: "450px",  59:                 hideFiltersDropArea: true,  60:                 disableColumnsDropArea: true,  61:                 disableRowsDropArea: true,  62:                 disableMeasuresDropArea: true,  63:                 tupleMemberExpanding: function (evt, ui) {  64:                     toggleTupleMember(true, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  65:                 },  66:                 tupleMemberCollapsing: function (evt, ui) {  67:                     toggleTupleMember(false, $remoteGrid, ui.axisName, ui.tupleIndex, ui.memberIndex);  68:                 }  69:             });  70:         });  71:     </script>  19:    20:     <h5>Remote JSON Access</h5>  21:     <h5 id="transferSize">Uploaded: 0KB, Downloaded: 0 KB</h5>  22:    23:    24:     <div id="remotePivotGrid"></div>  25: </body>  26: </html>

WEB config file

You need to add the lines below to your WEB.config file (you need to allow Cross-origin resource sharing for ASMX service). IE now 10 doesn’t require this settings but you need to add it for other browsers.

   1: <system.webServer>   2:   ....   3:   <httpProtocol>   4:     <customHeaders>   5:       <add name="Access-Control-Allow-Origin" value="*" />   6:       <add name="Access-Control-Allow-Headers" value="Origin, X-Requested-With, Content-Type, Accept" />   7:     </customHeaders>   8:   </httpProtocol>   9: </system.webServer>

Running Pivot using JSON via WEB service

Remote JSON implementation (this is the first option)

Select Remote XMLA link to open the view with Remote XMLA implementation. In this case you will see that the data traffic from the remote WEB server to your client is more than 5 times more larger.

Select Direct XMLA link to redirect to Direct XMLA view. In this case you will see the pivot grid with the same data

Conclusions:

Infragistics Ignite UI supports XAML out of the box via Data Source (igDataSource) option “serverUrl”

You could use remote and direct XMLA providers. It is easy to implement own WEB service where to serialize data to JSON and Data Source could use this format.

Remote access leads to less data transfer and it will be better to use this approach (doesn’t matter which format you are using: XMLA or JSON)

Sample source code with all referenced scripts and libraries you could download here:

You are probably thinking, how do I get my hands on Ignite UI Pivot Grid? It’s easy.

Click on this image to get a fully support trial version of Infragistics Ignite UI controls:

To view all the samples and code for HTML, MVC & ASP.NET, click here: .

http://www.infragistics.com/products/jquery/samples

Follow news from Infragistics for more information about new Infragistics products.

As always, you can follow us on Twitter @mihailmateev and @Infragistics and stay in touch on Facebook, Google+andLinkedIn!

Smashing Magazine - HTML5 Resource of the Day

Brent Schooley — Thu, 16 May 2013 16:43:50 GMT

I can’t say enough about today’s recommended resource for HTML5 developers and designers. Smashing Magazine has simply become a must read for me on a daily basis. The quality of content at the site is some of the best in the industry and spans a variety of topics from programming to design. If that wasn’t enough, they also have print and eBooks available from the site as well as a very active job board. Let’s take a look at what’s available on this great resource.

Articles

The “magazine” portion of Smashing Magazine is where the site gets its name and it is nothing short of smashing in terms of high quality content. The magazine is broken up into the following major sections: Coding, Design, Mobile, Graphics, UX Design, and Wordpress. Each of these sections is further broken down into subsections. For instance, the Coding section is broken down into CSS, HTML, JavaScript, and Techniques.

Books

Smashing Magazine has book sets available in both print and eBook form. These are sold either as bundles or individual books. For instance, The UX Bundle is a collection of 10 books on user experience for $42.40, but each individual book such as Navigation & Interaction can be purchased for $4.99. The print books are collections of useful topics that span multiple disciplines and are printed in a high quality color format. These are definitely coffee table caliber books and are worth checking out.

Summary

Smashing Magazine is an amazing resource for people developing and designing in the HTML5 world. The content is second to none and there is a lot of it produced every week across the various disciplines represented on the site. This is definitely a site you will want to visit frequently.

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

Export dashboard as a deck of PowerPoint slides with ReportPlus

Gabriel Lopez — Thu, 16 May 2013 01:41:00 GMT

So you’ve designed your first ReportPlus dashboard, congratulations!! Now you want to share it, right? Well, you have a number of options with ReportPlus:

Save the dashboard in a shared location, for other ReportPlus users to open it. This shared location can be a SharePoint document library, a Dropbox account, or a Google Drive folder.
Email the dashboard. For other ReportPlus users to open.
Email a screen capture. Send by email a picture of the dashboard, to share the dashboard with anyone, not just ReportPlus users.
Export the dashboard as a PowerPoint file. This is the option we are going to cover in some detail in this article.

Selecting what to export

By tapping the Export option in the actions popover a wizard that will guide us through the export process is displayed.

If the dashboard has page filters defined the first thing we will have to select is what to export, whether the current view of the dashboard, or a selection of pages, meaning an export of the dashboard filtered with the different values a page filter holds. For instance, exporting the HR Dashboard with all pages, will export the values for all the offices: New Jersey, London, etc. If the dashboard has multiple filters the first one will be selected to be used in the export process.

If the all pages option is selected then, ReportPlus will automatically walk through the different values of the first pages filter. The export is capped in 50 pages so you must select less than 50 values to export.

Introducing annotations

In the second dialog of the export wizard a table listing the contents to be exported is displayed.

At this point we have the option to introduce comments, and select which values are going to be exported by turning on or off the Visible switch.

Previewing the generated ppt

By tapping the preview button the generation process runs and the slides are displayed.

Sharing the slides

The final step in the export process is defining what to do with the generated file. The options are to send the slides to another iOS app, such as Keynote, or emailing the PowerPoint file.

Wrap up

Well, we've gone through the export feature which enables ReportPlus dashboards to be shared with anyone. Some of ReportPlus users have requested the ability to customize the PowerPoint template used in the export process, and I wanted to point out that this option is available in the Enterprise version as part of the rebranding support. If you want to know more about the Enterprise version, just let us know!

Xamarin.iOS Netflix Style Grid

Brent Schooley — Wed, 15 May 2013 19:50:53 GMT

Many people have been requesting more Xamarin.iOS samples for NucliOS. While I haven’t had a chance to work on any of my own recently (those are coming soon), I was happy to see that there are members of our community who have been taking it upon themselves to work on some. Claudio Sanchez has taken SteveZ’s “Creating a Netflix style iOS Grid” blog post and sample and recreated it using Xamarin.iOS.

Please check out Claudio’s work and read his great description on how he translated the sample from Objective-C to C#. There are some good insights to be gained from this work.

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

HTML5 Weekly - HTML5 Resource of the Day

Brent Schooley — Wed, 15 May 2013 16:54:35 GMT

Ever wish it was easier to keep up to date on all of the new things that are going on in the world of HTML5? Do you hate managing RSS feeds of the news sites and blogs you need to keep track of to stay current? Today’s HTML5 Resource of the Day will help you solve this problem.

HTML5 Weekly

HTML5 Weekly is a newsletter that will help you keep track of everything that has gone on in the HTML5 world while you’ve been busy programming your applications. Once a week, the newsletter will be delivered directly to your email. It includes a “featured” section that contains a few top stories from the week that you will want to read. There will also be a sponsored article from the company that sponsored that particular issue. There are sections for things to read and screencasts to watch. There is also a helpful section that contains job listings.

If you want to see some sample content, check out the latest issue here.

Summary

HTML5 Weekly is a great resource for those of us who are too busy to try to figure out what we should be reading. Delivered once a week, this newsletter makes it easy to ensure you will never miss important articles and screencasts. If working with HTML5, you should definitely check out Ignite UI. Our jQuery controls will get your data-driven application off to a great, and beautiful, start.

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

Tuts+ - HTML5 Resource of the Day

Brent Schooley — Tue, 14 May 2013 19:41:32 GMT

Today’s HTML5 resource is Tuts+. Tuts+ is a tutorial site that contains tutorials for a wide variety of subjects, including web development and design. It’s something I’ve been using in conjunction with Code School (yesterday’s resource) to help me get up to speed with the web world.

net tuts+

net tuts+ is the web development section of Tuts+. This site contains tutorials, articles, tips, sessions, resources, and videos that teach users of the site new things about web development. The quality of the content here is great. One of the tutorial series I’ve been going through is the Getting into Ember.js tutorial series by Rey Bango.

webdesign tuts+

webdesign tuts+ is the web design equivalent of net tuts+ and offers up the same type of content for designers. This is a great place to learn new tips and tricks and work through some tutorials to hone your web design skills. I’m currently looking forward to reading the tutorial The Best Way to Learn CSS to help me get up to speed on CSS, but there are many more tutorials from beginner to advanced.

Other related tuts+ categories

The psd tuts+ site can help you learn some valuable Photoshop skills if you are a designer. The mobile tuts+ site might be worth checking out if you are developing HTML5 sites for mobile devices as well.

Summary

Tuts+ is a wonderful resource with a wide variety of tutorials and tips. I’ve been using it a lot as I ramp up on web technologies. You’ll find a little bit of everything here for just about any skill set. If you are getting into HTML5, you should check out Ignite UI. Our jQuery controls will get your data-driven application off to a great, and beautiful, start.

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

Top 3 SharePoint Conferences Worldwide in 2013

Josh Anderson — Tue, 14 May 2013 14:46:00 GMT

Conferences are a great way to keep involved in the wider tech community. They offer a chance to meet new people, socialize, and network. They allow attendees to get involved with new product launches, to see demos, and test samples in person. Best of all, they generally offer tutorials and hands on sessions, run by a wide range of experts, showing off the latest techniques.

SharePoint has always been served by a particularly vocal and active community, and this community has over the years hosted many great conferences around the world. Below is a list of three conferences (one in the US, one in Europe, one in Australia) that we think you should consider attending this year.

While this list is covering some of the more unique SharePoint Conferences, one conference that isn’t listed is the official Microsoft SharePoint conference. This was last held in Las Vegas in 2012. As of yet there are no details of this year’s conference (when or where) but keep an eye on the official site for more information. When it is announced this show is well worth attending, if for no other reason that it is official show of the year.served by a particularly vocal and active community, and this community has over the years hosted many great conferences around the world. Below is a list of three conferences (one in the US, one in Europe, one in Australia) that we think you should consider attending this year.

1. Australian SharePoint Conference

June 11-12 2013, Melbourne, Australia - More info

The fourth annual Australian SharePoint Conference is centered around the theme of ‘Collaboration’. This is an intentional move away from the usual topics of ‘business outcomes’, toward the softer side of SharePoint projects and implementations. The show features a keynote presentation from Dr. Neil Preston entitled, “The psychology of collaborative maturity: How do you know when your team or organization is truly collaborating?”

2. IT / Dev Connections

Sept 30 - Oct 4 2013, Las Vegas, United States - More info

The IT / Dev connections show is a long established conference that caters to a wide range of Microsoft products, including SharePoint. The show is so big that anyone attending for just the SharePoint content won’t be disappointed. This year has a great list of speakers already confirmed, including:

Dan Holme - Technologies Evangelist and Consultant
Scot Hillier - SharePoint MVP
Paul Thurrot - Senior Technical Analyst
Tony Redmond - Exchange MVP and Senior Contributing Editor to Windows IT Pro

3. SharePoint Connections Amsterdam

November 19-20 2013, Amsterdam, Netherlands - More info

The SharePoint Connections Amsterdam conference is now in its third year. The 2013 show is supported by the ‘Dutch Information Workers Users Group’ (DIWUG) and the SharePoint Community Netherlands’ (SPCNL) which should lend it an additional level of kudos.

The organizers have listened to feedback of the previous shows and this year session content covers a much wider breadth of subject matter than ever before, including SharePoint Online, hybrid deployments, search, and apps.

Pre Register here for 399 EURO + VAT.

What’s in a Name? Job Titles for Software Engineers

Marie Berdini — Tue, 14 May 2013 13:39:00 GMT

What’s in a title? I guess it depends on whose title you are talking about. When it comes to job titles, and one’s own, the subject can be quite contentious. Many employees jealously guard titles, as often they are the only thing available to indicate seniority. Others just want a title that describes what they do. Some of course don’t really care.

The bigger issue comes when applying for a new job. There is a such a mix of titles out there that, at first glance, it can be difficult to understand what a job actually is.

When it comes to software engineering (or software development - but we will come to all that in a moment) it seems there is a fairly wide selection of titles out there. Some mean the same thing, some indicate specific skills, and some are just plain silly.

Let's try to make a bit of sense of it all:

Software Engineer - In Europe the term Engineer tends to mean people with some kind of engineering qualification or degree. Used more in the U.S., but it is definitely one of the more well used job titles out there.

Developer - Often prefixed with ‘Senior,’ ‘Junior,’ or some form of specialism like ‘.NET.’ This is another stalwart job title to go with Software Engineer.

Programmer - Less of a job title, more of a description. This doesn’t tend to be used too much in job description or advertisements. People might describe themselves as one informally.

Technical Lead - The term Lead in this one tends to indicate some kind of extra responsibility. But this role could really mean anything, so don’t jump to conclusions.

Architect - Job roles with Architect in them tend to be more senior, and tend to look at more overarching implementation and integration issues. A Developer might write the code for a particular module, but an Architect will design how the various modules fit together.

At the end of the day, does any of this matter? Hmm… probably not. As long as individuals are clear on the job role and what it means, that is the main thing. It would, however, be good to see a little more consistency. Consistency across the industry is probably a bit much to wish for, but consistency across a single organization would be a good start.

Let us know any strange or over complicated job titles you have come across in the comments below.

Interested in a career here at Infragistics? Check out our current openings!

Code School – HTML5 Resource of the Day

Brent Schooley — Mon, 13 May 2013 18:16:00 GMT

I’m currently going through a bit of a learning process trying to get up to speed with the web world and HTML5. As someone who has dedicated most of my time the past few years on desktop and mobile platform development, there’s a lot to learn. Not only do I need to get the basics under my belt, but I also have to keep up with new things that seem to come out every day. It is a lot to keep track of and I’ve been developing a list of things that can help the process along. I want to share those with you so that we can all benefit from whatever I pick up during the process. The first resource I want to share with you is Code School.

Code School - Learn by doing

Code School is an amazing resource for learning new programming skills. They currently have courses that cover Ruby, JavaScript, HTML/CSS, and iOS as well as some assorted topics they call Electives.

Code School has a unique learning experience that couples high quality video content with step-by-step coding challenges that you complete in the browser. This is truly learning by doing. Each course is broken up into levels and you receive an achievement for completing each level.

The video production quality for the lessons are top-notch. The instructor will often appear alongside the slide material. Here’s an example screenshot from the Try jQuery course:

The coding challenges tie directly into the material that was presented for the lesson and walk you through the concepts. Each challenge will be a simple task and you will receive immediate results for each mini challenge. If you get the challenge incorrect, they will help guide you based on what exactly was incorrect in your answer. It is a very smart system that can catch common mistakes. This is a great way to learn. If you are stuck, they offer a few hints for each challenge as well. Here’s a screenshot from the “Traversing the DOM” section of the Try jQuery course:

Summary

Code School is a great way to learn and they have free courses to get you started. I would highly recommend checking out the Try jQuery course to get a feel for how this process works. For me, it has been the best way to learn jQuery. I look forward to trying some of their other courses soon.

Contact

If you have any questions or comments in the meantime, please feel free to email me at bschooley@infragistics.com or find me on Twitter @brentschooley.

Quick-Tip: Creating Grid Lines on the IGGridView (Objective-C)

[Infragistics] Torrey Betts — Thu, 09 May 2013 14:48:00 GMT

Introduction

As of NucliOS 2013 Volume 1, the IGGridView currently does not support column separator lines. Until we add this feature natively, there's a simple workaround you can use to create gridlines.

Creating the Gridlines

The idea of the work around consists of using the IGGridView's backgroundColor in combination with the columnSpacing and rowSeparatorHeight properties to create a separation between the cells as shown in the above illustration.

UIColor *gridlineColor = [UIColor blackColor];
CGFloat gridlineSeparation = 2.0;
_gridView.backgroundColor = gridlineColor;
_gridView.columnSpacing = gridlineSeparation;
_gridView.rowSeparatorHeight = gridlineSeparation;
_gridView.rowSeparatorColor = gridlineColor;
_gridView.rowHeight = 50;

Using this work around doesn't require the IGGridView to stay in any generic design, you can still take advantage of the great layout functionality. The image below demonstrates this work around on an Excel-like grid.

Download the Example Project

The Xcode project source code for this quick tip can be downloaded by clicking this link. You will need to add the IG.framework to the Xcode project after you install the NucliOS trial.

A much easier to read format of this post is available here.

By Torrey Betts