<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Expanding and Collapsing Large Fields, DataView Style</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx</link><description>Okay, got a fun one today. I was asked by someone who had a list if the description column could be collapsed and expanded. Currently if you have a list with a description field and put the description field on a view, you're left with a large verbose</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Expanding on Expanding and Collapsing Fields in a View</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#403896</link><pubDate>Fri, 22 Apr 2005 21:45:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:403896</guid><dc:creator>TrackBack</dc:creator><author>TrackBack</author><description>&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=403896" width="1" height="1"&gt;</description></item><item><title>Expanding and Collapsing Large Fields : in a CAML way </title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#403821</link><pubDate>Fri, 22 Apr 2005 09:29:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:403821</guid><dc:creator>TrackBack</dc:creator><author>TrackBack</author><description>Renaud COMTE hat die Idee von Bil Simer aufgegriffen, mehrzeilige Textfelder in Listenansichten mit einer Erweiterung/Reduzierungs-Option zu versehen und die urspr&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=403821" width="1" height="1"&gt;</description></item><item><title>SharePoint : D</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#403283</link><pubDate>Tue, 19 Apr 2005 10:10:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:403283</guid><dc:creator>TrackBack</dc:creator><author>TrackBack</author><description>&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=403283" width="1" height="1"&gt;</description></item><item><title>re: Expanding and Collapsing Large Fields, DataView Style</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#400776</link><pubDate>Fri, 15 Apr 2005 18:25:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:400776</guid><dc:creator>Bil Simser</dc:creator><author>Bil Simser</author><description>This is a DVWP on a list so the only postbacks you have are if you use the sorting or filtering features. Yes, it does reset the JavaScript but the goal that was asked here was to do something simple to reduce the clutter when you do have lots of items on the screen. You can default all the collapsed values to true so it starts in that state.&lt;br&gt;&lt;br&gt;As to Erics comment about the variables, they're in a separate web part and through various magic you can toggle multiple items independantly. Again, this was a short excercise which solved the problem. There are certainly more robust ways to do this (including writing a full blown web part).&lt;br&gt;&lt;br&gt;Thanks for your comments.&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=400776" width="1" height="1"&gt;</description></item><item><title>re: Expanding and Collapsing Large Fields, DataView Style</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#400573</link><pubDate>Fri, 15 Apr 2005 13:51:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:400573</guid><dc:creator>Stuart Estell</dc:creator><author>Stuart Estell</author><description>FatEric, do you mean the saving state between postbacks? Going by the javascript above you'd certainly lose any toggling after a postback.&lt;br&gt;&lt;br&gt;It's good practise to prefix any global javascript variable names (even if you put them in a custom ows.js with your company name or something easily-identifiable that is unlikely to be duplicated elsewhere to avoid duplications of function names...&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=400573" width="1" height="1"&gt;</description></item><item><title>re: Expanding and Collapsing Large Fields, DataView Style</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#400564</link><pubDate>Fri, 15 Apr 2005 13:33:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:400564</guid><dc:creator>FatEric</dc:creator><author>FatEric</author><description>Am I wrong or are your javascript variables unique for the whole page ?&lt;br&gt;How can this be working when there are many lines in your list ? How can your variables save state for every lines ?&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=400564" width="1" height="1"&gt;</description></item><item><title>Tipp: Mehrzeilige Textfelder in Ansichten reduzieren und erweitern</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#400482</link><pubDate>Fri, 15 Apr 2005 09:55:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:400482</guid><dc:creator>TrackBack</dc:creator><author>TrackBack</author><description>Bill Simser hat unter dem Titel Expanding and Collapsing Large Fields, DataView Style einen Tipp zur Verf&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=400482" width="1" height="1"&gt;</description></item><item><title>re: Expanding and Collapsing Large Fields, DataView Style</title><link>http://weblogs.asp.net/bsimser/archive/2005/04/14/400421.aspx#400489</link><pubDate>Fri, 15 Apr 2005 08:50:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:400489</guid><dc:creator>Stuart Estell</dc:creator><author>Stuart Estell</author><description>Surely putting the Javascript into a content editor webpart leaves it rather vulnerable? I'd certainly be nervous about leaving that lying around for people to fiddle with. &lt;br&gt;&lt;br&gt;Would it not be better to have a custom ows.js registered with all of your templates by editing the default templates (with the appreciation that this needs to be done _before_ site creation)?&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=400489" width="1" height="1"&gt;</description></item></channel></rss>