Hm, okay to clarify, "cvs" stands for "concurrent version system", which is to say, it's what keep track of the code that has changed, and is also what is used to synchronize changes among developers. So anything under cvs/ is the copy of the code that is used to coordinate code between developers. Anything not under cvs/ is your actual working site. You can find an equivalent for all files between your actual site and the code under cvs.
So: cgi-bin/Apache/BML.pm cvs/bml/lib/Apache/BML.pm
Are basically the same file, and you'd only need to edit one of them when making your patch -- in this case, cgi-bin/Apache/BML.pm.
Anyway, the mention of editpics in cgi-bin/Apache/BML.pm looks like an explanatory comment; yup edit it.
cvs/bml/lib/Apache/BML.pm - mirror of cgi-bin/Apache/BML.pm, so the patch you make will be affecting both. No need to edit this cvs/bml/test/fake_root/bml-test.correct - these three files are used to test whether BML is working correctly, but they're more sample text than anything else. They're not used on the actual site, so it's not critical that they match wrt editpics versus editicons. No need to edit. cvs/bml/test/fake_root/bml-test.bml cvs/bml/test/fake_root/global.look
editpics.js and editpics.css -- hmmmm. no harm done if they're not renamed, since CSS classnames and function names are not user-facing, so you don't *need* to rename them, but I say sure, go ahead and rename.
en.dat -- nah, no need to rename.
if ($inline .= LJ::Hooks::run_hook("cprod_inline", $u, 'EditPics')) { if ($inline .= LJ::Hooks::run_hook("cprod_inline", $u, 'EditPicsMax')) {
-- hmmmm. No, don't edit.
Quick explanation: hooks are basically a way to implement site-specific logic. Those lines above basically mean to try to do any site-specific logic which was implemented for an inline cprod identified by "EditPics" (and "EditPicsMax"). We haven't implemented any additional logic for cprods, so changing them won't affect us. However, we can't guarantee that other sites using DW code have done the same, so to be safe, don't change them.
no subject
So:
cgi-bin/Apache/BML.pm
cvs/bml/lib/Apache/BML.pm
Are basically the same file, and you'd only need to edit one of them when making your patch -- in this case, cgi-bin/Apache/BML.pm.
Anyway, the mention of editpics in cgi-bin/Apache/BML.pm looks like an explanatory comment; yup edit it.
cvs/bml/lib/Apache/BML.pm - mirror of cgi-bin/Apache/BML.pm, so the patch you make will be affecting both. No need to edit this
cvs/bml/test/fake_root/bml-test.correct - these three files are used to test whether BML is working correctly, but they're more sample text than anything else. They're not used on the actual site, so it's not critical that they match wrt editpics versus editicons. No need to edit.
cvs/bml/test/fake_root/bml-test.bml
cvs/bml/test/fake_root/global.look
editpics.js and editpics.css -- hmmmm. no harm done if they're not renamed, since CSS classnames and function names are not user-facing, so you don't *need* to rename them, but I say sure, go ahead and rename.
en.dat -- nah, no need to rename.
if ($inline .= LJ::Hooks::run_hook("cprod_inline", $u, 'EditPics')) {
if ($inline .= LJ::Hooks::run_hook("cprod_inline", $u, 'EditPicsMax')) {
-- hmmmm. No, don't edit.
Quick explanation: hooks are basically a way to implement site-specific logic. Those lines above basically mean to try to do any site-specific logic which was implemented for an inline cprod identified by "EditPics" (and "EditPicsMax"). We haven't implemented any additional logic for cprods, so changing them won't affect us. However, we can't guarantee that other sites using DW code have done the same, so to be safe, don't change them.