RE: [Rainbowportal-devel] The Tab/Page rename - only in UI?

[William F. <WF...@im...>]

I didn't mean to say that only I should be working on the core, just
that before you go off and do a bunch of stuff you should tell me about
it because I may have already done it or it may be irrelevant after my
changes are done.  Did you check out the word doc in that yahoo group I
made yesterday?

First off, Tab is gone in my version when it is done except where it may
refer to menu items for pages.  Second, Portal in my version is a
portal.  Site in my version is the global variable class that holds all
the Portals.

The security framework is being completely gutted and redesigned.  I am
currently trying to decide what to do with it and I have some ideas, but
I need a good user/role manager class first.  The ASPNET backported one
is very limited in its current form and the enterprise library one is
just a little better.  Maybe we need to write our own...  I will need
help with this, but it must fit into my new object model.

As to the cookie thing, that is not a core issue any longer.  It is
strictly the web layer's problem and I haven't messed with that much
except to chop out core pieces from it.

In order to do the DAL changes it became obvious that the entire core
needed to be redone because it was all 2 tier and data code was mixed in
everywhere it shouldn't have been.

I think we need to regroup and work out the specs first, then go
continue the reorganization because if we don't we will just trample
each others' work.  I am basically creating a new core using snippets
from the old core as a guide/starting point.  I created several new
classes and am still rearranging things but need help doing it.  Several
people have volunteered but we need to get everyone on the same page so
that it will be easier to bring others into the process.

I'm attaching a recent version of the design specification.  I had
started out with Gentle.NET as the data implementation layer and we may
consider keeping it for modules but I want to move us into using iBatis
for the core and related data implementation.

I am using enterprise library configuration block to split the config
file up into some new ones to make things easier for newbies to read.

Also, I haven't got the entire plan on the doc yet but take a look, feel
free to edit/add to it and send it back to me.  I will merge in any
ideas you have.  This file is to become the design spec for developers
who want to work with and help build Rainbow.  I like the idea of having
everybody able to contribute to it, but I don't like confluence for this
because it slows me down.

As it sits now, some projects in the new solution work and some don't
compile.  The more help I can get from those of you who understand what
I'm doing the better.  :)

To get the new 1.6 version, checkout all the Extensions projects, and
checkout the Rainbow_1_6 tag/branch of the CVSROOT/Rainbow folder.  The
solution file is in there.  If you need any 3rd party stuff to get it to
load let me know and I'll send it or tell you where to get it.  :)

Thanks,

Bill

-----Original Message-----
From: rai...@li...
[mailto:rai...@li...] On Behalf Of
jon...@jo...
Sent: Monday, March 28, 2005 3:01 AM
To: rai...@li...
Subject: RE: [Rainbowportal-devel] The Tab/Page rename - only in UI?

OK,

So then... I can split the page manager from my vurrent version, and
included as module for current
CVS verison... using TabSettings, TabItem, TabsDB,=20
and then the core would stay the same as yours.

What about bug fixing in core?
What about changes in logic before you comepltly write the core over
again.. which you have been
doing.? I think there needs to be a way to map out the work then,
becuase if over the next few
months a bunch of use are working on exclusivly modules/resources/and
usability... while you are
solely working on the core. I think we need to know certain things are
going in there, from the
start and not things that need to be added in later, as they would be to
the current core.
I am willing to cancel out all the Tab->page stuff i did, and convert
PageManager to work with
current working core. But to ask people to avoid fixing bugs or wroking
on core, we need to know
then that certain things will be done as well in the rewrite you are
doing, ebcause if not the
learning curve on implementing these changes later, means all of us have
to slow down substantially
to familiarize ourselves with the=20
1.6 core.
By changes I would like to see you are saying will be in 1.6 before I
can promise not dedicating
time to them are then....
1) As far as code base, there is no more "Tab" Must be "Page", "PageID",
"ParentPage".....etc...
2) Preferably "Portal" becomes "Site" as well.... I still say portal is
subsect of sites, if you
want to call your site a portal, than do so, but not all peoples of
Rainbow instance are portals.
Lots of people have small sites, a products shop, wahtever.. these are
not portals, they are sites.
3) Some sort of enhancments to the Roles / and permissions way things
are in rainbow. There are
lots of discussion on this in the forums. ( Application Admin, Page
Admin )
4) Cookie Problem in multiple sites on same domain
domain.com/default.aspx?alias=3D1 gets mixed up
cookie with domain.com/default.aspx?alias=3D2

If your work is however more geared to the datalayer as was my
understanding till now... and not an
entire core makeover, then why would any of the core makeover being
done, effect your updates to
all the DAL areas?
Also, are you working on this entire core update by yoruself, or are
others in the dev process with
you? Maybe I misunderstood from my previous messeeges with you, about
the level of the 1.6 change.
Perhaps this is a common misconception, since it seems I am not the only
one who was getting into
these sorts of changes at this time.=20
Working on the Wiki module alone means chanegs to DB layer, and probaly
a bunch of stuff chucked
around the core somewhere...=20

I guess if you are saying that I (we) should not work on certain areas,
or do certain things, then
ALL of us need a better understanding of what it is you are doing, what
stage in development you
are at, how much code you have actually been through, estimates as to
when you are looking to have
this ready, because even at best... if you change the whole core, I am
sure we will need to arrange
a fair ammount of testing time and rounds.


I am sorry you felt like I was wasting yoru time, that was the farthest
from my intentions. The
issue lies in probably a misunderstanding of where you are at and what
you where doing. If
anything, I thought that cleaning up core and code was helping you and
saving work later. So please
don't be mad... let's get on the same page instead.

- Jonathan


----- Original Message -----
From: William Forney
To:  <rai...@li...>
Sent: Mon, 28 Mar 2005 02:34:10 -0800
Subject: RE: [Rainbowportal-devel] The Tab/Page rename - only in UI?

Again, I am already working on this stuff, and have been since December.
Please coordinate with me or we are wasting each others' time.  And I
don't have time to waste on rainbow if my contributions are going to be
ignored.

-----Original Message-----
From: rai...@li...
[mailto:rai...@li...] On Behalf Of
Jonathan Minond
Sent: Monday, March 28, 2005 12:31 AM
To: rai...@li...
Subject: RE: [Rainbowportal-devel] The Tab/Page rename - only in UI?

Also,

Since there is a stable release that was just made, and a lot of people
seem
to be actively working on some big tasks, 1.6, wiki, resources, and some
other stuff.

It seems to me like a good time to start getting rid of and fixing some
of
the mistakes or missing logic in rainbow, to make preparation for this
other
enhancements, as well as improve rainbow a lot.
For example=20
	Tab->Page=20
	Cleaning up and brining in new resource files
	Correcting bug of misuse use by cookies, when two portals like
in
same domain
	Implementing some extra system roles??? I may be dreaming on
this
one but what about SysAdmin who goes above "admins", admins to me are
site
admins, should not have multi-portal admin functionality unless portals
share one user base. PageAdmin - let you assign users who get "Edit this
page" but not site admin pages.
	Password security mechanism... imagine setting in web.config, or
site settings table that would allow admins to choose weather to store
passwords as plain text, or hash them.
	Module cleanup/enhancements/and new mods ( there are people
actively
working on blog/wiki/smoothing YAF integration )
	Closing bugs on Jira

Imagine if as a team, we all can dedicate 2 or three months to this. Not
full time, everyone has jobs, but if several people took testing rounds
seriously, and worked on getting some of these tasks done in that time.
We
could have Rainbow2005 SP1 in a matter of months, that would work well,
and
up the RB level a lot.

- Jonathan



-----Original Message-----
From: rai...@li...
[mailto:rai...@li...] On Behalf Of
Jakob
Hansen
Sent: Monday, March 28, 2005 9:13 AM
To: rai...@li...
Subject: [Rainbowportal-devel] The Tab/Page rename - only in UI?

I had a second thourght about the global change of "Tab" to "Page". I
fully=20
agree that it is a good thing and we should do it. But I strongly belive

that the changes in the code will result in many bugs and make Rb
unstable.

So I suggest we only do the change in UI! If we choose to go on with
rename=20
Jonathan did we need people to test: About the new code he says
"Basicaly=20
the entire core code was hit one way or another."

Jonathan: I know that you used countless hours to do the overall
rename... I

should have started this discussion much earlier...

Jakob


>From: "Jonathan Minond" <jon...@jo...>
>Reply-To: rai...@li...
>To: <rai...@li...>
>Subject: [Rainbowportal-devel] Pages
>Date: Sat, 26 Mar 2005 03:01:39 +0200
>
>Emmm....
>
>Ok, So, I pretty much had the page manager done, until I decided I
would do
>us all a favor and go on the hunt of changing tab -> page.
>I have done I would say about 95% of the code so far, I am not doing
any DB
>changes though. I should be done sometime tomorrow or Sunday with a
working
>version of Rainbow with this change... I only 10 minutes ago, got my
portal
>to run again. Apparently I dove into this a little foolishly at first,
but
>luckily was able to debug my way out of it.
>I am a little embarrassed to say, I do not feel comfortable taking
>responsibility of the DB changes of actually renaming the tables,
sprocs,
>and then dealing with all the data that would reside in module, portal
and
>page settings. I posted message to source forge, maybe ill find a
volunteer
>for this in the future.
>But by sometime tomorrow or mid Sunday, what I will give you is.
>Rainbow, improved discussion module that is on my site, Page Manager,
some
>cleaned up HTML here or there. Means you cant just take the page
maanger=20
>and
>swap into any current app... you need the whole app and can put on top
of
>current db.
>And as far as code, there is no more "Tab" it is now "Page"
>Meaning TabDB -> PageDB
>AddTab -> AddPage
>Etc... Etc...
>Internally, however, PageDB deals with the same sprocs and fields that=20
>TabDB
>did.
>The over all change also included correcting Zen Engine in some places,
not
>all. Meaning this task is really only partially complete. But good
enough
>for me to close It up and get some rounds of testing with you, me and
some
>others going. The Page Manager will make it all worth while though. So
>basically its strictly application change... 0 DB change.
>The final missing step, that I already found a volunteer for from the
dev
>list, is the resource files. Need to add new keys for page manager, as
well
>as hunt down instances of "Tab" and change to "Page" mainly English
>resource, I don't know about the other ones. The resources are just
>something I am not so familiar with, and to swamped to learn about now.
>
>I don't think this should go straight to csv. It hink It should go to a
few
>people as a zip that I will provide, and need to get tested because of
the
>ammoung of code changes all at once. Basicaly the entire core code was
hit
>one way or another.
>
>People who will want to help in testing phase please contact me
directly,
>since I will not put in csv directly.
>
>- Jonathan
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real
users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
>_______________________________________________
>Rainbowportal-devel mailing list
>Rai...@li...
>https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Rainbowportal-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Rainbowportal-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel






-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id=14396&opick
_______________________________________________
Rainbowportal-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel