Things that must be done prior to the first release:
figure out some documentation system for noting which environments support each function (getComputedStyle, etc.) check all links in source comments make sure every supported browser has a working iframe make sure that every browser supporting XMLHTTP or Load & Save works get Opera and Safari to load script dynamically figure out messy data loading issues: content-type http status Gecko problems with 'file:' urls re-use of an iframe error handling
The next release must have:
full widget set
Some futures for some undetermined time:
Library additions:
burst.web.Cookies burst.graphics.Vector (SVG and VML) burst.graphics.Image (various hacks for client-side bitmap image manipulation) burst.graphics.Map (client-side maps and GIS) burst.graphics.3D (opengl/vrml/java3d/etc.) burst.av.* (audio and video and SMIL) burst.Crypto burst.Math burst.collections.* (data structures like linked list etc.) burst.concurrent.* (when/if the runtime is multithreaded) burst.rpc.SOAP (using native SOAPCall when available) burst.webui.Forms (XForms/Web Forms/etc.) burst.webui.Data (data binding) burst.webui.Timing (measuring response time like http://www.research.ibm.com/arl/projects/papers/USITS.pdf ) burst.xml.XSLT (convenience utilities)
Library improvements:
burst.web.WindowEvent burst.web.DragDrop
mouse support, such as drag/drop, resize
keyboard support, including special support for tab, return, arrow, etc.
burst.Lang
perhaps pull out burst.StackTrace and integrate with burst.BurstError
burst.xml.XPath
when available, use native browser XPath
burst.xml.HtmlBox
fix for IE box model
Architectural:
some way to package an application some way to package a component complete with any css, html, images, and script (XBL, etc.)
Tools:
JsLink - static analysis to determine dependencies, and extract only code actually needed.
Apps:
photo library slide show email