Austin Moore

Alright, I'm off to lunch. Thanks for your help guys

@MichaelT just read those files into an array. Sometimes, we count lines, sometimes we put the file in it's own worksheet

Crap what field am I getting into

@GlenH7 That so good to know...

Whelp, I guess I'm just gonna stop caring about the project

But I'm doing that...

"Only those who are unconcerned about architecture, and, perhaps, are comfortable with the inertia of the day-to-day chore of patching the holes in these failing dikes, are content to work on such systems." I don't want this

ah

NCube?

I'm 21

For reference, I'm on my last year of a CS degree, working at this company to make money. So I'm not exactly an important person

He's not my boss, just a pest that my boss had me and a few others 'help'

@GlenH7 Yup thats what all the devs are frustrated at. He can't program, but he wants it in perl because he's says he wants to be able to maintain it. I've heard him say before though that he needs to learn perl because he has no idea what is going on

It's a stupid project. Luckily, its just a side one

And we do tons of work as well

Problem is that he still does tons of work

The purpose of this project is to save him time by automating the work he does

@MichaelT ah I see the point you were making now

I guess where the data is placed on the website is 'hardcoded' but at least I don't have to worry about borders, shifting cells down when I need to add a new field, borders

This guy also ends up adding in graphs and other excel goodies to help with data digestion. On a website, we could handle that for him. Each new worksheet could be a new page and on each page, I could just throw the data in a table at the bottom of the page. I don't have to worry about whitespace between each subsection, because each subsection is on a page. Styling would be handled via CSS, not these awful excel formats that you have to apply to each cell

I don't have to worry about cells on a webpage

@MichaelT I'm still wondering how I should get around the hardcoding issue though

@Ampt yeah apparently we're pci complaint. From what I can see though, nothing too sensitive is in them

@MichaelT I had thought just that. All the data is stored in text files (another problem, but by far not the biggest one) with the name of the file describing the data inside. Every few days, the data in these files are updated. We could definitely just grab the data and plug it into a website. I think that would be better too, because instead of this guy having to send out emails every month, people who are interested, could just go to the website

@MichaelT Yeah I remember switching over to Writer::XLSX but when I double checked, it was WriteExcel. I'll have to check why we went back to WriteExcel later

@ratchetfreak I am with you on that. The project is for this guy who likes to send out a monthly report on our assets. He wants everything to be formatted and pretty much done for him. Problem is, he ends up changing everything before he sends it out, so writing as a CSV wouldn't be much different than what we're sending this guy, but he wont have it... Aw well.

search.cpan.org/~jmcnamara/Spreadsheet-WriteExcel-2.40/lib/…

We're using Spreadsheet:WriteExcel

I'm back