Anant.Public.Community

Knowledge Management and Collaboration Platform
Welcome to Anant.Public.Community Sign in | Join | Help
in
Home Blogs Forums Photos Files Roller

kono

  • A taste of our style. : Progress on Rainbow

    Over the last week, I have been giving a good portion of my time to the Rainbow Project. With the help of others in the Rainbow Team, Eric and I have started to make positive improvements to the organization and the software. (Links: Eric's Rainbow Blog, Rahul's Rainbow Blog)

    As Project Manager and Admin, I have been working to create a big picture of where we are and where we are going. Right now the proposed teams are in the process of forming as we are still in the initial recruiting phase to find the right members for each. Five core teams will be needed to carry out specific functions. In order to compete with commercial software, I am organizing this team as if it were a commercial organization. Read More about our new Team Structure

    A different customer centric site strategy has been proposed as well. All Rainbow Sites will be redesigned and re-architected to serve the customer's needs. The main site will be broken up into three separate sites. One to convince prospective customers to use our software and provide a launch pad to our other sites, one to cater to the information needs for existing customers, and another to be completely focused on support. Read More about the new Sites

    I am going to be imposing very strict standards in all of our efforts such as design and architecture. I tend to know what's good in design in architecture, but I'm going to let the designers and architects come up with their plans of actions. Read More about Design Guidelines

    As far as development goes, I am employing what I learned at Merrill Lynch and Independence Air to produce software. We are utilizing a mixture of normal open source grass roots development with a more formal system. Each developer will get their own sandbox to work with the code. As their functionality becomes real and works in their environment, Architects will approve these changes to go into DEVINT environment. After this, the team goes through a process to integrate, test, and release the product. Read More about our Production Methods

    If you are interested in where Rainbow is going, I suggest you start looking at the Rainbow Community Site. We are constantly blogging about what we are working on.
  • How to Deploy Rainbow

    Rainbow is a pain in the neck to install compared to CommunityServer.org. But it's not that bad.

    There are a few steps involved that I've been doing for a while. I've sent them a few ideas on how to improve it so that they can be easier to install.

    1. Download the Rainbow2006Release.ZIP
    Go to http://www.rainbowportal.net and click Download.

    2. Extract and Install Code
    Go to your Inetpub directory. Normally c:\Inetpub\Wwwroot\ and unzip Rainbow2006Release.ZIP. After Unzipping, I usually rename the main folder to something else like "site" or "clients" so that I can have multiple installations if I want them.

    3. Create your DataStore
    Create a MSSQL Database and a login which has DBO permissions on it. Ask a DBA to help you, if you don't know how to do this.

    4. Connect the DataStore in the code.
    In the web.config, find and edit the connection string to point to the DataStore you created.

    5. Create Application
    In IIS, go to your Default Website Root and right click on your Rainbow folder. Click on Properties. Click on "Create Application." Click Ok.

    6. Ensure Corrent Permissions are Set
    Make sure that that the ASPNET worker process has permissions to write to rb_logs and the Portals directory.

    Go to http://localhost/site/ . You should be greeted with an Install Page which you can click continue until your site's DataStore is initialized. If this fails, you will need assistance.

    Rahul
  • How to Improve Portal Software

    I've been observing a lot of software and I know that there are thousands of ways to improve them. I would like to start with Open Source software specially because there are lots of hard working open source developers who make decent software but need assistance on making it marketable.

    Open Source software fails because they aren't able to compete in the market place because of either a lack of resources or because a lack of adoption.

    For the purpose of analysis, I will focus on and evaluate Rainbow and DotNetNuke and post my findings. I have used past DNN releases and have been consistently using Rainbow for a while. Don't expect a weighted observation towards either because my improvements most likely will apply to both.

    Application construction is changing for businesses. Software cannot be made like it was made a decade ago. Technology is consistently improving from many different vendors and a little of each can be used to make great solutions.

    Portals and such have been cropping up in use for a long time. I saw the beginnings around the time that portals.com ( I think thats what it was called ) plunged down in stock. It's ironic that I'm talking about them because I see the usage of portals/cms systems almost everywhere that real business is conducted.

    The internet empowers business people to do just more than what they do , but also to do business together with others over the internet. Yahoo, one of the major portals out there right now serves millions of users. There are people talking on Yahoo Groups. There are people doing business on there. There are even people posting their blogs and family pictures using Flikr. ( Wow what a great product!).

    Small businesses can now start putting up interesting storefronts and client areas which they wouldn't have been able to do with anything else. Dreamweaver? That's an advanced user tool. FrontPage? Are you kidding me? My friend Charles used it just to edit files because of its' ability to open a "web". I agree, that was a nice way to edit files remotely.

    With Rainbow and DNN, you can do that without have ANY software on your machine. The software runs on the internet. Administrators install it (or your hosting company is cool and has an installer), and you are set to go.

    It's too bad that people who build these solutions have to spend so much time creating pages, adding modules manually everytime. This process needs to be revised. Module development also takes way too long. It is not efficient. So many of the same steps have to be done over and over again. Code generators help a little, but they aren't exactly what I want to see while developing.

    Module Development

    The module development process involves designing a table in the database, creating providers, creating interfaces, hooking up events. UGH. Well I can deal with this now because I've been dealing with it for a while. I think there are better ways to do this.

    Portal Construction The portal construction process is less than fun. You have to do a thousand clicks before you actually have anything tangible. The people doing business don't want to be creating portals, they want to their jobs. The people who want to be constructing portals should have better tools to serve the business community. Portal Deployment Once you build a Portal, its just sitting there. You have to back up the database, send it over, restore the database, and then configure the application. ( You also have to copy the files over). Installation should be a lot easier than it is. GUYS, COME ON! CommunityServer.org's installation is SO easy compared to DNN and Rainbow.

    Those are probably the three main things I see that need improvement for the system administrators, developers, and portal constructors.

    Since so many different types of end users can use the software, how they interact with the software from their end has to fit what their goals are. Currently, alot of the Modules I see are glorified database edit screens with some nifty intertwined business logic or validation. I know the difficulties from the backend, and I'll have to think before I post about how to improve the interface. Rahul
  • Using Rainbow for Content Management

    Rainbow Portal can be used for many different uses. It comes with about 40 standard modules which can let you or your business build and manage a site from a web interface.

    Why use Rainbow for managing your site? There are many reasons, but here are a few.

    Open Source
    This means that you can hire outside developers to develop extensions as you need them. (Like Us)

    Great Template Engine
    They have one of the better template systems currently in use. This lets your web designer use his current skill set of HTML and CSS to build a look and feel for your site that can be applied to all your pages.

    Extensability
    Rainbow modules can be created by anyone who knows SQL Server and ASP.NET. Sometimes you may need to have specialized content structures and this extensability lets you do that easily.

    Security
    If you want to have a section of your site that is just for certain people, such as Clients or Employees, that can be taken care of using the built in security and permissions system.


    A standard installation of Rainbow starts out with one Page and an Administration section. The setup is currently a little complicated, but its nothing that an experienced system administrator can't figure out. Actually its' not that hard, you just have to do the right things in order to get it up and running. I would suggest getting someone to help you do this if you are just a business person or an individual.

    Pages
    Rainbow Sites are made up of Pages which can have SubPages. Pages are like containers. They keep all your content in one of three panes. Although all pages share the default template, you can specify a different template for a special page.

    Panes ( Left , Center, Right )
    You have three panes where you can put just about anything. I think they are working on more, but not many sites need more panes than that. I know, I've built quite a lot of them. The panes don't have to be positioned left to right and can be placed anywhere in any shape using CSS.

    Modules
    Each Page can have many modules in one of the aforementioned panes. There are many different modules that come packaged with Rainbow. We've made one called the Amazon Books Control. We'll release a new version once we get our pending work done.

    Once you've logged in, you can go to the Page Manager under Administration and start Adding pages. Once you've added a page, you can click "Edit This Page" and add modules of your choice on the pane of your choice.
    There aren't too many things you need to learn as an End User that manages content. Here are a few actions.
    • Add A Page
    • Move a Page
    • Protect a Page
    • Add Modules to a Page
    • Move Modules on a page.
    • Move Modules from Page to Page.
    • Delete Modules
    • Recover Deleted Modules
    • Add Content to a Module
    • Move Content from Module to Module.
    Some Useful Modules
    The most useful module for a content site made in Rainbow would have to be the "HTML Document" module. After placing this module on your site, you can insert any HTML content that you would normally put on your site using outdated tools like DreamWeaver or FrontPage. I would say you should still use tools like that to do your layout, but for content edits, its just way too much overhead and inefficient.
    Another very useful module is the Enhanced HTML Module. This module lets you publish multipage HTML documents in multiple languages. This is great if you are writing a multipage article that needs to be split into sections.
    Some other modules that you can find on the system are Articles, Announcements, FAQs, and Events to name a few. Once you've been introduced to Rainbow it's hard not to use it for your content needs. More to come on using on using Rainbow for Content Management.
  • KonoTree : The Tree of Knowledge

    KonoTree started as one of the research efforts initiated at Anant Systems a couple of years ago. We were on a quest to focus our resources into an area of expertise. In order to decide where to focus, I decided to have our team research and look into a few areas of interest.

    The release of KonoTree is a result of many people's effort. Our research has not only empowered us with the knowledge of various Content Management Systems and Portals, it has let us understand the problems of current systems which is now fueling our current projects.

    We will be posting articles here about subjects related to CMS and Portals.

  • Portals

    Yeah so I have been assigned to write about : 

    [21:24] Rahul: what is a portal
    [21:24] Rahul: how to use rainbow as a cms
    [21:24] Rahul: how to use rainbow as a portal

    [21:25] Ramseur: i can take the bottom 3

     

         That being said.  I want to at first do some research and give my audience many blog entries on those three topics.  I will first describe portals and their uses, best practices.  I will give links[ my speacialty] as sources that back me up and introduce Rainbow Portal as the clear front runner on the .NET Framework.   You may say ' what about DNN'.  Well I say it blows.  The UI looks ugly and its also in VB.  Eventhough I have mad respect for the keyword languages ( not down for memorizing a whole bunch of keywords when you should man up and learn syntax ), C# just comes to me better as a C++ background developer. 

         Rainbow is a great system.  Its just like any other open source application; it has quirks.  However, these quirks can be solved by smart developers and numerous help resources.  There are many groups, rainbow portal on yahoo groups is a good one.  Rainbow portal is ok to extend but hey its better than DNN.  I didnt even begin to try to understand how to extend that ugly UI.  With rainbow, I can put any UI I want and make it a CMS or Portal system.  With the single file module, I can paste clear aspx right into the portal.  I can also by adding private assembly modules that are simply user controls.  I however, like some cool functionality and prefer the full application method.  My future for rainbow includes what I like to call an application tab.  Rainbow has tabs that it uses to represent pages.  Why not different types of tabs that do common scenearios?  Like um the application tab.  Translation, I can stick any application with any functionality right smack dab into rainbow and it works with rainbow's hooks on the outside.  That I will give rainbow.  They have good hooks.  Its really easy to see if a user is in a role or authenticated.  You can then edit the page settings and restrict by role.  If they arent in the role, they cant see nothing!!  Many applications is the first step of creating portals in rainbow.

     

    Cheers,

     

This Blog

Post Calendar

<March 2010>
SuMoTuWeThFrSa
28123456
78910111213
14151617181920
21222324252627
28293031123
45678910

Syndication

Powered by Community Server, by Telligent Systems