Where is phase one going....?
Ok, since I bet everyone is curious as to what I am up to now....I thought I would give a sneak preview.
There is a new project, Rainbow.Framework.Web, most of the web ui stuff, and elements from framework are being moved to there, allowing a cleaner more basic core framework project... i will probably rmeove framework, and only have
- Rainbow.Framework. Core
- Rainbow.Framework.Web
- Rainbow.Framework.Web.UI.WebControls
- Rainbow.Framework.Windows (This one is future concept)
This will be the final refactoring in phase one, that doesn't mean it will be the final core changes, but it will be the final major refacotring, which causes interface change, and breaking changes in the modules. These are the things, that I do for all of the modules currently within my solution.
By the way, if someone want's to help me out, the google search module is aparantly not in the solution, so if someone wants to find it from their old solution, put in solution, remove esperantus, convert to partial class, and commit... that would be great :-)
I have added a bit of linking in some of the core code coments as in referneces within the namespaces... so for example secure page links you to page... things like that. It's cool, and when I commit, as always, I will shortly after update the codedocs site as a reference for anyone working on the solution. I hope to join these changes with mourdik's commit's on testing, and ramseur's work on xhtml. Hopefully both will continue to smooth out all the edges, and other people are continually joining the efforts in cleaning the web project modules, missing events.
Major things that we could use some volunteers for:
- In module settings, there are messages for missing keys, these needed to be added to the default resource at least, and hopefully soon localized into all the other resource files.
- Country / States missing still a major issue, the countries.xml holds all the info, and the code is in the esperantus project.... it jsut needs to be converted to rainbow framework logic, updated to 2.0 and hopefully using some cool stuff like generics for the lists... or soemthing cool, whoever works on it... you have free rieghn, just make it work :-) and put it in namespace Rainbow.Framework.Localization or something logical that you think. You should use ghostdoc to help you automate the documentation of your code, it does some cool stuff.
- Events that where lost because of partial classes, need to be returned, however in 2.0 we shoul not use InitializeComponent, so that method shohuld be removed, all events should be attached in the OnInit Mehtod, also if events are devlared in the page, they should be moved to code behind oninit, it leads to better performance, cleaner html code, and nicer overall expereince for the coders. Events are for code, not html, at least that's my opinion.
- Maybe a fe other things people find.
- Content needs to be added to www.rainbowbeta.com , anyone who registers, if you give me your user id, i can give you permission to create and edit content. We really need people to update beta.com and www.rainbowportal.net (Yannik has resently updated the module demo section by the way adding m-z).
In the next part of phase 1, I am going to look into replacing the page logging monitoring method with an implementation of an event in the native 2.0 health monitoring system. I am hoping that this is a threaded call, that will remove the page hit time for a page, especially once monitoring table has become very large. (Even thoguh I think this performance hit was improved by manu fixing an index problem in the table perhaps). I also want to convert to monitoring logs view to a paged gridview, becuase that grid takes forever once your log count becomes large.The charts are cool, but could be updated, I won't be doing that thoguh, as we have more important issues (mentioned above) to take care of.