<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: New WordPress Dashboard</title>
	<atom:link href="http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/feed/" rel="self" type="application/rss+xml" />
	<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/</link>
	<description>A Journal of the Digitization of a Civil War Battle</description>
	<lastBuildDate>Thu, 23 May 2013 14:38:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Rene Tyree</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3160</link>
		<dc:creator><![CDATA[Rene Tyree]]></dc:creator>
		<pubDate>Sat, 12 Apr 2008 23:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3160</guid>
		<description><![CDATA[Harry,

I&#039;ve figured out how to tweak the CSS. Let me know if you&#039;re interested... glad to share. 

I believe the dashboard change upgrade was the root cause of my post (worked two hours on it) disappearing as I hit publish. I believe they were rolling out the new code at the time. I was not amused.

Having managed a SW dev team at one point in my career, I&#039;m a big believer in letting people know you&#039;re going to make a change and then telling them when you&#039;re rolling the new code. If they did that, I totally missed it. Given the number of complaints, I&#039;m assuming that said nothing.

Rene]]></description>
		<content:encoded><![CDATA[<p>Harry,</p>
<p>I&#8217;ve figured out how to tweak the CSS. Let me know if you&#8217;re interested&#8230; glad to share. </p>
<p>I believe the dashboard change upgrade was the root cause of my post (worked two hours on it) disappearing as I hit publish. I believe they were rolling out the new code at the time. I was not amused.</p>
<p>Having managed a SW dev team at one point in my career, I&#8217;m a big believer in letting people know you&#8217;re going to make a change and then telling them when you&#8217;re rolling the new code. If they did that, I totally missed it. Given the number of complaints, I&#8217;m assuming that said nothing.</p>
<p>Rene</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Smeltzer</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3133</link>
		<dc:creator><![CDATA[Harry Smeltzer]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 13:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3133</guid>
		<description><![CDATA[Jenny,

From what I hear, the response has been overwhelmingly negative.  But the powers-that-be seem to have indicated that there is no turning back.  I sent a question to support on Saturday but have received no response...I&#039;m sure they are flooded with questions/complaints.]]></description>
		<content:encoded><![CDATA[<p>Jenny,</p>
<p>From what I hear, the response has been overwhelmingly negative.  But the powers-that-be seem to have indicated that there is no turning back.  I sent a question to support on Saturday but have received no response&#8230;I&#8217;m sure they are flooded with questions/complaints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aphillcsa</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3132</link>
		<dc:creator><![CDATA[aphillcsa]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 13:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3132</guid>
		<description><![CDATA[Supposedly some great usability guru firm came up with the new interface.   I hope WordPress didn&#039;t pay too much for the consult, because it seems like no one likes the changes.  The Write Post screen irritates me the most.  It makes common tasks that used to be so simple (putting the post in it&#039;s category for example or editing the time stamp) now much harder because it requires either scrolling down the page or clicking open several links.  I run the software on my own host, and I really wish I hadn&#039;t &quot;upgraded&quot; from 2.3 to 2.5.  It feels like a downgrade.]]></description>
		<content:encoded><![CDATA[<p>Supposedly some great usability guru firm came up with the new interface.   I hope WordPress didn&#8217;t pay too much for the consult, because it seems like no one likes the changes.  The Write Post screen irritates me the most.  It makes common tasks that used to be so simple (putting the post in it&#8217;s category for example or editing the time stamp) now much harder because it requires either scrolling down the page or clicking open several links.  I run the software on my own host, and I really wish I hadn&#8217;t &#8220;upgraded&#8221; from 2.3 to 2.5.  It feels like a downgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Smeltzer</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3131</link>
		<dc:creator><![CDATA[Harry Smeltzer]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 11:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3131</guid>
		<description><![CDATA[Kevin,

All in all, I like WordPress.  I think it still has significant advantages over other packages.  In fact, someone who is not already &quot;in a groove&quot; with the old version of the dashboard probably won&#039;t have a problem.  It&#039;s the old-timers who need to adapt to the changes.  Think of it like the Electric Map vs. whatever it is they&#039;re going to use now at the Gettysburg VC.]]></description>
		<content:encoded><![CDATA[<p>Kevin,</p>
<p>All in all, I like WordPress.  I think it still has significant advantages over other packages.  In fact, someone who is not already &#8220;in a groove&#8221; with the old version of the dashboard probably won&#8217;t have a problem.  It&#8217;s the old-timers who need to adapt to the changes.  Think of it like the Electric Map vs. whatever it is they&#8217;re going to use now at the Gettysburg VC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3130</link>
		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 11:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3130</guid>
		<description><![CDATA[Wow...and I was actually considering making the transition from Typepad to Wordpress.  Goog luck sorting all of this out.]]></description>
		<content:encoded><![CDATA[<p>Wow&#8230;and I was actually considering making the transition from Typepad to WordPress.  Goog luck sorting all of this out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Smeltzer</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3129</link>
		<dc:creator><![CDATA[Harry Smeltzer]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 07:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3129</guid>
		<description><![CDATA[Robert,

I don&#039;t know from CSS...I only have the basic WordPress with no upgrades.  All I can say right now is some of the changes are good: in WYSIWYG, you can cut and paste during the posting process (not just one paste at the beginning), underline, block the paragraphs (carefully), expand the posting box to full page, change the text color, undo (that&#039;s a great thing for me), and change font sizes (for headings only - it also bolds at the same time).  You can also now add audio.

On the bad side, when copying from Word it seems you can keep your font size, but not your font type.  The post will return to your theme&#039;s default font type.  I like Arial, because on this dark (not quite black) background, it shows up better.  Also, the process for posting pictures has changed.  Whereas you used to be able to place your cursor in the text before inserting the photo, it now looks like you can only insert the photo at the beginning of the text you have posted, and then must move the photo where you want it to be.  I have found in the past that moving photos around in the text does not work so well.  Some of my posts are picture heavy, with lots of inserts in and between paragraphs.  We&#039;ll have to see how that works.

There is also a &quot;paste from word&quot; key that, as far as I can tell, keeps your paragraph breaks from Word, but otherwise makes the post the same as plain text, defaulting to the theme&#039;s font type AND size, which in the case of my theme is a tiny, nearly unreadable font when the page view in IE is set to MEDIUM.

I&#039;m hoping I don&#039;t need to change my theme.  I&#039;ve had it since day one, and most of my readers (with a very few exceptions) like it.]]></description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>I don&#8217;t know from CSS&#8230;I only have the basic WordPress with no upgrades.  All I can say right now is some of the changes are good: in WYSIWYG, you can cut and paste during the posting process (not just one paste at the beginning), underline, block the paragraphs (carefully), expand the posting box to full page, change the text color, undo (that&#8217;s a great thing for me), and change font sizes (for headings only &#8211; it also bolds at the same time).  You can also now add audio.</p>
<p>On the bad side, when copying from Word it seems you can keep your font size, but not your font type.  The post will return to your theme&#8217;s default font type.  I like Arial, because on this dark (not quite black) background, it shows up better.  Also, the process for posting pictures has changed.  Whereas you used to be able to place your cursor in the text before inserting the photo, it now looks like you can only insert the photo at the beginning of the text you have posted, and then must move the photo where you want it to be.  I have found in the past that moving photos around in the text does not work so well.  Some of my posts are picture heavy, with lots of inserts in and between paragraphs.  We&#8217;ll have to see how that works.</p>
<p>There is also a &#8220;paste from word&#8221; key that, as far as I can tell, keeps your paragraph breaks from Word, but otherwise makes the post the same as plain text, defaulting to the theme&#8217;s font type AND size, which in the case of my theme is a tiny, nearly unreadable font when the page view in IE is set to MEDIUM.</p>
<p>I&#8217;m hoping I don&#8217;t need to change my theme.  I&#8217;ve had it since day one, and most of my readers (with a very few exceptions) like it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Moore</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3128</link>
		<dc:creator><![CDATA[Robert Moore]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 02:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3128</guid>
		<description><![CDATA[Oh, this is depressing. I haven&#039;t made a post since the change, so I&#039;m afraid to see what happens when I am back at it tomorrow. From time to time, when cutting from Word and pasting to the blog (in WYSIWYG format), I found that I needed to adjust the font and could do so through tweaking the content in CSS. Am I to understand that this is no longer an option? I have also found, from time to time, problems with left, right and center justification, prior to the change.]]></description>
		<content:encoded><![CDATA[<p>Oh, this is depressing. I haven&#8217;t made a post since the change, so I&#8217;m afraid to see what happens when I am back at it tomorrow. From time to time, when cutting from Word and pasting to the blog (in WYSIWYG format), I found that I needed to adjust the font and could do so through tweaking the content in CSS. Am I to understand that this is no longer an option? I have also found, from time to time, problems with left, right and center justification, prior to the change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Smeltzer</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3127</link>
		<dc:creator><![CDATA[Harry Smeltzer]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 00:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3127</guid>
		<description><![CDATA[You have nothing to lose but your chains, my brother.  I feel your pain, I really do.  I&#039;m holding off posting any ORs for a few days in hopes they get this ironed out, though it was too late for my revision of McDowell&#039;s report.]]></description>
		<content:encoded><![CDATA[<p>You have nothing to lose but your chains, my brother.  I feel your pain, I really do.  I&#8217;m holding off posting any ORs for a few days in hopes they get this ironed out, though it was too late for my revision of McDowell&#8217;s report.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caswain01</title>
		<link>http://bullrunnings.wordpress.com/2008/04/05/new-wordpress-dashboard/#comment-3126</link>
		<dc:creator><![CDATA[caswain01]]></dc:creator>
		<pubDate>Mon, 07 Apr 2008 00:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://bullrunnings.wordpress.com/?p=769#comment-3126</guid>
		<description><![CDATA[The new interface was foisted upon me also.  I&#039;m hitting the streets with Trotsky and Che to protest this.  It&#039;s like working with Windows Millennium all over again!]]></description>
		<content:encoded><![CDATA[<p>The new interface was foisted upon me also.  I&#8217;m hitting the streets with Trotsky and Che to protest this.  It&#8217;s like working with Windows Millennium all over again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
