TicketDesk 3 is mostly about re-architecting the core system for current asp.net webstack technologies. It will not be a feature heavy upgrade, though it will come with a completely new user interface on top of the existing feature set.
The following is an incomplete high-level feature list. Several aspects will change once I’ve done more research in certain areas.
- Ticket Subscribers: anyone can subscribe to a ticket’s notifications
- Editable lists in TicketCenter: a TD1 feature that never got back into TD2
- New Security System
- Local users (forms)
- oAuth support
- Active Directory via ADFS
- Legacy Account Migrations (TD2 upgrades)
- New User Interface
- Entity Framework 5
- Code-First Model
- EF Migrations
- Legacy Migrations (TD2 upgrades)
- SQL Server 2012
- localdb, Express, and full editions
- SQL Azure
- SQL CE 4 (tentative)
- MVC 4
- SPA Based UI
- Responsive Design
- Knockout.js & related
- oData (tentative)
- Windows Azure deployability
- MEF 2 or Ninject (tentative)
- SimpleMemebership or Universal Providers (tentative)
- AD integration via ADFS
- WIF (tentative)
Mobile is of course the hot-topic these days, and to a lesser extent so are native Windows 8 applications. I intend to design TicketDesk 3 around WebApi, which should go a long way towards enabling support for many different front-end clients. I’m looking at responsive design to enable the initial web application to scale around different screen sizes, but I’m not sure responsive design alone can bridge the gap all the way down to the small-screen devices (phones and mini-tablets).
After the initial TD3 release, I hope to build mobile specific HTML 5 views. These should enable a good experience on any modern smartphone, but I don’t want to get into building a native app for each phone platform.
I do hope to build a native Windows 8 metro (or whatever they call it this week) client app.
I plan to support upgrades for existing TicketDesk 2 installations, and the databases will continue to be self-initializing and self-upgrading.
Localization has also been a highly requested feature, much to my surprise. I’m monolingual, and have very little experience with localization, so don’t expect too much. I do plan to use localizable resource files for all the application’s various text, and will support localized date, time, and number formats.