Background processing needed...

Question

iWeb needs to background process.
Each shape/rollover/png/navbar/image-resize file needs to be generated as you make it, or in the background if you're working fast. Every time you alter the item's size or appearance on the iWeb page, it should regenerate it, but if you don't alter the item it leaves the generated file untouched. Moving the item on the iWeb page should not alter the already generated file. Altering plain text on a page should not change anything, only the html file.
There should be an info page like iDVD informing you of background encoding status. You can however save at any time (like iDVD).
When you come to publish, it should generate all other items that have changed or not yet been background encoded (as it does now).
Next time you open iWeb to work on it, all encoding is all up to date (as it did it all prior to publish), so any items that have not been changed should be untouched, and only new items need to be encoded and hence published.
That way, only changed items are generated, not the whole shebang. Thus saving everybody's wasted time and effort in uploading/finding changed files etc.
It should be perfectly possible as iWeb has an undo and a restore feature, so it is already keeping track of changes all the time.
What do you think, will this be in iWeb 1.2, iWeb 2.0, or Web Studio Pro 1.0 ?
Michael
Quicksilver G4 Dual 1GHz   Mac OS X (10.4.5)   http://www.rowan-cottage.co.uk

Answer 1

Hi,
This is the F1 documentation for calling a FM in Update task
Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task.
This is the F1 documentation for calling a FM in background task
Flags the function module func to be run asynchronously. That is, it is not executed at once. Instead, the data passed using EXPORTING or TABLES is placed in a database table and the next COMMIT WORK executes it in another work process.
Hope this helps
Regards,
San