This Version:
Archived at: https://www.skybuilders.com/Action/Strategy.20001007143744.html
Requests
Version: 1227 | Series: 7056 Launch Plans (in Company > Launch.html)
September Here's our current game plan in terms of the next few weeks work (not necessarily in the order it will take place): ~ 1 week 0.90 stability/bug fixes ~ 4 weeks New feature: E-Commerce: Shopping Cart, Products Catalog, Accounts. Digital certificate/web Credit Card acceptance. This will let orgs (esp. us) sell (digital and physical) things over the web ~ 1 week New feature: Forms capability in Pages Module. This will let orgs gather info from members into db. ~ 1 week New feature: timeLines in-frame design, including new Ranger control ~ 1 week New feature: skyWriter redesign - streamline editing of pages ~ ? Misc smaller features: rationalize Tasks and PIM Possible reminders possible relating places & items/synchronizing events & reservations ~ ? 1.0 (or just under) stability/bug fixes ~ 8 weeks puts us in the first week in November. This should put us within spitting distance of commercial launch. A couple of weeks of beta testing from all of our deployments should put us at 1.0, where we actually start to be able to sell this thing over the web. High Priority Items: Eliminate reload in timeLines window (part of timeRanger rework) In any page that sets a global like whichPlaceID that also has a setting in the User's record in the DB, the DB setting should also be set. This was always meant to be heuristic - it isn't currently and so there is bad data clogging the db. Bug. Priority: High. In AdminEditSortPage - If a page is renamed with a longer name that contains the old name, it recurses, making longer and longer names, god over djinn, until it reaches the file name (or is it path) limit (255?). The bug is that the loop recurses - instead it should take a list in once, then operate on each file in the list, rather than checking and rechecking the file list and repeating the work on the same file(s) over and over. Bug. Priority: High. The NameOption setting in globals should override a personal setting of the same, which says what they would like to see in the interface. Admin should never be overridden. New feature. Priority: High.