Forum OpenACS Development: OpenACS Developer tools

the extractor tool, i was talking up earlier this week is out and
ready for developers.

it can be downloaded from

http://www.zope.org/Members/k_vertigo/openacs-tools.tgz

it conforms to the latest additions to the query dispatcher xml
spec, as referenced on the bboard and the files in cvs.

i rewrote the extractor's parser so its a lot cleaner, faster (cut
running time in 1/3:), and does better assoc of queries->procs.

running it on the acs-packages cvs takes about 4.4s on my laptop,
with no abnormal errors. the errors that were generated were all
from library files that either use namespaces, do db calls outside
of procs, or db calls in ad_proc_register_filter. if people feel
that these types of things should be added in let me know.

theres a good amount of documentation included (including some auto
generated documentation of the apis).

i'm going to work on transforming the package files to html tomorrow
and then i'll start helping out with the port.

if you find any bugs, or have some comments post them here or email
me.

i've uploaded a tarball to
http://www.zope.org/Members/k_vertigo/openacs/package_html.tgz

which contains a nice set of html pages for browsing package
information. it includes a set of indexe pages that include packages
sorted by release date, number of dependencies, version number,
number of files, and also a detailed page for each packaged.

just untar and point your browser to the index.html

it would be nice if this could be setup on the web here on the
openacs.org, until a fully dynamic one based on either the apm or
sdm comes out.

please note that i'm moving the openacs-tools (the extractor) to
http://www.zope.org/Members/k_vertigo/openacs-tools.tgz

the script i used to write the html will be included in the next
release of the openacs-tools along with html generation for the
query files.

Dan's already working on workflow - let's not duplicate efforts.

Can you package up the query extractor by itself so we don't need to download things like pyXML in order to run the basic extractor?  Or am  I reading too much into your post?

I'm going to e-mail you some comments on the query extractor, overall it looks like a great start...

Kapil ... I just started talking to folks about package assignments via e-mail about five or six hours ago.  I don't think it's terribly fruitful to post every question I put to an individual here on the bboard.  Group discussions - yes.  Individual posts - that's way too much detail.  Dan informed me sometime yesterday or early this AM that  he was going to start in on acs-workflow, because the content repository has a dependency on it.

Jon Griffin is going to look into acs-notification.  He and I exchanged e-mails just a few hours ago (see above).

So ... give folks a chance to get back to me before you demand that I summarize everyone's answers in public, OK?  It's hard to summarize responses that have yet to hit my e-mail inbox.

For the record,
you didn't answer my question as to whether or not you wanted to work on templating for FIVE DAYS (I posted it on April 3rd).  The fact that  I turned elsewhere FIVE DAYS after asking you in public and getting no response either in public or via private e-mail isn't really an indication that I'm plotting in secret to assign packages to  others behind your back or whatever.

As soon as we figure out exactly how we're going to structure the tree and how we'll decide who can commit where I will work on getting a list of who is doing exactly what and on which package.

I can't move forward on this sub-issue until I hear from Ben, and he's  incommunicado this weekend.  I'm sure he'll get back to me on Monday and we'll get things figured out and published by Wednesday.  The machine belongs to his company so questions about access are by nature  going to be his to make, not the group.

Cut us a little slack, Kapil.  I wasn't going to mention that it took you FIVE DAYS to get back to me on my question about templating, but if you're going to slap me around in public I'm going to slap back!

As I mentioned in my e-mail to you regarding the query extractor, it looks like a great starting point but there are some additional things that could be done that would make it even better.  The extractor's a great idea, I really appreciate your doing it, and when improved it is  going to remove a tremendous amount of tedious work from our plate.

This is where you can really help us the most at the moment.  At the moment Ben (or I if he doesn't have time tomorrow) need to modify the query dispatcher to allow the rdbms to be spec'd in the queryset as a default, and the extractor needs to build them that way.  As I mentioned, you don't need to build the list of bindvars unless -bind is used, and querytype is no longer needed.

another release of the extractor tools is out. same place as before

http://www.zope.org/Members/k_vertigo/openacs

ChangeLog

mainly changes to become in line with the spec and comments made by don baccus.

• removed query_type tag in xml
• removed query text bind vars
• added in experimental support for -bind vars (i'm still trying to figure out whats supposed to go here.)
• made the default config file not require any extra libs
• cosmetic changes to output
• changed file output from .dbname.xql to -dbname.xql
• added in docs of new features
• checked xml output with pyxml

as for don's comments on this thread, i'm going to respond directly via email since IMO discussion of these comments in a public forum is of dentriment to the community.

-bindvars...NOTHING NOTHING NOTHING!

If it was needed by the query dispatcher, it would've been included.
IGNORE THEM.

(I've e-mailed more details to Kapil, but the spec didn't suggest we needed support for them in the query dispatcher, and the spec was reviewed by Dan Wickstrom and I, who both worked on the bindvar parts of the driver, i.e. we would know if support was needed so our silence wasn't entirely out of ignorance...)

I wrote a small perl script that swap the parameter value with
the parameter name in function calls.

obj_type    => 'acs_object',
description => 'area'

becomes

'acs_object',  -- obj_type =>
'area'         -- description =>

save the code bellow to a file.

--------
while (<>) {
    if (/(s+)(.*=>) (.*)/) {
            print "$1$3		-- $2
";
    }
    else {
	print $_;
    }
}
-----

execute it:

perl file_where_script_saved file_to_swap_paramteres.sql