My issue solved!
I want to collapse all Page Block sections by default on page open.
I can write code in a VF Page, but I get cross site scripting errors.
Create a Static Resource using JavaScript to accomplish the default collapse:
function twistSection(twisty, sectionId) {
//twistSection code from salesforce.com
var parentDiv = twisty;
while (parentDiv.tagName != 'DIV') { parentDiv = parentDiv.parentNode; }
var headerId = sectionId || (parentDiv.id.split('_'))[1];
var div = parentDiv.nextSibling;
var elemWasOn = false;
if (div.style.display != 'none') {
div.style.display = 'none';
twisty.className ='showListButton';
twisty.alt = twisty.title = 'Show Section - '+twisty.name;
elemWasOn = true;
}
}
var registeredSections = new Array();
function registerTwistableSection(headerId, mainTableId) {
var obj = new Object();
obj.headerId = headerId;
obj.mainTableId = mainTableId;
registeredSections[registeredSections.length] = obj;
for (var i = 0; i < registeredSections.length; i++) {
var obj = registeredSections[i];
var img = parent.document.getElementById("img_" + obj.headerId);
//go right into twistSection if we have the img obj.
if(img){
if (img.className =='hideListButton') {
twistSection(img, obj.headerId, obj.mainTableId);
}
}
}
}
function registerTwistableSections_ep() {
//these are the sections I know about from viewing source code...
registerTwistableSection('01B30000003osTc', 'ep');
registerTwistableSection('01B30000003osTd', 'ep');
registerTwistableSection('01B30000003osTe', 'ep');
registerTwistableSection('01B30000003osTg', 'ep');
registerTwistableSection('01B30000003osTh', 'ep');
registerTwistableSection('01B30000003osTi', 'ep');
registerTwistableSection('01B30000003osTj', 'ep');
registerTwistableSection('01B30000003osTk', 'ep');
}
registerTwistableSections_ep();
Now for the cross site scripting hack:
Found this in another post and am so thrilled that it works:
1. Create a Custom Homepage Component that is HTML, refer to your Static Resource code:
<script src="/resource/1284395872000/pageBlockSupplement" type="text/javascript"></script>
2. Make sure this component is included on the Home Pages layouts. It is invisible, so you don't have to worry about it.
"
I'm very excited to report that we've published a new section of developer.force.com, Force.com Secure Cloud Development. This brings together the complete set of developer resources covering secure development practices on Force.com, and represents our continuing investment in tools and content designed to maintain the security of the entire Force.com ecosystem.
In my previous post, I mentioned that we had a number of new and free tools, training and resources for our developer community. I'm happy to be able to discuss them in more detail. Below you'll find the resources outlined in a typical software development lifecycle.
(Secure) EducationWe are actively looking for community feedback and want the resources we're making available to continuously improve and can only do that with your help. Together we can all build a trusted ecosystem. Any queries can be sent to securecloud {at} salesforce {dot} com or post questions to our community discussion board.
If you know anyone developing on the Force.com platform, help spread the word!
I remember when I first started programming in Java many years ago. I used to walk the isles of my local bookstore (remember those brick and mortar things we all used to visit?). The shelves were filled with books on C, a few smatterings of web design, and of course, the trusty O'Reilly In a Nutshell books; but alas, there were no Java books.
Then all of a sudden----wham! Shelf after shelf of books covering every aspect of Java. I was in techie heaven. When I look back however, the initial books actually trickled in and became the catalyst for much of the future explosion of titles. With my experience writing fiction novels, I know these initial books also serve another very important purpose: to serve as a litmus test for publishers to identify hot markets and trending topics.
I see Force.com at a similar juncture in its evolution. We often forget Apex and Visualforce is only about two years old, and has already achieved remarkable things. Heck, I still remember writing socket connectivity in Java to connect to databases before JDBC was available! Oh how things have changed. Now, we not only take database connectivity as a given, with Force.com we don't even have to write anything to handle scalability, deployment, etc.
Just like Java, we are starting to see some early books on Force.com hitting the shelves. Jason Ouellette recently wrote a great book called Development with the Force.com Platform available from Addison-Wesley, which should be on all Force.com developers bookshelves. Aside from the sample chapters available from the link above, Jason has also provided a great article on Dr. Dobbs with additional information that really gives you a sense of the what Jason's book offers.
Great job Jason. I suspect this book will be the catalyst to many more to come.
We've known for a while that Google wasn't actively improving Gears, their tool that offers offline support for many popular web applications. Now the Official Gears blog explains their transition to the game-changing HTML5:
If you've wondered why there haven't been many Gears releases or posts on the Gears blog lately, it's because we've shifted our effort towards bringing all of the Gears capabilities into web standards like HTML5. We're not there yet, but we are getting closer. In January we shipped a new version of Google Chrome that natively supports a Database API similar to the Gears database API, workers (both local and shared, equivalent to workers and cross-origin [workers] in Gears), and also new APIs like Local Storage and Web Sockets. Other facets of Gears, such as the LocalServer API and Geolocation, are also represented by similar APIs in new standards and will be included in Google Chrome shortly.
The HTML5 transition should mean great things for users in the long-run, but it's a bummer to see good solutions fall by the wayside while we wait for the major browsers to catch up to, agree on, and support the latest standards. The cost of progress, I suppose. [Gears API Blog]
Spring '10 is just around the corner, with many great new features. One of the Apex Code enhancements which caught my attention was the limits on the number of items a collection can hold has been removed. The previous limit was set at 200. Add this to the new ability to use generic sObjects to create a collection and Collections within the platform just got a whole lot more powerful.
As Ben Parker, the o-so-wise uncle of Peter Parker (aka Spiderman) once said: "with great power comes great responsibility." Changes to Collections is no different, and require some new thinking in regards to best practices.
The release notes, for example, mention that there is still a limit on heap size so care must be taken to not load up a collection and hit this limit. Good news is that a few other other Spring '10 changes can certainly be used to ensure you design your applications as efficiently as possible.
Here are just a few new SOQL clauses and functions which can be used with collections to help make the most fo the changes.
