OutPost 2.0 Released
Tuesday, March 13, 2007
New version ready to download!
It is much better at dividing the page up and sending only what's changed. One of the reasons for this is that OutPost no longer restricts itself to looking at html tags that has an ID on them. Any element goes! Also a Delete command and a Copy command is introduced.
Hope you like it and have fun with it! Please, write a comment if you use it for something cool!
Changes since last release, which was 1.6.002:
- 14/03-2007 - 2.0.001
- Added support for specifying LocalHost dynamically by setting it to $CURRENTHOST$.
- Added support for hiding LASTFOCUS field.
- Fixed support for storing/restoring selected text.
- Added support for client debugging modes.
- Added support for simulating (triggering) onload, onunload and onbeforeunload events.
- Added support for adding rows to tables.
- Added support for url redirect
- Added support for deleting elements by sending a Delete command to the client.
- Added WebParts and Cars demoes.
- Added support for chunked response.
- 23/01-2007 - 1.7.001
- Added support for adding client side event 'onsuccess' to the form.
- Added support for sending modified tags without id or name back to the client.
- Added support for copying html from elements that are already present on the client to other elements in stead of sending it again.
- Added support for sending table rows (tr) back to client.
- Added support for sending only value of input tags back.
- Added support for sending only modified script blocks back to the client.
- Added cross-browser support for using following DHTML features: outerHTML, replaceNode, parentElement, canHaveChildren.
- Added support for adding response headers by specifying appsetting "AddHeaders" (syntax "key1=value1&key2=value2").
- Fixed problem with repeatedly submitting a form and not getting the form updated or reset (as pointed out by Jomar Coquia).
- 23/11-2006 - 1.6.004
- Fixed problem with inserting carriage returns into textarea.
- 15/11-2006 - 1.6.003
- Added if there is no difference between two or more post backs the browser is re-updated with the last post back that had a difference. That means if you modify the DOM between the post backs this resets some or all of these modifications (which i closer than before to what is normally expected).