Autosave usage

[J. Tyler]

I really like the concept of the autosave feature, but in practice our internal users have found it confusing.  They are often prompted that autosave contents exist, but it is for a different piece of content that they were editing.

From my side, I think it would be more valuable if we could pass a unique identifier to the autosave plugin.  This way the autosave content would only be displayed if the unique identifier of the autosave content matched the piece of content they are editing.  

The next "nice to have" would be to have 5 or 10 autosave files at one time.

[Damien Fitzpatrick]

Hi J,

Thanks for the feedback, adding a ID API to autosave is certainly something
we¹re interested in doing in future.  It¹s something we¹re already tracking
in our feature database and I¹ll add your request to that as well.

With our initial version of autosave we were really focused on getting
something out the door that was applicable to as many users as possible and
as ³out-of-the-box² as possible.  This meant that we tried to keep APIs and
configuration settings to a minimum.  I¹d like to drill a bit deeper on
what¹s confusing your users and the details of your setup though, but I¹ll
take that off-list as I don¹t want to get into an in-depth technical
discussion on your particular configuration here.

Can you elaborate on what you mean by having 5 to 10 autosave files at one
time...I¹ve only just had my coffee here and I¹m still not sure I¹m grasping
what you mean by this.

Thanks,
Damien




On 19/10/09 11:07 PM, "J. Tyler" <[hidden email]> wrote:

>
>
> I really like the concept of the autosave feature, but in practice our
> internal users have found it confusing.  They are often prompted that
> autosave contents exist, but it is for a different piece of content that
> they were editing.
>
>> >From my side, I think it would be more valuable if we could pass a unique
> identifier to the autosave plugin.  This way the autosave content would only
> be displayed if the unique identifier of the autosave content matched the
> piece of content they are editing.
>
> The next "nice to have" would be to have 5 or 10 autosave files at one time.
> --
> View this message in context:
> http://n2.nabble.com/Autosave-usage-tp3848894p3848894.html
> Sent from the Ephox LiveWorks! mailing list archive at Nabble.com.
> _______________________________________________
> [hidden email]
> List instructions at http://liveworks.ephox.com/mailing-list/
>

_______________________________________________
[hidden email]
List instructions at http://liveworks.ephox.com/mailing-list/

[J. Tyler]

Some javascript/style in this post has been disabled (why?)

Our users are editing content that is stored in a database.  Each piece of content has a unique identifier. 

 

Let’s go through a scenario:

A user edits content_id 1, but decides not to save it.   They press back on browser or use the menu to change pages.  They then edit content_id 2.  When the editor loads they are prompted that an autosave version of this exists.  If they looked at it they would see that it is for content_id 1.

 

My idea would be that the autosave file would have a unique identifier associated with it (table id, file name, etc.).  This way editlive would know when the user is editing content_id 2, that an autosave file did not exist (in the case above).

 

The reason for having 5 or 10 autosave files is so that users could have autosave files for content_ids 1, 2, 5, 15, etc.   Their most recent changes.

 

Joe

 

 

From: Damien Fitzpatrick [via Ephox LiveWorks!] [mailto:[hidden email]]
Sent: Monday, October 19, 2009 6:44 PM
To: Tyler, Joseph
Subject: Re: [Liveworks] Autosave usage

 

Hi J,

Thanks for the feedback, adding a ID API to autosave is certainly something
we¹re interested in doing in future.  It¹s something we¹re already tracking
in our feature database and I¹ll add your request to that as well.

With our initial version of autosave we were really focused on getting
something out the door that was applicable to as many users as possible and
as ³out-of-the-box² as possible.  This meant that we tried to keep APIs and
configuration settings to a minimum.  I¹d like to drill a bit deeper on
what¹s confusing your users and the details of your setup though, but I¹ll
take that off-list as I don¹t want to get into an in-depth technical
discussion on your particular configuration here.

Can you elaborate on what you mean by having 5 to 10 autosave files at one
time...I¹ve only just had my coffee here and I¹m still not sure I¹m grasping
what you mean by this.

Thanks,
Damien




On 19/10/09 11:07 PM, "J. Tyler" <[hidden email]> wrote:

>
>
> I really like the concept of the autosave feature, but in practice our
> internal users have found it confusing.  They are often prompted that
> autosave contents exist, but it is for a different piece of content that
> they were editing.
>
>> >From my side, I think it would be more valuable if we could pass a unique
> identifier to the autosave plugin.  This way the autosave content would only
> be displayed if the unique identifier of the autosave content matched the
> piece of content they are editing.
>
> The next "nice to have" would be to have 5 or 10 autosave files at one time.
> --
> View this message in context:
> http://n2.nabble.com/Autosave-usage-tp3848894p3848894.html
> Sent from the Ephox LiveWorks! mailing list archive at Nabble.com.
> _______________________________________________
> [hidden email]
> List instructions at http://liveworks.ephox.com/mailing-list/
>

_______________________________________________
[hidden email]
List instructions at http://liveworks.ephox.com/mailing-list/

---

View message @ http://n2.nabble.com/Autosave-usage-tp3848894p3855657.html
To unsubscribe from Autosave usage, click here.

 

[Andrew Herron-5]

> The reason for having 5 or 10 autosave files is so that users could  
> have autosave files for content_ids 1, 2, 5, 15, etc.   Their most  
> recent changes.

This is how Autosave works today, except that the ID is a bit more  
general - we use the website domain.  When we add support for custom  
IDs this will definitely carry over.


Regards,
Andy

---
Andrew Herron, Senior Software Engineer
Global: [phone] x705  Australia: [phone]
Ephox <http://www.ephox.com> | Ephox Blogs <http://people.ephox.com>
_______________________________________________
[hidden email]
List instructions at http://liveworks.ephox.com/mailing-list/