This highly interactive product is specifically designed for non-profit organizations that manage their memberships using TMA Resources’ Association Management System (AMS), Personify.

The mobile conference application was initially commissioned by one of the nation’s largest non-profit associations and is now deployed and providing its constituents with mobile access to their upcoming events.

The application gives smart phone users an easy and convenient way to view conference information, particularly before they arrive at the conference and have access to the printed on-site program. 
Its main features include:

• The displays professional programs
• The displays special events
• The displays competitions
• Search enabled exhibitor listings
• Area maps, with custom locations*
• Twitter feeds specific to the selected conference*
• and more…

Users of the mobile application can quickly view the program by upcoming sessions, session listing by day, or by track. The application also provides functionality that promotes social networking through twitter feeds and links to the conference’s Facebook group page*. The exhibitors “search by booth” or “by exhibitor” feature enables users to quickly identify the location of exhibitors’ information including their booths on a map of the exhibit hall.

Non-Profit organizations that operate multiple conferences each year in support of its mission and members can, at last, easily enable mobile access to an interactive view of each conference while on the go.  The application currently supports all smart phone devices such as:

• iPhone
• Android
• BlackBerry
• and any other rich-browser based device **

The  Mobile conference application comes in an easy-to-install module compatible with the Personify eBusiness application framework (or DotNetNuke + Personify).

A photo slideshow of the application can be viewed here.

For more information and/or a live demonstration please contact us today.

* Requires Personify customizations
** Some features are disabled based on supported devices

No related posts.

Written by the best programmers in the their fields, Wrox Blox are short informational pieces and code that help other programmers get up-to-speed and keep up-to-date.  Wrox Press and its official website, Wrox.com, is a part of the John Wiley & Sons, Inc. publishing house, a leading publisher of scientific and technical information.  As a Programmer to Programmer publisher, Wrox Press publications are written by programmers for programmers, and the Wrox brand means authoritative solutions to real-world programming problems.

No related posts.

Our understanding of the unique culture of the non-profit sector and our unique mix of expertise and knowledge of the TMA Resources Personify platform made us the smart choice when it came to selecting a technology vendor. We are proud to support Toastmasters International’s efforts in overhauling and upgrading their systems anew.

Solutions

Inspector IT brought the right blend of business analysts, system architects, developers and creative design specialists to successfully solve complex problems to a large and tedious ERP upgrade plan. During the entirety of the effort Inspector IT supported and continues to support Toastmasters by providing the following technology solutions and services:

• Strategic and Technical Consulting
• Personify Enterprise Customizations
• Personify eBusiness Development & Customizations
• DotNetNuke Skin Development
• DotNetNuke CMS Development
• DotNetNuke Development Training

No related posts.

Inspector IT’s team of  developers & designers took Concep’s existing design templates and transformed them into DotNetNuke skins. All our artifacts have met all of Concep’s expectations as well as complying  with all modern web standards. “Inspector IT is exactly what we needed for our DotNetNuke solutions and integration with Personify” — Matt Parfitt, Vice President of Business Development.

No related posts.

ZoomSafer is easy-to-use software that helps ensure safe and legal use of mobile phones while driving. The Inspector IT team developed the ZoomSafer’s website and executed on a meticulous SEO requirements for maximum search engine exposure. The ZoomSafer website is hosted by Inspector IT on its DotNetNuke based CMS platform.

Solutions

Inspector IT brought the right blend of business analysts, system architects, and creative design specialists to successfully launch the ZoomSafer website and by providing the following technology solutions and services:

• Strategic and Technical Consulting
• DotNetNuke Skin Development
• DotNetNuke CMS Development
• DotNetNuke Hosting
• Content Development  & Management
• Search Engine Optimization
• Ongoing Support

No related posts.

The Inspector IT team provided consulting, integration and development services for the AT&T’s Insights corporate intranet application suite. The project consisted of the migration of a variety of existing hybrid and home-grown custom web-applications over to a single DotNetNuke based portal solution. Inspector IT was also instrumental in the reverse engineering effort of a Plumtree portal SDK which was then redeveloped for DotNetNuke to support the overall migration.

Solutions

• Software Architecture Design
• DotNetNuke Module Development
• DotNetNuke Skinning Development
• DotNetNuke SkinObject Development
• Custom .NET development
• IT Infrastructure Design Guidance and Implementation Support

No related posts.

Inspector IT’s customers have been upgraded  at 12:00am EST from version 4.6.0. The compelling list of enhancements, bug fixes, and security vulnerability fixes were announced on the day of its release.

No related posts.

BT Tradespace is a thriving community with 360,000 members and growing. Tradespace also awards BT a forum to build brand loyalty and to promote its own offers in a non invasive environment. Our relationships influence almost all aspects of our lives, both personal and professional; BT Tradespace redefines the way SMBs aquire and grow those relationships.

No related posts.

Of course the drawback with the afore mentioned controls is that they do not come equipped with an integrated paging control as the datagrid does, but the folks at DotNetNuke did a fine job at remedying the situation: they built a re-usable Paging Control. If you are a DotNetNuke module developer, you should definitely consider using it instead of building your own. This is exactly what I did, and I am now sharing my experience since finding these "nuggets" of useful built-in functions and controls within DotNetNuke is more like "treasure hunting"!

First and foremost, I have to note that the DotNetNuke paging control does not manage the data, in fact it does not even bind to a source. All that the DotNetNuke Paging Control does is generate a paging interface, and builds the paging links based on some key data that you feed into it at run time. The information you provide control at runtime is as follows:

• TotalRecords
  Once you have filled your collection object, get its row count and feed it to this property of the control
• PageSize
  Define the size of each page (i.e. the number of records you wish to display on each page)
• CurrentPage
  Get the current page index and feed it into this property (i.e. Once the pager initiates the paging, you can get the pageindex from the querystring called CurrentPage)
• Querystring
  If your module needs its own custom querystring parameters, feed them into this property, the paging links will append them for you so that your data continues to load normally)

The following is a code example for filling the the properties mentioned above:

ctlPagingControl.TotalRecords = TotalRecords
ctlPagingControl.PageSize = PageSize
ctlPagingControl.CurrentPage = PageIndex

The following is a screen shot of the generated Paging Control:

Putting it all together

Let’s start by adding the control to your UI page. First we must register the WebControl assembly (DotNetNuke.UI.WebControls) at the top of your page, and then add the control to a location of the page of your choice. The code example below assumes you are adding this paging control below your datalist/repeater:

<%@ Register TagPrefix="dnn" Namespace="DotNetNuke.UI.WebControls" Assembly="DotNetNuke" %>
<asp:Datalist ID="Datalist1" runat="server"></asp:Datalist>
<dnn:PagingControl id="PagingControl1" runat="server"></dnn:PagingControl>

The next (and last) thing to do is stitch the control to your data source.

First let me explain that there are two ways (that I know of) you can page your data:

1. Via Stored Procedure or Data Access:
   
   This is the most labor intensive, but will give you better performance. Basically you page the data in the stored procedure itself by passing the PageIndex and the PageSize into it so that it return and fills your collection with just the rows that you need.
2. Via Use the PagedDataSource Class

   This class enables you to page the entire source with much less code, however, all the rows are fetched at each page request, regardless of which page you are on (Unless you do some additional data caching in your asp.net code, in which case you are ok).

   For simplicity’s sake, the example I provide below implements this methodology.

Private Sub BindDatalist()
Dim PageSize = 20 'Display 20 items per page
'Get the currentpage index from the url parameter
If Request.QueryString("currentpage") IsNot Nothing Then
_CurrentPage = Request.QueryString("currentpage").ToString
Else
_CurrentPage = 1
End If
'Call you data layer and get the data you need to bind to the datalist
Dim objDataController As New YouDataController
Dim objCollection As List(Of YourObject) = objDataController.GetData()
'Fill the PagedDataSource object's datasource property with your collection
Dim objPagedDataSource As New PagedDataSource
objPagedDataSource.DataSource = objCollection
If Me.PageSize > 0 Then
objPagedDataSource.PageSize = PageSize
objPagedDataSource.CurrentPageIndex = _CurrentPage - 1
objPagedDataSource.AllowPaging = True
End If
'Bind the datalist
dlWhoIsOnline.DataSource = objPagedDataSource
dlWhoIsOnline.DataBind()
'Show/hide the pager based on on the number of rows fetched vs pagesize
If PageSize = 0 OrElse objDataController.Count <= PageSize Then
ctlPagingControlBottom.Visible = False
Else
ctlPagingControlBottom.Visible = True
With ctlPagingControlBottom
.TotalRecords = objDataController.Count
.PageSize = PageSize
.CurrentPage = _CurrentPage
.TabID = TabId
End With
End If
End Sub

You should now be able to run your project and test the paging control.

Feel free to post your comments below if you need additional information.

No related posts.