On Fri, Nov 14, 2008 at 12:50:57PM +1100, Rick Welykochy wrote:
> Anyone have experience with the impending CPAN replacement called
> CPLANPLUS?
> I raise this in light of addressing the issue of problems many seem to
> be having installing the perl module requirements for Koha.
i have a sight on
Anyone have experience with the impending CPAN replacement called
CPLANPLUS?
http://cpanplus.dwim.org/
"CPAN++ (also referred to and pronounced as CPANPLUS) is a new and
flexible method of perl module management and installation using
the Comprehensive Perl Archive Network (CPAN). It a
Mason James wrote:
> check this link for hearty examples of 'tabs versus spaces'
> discussion, enjoy ;)
>
> http://www.perlmonks.org/?node_id=576936
>
>
> for me, the above discussion eventually has a obvious conclusion,
> which is...
>
>tabs have the possibility to be displayed in a w
On 2008/11/14, at 2:50 AM, Paul POULAIN wrote:
> Rick Welykochy a écrit :
>> Mason James wrote:
>>
>>> but i think we might have to allow either tabs or spaces from
>>> developers -
>>> (thats perltidys behavior too afaik)
>>
>> Why would anyone indent with spaces?
check this link for hearty
Jesse Weaver wrote:
> As far as I know, the staff side already has this requirement; are you
> referring to the OPAC?
There are many scripts on the staff side that have
the flag enabled, i.e. login not required.
grep -rl "authnotrequired => 1" /usr/share/koha/intra*/*
will show which ones.
S
DBIx::Class, in all likelihood, will be the real solution. As the author of
C4::Table, I still think it is cool, easy to use and relatively tight, but
it's unfinished, and there won't be a real need for it once we have
DBIx::Class involved.
--Joe
On Thu, Nov 13, 2008 at 4:59 AM, Rick Welykochy <
On Thu, Nov 13, 2008 at 7:03 AM, Owen Leonard <[EMAIL PROTECTED]> wrote:
> >> And what about the templates? They are often mind-bending to edit, and
> I've
> >> seen no tools to assist in comprehending their structure.
> >
> > agreed...
>
> The Perl scripts are mind-bending to me. I suspect it's w
I have a few patches to that end. I think I even posted them to the
patches list. At least I remember some suggestions made on the patches
list that I implemented on my branch. Only thing I haven't done is put
them in a syspref.
On Thu, 2008-11-13 at 16:19 +0100, Paul POULAIN wrote:
> Owen Leon
On Wed, Nov 12, 2008 at 7:19 PM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
> Hi all
>
> I am about to lock down a client Koha site so that users *MUST* be
> logged in to access any page. In Koha/2.2.9 this was straightforward:
>
>vi `grep -rl "authnotrequired => 1" /usr/local/koha/`
>
>an
Galen,
Thank you for getting started on this.
John
+---+
John Chadwick, Ed.D.
Information Technology Manager
New Mexico State Library
1209 Camino Carlos Rey
Santa Fe, NM 87507
505-476-9740
505-476-9761 (FAX)
[EMAIL PROTECTED]
-Original Message
Owen Leonard a écrit :
>> here is the catch, i suspect even a wav file needs a plug-in to play
>> correctly
>
> This is the case in my tests on Windows.
The sound will have to be played only on circ-desk (not on OPAC or on
all library computers)
So I think it's acceptable to have something needi
Joshua Ferraro a écrit :
> On Wed, Nov 12, 2008 at 9:39 AM, Galen Charlton
> I agree, capitalizing on the first word except for proper nouns I suppose.
http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2780 filed
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-
>> And what about the templates? They are often mind-bending to edit, and I've
>> seen no tools to assist in comprehending their structure.
>
> agreed...
The Perl scripts are mind-bending to me. I suspect it's whatever
you're most used to (I've spent WAY too much time in template world by
now). Bu
Hi,
On Thu, Nov 13, 2008 at 3:06 AM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
> Paul POULAIN wrote:
>
>> one thing that is a real shame is that, atm, if something fails due to
>> FK constraint, the user is NOT warned that something was wrong. he just
>> sees that the data has not be saved. That's
Rick Welykochy a écrit :
> Mason James wrote:
>
>> but i think we might have to allow either tabs or spaces from developers -
>> (thats perltidys behavior too afaik)
>
> Why would anyone indent with spaces?
we spoke of that a loonnnggg time ago.
I don't remember the details, but i remember that
On Thu, Nov 13, 2008 at 12:45 AM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
>
> As far as a standardised .perltidyrc, my only comment is "please
> explain!"
Hi again, Rick -
perltidy is a tool that attempts to format perl code in a consistent
way. That .perltidyrc file sets most things to the def
On Thu, Nov 13, 2008 at 12:45 AM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
> May I assume then that the answer to tab stops is:
>
> (*) yes, use them to indent
That doesn't seem to be historically the most preferred method. Here
are some statistics (that are probably lying in some way):
number o
Joe Atzberger wrote:
> The purpose of Table is to provide all the basic functionality that
> is reimplemented multiple times throughout Koha for each DB table.
> This code is considered experimental and does not yet supplant any
> production code. Please examine and test, like:
> use C4::Tabl
Mason James wrote:
> but i think we might have to allow either tabs or spaces from developers -
> (thats perltidys behavior too afaik)
Why would anyone indent with spaces?
> the important thing is a consistent indent length of 4, i think.
Hooray for that!
>> As far as a standardised .perltidy
On 2008/11/13, at 7:45 PM, Rick Welykochy wrote:
> Mason James wrote:
>
>> I don't know the history of this comment, but i wouldnt wotry too
>> much about it
>> its old and not very well enforced (at least)
>> I think we should all agree on a standardised .perltidyrc format,
>> and i vote fo
Paul POULAIN wrote:
> one thing that is a real shame is that, atm, if something fails due to
> FK constraint, the user is NOT warned that something was wrong. he just
> sees that the data has not be saved. That's really bad !
The INNODB driver for MySQL reports an error if the FK doesn't exist
21 matches
Mail list logo
