How to run out of memory in Revolution

"Raw" content is referred to as Content throughout; the result of processing is referred to as "Output".

Quote from: OpenGeek at Oct 13, 2008, 02:28 PM

"Raw" content is referred to as Content throughout; the result of processing is referred to as "Output".

Good to know. A ubiquitous getOutput() method might make sense. It’s more intuitive than process(), IMHO and makes a more logical companion to getContent().

Quote from: BobRay at Oct 13, 2008, 02:45 PM

Good to know. A ubiquitous getOutput() method might make sense. It’s more intuitive than process(), IMHO and makes a more logical companion to getContent().

We are now on the same wavelength in this regard. getOutput will also be added. These are exactly the kinds of improvements feedback from developers will be a catalyst for; great stuff!

Quote from: OpenGeek at Oct 13, 2008, 02:48 PM

Quote from: BobRay at Oct 13, 2008, 02:45 PM

Good to know. A ubiquitous getOutput() method might make sense. It’s more intuitive than process(), IMHO and makes a more logical companion to getContent().

We are now on the same wavelength in this regard. getOutput will also be added. These are exactly the kinds of improvements feedback from developers will be a catalyst for; great stuff!

Thanks! Now I feel a little less guilty about wasting your time and hijacking these threads.