I don't think that ELB is causing problem to zen
client side, it can not cause problem to zen and css. Taking it out won't
fix your problem with zen and css. I do share the point
of Jonathon that carefully tuning up the html code of the module and
css settings will resolve the problem.
----- Original Message -----
Sent: Saturday, January 21, 2006 9:31
Subject: RE: [Rainbowportal-devel] Re:
Rainbowportal-devel digest, Vol 1 #1208 - 4 msgs
I have spent 100s of hours trying to get to the bottom of
the problems with themes with and without ZEN and CSS.
It appears all roads lead to ELB as the major
If you have time to identify where it is so that it can
be taken out then great. Possibly then we should see if there is a new version
of it that we can use.
Let me put it this way, ELB should never have been put in
without major testing.
I just loaded the HWMenudropdown layout and default theme
and the same problems occur with the admin pages as I was having with the zen
This is what really makes people wonder if Rainbow is
ever going to be serious.
I ask again to be patient with MagicAjax, there is no
magic in coding, just hard work. We must fix the major problems and get a
ASP.NET 2.0 version without the problems we have been having because of bad
I have decided that fixing Rainbow 2006 is impossible.
After a review of the problems, I have decided that it is a waste of
Therefore I would like to make an ASP.NET 2 version
without bugs and allows people to upgrade from Rainbow
Therefore we should be looking to fix the existing
problems, by either fixing or removing offending code. I request everyone look
to this please.
Its good to see the traffic on the dev list heat up. Manu and
I are in the process of reorganizing the Rainbow project. We are
compiling a solid roadmap and correcting it before displaying it to the
list. It includes a new site Design with Community Server [ hopefully
2.0 ] forums. I think most to all the issues in the current rainbow
version will be solved in 2.0. From my test its pretty solid in only
having warnings for obsolete code and having only a couple little
errors. Im going to start refactoring code and making small adjustments
on my test boxes but I have a fresh install. I am targeting this install
for an aqua release but would be willing to offer my help on getting just a
fresh 2.0 port on dev. I will check on the ELB because I definitly saw
it in one of the many versions of rainbow that I currently have. I will
check tonight when I go back to northern virginia if my 2.0 version contains
the ELB assembly and thus ELB. I dont mind ELB at all. Im just
saying if elb can be there why not magicajax? Its just a dll and a
web.config change. I am currently working with Manu also in getting
MagicAjax to work with the Rewrite Module and do a ajax hit with rewrite
instead of a post. Aqua is very fast and its hosted on my dev machine
with a network connection to SQL Server 2005 Enterprise. I am going to
test it with Caching turned on and do some benchmarks with Rainbow 2006
1.6 Sql Server 2000 ent VS Aqua Sql Server 2005 and release my