nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Better option than installing Config::Properties?

Tbag

Hi,

I'm *sure* there's something already installed in one of the various iw-perl/../lib folders, but I'm having trouble finding it.

I just want to be able to parse a "java standard" .properties file like:
someKey = someValue

The closest thing I could find to a perl module that already did all that work was the TeamSite::IW_Cfg module, but that's entirely too specific.

Short of installing Config: Smiley Tongue

roperties from cpan, does anyone know of something pre-existing that does what I'm looking for?

P.S. Before anyone rants at me about how easy it is to write something like this in 2 lines of perl . . . believe me, I KNOW. A client of mine puts a very high value on not re-inventing the wheel, so I'd have some egg on my face if I rolled my own only to have them point out a pre-existing module sitting right in the iw-perl/lib folder.

Find more posts tagged with

Comments

Migrateduser

P.S. Before anyone rants at me about how easy it is to write something like this in 2 lines of perl . . . believe me, I KNOW. A client of mine puts a very high value on not re-inventing the wheel, so I'd have some egg on my face if I rolled my own only to have them point out a pre-existing module sitting right in the iw-perl/lib folder.

I know what a pain in the **** that can be (i.e. having such a retarded customer) but what if you were to suggest that it will take you roughly 5 minutes to write and test the two lines of Perl versus the additional time it will take to install the module. While that's not much additional overhead, there is additional overhead in loading up Config: Smiley Tongue

roperties each time the script is run, however.

nipper

Well if you are a consultant that has done more than one of these implementations, then I suggest you write a generic constants/properties/etc PM along with a utilities PM. You probably already have done most of the work, just make it a PM.

Andy

Johnny

TeamSite::JavaResourceBundle

It's there and it's nice and easy... I believe the old solution workflows use it (it showed up around the same time they did)

Tbag

Duh. . . thanks for pointing that out, Johnny. I think I had glanced over that a couple weeks ago but got cold feet from all of the "#*** NOT READY FOR PRIMETIME" comments scattered through the module ;-0

Johnny

Nah... works like a treat! If you're worried, you could always copy it somewhere else (site/lib) incase it gets overwritten etc. Considering it's used by the solution workflows, I doubt there is anything to worry about.

nipper

****, this is pretty good. I have always just used a pm for constants and use something like this:

$dest_host = BigCo::Constants: Smiley Tongue

RODUCTION_SERVER;

I may need to change and use this instead. Cause I have not liked changing the pm to change a constant. But then if it is a constant, it should not need to change. Hmm, I wonder if Adam will chime in on that statement. Smiley Very Happy

Parameter.jpeg

Adam Stoller

****, this is pretty good. I have always just used a pm for constants and use something like this:

$dest_host = BigCo::Constants:RODUCTION_SERVER;

I may need to change and use this instead. Cause I have not liked changing the pm to change a constant. But then if it is a constant, it should not need to change. Hmm, I wonder if Adam will chime in on that statement.

Constants change over time and common sense isn't.

How's that?

Tbag

Constants change over time and common sense isn't.

How's that?

Zen.