1 / Enter control.
.Text's input control used freetextbox, it is OK, and later I joined fckeditor 2.0. In actual use, I feel that the performance of fckeditor is debatable, especially when editing a big text, it becomes very slow, and browsing the data. It is easy to die. And open speed / editing speed is not ideal. Look at those JavaScript know, especially because his toolbar and the synchronization problem of the selected text format, resulting in a large number of text paste ( Especially word text), the reaction speed is slow. Moreover, it is very doubt about whether the BLOG is really needed. I think, the most useful, may just be uploaded. Other, complete Can be removed.
2 / skin editor
.Text skin editor will always become a problem. Although I followed. ITEXT's masterpage and url Rewrite technology, but the simple extent of skin editing is always psychological guilty. But a person is limited, only first Do it, then change it again. In addition, the code of Asp.net is really a cow, I can support multiple ASCX files with a UserControl class, just the data source and display formats. It saves a lot of strength.
3 / Forum / Personal Album / Blog integration.
I have been working hard to integrate the forum / personal album / blog, just 17th to see the demo of Community Server Beta2, feeling a lot, there is not a lot of outstanding places. And because there is no source code, I don't know how the internal implementation is. From Scott On the post on the forum, the blog in CommunityServer lost a lot of features in .Text, I think some are very important, such as the support of Atom / Common API. It is very not worth it. The editor of the skin is still ascx The form is present. The style sheet is limited. I hope they can be perfect in the Final version.
