<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV dir=ltr>
<DIV class=gmail_extra>
<DIV class=gmail_quote>
<DIV><FONT size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><BR></DIV>
<DIV>It sounds to me like you should treat these text files as the data model
</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> Are you suggesting I do something to them, or
is this just a linguistic point about what to call or refer to the data
as?</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>I'm new to Catalyst and </FONT><FONT size=2>previously
coded in procedural perl, where I </FONT><FONT size=2>always used a policy of:
data - processing - layout.</FONT></DIV>
<DIV><FONT size=2>I equate that to Catalyst's Model - Controller - View.
</FONT><FONT size=2>However, my data was always text files, my processing was
cgi scripts, and my layout was always html templates.</FONT></DIV>
<DIV><FONT size=2>I now code with my processing as subroutines within *.pm
files within Catalyst's Controller folder,</FONT></DIV>
<DIV><FONT size=2>however I haven't touched the View or Model folders - am
still reading in html templates, substituting values, and spitting them out as
the response to the browser - all within my controllers - it's processing
after all.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>In short, I'm happy to call my text files the data model,
where before I would have called them the data.</FONT></DIV>
<DIV><FONT size=2>However - are you suggesting I do
anything?</FONT></DIV></FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>and yes, do not check it in to your repo.</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> I have no idea what repo is. Do you mean repository,
for a versioning system? Atm, my versioning system is to download the lib
folder from the dev server using Cyberduck, and put it in a folder on my
computer hard drive - the folder having a version number. Then I can
upload whatever version I want to the production server - normally the lib
from the latest version folder created. </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> Rather create a model class to access it</DIV>
<DIV><FONT size=2>---> I will have to research how to do this. My resources
include google search, and the Definitive Guide to Catalyst
book.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> and configure the path in you config file.</DIV>
<DIV><FONT size=2>---> At present, I am reading the path in from a separate
text file.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> When it comes to testing you are going to have to create a sample
of those text files under the t/ directory.</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> Still learning Catalyst and haven't touched testing.
I generally don't get it. Either a web app works, or is broken. I don't get
writing code to test if code works. Comes across as some sort of coding
narcissism.</FONT></DIV>
<DIV><FONT size=2></FONT><FONT size=2></FONT> </DIV>
<DIV>Having said that, you should probably find a way to use a database. It
sounds to me like your data would fit nicely into a database and your
permissions problems to be less significant.</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> Yes, I've painless experience of connecting to a
MySQL database. I just hoped I could use Catalyst whilst working in the same
simple way I worked before, where turn around was very fast. I just have one
small task to accomplish, and some files seemed the easiest quickest way to do
it, and I've hit all these permission problems, and I just thought it must be
such a common problem, someone is bound to have solved it - so I thought to
ask the group.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> Right now my solution is super simple - just use
spew, and avoid using append.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> If there's any advice or tutorials on how to sort
out permissions, or how to use text files as your model in Catalyst, I'd
appreciate it. </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>Hope that helps,</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> It was insightful, and has given me something to
research. Right now I don't understand enough about how Catalyst works to know
what creating a model class involves, and if it will solve the permissions
problem, or if it was just mentioned as a way of putting the data folder's
path into the config file. I shall look into it, and hopefully won't be
ignorant for too much longer.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> And thanks for getting back to me! =D</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>---> Yours,</FONT></DIV>
<DIV><FONT size=2>---> Andrew.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>Dermot.</DIV>
<DIV><FONT size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><BR></DIV>
<DIV><FONT size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><BR></DIV>
<DIV><FONT size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><BR></DIV>
<DIV><FONT size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><FONT
size=2></FONT><FONT size=2></FONT><FONT size=2></FONT><BR></DIV>
<DIV><FONT
size=2></FONT> </DIV></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>