Welcome to Rainbow Portal Community Sign in | Join | Help

Rainbow.Framwork Spec Blog

I wanted to explain a bit more about Rainbow.Framework.

Rainbow.Framework is step one in pushing the application toward clean and seperate api's.

What we will be left with is something along these lines

  • Rainbow.Framework
  • Rainbow.Framework.Extensions
  • Rainbow.Web
  • Rainbow.Web.Modules

Rainbow.Framework will then work it's way farther, possibly joining with several of the extensions, or replacing them. The framework will eventually part into routes such as these, not nessesarily in this convention or order, but more or less... they will end up somwhere along the lines.

  • Rainbow.Web
  • Rainbow.Web.Modules (Smart modules??? mobile devices, is this easier in 2.0? )

 

  • Rainwbow.Framework.Datastore
    (MSSQL,  XML, MySQL, Oracle)
  • Rainbow.Framework.DAL
  • Rainbow.Framework.Security
    • Rainbow.Framework.Security.Forms
    • Rainbow.Framework.Security.AD
    • Rainbow.Framework.Security.Windows
    • Rainbow.Framework.Security.Passport
  • Rainbow.Framework.Web
    • Rainbow.Framework.Web.UI
      • Rainbow.Framework.Web.UI.WebControls
      • Rainbow.Framework.Web.UI.MobileControls
  • Rainbow.Framework.Helpers
    • Rainbow.Framework.Helpers.Javascript
    • Rainbow.Framework.Helpers.XSL
    • Rainbow.Framework.Helpers.FileSystem
  • Rainbow.Framework.Application
    • Rainbow.Framework.Application.Portal(Site)
      • Rainbow.Framework.Application.Portal.Page
    • Rainbow.Framework.Application.User
    • Rainbow.Framework.Application.Notification
    • Rainbow.Framework.Application.Audit
  • Rainbow.Framework.Membersip(Profiles)
  • Rainbow.Framework.Content
    • Rainbow.Framework.Content.ContentItem
    • Rainbow.Framework.Content.Permissions
    • Rainbow.Framework.Content.Utilities
      • Rainbow.Framework.Content.Utilities.NewsFeed
      • Rainbow.Framework.Content.Utilities.Export
        • Rainbow.Framework.Content.Utilities.Export.Excel
        • Rainbow.Framework.Content.Utilities.Export.CSV
        • Rainbow.Framework.Content.Utilities.Export.XML
  • Rainbow.Framework.Content.Categories
    ( This is a discussion going on here )
  • Rainbow.Framework.Messaging
  • Rainbow.Framework.Installer
    (This is a concept thought up and discussed somewhat on confluenct... but can be expanded and developed utilizing 2.0, deployment featurs, and application updaters perhaps... basically, Installer would be able to install themes, layout (master pages), and modules at the application and portal levels. )

 

Rainwbow.Framework.Datastore
I will be updating this section, so check back periodically

Rainbow.Framework.DAL
I will be updating this section, so check back periodically

Rainbow.Framework.Application
I will be updating this section, so check back periodically

Rainbow.Framework.Content
I will be updating this section, so check back periodically

Rainbow.Framework.Content.Categories
I will be updating this section, so check back periodically

Rainbow.Framwork.Messaging
I will be updating this section, so check back periodically

Rainbow.Framework.Installer
I will be updating this section, so check back periodically

Keep in mind this is a long process, that will involve a few breaking changes possibly in my opinion, major versions, for example at some point mking a clean move to 2.0 master/skinning/themes will probably unless a viable solution is crafted, break old themes (I am working on an idea where zen themes could be upgraded to master pages, but not classic). Also, Content API will be able to upgrade most but not all, and not custom modules. their code would porbably need to be upgraded, unless old modules could be wrapped somehow. which brings us to Rainbow.Framework.Wrappers... wrappers for sharepoint modules, acsx files, how about any .net control?? is it possible?

Ok, it's time for me to go to bed, I hope I explained a little more about my last post on Rainbow.Framework (which is moving along quite nicely).

Published martedì 14 febbraio 2006 6.55 by Jonathan

Comments

# re: Elaborating on framework

martedì 14 febbraio 2006 21.51 by anantatman
John, It looks like you have an awesome grasp of the framework. Do you have a delivery timeline for this?

Rahul

# re: Elaborating on framework

martedì 14 febbraio 2006 22.06 by Jonathan
I am estimiating 2-3 weeks to deliver (With luck sooner, without luck slower )
Rainbow.Framework
Rainbow.Web ( exact copy of today, minus anything moved to Framwork )
Rainbow.Modules ( pretty much is what it is today )

In doing so I am also getting rid of some of the extremly outdated code or dead comments. I know this is not very accepted historically in rainbow, but if people want credit, that's what ahistory and comments area is for... i am tired of scrolling for hours thorgh comments of dead code. By dead i mean something that is dead for 2 or more versiosn.

# re: Rainbow.Framwork Spec Blog

mercoledì 15 febbraio 2006 3.46 by Jonathan
Why does Community Server have to mess up my formating for html? DAMN THEM!!

# re: Rainbow.Framwork Spec Blog

mercoledì 15 febbraio 2006 12.05 by ramseur
Add an LDAP in your authentication types. And hey CS 2.0 official release is soon dont fret.

# re: Rainbow.Framwork Spec Blog

mercoledì 15 febbraio 2006 12.06 by ramseur
We need to make a framework for Request for post and one for Ajax. Please find a fit for these two features. Framework.blah.Ajax...

# re: Rainbow.Framwork Spec Blog

mercoledì 15 febbraio 2006 12.55 by Jonathan
I am not sure what you mean by fraemwork for post and one for ajax..... we only want one framework i believe? and first one wont have ajax nessesarily.
Anonymous comments are disabled