<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by EPiDave</title><link href="http://world.optimizely.com" /><updated>2009-09-25T23:02:00.0000000Z</updated><id>https://world.optimizely.com/blogs/EPiDave/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Detecting Edit Mode view of an EPiServer page</title><link href="http://epidave.blogspot.com/2009/09/detecting-edit-mode-view-of-episerver.html" /><id>Today I was given the slightly unusual requirement that my page must behave differently depending on whether it is being viewed normally, or through the IFrame in EPiServer&#39;s Edit Mode. It was a little tricky finding the answer so I thought I would explain it...Obviously the only way that the Edit Mode view can be detected is if there is something in the IFrame source URL used to request the page</id><updated>2009-09-25T23:02:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Composer layouts should not replace mark-up</title><link href="http://epidave.blogspot.com/2009/08/episerver-composer-layouts-should-not.html" /><id>I’ve been using EPiServer Composer (formerly X3) for over a year now. EPiServer Composer can allow you to develop a very nice drag and drop interface for your editors, essentially allowing them to layout areas of new pages as and when they’re created. The temptation here, is to develop a series of functions (droppable objects like controls) which are so generic in nature, that you could allow </id><updated>2009-08-25T00:41:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Custom Properties and Modal Dialogs</title><link href="http://epidave.blogspot.com/2009/08/custom-properties-and-modal-dialogs.html" /><id>Ever wanted to be able to easily throw together a pop-up window custom property simply and easily? This blog entry describes the a set of base classes I use when I want to create such a property, and shows an implementation of a simple key-value editor.Why use modal dialogs?I use this approach whenever I think my new custom property is likely to get a bit too complex, or if I’m adding to an </id><updated>2009-08-24T09:08:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Storing business objects in EPiServer</title><link href="http://epidave.blogspot.com/2009/08/storing-business-objects-in-episerver.html" /><id>I recently had a discussion with someone about how best to store collections in EPiServer, such as RSS feeds, advertisements, frequently asked questions, customer details etc. Here are my thoughts...Using custom propertiesIf you wanted to display a collection of objects on a page, then usually you might create a custom property with a suitable interface so that editors can add to, and maintain </id><updated>2009-08-03T22:43:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Enterprise Virtual Path Provider</title><link href="http://epidave.blogspot.com/2009/07/episerver-enterprise-virtual-path.html" /><id>This article demonstrates how to create a virtual path provider which can be used to serve site specific files, while still using the same application directory for your sites.Introduction to EPiServer EnterpriseFor those of you who have been able to play with a copy of EPiServer running an enterprise license, you can skip the next couple of paragraphs. For those who haven’t, here’s how it </id><updated>2009-07-31T21:48:00.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>