ahhh.

I decided to inprove my page manager and brook my web part admin section.

oh well it needed to be done

the previous api didn't support long urls, the new api does.

now I just need to find the bug.... where oh where did I put that bug.... ahhh

Update

The project has been put on hold while I research BlogEngine.net and get my website to where I'd like to have it then I'll come back to application development.

Original

It's taking longer that I thought to get out the first release. ahhh.

 I've got the whole day tomorrow, hopefully I'll upload it.

Today I was playing around and decided to upload the TFRPortal to some domain names I have, just to have a place for people to look at it live.

Take a look at TechsForRent.com for a live version of the TFRPortal.

Today I got the project working properly with FireFox and I am 98% Safari compatible.

You can download the code here (3.65 mb).

The issues where element.firstChild and element.nextSibling they where resolved using the following functions.

More...

Last night I figured I'd better do some Fire Fox testing other wise I'd end up with a night mare full of code rewriting and guess what, I had to do some code rewriting not a lot so fare but I didn't expect Fire Fox to have issues with element.firstChild so I used it while developing the WebPartExtender and the WebPartZoneExtender. Most of my professional work all targets IE so I expected firstChild to work it works in IE, very frustrating but hey who writes perfect code anyways.

Anyways I found a possible solution to the issue, you can read the post here.

I'm still testing to find the differences in the DOM between IE and Fire Fox. I'll post more about my findings later. I have a server that needs configuring, it should take too long but it does take me away from the project.

I resolved the issue with master pages I was using clientId instead of uniqueid

here is a screen shoot of a web part being moved to another zone

Click here to download to latest version

Today I figured I'd add some style to the portal and while do so I ran into a bug. This bug showes up when you put the controls in a master page. I'm working on fixing the issue now and should have a fix soon.

Here is a screenshoot of the current theme.

I debating on removing the post back when a WebPart is dropped to another zone or zone index inside the current zone. It’s not needed and there are advantages on both sides. To post or not to post, well I’m thinking about, I’ll have an answer soon.

Here is the first version of the TFRPortal, it is still in beta but I figured I'd upload it anyways.

What I have done is create css friendly web parts with drag and drop support. The task of creating drag and drop support with divs took longer that I had anticipated, I had the bulk of it done in a few hours just the last like 5% took a day in itself. I think in the long run having css friendly web parts will save me time when I get to themes.

References I used while developing this project. I also debugged the .net framework to view how the Microsoft web parts worked.

1. Tableless WebParts and WebPartZones
2. Drag and Drop like iGoogle with ASP.Net Ajax Toolkit
3. Build Google IG like Ajax Start Page in 7 days using ASP.NET Ajax and .NET 3.0

Download the code here (955.55 kb)

The code download contains one main dll called TFR.Web.dll. This component consits of the following custom controls and components.

1. PartChrome.vb
2. WebPartManager.vb
3. WebPartManagerBehavior.js
4. WebPartManagerExtender.vb
5. WebPartZone.vb
6. ZoneButton.vb
7. ZoneLinkButton.vb

More...

At the very least I believe all projects should have a simple document outlining the project features and requirements, as what is show below.

The fist development challenge we will take on will be about is creating a dynamic web site with the following feature requirements.