Road Map Home » Kartris ASP.NET Ecommerce Software » Kartris suggestions https://forum.kartris.com/Topic1228.aspx

Print Topic | Close Window

By jenkins - Fri 19 Aug 2011 Hi there, Is there a roadmap of whats going to be happening with Kartris and to see whats being developed for the new edition? Thanks Dave By Paul - Sat 20 Aug 2011 I will try to get something more formal on the site. As a quick guide to 1.4, which is in production: - ASP.NET 4.0 - graphical charts in back end for some stat data previously only available as tables (using the charting controls in ASP.NET 4.0) - tax system calculations handled from algorithms in XML config files, so support for specific jurisdictions can be more easily added in future; some extra fields to support Canadian tax (which has regional and national taxes) - simplification of setting up tax for a store via a wizard page in the back end - product and version level 'object config' settings. This enables us to have things currently set globally set at product or version level. For example, some items like cloth might be sold in metres, and you want to sell in 0.05m increments, allowing someone to add 1.55m to the cart. But most items you want to sell in increments of 1. Some other items you might want to sell in increments of 50 (e.g. nails or screws). - numerous other minor improvements and enhancements We did also have mobile interface support, but this will probably only come in a later version now. By Neil - Fri 2 Sep 2011 We did also have mobile interface support, but this will probably only come in a later version now. This is interesting, would love to see this. I assume this would be done through just css? A surprisingly high number of visitors are using mobile interfaces. By Paul - Fri 2 Sep 2011 CSS can get us so far - thinner pages, and so on. An alternative template master helps us hide nav menus and other things we don't really have room for on mobile pages. But some parts of Kartris don't scale well to a small page, such as the tabbed dialogue on the product page, if there are reviews, attributes, quantity discounts etc. Also checkout. Ideally for mobile devices we'd have simpler pages and may need to rethink areas such as tabbed dialogs. This issue is whether we do this by modifying existing controls such as the basket, product view, etc. to render differently on mobile devices, or whether we end up building special mobile controls and pages. There are pros and cons of both approaches: New mobile-only controls will be simpler in themselves, but duplicate code elsewhere, so fixes or changes in one place may need to be made separately for the mobile version. Modifying existing pages and controls to hide or change certain areas on mobile devices will make those controls more complex. It's something that is definitely on the radar, but want to make sure we do it properly and don't complicate or mess up the code elsewhere to do this.