Robert A. Rosenberg said: > If all you are interested in are the functions in one .js file, why not > just make up a page that links to that one file and then feed that page > into Firebug? There would then not be any other .js files to confuse the > issue. >
I thought of that, but had a feeling it wouldn't be so straightforward... anyway I just tried it, and as I suspected, it's a lot more complicated than it sounds. This isn't a general-purpose "standalone" JS library; it has a lot of dependencies on stuff from the other JS files that get sucked in to the same pages, as well as dependencies for the particular type of HTML pages it's expected to run in (looking for specific DOM elements, etc.). Firebug immediately stalled out complaining where's this? Where's that? I could work around those dependencies but it would be more trouble than it's worth. Charlie Garrison suggested: > Node.js... Text Filter... shebang... > Thanks, Charlie, but you're over my head there. It makes sense that I should learn how to use Node.js at some point, mostly to replace the PHP on my server, since I'm a fairly good (mid-level) JavaScripter but my PHP skills are pretty basic... but I have too many things on my plate already. I'm not going to mess with Node.js now. As for Text Filters and shebang... I've heard of them, but I don't even know what they are. I'm not saying these aren't good suggestions; it's just that making a printable list of active functions seems like it should be a fairly basic thing to do. I don't want to get sidetracked into learning entirely new skills (although that's always fun and tempting) when I'm just trying to troubleshoot my current project. The most direct way to make the list is to leverage the skills I already have, as much as possible. Thanks again! Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Sun, Mar 23, 2014 at 7:57 PM, Charlie Garrison <[email protected]>wrote: > Good morning, > > > On 23/03/14 at 4:06 PM -0400, Lawrence San <[email protected]> wrote: > > Charlie Garrison said: >> >> IOW, javascript knows the functions it just parsed, so let it give you >>> the >>> list. Will almost always be more accurate than a regex solution. >>> >>> I'm sure you're right... in theory that would be more accurate. Of >> course I >> don't know any way to run JavaScript on a BBEdit file directly; BBEdit >> doesn't contain an internal JS engine. I guess I could run a >> list-the-functions function in Firebug's command line, >> > > Node.js > > (from memory) > $ brew install node > > No need to use a web browser to run javascript. > > > The other drawback would (I think) be that I'd have to leave BBEdit >> entirely to do that, >> > > Use a Text Filter; no need to move away from your .js file. Create a text > filter that uses node.js to run your javascript code that examines the > source of your front window. > > I know, sounds complicated, but it's not. Have a look at a variety of > existing Text Filters; they are really just normal scripts with a shebang. > Use same idea to create one that runs javascript (node) instead of perl, > python, bash, etc. > > > > Charlie > > -- > Make-Tracks Secure Hosting Pty Ltd <http://www.make-tracks.com> > PO Box 141 <[email protected]> > Windsor NSW 2756 Australia Ph: +61 2 9043 0613 > > ** Take Control of Your Website ** > > -- > This is the BBEdit Talk public discussion group. If you have a feature > request or would like to report a problem, please email > "[email protected]" rather than posting to the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> > > --- You received this message because you are subscribed to the Google > Groups "BBEdit Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
