- Removal of Esperantus - this is 92% complete, the last things missing are the stuff that deals with regions like country and state... there is also one money thing i need to look into. What I did was make use of the new .NET 2.0 App_GlobalResources folder, and converted all the Esperantus stuff to 2.0 Localization and String retrieval. We might look into how to enhance performance if we want, as it is all encapsulated in one easy method GetString :-) Controls on pages can use the new 2.0 native text="<%$ Resources:Rainbow, AM_MODULELOCATION %>" I have done this in some modules, to prove it works, but for most, i made a quick helper class that added the Textkey property to all the native asp.net controls, so that all i did was replace tra:esperantus controls, with rbfwebui:controls rbfwebui = Rainbow.Framework.Web.UI .Controls ( It's only declared once in the web.config, so mode of the <%@ register ..... code for esperantus was removed as well, making the overall source size smaller.
- Rainbow core code separation - this is mostly done as far as version one, by that i mean we have a nice clean web project, and core code projects, the modules have been placed back in the web project for now, for the sake of making mass changes easier, as well as we want to clean out some modules, and consolidate others, and in any case, we had to separate which modules where core code necessary... etc.... blah blah.
- Use of Partial Classes - this is something I started doing in a few of the pages I am working on for a few reasons. I don't really know if partial classes change performance or anything, however they make the code pages a bunch shorter, so the source downloads will be quicker, also the pages are a little cleaner, and it goes a way in proving rainbow is officially .net 2.0 capable.
- Namespace preparation for API's - This will be a much longer process, but I have made an effort to begin introducing concepts in the code such as Rainbow.Framework, Rainbow.Framework.Web, Rainbow.Framework.Web.UI.Controls Rainbow.Framework.Services ( maybe this should be Rainbow.Framework.Web.Services )... who knows. and some other stuff.
- Updated IE7 Scripts to version 0.9
- Ability to "Publish" your site in any of the native .NET 2.0 forms, udpateable, non updateable, single page assemblies... I have only begin marginally testing what effect fully compiling rainbow has, so i don't know if i would say it's stable, but supposedly it should work, just like a regular site... ???
- New format for History file - History.xml , this is not fully complete, i am still working on the schema and am open to suggestions, but for Rainbow 2.0 and forward, i thought it would be nice to update the history, so we can make nice xslt's and post online... or make it easy to search and find relevant comments. I added a type attribute to the comments, so you can define things like bug, fix, enhancement, development, we can add more as they are needed / wanted, as well as grouping changes and stuff the text file made difficult. We could make a cool winform or web form to administer the change file... so we can make one online global repository change log, so people can always be updated about new things in the different codes, dev, stage, prod. Imagine we have on community site or something, and xml module that filters out only the latest dev comments in the history file, or something like that.
- As a first run, I converted Service Items list to an ASP:Grid view control, with AJAX paging and sorting :-) I also did it on Tasks, but I was not able to add Client Side events there and I wasn't going to waste time to fix it now.. but to show you the new Tasks Grid and ServiceItemsGrid look like this.:
1: <asp:gridview id="myDataGrid" runat="server" allowpaging="False" allowsorting="True"
2: alternatingrowstyle-cssclass="Grid_AlternatingItem" autogeneratecolumns="False"
3: borderwidth="0" headerstyle-cssclass="Grid_Header" rowstyle-cssclass="Grid_Item"
4: width="100%">
- When working on the web project, in pages that are partial classes, maybe regular ones too... not sure... you can make changes in the code behind, not build, just go refresh your page in localhost, and the changes are there... so you can trap errors, or see design changes immediately without waiting for a site build or solution build.
- Added some comments in a few places, there are allot missing , but everyone should try to add some when they can, it only takes a few moments, and we will be able to generate great code documentation that way, just like MSDN
|