Patrick Ohly > I have already verified manually that it is possible to replace > the <a href="javascript"></a> with a <form>...</form>, but this > doesn't really help I guess. Is there any way how I can cause > any of the plucker frontends to trigger a POST operation and then > include the result in the pdb file?
Python can handle posts. (url-fetching functions take an optional third argument of "data".) PyPlucker has some support for it, but not quite. (It may be urltext_key). To my knowledge, you would probably have to make code changes. Part of the catch is that post actions are supposed to involve the user saying "yes, I really want to do this", but get actions can be automatic. This means that at a properly designed site, GET is safe, but POST might order thousands of dollars worth of junk. You don't want that happening by accident. > Ideally, I'd let JPluck transform the starting page with XSLT > automatically. As I have never used XSLT before, I am looking for > an easier way to debug a stylesheet than running JPluck on > a page and looking at the resulting pdb: in particular, it would > be nice to get a serial dump of the parse tree that the stylesheet > is applied to and the result of the transformation. I agree, but can't offer much help just yet. I have heard that IE can use the same XSLT, which might speed your testing. "David A. Desrosiers" <[EMAIL PROTECTED]> > Using javascript to navigate between links is not HTML, > and Plucker shouldn't be expected to handle that. Plucker > also doesn't handle forms Is there anything that Plucker *should* handle? >From a user's perspective, we want to see the information on a web page, and our browser (including plucker) ought to handle any fetching for us - including authentication, cookies, and forms. It doesn't quite yet, but it is getting closer (particularly with jpluck) and should continue to improve. > Convert the links back to their native HTML equivalents, > and you'll see better results. There may not be one, if the post data is essential. (And if it weren't, GET would probably have worked.) > Perhaps the - --url-pattern options would help here. Apply > a regex to convert the invalid Javascript code to HTML, and > parse again. Hunh? Have you seen url-pattern doing something more than filtering which urls to fetch? Transformations (including regex) are good, but I haven't seen it in PyPlucker yet, and I haven't seen it in JPluck without XSLT (which he is still debugging). If you think it is there, please tell me where/how and save me some coding that I wouldn't get to this month anyhow. -jJ _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
