Hi Richard,

        >But that's not the case, either you didn't read the documentation
properly,
        >or I didn't explain it very well.

Nahhh, just my lazy side showing :)
Seriously, I didn't read it carefully enough.

Thanks for explaining it clearly.
I'm rewriting it now.

        >Another thing is that you're using the latest release I suspect, instead
of
        >the latest snapshot (or my one), so you are documenting some extensions
that
        >don't exist any more, like sprite.js.

Yup. I didn't know if everybody (like me) always goes for the beta instead
of the latest release. So I played it safe. :)
Anyway, I did it in PHP/MySQL but I come across some problems setting up the
online
database, so I opted for a HTML version of it for now. But the next version
will
definitely be PHP driven (as you could see it's a lot of methods!)

        >Of course if you are willing to update it regularly, I'd be more than
happy
        >to put it on the site (or mirror it) if you want.

Yeah, I'm willing to do update it, though at this stage it's just a list of
methods.
I will appreciate if you mirror it, as long as people understand that right
now it's
work in progress (but then again, what isn't?).

Of course what I want is for each link to have it's own page, describing it
with parameters and examples. That's another reason that I used the latest
release
and not a beta, to have a stable (in terms of functionality) version to
develop on.

        >Oh, I almost forgot to say, I already rewrote it with the correct code, it
        >renders in about 4 seconds now (download time not included)
        >check here:

Yikes! That's... wonderful. Thanks Richard!

        >If you decide to finish this job, it might be worth considering if you
can't
        >include the values from text files or something (or through php), so you
        >don't have to edit your html each time. This is what I did for my
"examples"
        >tree, all the code is written on the fly by a php script, which checks the
        >contents of directories on the server, and adds the nodes it needs.

I've got a version of it working locally on my comp that accesses a MySQL
database
where all the nodes are stored in a tree (each node or link has a ID, and a
parent_ID,
with parent_ID=0 being a top node). But I still have some problems with the
recursive function that I use to build the tree. I will be working on it
more
thouroughly though, and building a simple backoffice to update it more
easily.

thanks for excelent help,

Nuno Ferreira


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to