Starting work with Silverlight...

I've been amused by the toys out on the web that have been developed in Flash/Flex and Silverlight over the past few years. Even some as big as the Olympics being broadcasted over the world in part by these technologies... and now, with Microsoft finally releasing Silverlight 3 to the web a few months ago, it has enough "brass" available that someone can build a decent LOB application.

I've been pondering converting dealprocessor to be hosted for many reasons, inclusive of the support nightmares I've already had with only two companies running the software.  My hope is that by having the COR hosted on a web server "in the cloud" somewhere, I can relieve at least one headache for the businesses that will start to purchase the software.  Only time will tell... and it's going to be one hell of a Ride... I can't wait to be able to start posting preview links for the app!

POS 2009 - Timeforge Integration

We're in testing... although I don't see many POS 2009 dealers jumping for joy... most of them are not quite willing as of yet to bit the bullet on this new system.  I hope that things improve for SP1, and that more dealers come on board, or Microsoft will lose a pretty sweet opportunity for third party integration.

Timeforge Integration - First Steps

So, first real step was taken today... to see how long it would take to get the workstation components into the POS interface, to make a homogenious environment for the POS user to update the required data for Timeforge.

In the POS Bootcamp, this is something that took about 10-15 minutes, after all the discussions... after about 45 minutes or so, I finally got things working. It turns out the manifest file gets to be quite picky. In the manifest file, you define the following (according to the POS 2009 Beta 2 SDK Documentation):

<AddinManifest>
<AddinAssembly
assembly="Name of the developer's add-in .dll file"
implementedViews="Microsoft.Rms.AddInViews.ServiceModel.IPosAddIn"
namedPermissionSet="FullTrust"
exposeUI="true/false"
addInID="b9ac2dda-1520-4a48-b8da-ac187b0ad172"
addInDisplayName="Simple POS Add-in Sample"
addInDescription="Simple POS Add-in sample"
company="AddInDeveloperCompanyName"
version="1.0"
url="AddInDeveloperCompanyURL.com"
enabled="True"
/>
</AddinManifest>

So, I did this, copied it, inserted it into the Timeforge.manifest file, and tried for over 30 minutes to figure out why it wasn't working. Finally, I looked at a few of the other manifest files, and discovered something quite interesting... See if you notice it:

<AddInManifest>
<AddInAssembly
url="http://go.microsoft.com/fwlink/?LinkId=126931"
enabled="True"
separateAppdomain="True"
/>
</AddInManifest>

And in case you are wondering, no... it doesn't have to do with the fact that there aren't as many attributes on the AddInAssembly tag. It's all about the capitalization. The POS Beta 2 SDK documentation states to do it the former way, and the way it needs to really be written (as far as capitalization goes) is the way it looks in the latter.

So, I simply made those edits, and away I go now to start the real work on the POS 2009 implementation for Timeforge.

New Project - Timeforge Integration

Now that Microsoft Dynamics POS 2009 is finally to RTM stage, it is time to begin a new project, and one that I have been looking to work on for some time... integrating an online scheduling software package with Dynamics POS 2009.

When we headed to the POS SDK Bootcamp back in January, 2008, one of the requests I had made was to provide a method that would allow us the ability of creating a custom add-on data entry screen for common entities in the system, like Items and Employees.  Although the development team couldn't quite grasp the concepts that we needed to deal with, they did provide the necessary interfaces, and I look forward to use them shortly.

The package I am looking to integrate is called Timeforge.  It is already integrated with the Restaurant Point of Sale package, Dinerware, as well as other packages that are on the market.  Anthony Presley, one of the founders of Timeforge, was more than glad to have someone offer to do the integration, as it will save him time in hunting down a developer that can handle the intricacies of Microsoft Point of Sale 2009.

So, I look forward to start posting more about the integration, as we hope to have something that is "showable" by the RSPA show next month in Las Vegas, NV. (A trip that I have long been wanting to make)

Update - '09 Goals

Well, it's almost May.... ~4.75 months since I wrote the '09 goals post.

I ahve two updates to give at this point:

Wrap up the Dinerware - Sales Watch... This is technically wrapped up, although I had hoped that POS Leader would have marketed the software Add-on more, and given better feedback so we could truely make it a whizz-bang Add-on that other restaurant POS systems cannot offer.

Re-build the Dinerware Report Scheduler... TBD... things are going well, and I have done significant work to it. The software is now completely re-built, and seems to be functioning well. There is now interest for this Add-on from another Dealer out of the Carolinas, and they are in the process of test-implementing the software now. Hopefully, that will go through, and I can see some revenue come in.

I'm anxious to get through the rest of second quarter, and to run the quarterly sales reports to see how I did this quarter in comparison to last!

New Project Getting Ready for a 1.0

Not sure what we will call it yet, but there has been a lot of flack against the idea that Dinerware cannot easily show drink recipes like Aloha or Digital Dining can, so I got aggravated after hearing that another deal was lost in part to not having that feature, so I just spent the past two weeks developing an electronic version of "The Bartender's Bible" which should handle the needs of any clients.

Hopefully, no-one will balk when we present them with the cost of the Application.  Only time will tell.

Once it's out there, and licensed, it will be available for Retail sale (end-users) and Wholesale (resellers) via tailoredPOS.com

'09 goals

I have to laugh as I begin to write this entry.  I look over the past 52 weeks, and realize that they came and left, and I didn't realize that they were ever there.  A day is a mere 24 hours, and they go by so fast that you wish it would contain 36.  Most of my past year was spent doing one of several things... programming, sleeping, driving all over kingdom come, or drinking (as in beer).

As I think about it, it was a fun year, with many new opportunities that I wouldn't have had if I were to still be working at a Corporate job, such as travelling to Portland & Seattle, eating at an underground restaurant, trying an USDA Prime NY Strip steak at Table 31, and learning a whole lot more about life.

The year did have its downturns as well, both parents fell ill, and having to watch them slow down in comparison to where they were at this time last year... facing the music that they are acutally mortal and will not be here at some point in the future, and realizing that I need to set achievable goals for what I want to accomplish by December 31. So, here goes:

Goals for '09:

• Build dealprocessor COR to be web based, hopefully using Silverlight where applicable to still over a rich-client experinence, but yet have it easily accessible no matter where you are working.
• Wrap up the Dinerware - Sales Watch project and get that published so it can begin drawing revenue.
• Re-build the Dinerware Report Scheduler to be more user friendly, and get it to market for the July Trade Show in Las Vegas, NV.
• Attend the Dinerware Trade Show in Las Vegas, NV
• Go to RSPA and talk with vendors about dealprocessor, and build a good lead base to go off of for the fall of the year.
• Clear some revenue on dealprocessor, so that I can continue to afford developing the package.
• Work with revolutionPOS to develop a decent VAR line so that we may both be able to prosper.

Now, hopefully since I have finally written them down, I can sit here on Dec 31, and look back and go right down the list and say "done, done, done... DONE"  We shall see.