Warning: Declaration of FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php on line 275

Warning: Declaration of FEE_Field_Tags::wrap($content, $before, $sep, $after) should be compatible with FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php on line 284

Warning: Declaration of FEE_Field_Category::wrap($content, $sep, $parents) should be compatible with FEE_Field_Terms::wrap($content, $taxonomy, $before, $sep, $after) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php on line 293

Warning: Declaration of FEE_Field_Post_Thumbnail::wrap($html, $post_id, $post_thumbnail_id, $size) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php on line 335

Warning: Declaration of FEE_Field_Post_Meta::wrap($data, $post_id, $key, $ui, $single) should be compatible with FEE_Field_Post::wrap($content, $post_id = 0) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php on line 401

Warning: Declaration of FEE_Field_Widget::wrap($params) should be compatible with FEE_Field_Base::wrap($content, $data) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/widget.php on line 98

Warning: Declaration of FEE_Field_Comment::wrap($content) should be compatible with FEE_Field_Base::wrap($content, $data) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/other.php on line 54

Warning: Declaration of FEE_Field_Term_Field::wrap($content, $term_id, $taxonomy) should be compatible with FEE_Field_Base::wrap($content, $data) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/other.php on line 104

Warning: Declaration of FEE_Field_Single_Title::wrap($title) should be compatible with FEE_Field_Term_Field::wrap($content, $term_id, $taxonomy) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/other.php on line 120

Warning: Declaration of FEE_Field_Option::wrap($content, $key, $ui) should be compatible with FEE_Field_Base::wrap($content, $data) in /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/other.php on line 267

Warning: Cannot modify header information - headers already sent by (output started at /homepages/9/d602960330/htdocs/blog/wp-content/plugins/front-end-editor/php/fields/post.php:275) in /homepages/9/d602960330/htdocs/blog/wp-includes/feed-rss2-comments.php on line 8
Comments for SimBu http://simonburgoyne.com/blog Backspace and beyond Sat, 15 Jan 2011 11:43:56 +0000 hourly 1 https://wordpress.org/?v=4.6.14 Comment on MVC, Building and persisting view models. by simbu http://simonburgoyne.com/blog/2010/11/25/mvc-building-and-persisting-view-models/#comment-102 Sat, 15 Jan 2011 11:43:56 +0000 http://simonburgoyne.com/blog/?p=175#comment-102 Your the first legitimate non colleague comment on this site!!! Thx.

I’ve worked on two big MVC apps since dec 2008 see my linkedin profile for details.

Both have required session persistence for wizards and complex forms, this was just a stab at refactoring this experience into a class.

So no I’ve not used these classes in production yet, but a lot of similar code is working in production, no guarantees I’m afraid.

Some other options:
– Persist to a repository e.g. DB
– Use temp data which also uses session(Ajax calls may be a problem).
– Have a single page and show and hide the form elements, I worked on another project that worked well with this approach.

Hope this helps Simon ;o)

]]>
Comment on MVC, Building and persisting view models. by mchid http://simonburgoyne.com/blog/2010/11/25/mvc-building-and-persisting-view-models/#comment-101 Fri, 14 Jan 2011 09:26:12 +0000 http://simonburgoyne.com/blog/?p=175#comment-101 Hi Simon,

Very interesting article. I have a web application that requires the user to build a complex ‘Order’ over a large number of steps. I have struggled to identify the best approach for maintaining the state of the Order as it is being built.

I am surprised that there seems to be very little on the web or documentation that describes the options.

My latest thinking matches yours whereby I use Session to store the ‘OrderViewModel’ during the steps. When ready to submit I map this to the domain entities for saving (I am using Entity Framework).

I am yet to implement this and your approach looks good.

Did you have a similar journey to get to this point? Did ‘alarm bells ring’ by the fact that this seems to be such an uncommon requirement that you might be doing something wrong? This is certainly the case for me – I thought this was a relative common requirement yet so little discussion is out there about state and persistance before saving.

Can you point me to any other sources of information related to this?

Have you actually applied this to a complete application? If so what is your experience with this approach?

Sorry about all the questions – you don’t have to answer them all!! 😉

Mark

]]>
Comment on MVC, Building and persisting view models. by Gurpreet Singh http://simonburgoyne.com/blog/2010/11/25/mvc-building-and-persisting-view-models/#comment-12 Wed, 24 Nov 2010 22:08:38 +0000 http://simonburgoyne.com/blog/?p=175#comment-12 Very nice. Look forward to the followup blogs

]]>
Comment on Squashing your old sql scripts into migrations using T4 templates. by Gurpreet Singh http://simonburgoyne.com/blog/2010/11/24/squashing-your-old-sql-scripts-into-migrations-using-t4-templates/#comment-10 Wed, 24 Nov 2010 02:06:23 +0000 http://simonburgoyne.com/blog/?p=133#comment-10 Nice idea! Thanks for sharing

]]>