Yes, it is very strange that way.

I had to install a dependent module by hand and so I wondered what it did. 
There was not one single comment in it at all in any file beyond the license at 
the top. Even my bash scripts have a one liner somewhere to remind me why I 
wrote the thing. But I'm old and forgetful and have a lot of scripts lying 
around :-)

The twenty minute tutorial from last year or so hooked me. Esp. because I could 
emulate it with a foo module myself in a short time. I think it took me an hour 
actually. Not twenty minutes, but not bad for not knowing anything.

So far I've learned that you can change or extend existing things simply by 
writing a class with the same name to over-ride it, which is very cool. terp 
takes care of creating any new columns. Defs are just normal postgresql.

The c2c naming extension has  a good example of moving existing data to a new 
column.

It's easy to create new tables and hang it off existing too.

I don't quite understand the views in xml yet though. Sometimes I win, 
sometimes I lose. Don't quite 'get it'. Haven't spent much time on those yet 
either. I've created some astonishingly ugly views though :-)

I'm still learning what's available already too. Often I look for functionality 
and it is already there, but I don't spot it in the gui or maybe don't realize 
how to use it. Other times I start to plan functionality and then find it in an 
existing module. Lots of code and not much for docs -- we're just in for a long 
ride is all. I'm still really impressed with how things fit together. Just 
having a slow time discovering all the 'things'.

I have a few monitors in front of me, so I can easily play with multiple 
clients on the same box or remote with synergy. The other thing I'm doing is 
eschewing psql for now and watching things with knoda. Just nicer for casual 
browsing of changes and to read table defs.

Got a handful of db's on the go to try figure things out: a minimal install to 
use as a touch-stone, a db full of every module known to man (until I drop it 
and start again), a pretend 'real' one as I wish it to become and a db with my 
own (so far) useless modules. All of those db are subject to being dropped and 
recreated at any point in the day.

Early days though, we'll figure it all out eventually rincewind.




_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to