October 2002 - Koha-devel - lists.koha-community.org

RE: [Koha-devel] question about templating and directory structure
by Eyler, Patrick 01 Oct '02

01 Oct '02

> -----Original Message----- > From: paul POULAIN [mailto:paul.poulain@free.fr] > Sent: Tuesday, October 01, 2002 8:03 AM > To: koha-devel(a)lists.sourceforge.net; Finlay Thompson > Subject: [Koha-devel] question about templating and directory > structure > > I'm working a little on templates, for MARC support, and i've some > problems. > > How templates are supposed to be organised ? > I thought it was : > includes/templates/[theme_name]/* > > but i saw some posts about [language]/[theme_name]/* I think that we need to include the language identification above the theme identification. includes/templates/[language]/[theme_name] makes sense to me. > > and today, finlay released files into > koha/koha-tmpl/intranet-tmpl/default/en/* I think this is broken WRT previous discussions. It seems like thes should be includes/templates/en/default/intranet/* If I'm wrong, please let me know. > > I begin to be lost, and think that before beginning translations > and/or > releasing templated koha we should say definetly where are > templates, > and modify move file accordingly... > > to end, i think we should spend some time to merge 1.2 templating > stuff > to main branch too... This is certainly true. Does anyone want to step up to running the merge? -pate > -- > Paul > > > > ------------------------------------------------------- > This sf.net email is sponsored by: DEDICATED SERVERS only $89! > Linux or FreeBSD, FREE setup, FAST network. Get your own server > today at http://www.ServePath.com/indexfm.htm > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel

4 5

Re: [Koha-devel] Repetitious behavior repeatedly
by paul POULAIN 01 Oct '02

01 Oct '02

Nathan Gray wrote: >I believe what you are considering is object-oriented programming, >which can make a lot of sense, if you build your objects correctly. >You decide which information is allowed to be stored in the object, >and which methods (functions) will be handled internally by the >object. Then you just pass around one variable, usually called >'$self'. When you want a dbh, you could run: > > my $dbh = $self->dbh; > That's it ! Great idea. Thus, there will be only a few things to change in koha. Every script starts with my $param_object = buildparam->new(); Every C4 sub is called with $result = C4Function($param_object,$other_param1, $other_param2,...); And every C4 sub needs only to have 2 lines rewritten : sub MySub(); my ($param,$other1, $other2) = @_; my $dbh = $param->dbh; instead of sub MySub(); my ($dbh,$other1, $other2) = @_; If in a C4 sub we need an other parameter, we can use : my $HashOfStopWord = $param->stopwordlist(); and work with HashOfStopWord. >The 'dbh' method would know how to get a new database handle, or would >return the existing one, if it has already made a connection. > Very nice idea too. With this one, we fill, for example stopword list only when ->stopwordlist() is called : no unuseful DB readings. Note that the DB handle is so necessary that i think this one should always be created when object is created. >You could very easily create a 'prepare' method in self, that would in >turn run 'prepare' on the dbh. > sub prepare { > my $self = shift; > my $query = shift || return; > my $dbh = $self->dbh || return; > my $sth = $dbh->prepare($query); > unless ($sth) { > warn $dbh->errstr; > } > return $sth; > } >Each method would handle its own error handling, when appropriate. >Adding methods for 'param' and 'stopwords' would also be really easy. >Let me know if you need any help, if you decide to go this route. I >now write most of my code in an object-oriented style, because I find >it much easier to keep track of where everything is. Then you can >also inherit methods from other objects, and all sorts of fun stuff >(perhaps down the road a ways). > I'm very poor at Perl-OOP, so any help is greatly welcomed ;-) Give an object with db handle and stopwords management, i'll copy/paste for other tables if you don't do. Don't you have a cvs account on sourceforge ? >kolibrie > I think we've got a winner at Perl Programming... (twice winning in 1 week. Kudos Nathan ;-) ) -- Paul

2 2

question about templating and directory structure
by paul POULAIN 01 Oct '02

01 Oct '02

I'm working a little on templates, for MARC support, and i've some problems. How templates are supposed to be organised ? I thought it was : includes/templates/[theme_name]/* but i saw some posts about [language]/[theme_name]/* and today, finlay released files into koha/koha-tmpl/intranet-tmpl/default/en/* I begin to be lost, and think that before beginning translations and/or releasing templated koha we should say definetly where are templates, and modify move file accordingly... to end, i think we should spend some time to merge 1.2 templating stuff to main branch too... -- Paul

1 0

KDE3, Mandrake 9 and CVS
by paul POULAIN 01 Oct '02

01 Oct '02

For those who are looking for a graphic tool to manage CVS : In Mandrake 9, kde3, Konqueror now includes cervesia, CVS management tools. Works nice, seems translated (at least in french), integrated with konqueror. You know what, I'm happy ( @ Droopy) -- Paul

1 0