Open uaktags opened 11 years ago
Instead of having them in a GET like 1.x does, why not stick them in a session, and then after the messages are displayed, clear that session.
That's what I did with the rework. But rather than having this feature, let's try to find a solution around it. HTTP is a stateless protocol, so let's try to make the messages we show as well. — Sincerely Ferdi Schmidt
On Sun, May 26, 2013 at 1:01 PM, Jake B. notifications@github.com wrote:
Instead of having them in a GET like 1.x does, why not stick them in a session, and then after the messages are displayed, clear that session.
Reply to this email directly or view it on GitHub: https://github.com/uaktags/Rework-Revisited/issues/6#issuecomment-18461397
I don't believe I used a GET method like 1.x in this prototype?
ezRPG 1.x used Get data to do messages, I'm testing an idea that I'm about to post with $this->view->setMessage('This is your warning!', "WARN');
Later I was thinking of turning the set message into an array, so that the view file would just have to parse foreach message create the message span associated. Multiple (if need be) messages could then be utilized.