Where has this tool been all my life….?

Check it out!!  My productivity is going to just improve with this - no more clicking through just command prompt it all in a browser

Small issue with IE7 and composer, spaces - if you have too much content within your widgets and overflow set as auto to create scrollbars in the widget then the SDF is stretch. This bug does not appear to happen on Firefox, Chrome, or Safari..

I was also surprised to find Spaces doesn’t support Opera?? I wounder why..
I’ve always considered Opera to be a great browser, although the power of Firebug keeps me using firefox nothing compares to it..

You can fix this issue by playing with the widget configuration stretch option.. But a lot of the times you will require this… Waiting for bug update from metalink I`ll update you guys with a solution.

The bug is not caused by the skins but from inline styles defined from the renderkit..

Note:: I have also seen this bug replicated on FF 3.5.9

So a slight change with the Spaces design approach.
Sometimes you will want to create a widget stack instead of seperating the widgets out when you collapse them like the example above; this can be achieved by updating the Trinidad CSS Skin.

Here it is::
/***/
/***/
/*Widget Outer Container*/
af|showDetailFrame {
border:0px;
}

/*Widget Header Container*/
af|showDetailFrame::header,
af|showDetailFrame::header:light,
af|showDetailFrame::header:medium,
af|showDetailFrame::header:dark {
height:80px; /*Widget heeader height*/
border:0px;
background:none;
margin-bottom:-40px; /*Pull following content container or next widget -40px into header*/
}

/*Widget Content Container*/
af|showDetailFrame::content,
af|showDetailFrame::content:light,
af|showDetailFrame::content:medium,
af|showDetailFrame::content:dark {
margin:40px 5px 50px 5px; /*this provides the bottom margin to the next widget and pushes content to correct level position*/
}
/***/
/***/

How does this work?
When you select the collapse icon the content widget container DOM is removed completely.  The widget below is negatively pulled up into the header widget where the content area was displayed previously. The 50px margin that separated the widgets is now gone.

I never use XML when doing AJAX I’ve always believed in using the JSON format. For me XML and Soap requests are too bloated and there is way too much overhead. But recently I had a client that wanted xml over json and for some reason I couldn’t figure what was going on with IIS as I’ve never had this problem in apache - well here’s the solution for you and a little background info.

Getting XML demos to work on IIS 6-
1. Right click on “Default Web Site” Select “Properties” from context menu.
2. Select “Home Directory” Tab.
3. From Application Settings select the “Configuration…” button.
4. Add an application extension.
5. Enter the asp executable extension - C:\WINDOWS\system32\inetsrv\asp.dll
6. Select all verbs radio or enter XML,GET,HEAD,POST,TRACE
7. Goto Mime Types Within the “Default Web Site Properties” window under the HTTP Headers Tab.
8. Add .”xml” and “text/xml” - although this should be already set on the root “Web Sites” folder aswell.
9. Goto “Web Service Extensions” Make sure “Active Server Pages” are enabled.
10. stop start IIS or do a iisreset
11. Open all xml files and enter the asp tag to set the content type.
12. <%response.ContentType=”text/xml”%>
13. extjs, jquery or any other framework will now work with IIS.

IIS by default will not return POST or GET http requests of any file format that is not defined - therefor you have to set this up under the application extensions.
Unfortunately the asp extension returns the content type as text/html as a result you have to enter the asp tag to return the content type of text/xml. <%response.ContentType=”text/xml”%>

Passing the incorrect content type to javascript will not break or crash the script however will not display any results.
For example if IIS returns the content type of text/html for a xml file then the javascript method - response.responseXML will not work - using the response.responseText method will return text however this does not help as further methods may be expecting an xml structured response.

As an alternative you may by able to install FastCGI and set up the xml extension in there instead of asp I believe this will automatically return the correct content type for xml.
However there could be security risks by doing this as php cgi could be now extecuted from the server - and I would recomend a security audit if you took this approach.

Quick Tip..

Some times you won`t want to display the widget vertical resizer until you hover over the widget..
So here;s the Global Component CSS to apply to your skin to display your custom img resizer on mouseover of a widget.

/***/
/***/
/*Widget Hide Resize Icon*/
af|showDetailFrame::resize {
display:none;
}

/*Hover Show Resize Icon*/
af|showDetailFrame:hoverTarget af|showDetailFrame::resize,
af|showDetailFrame::content:hover af|showDetailFrame::resize,
af|showDetailFrame::container:hover af|showDetailFrame::resize {
display:block;
background:url(/webcenter-spaces-resources/META-INF/custom/spaces/skins/360/images/bb-widget_resize.png) no-repeat;
width:25px;
height:25px;
}
/***/
/***/