dmitri wrote: |
I don't know any better solution for developing such scripts where you deal with large variables, but arranging environment as closer as possible to your front-end IDE, preferably on local desktop or on a locally running VM.
You may also want to think about storing large values by chunks in a locally running cache or something like that instead of PHP. |
My script works fine with large variables, and wouldn't normally have necessary resources to work on local VM without having to copy there also a huge database system with quickly changing data and a lot of other resources. Such copy would likely need weeks of debugging by itself, if even my local disks have enough space to host it.
Wouldn't it be possible to have the debugger displaying (and thus transferring) only small excerpts of these long variables, along with the actual length, and include in the display zone for example a button for viewing the whole contents, only if needed, in a hex viewer window ?
(it would be useful anyway to be able to view any string in a hex viewer window, even if it is short).
As a hex viewer window is expected to be scrollable, this wouldn't require transferring the whole string across the network, only the viewed parts would have to be copied from the server to the IDE.
Gingko