Hi Apostolis,

I want to create a plugin that would be part of the enviroment of a number of pages.
the plugin wants to know the user that is logged in, the owner of the page that is viewing and the absolute path of the page.

So  to get this i ll put in my component these lines right?

PRContext user
PRContext structure owner
PRContext structure absolutePath

If you derive your component from PRWidget rather than WAComponent you have access to #context, see for example PUSecurityWidget 
 
I guess that the absolute path is the only way to identfy a page.

Another problem i have is with persistency..
I googled and found that lots of people have already talked about it.
For me and i think every new programmer, it is the biggest obstacle for using Pier...
Pier is very powerfull , easy to use and programm due to its smalltalk foundation. The code is so easily understood and the reusability of the code is phenomenal.

So If this persistency problem is solved with the new programmer in mind, the one that just wants its objects to save, no questions asked, Pier would rock.

So to use Pier, the only option for me is to go for a non-free DB like gemstoneS. All i have to do is tell Pier to save objects and gemstone will do it automatically without me changing any of the code, right?
Unfortunately at the time of writing i have access to a 32bit CPU so i cant check for myself..

I know there are other options like magma, but from what i understand you have to understand the underlying structure and i dont want to.

If you go the Gemstone route, for deployment you can use a free Amazon EC2 micro instance. See: http://nickager.com/blog/Screencast-creating-a-new-instance-based-on-pre-configured-AMI/ and http://nickager.com/blog/Create-a-free-Gemstone-server-in-the-cloud-in-10-minutes/

Hope this helps

Nick