Intelligent save operation for online collage editor
In a server-based system for creating and editing image-based and or text-based projects, the system having access to a digital medium containing an executable graphics user interface (GUI) accessible by computer browser, a method is provided for triggering automatic page save operations and includes the steps, (a) monitoring editing activity occurring in the project editor viewport, and (b) upon detection of a loss of a page from an editor viewport and or detection of a violation of a safety measure, automatically persisting the current page data to the server.
1. A Internet connected server providing a software application for creating and editing image-based and or text-based projects, the server having access to a remote digital medium containing an executable graphics user interface (GUI) accessible by computer browser, a method for triggering automatic page save operations comprising the steps:
(a) monitoring editing activity of the projects occurring in a project editor viewport of the application; and
(b) upon detection of at least one of a loss of a page from the editor viewport, pending crash of the software and detection of a violation of an editing rule of the software, automatically persisting the current page data to the server via an Action Script Message Format (AMF) framework.
2. The method of claim 1 the image-based projects include but are not limited to photo books, photo cards, photo calendars, and mouse pads.
3. The method of claim 1 wherein in step (b), a client/server communication channel is used in persisting data to the runtime server.
4. The method of claim 1 wherein in step (b), the data is persisted to the server in the event of a pending server-crash or problem.
5. The method of claim 1 wherein in step (b), the data is persisted to the server after a given amount of time of inactivity of the interface.
6. The method of claim 1 wherein in strep (b) the data is persisted to the server in the event of system maintenance on the server.
7. The method of claim 1 wherein in step (b), the data is persisted to the server in the event of a pending computer crash, or application hang on the client.
8. The method of claim 1 wherein in step (b), the data is persisted to the server in the event of breach of a threshold number of changes or edits made to a page.
9. The method of claim 1 wherein in step (b), the data is persisted at pre-configured periodic intervals.