phpwiki-talk

[Phpwiki-talk] transform.php

[Thomas K. <th...@co...>]

Had anybody already thought about coding transform.php completely=20
in object oriented style ?

I`m thinking about reimplementing it in this manor:

a) First parse the WikiPage into a Structure of Objects=20
    (this part is totaly independent of html)

b) these objects have the ability to transform into different
    outputs (for example html, plain-text, TeX, ...)
   They get this ability mostly by inheritance from simple=20
   TransformationPrototypeClasses

Thomas

[Phpwiki-talk] transform.php

[Tara S. <te...@cl...>]

Hello again,

after having fiddled enough with my templates to make them xhtml strict=20
compatible, I'm attacking the big bit: transform.php.

I'm having a bit of a hard time figuring out everything (coding there is=20
  wayyyy too complex for my limited php knowledge), but I'm more or less=20
getting an idea of what I need to change.

One part which is resisting (there are probably others to come) is this o=
ne:

function wtt_bracketlinks($match, &$trfrm)
{
    $link =3D ParseAndLink($match);
    if (strstr($link['link'], "</form>")) {
        // FIXME: BIG HACK: see note in wtm_plugin.
        return "</p>" . $link['link'] . "<p>";
    }
    return $link["link"];
}

What is the </form> doing there? do I understand right, are we talking=20
about dealing with bracketed links?

Thanks for any explanations :)

Tara

--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] transform.php

[Jeff D. <da...@da...>]

On Sat, 10 Nov 2001 22:24:55 +0100
"Tara Star" <te...@cl...> wrote:

 
> function wtt_bracketlinks($match, &$trfrm)
> {
>     $link = ParseAndLink($match);
>     if (strstr($link['link'], "</form>")) {
>         // FIXME: BIG HACK: see note in wtm_plugin.
>         return "</p>" . $link['link'] . "<p>";
>     }
>     return $link["link"];
> }

If you read pgsrc/MagicPhpWikiURLs, you'll see that things like
'[phpwiki:TitleSearch?s=()]' gets transformed to a form.
The transformation is done by MakeWikiForm and LinkPhpwikiURL
which get called from ParseAndLink.

I think <form>s are not allowed within <p>s (you probably know
better than I about that) --- in any case, I remember that
<form>s within <p>s caused problems with CSS handling in certain
browsers.

(Of course, most bracket links, like [some page] or [http://a.b.com/c]
just expand to regular <a>'s.)

So the code is there so that if the bracket link expands to a <form>
tag, we close the current <p>, spit out the <form>, then open a new
<p>, so that no one will be the wiser.

It's buggy and ugly.  Sorry.  But I think the MagicPhpWikiURL forms
will be a thing of the past fairly soon, so it's probably not worth
worrying about too much.

As I said before, at some point I plan on taking another crack at
rewriting the transform code.

Re: [Phpwiki-talk] transform.php

[Steve W. <sw...@pa...>]

On Fri, 2 Mar 2001, Thomas Kalka wrote:

> Had anybody already thought about coding transform.php completely
> in object oriented style ?

The new one Arno wrote, or are you using 1.2?

> I`m thinking about reimplementing it in this manor:
>
> a) First parse the WikiPage into a Structure of Objects
>     (this part is totaly independent of html)
>
> b) these objects have the ability to transform into different
>     outputs (for example html, plain-text, TeX, ...)
>    They get this ability mostly by inheritance from simple
>    TransformationPrototypeClasses

What would the page objects be? For example, WikiSentence, WikiParagraph,
WikiLink, etc?

~swain

---
                  http://wcsb.org/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa