Hi Jason,
Thanks for your reply. You're right it's a group of about 5k users, although I must say that while on webiopi group with less than 150 users I would get an answer on the same day, which I thought was amazing given the few users and just one developer. I guess the more users the more difficult to get answers as many ask and few can provide an answer.
Regarding the verbosity of my post you may notice that my original post had a mere 5 lines (well on my large screen it is at least ;D), before I stated "My experience so far to give you a bit of background context..." which was only a recount to give those interested in reading further, an idea about what I had tried before landing on web2py, but was not to needed to understand what I was asking in the prior paragraph.
About the bump, mine didn't mean to be one (which was also about 4 lines long going by my screen). In all honesty I was just thanking everyone on my way out.
I had spent several sleepless nights digging for info and reading docs to make this work and that got me nowhere. In the meantime the author of the referenced instructable was nice enough to get back to me, but unfortunately it was (in short) with a "sorry can't be of more help" reply. So I figured it wasn't meant for me to go down the web2py path.
I didn't look at what I was asking in terms of percentages, I thought web2py on raspberry isn't much different than web2py on linux, so I thought I was asking 100% about python programming in web2py, while referencing the small application in the linked instructable tutorial, my bad. Anyone curious or wanting to help would have only needed to install that same app on a raspberrypi to replicate understand what was being asked.
Thank you for the generic info which validate what I already knew. Indeed there is the need of a "deamon" or service running on the same host where web2py is installed to have a permanent listener to events (whether triggered by webUI or a sensor change). In the case of the referenced instructable, that'd be the "GPIOServer.py", which once launched (by rooting into the raspberrypi), it will stop for unknown reasons after an unmetered amount of time but surely more than a couple hours. That's already a deal breaker if I can't manage to have that script running reliably and continuously upon each reboot. I haven't tried an /etc/init.d/GPIOServer.py defaults perhaps will do that just before I drop the web2py option.
Concluding, the help I was asking for was by a fellow tinkerer who had followed the same instructable, was about to, or was willing to follow and replicate the same steps. Without doing that, I am aware that the reply would most likely have been "I don't quite know what your wanting." ;D
To know what I am trying to achieve and the issues I'm experiencing, all that's needed it's simply to upload the application in the instructable on a web2py installation running on a raspberrypi. At that point after following the same steps, it would be clear what I'm asking and, for those with more experience and knowledge than I, it would probably be relatively easy to spot what's needed to be done in order to:
1) have the GPIOServer.py running without stopping,
2) have the UI buttons change from simulating button presses on a remote, to a simple click/ON (to set GPIO pin high) and click/OFF (to set the same GPIO pin low)
Thanks once again for the much appreciated reply and for your suggestions to help with this project.
Cheers! :)