Thursday, December 23, 2010

DreamWeaver 3: how to publish (1999)

Here's a tutorial I had written back in 1999 when managing web-sites was a big thing and Dreamweaver was the most advanced tool on the market

 Go to Sites>Define Sites

You will see this window

Click on New


Fill it out as follows


Now after you fill out the Local Info. Fill out the Web Server Info



Good. Now fill out the Check-in Check out window info


Site map layout is next



Home Page: enter your own path to the index.html that lives on your hard drive. (in the above picture I store it in a a folder called which is in a folder called www which is under a folder called MyFolder in C drive). Give your own path or browse to it.


Next few settings are simple



Click OK and Done. You can connect and “checkout” the site. From Dreamweaver.





Monday, December 6, 2010

Dream Act will Support Small Business and Entitlements

In the next two decades America will see a structural shift and displacement of its demographics that it hasn't experienced in the past 50 years. Baby Boomers will retire and depend heavily on entitlements like Medicare and Social Security. A significantly contracted workforce will threaten the stability of the United States government and it's global economic power.
Fast Forward 2010: Immigrants Have a Dream

Structural adaptation, and realignment is going to be desperately needed starting 2011.

The Dream Act, that is currently stalled in Congress, will boost small businesses and the American economy over the next decade. The bill indirectly provides necessary relief to citizens and retirees. Here's why: as children of immigrants in schools and colleges across America graduate - a permanent residence status ("Green Card") will legally permitted them to start small businesses all over. This educated and skilled workforce will provide, fill and generate jobs at all scales of businesses and support entitlements via taxation. However, a vast majority of the American population feels threatened by a misguided notion that illegal immigrants hurt the economy and legal immigrats "take our jobs". The immigration grid lock over the past 10 years has led to a brain drain via "outsourcing" of services and manufacturing. This is not sustainable. Continuing to penalize children of immigrants is not a good way to move forward.
The Dream Act supports children of illegal immigrants to gain a status that allows them to work, open a business and go to college in the United States.

We need to legalize the next generation so they can support small businesses.

Our greatest danger is to brand children of immigrants and college graduates from other countries as "aliens" who need to "go back". A regression in a skilled workforce will cause a stagnation in the U.S economy. If the policy of the new congress is to promote a reverse brain drain via a strategic policy of inaction, future congresses will face an imminent threat of economic depression. It is in our best strategic interest to allow future hardworking children of immigrants in America to realize the American Dream.  

Saturday, December 4, 2010 - an example of what NOT to do

One message for "" : Establish an Exception Handling Architecture


Server Error in '/' Application.

Server was unable to process request. --> Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.Services.Protocols.SoapException: Server was unable to process request. --> Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SoapException: Server was unable to process request. --> Object reference not set to an instance of an object.]
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +431766
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +204
WebReference.SeatBook.ShowSeats(Int64 TheatreId, Int64 BookingId, String ShowClass, Int64 NoOfTickets, String PartnerId, String PartnerPwd) +195
seatlayout.Seat_Layout() +743
seatlayout.Page_Load(Object sender, EventArgs e) +3161
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082


Wednesday, December 1, 2010

Removing Oxy Mouse Pointer

I have been using Linux off an on for the past 10 years for personal needs. Having never tried KDE, I installed it on the latest Ubuntu distribution. It is quite fancy and has lots of good features, however it has its share of issues too.
Surprisingly one of the features leaked into my Gnome sessions: the mouse pointer.

For whatever reason KDE's Oxygen theme with its weird mouse pointer would refuse to go away in Gnome - no matter how much I tried changing the theme.

rohit@lenovo:~$ uname -a
Linux lenovo 2.6.32-24-generic-pae #42-Ubuntu SMP Fri Aug 20 15:37:22 UTC 2010 i686 GNU/Linux

After scouring the net, and not finding much help I decided to "reset"; this turned out to be difficult as well. No matter which other default theme I selected, it still did not remove the offending pointer style. Oxy persisted. Here's what worked - I  removed the theme files under ~/.theme. Brutal, but it works. Now I have a nice black pointer.