[Dojo-interest] public dojo.Uri
jburke at dojotoolkit.org
Tue Apr 1 19:19:39 UTC 2008
Feedback given in this ticket:
I agree we probably need to make dojo._Url public, but I'm more in
favor of demonstrating where dojo._Url is insufficient and addressing
them within dojo._Url.
On Tue, Apr 1, 2008 at 1:09 AM, Wolfram Kriesing
<wolfram.kriesing at gmail.com> wrote:
> There is a tiny utility that needs some love in dojo,
> so I would like to get some votes/hints/etc on it to know
> what shall be the next steps.
> http://trac.dojotoolkit.org/ticket/5548 states very well
> "Given the how central URLs are to the web, it seems
> like dojo._Url should not be a private constructor."
> And in parallel I had created another ticket
> which in the latest implementation extends dojo._Url
> and provides dojo.Uri, that offers the following functionalities
> (where some are of course "borrowed" form dojo._Url)
> * URL parsing and providing access to the parts of it via
> properties: scheme, host, port, path, fileName, query, ...
> * allows to change parts of the URL and toString() it again
> * support for relative URL's
> * make a URL absolute isAbsolute(), getAbsolute("hostname", port)
> * parse the query and provide the property as an object, for interacting
> with like: url.query.foo
> looking forward to input, to get this tiny thing done :-)
> FAQ: http://dojotoolkit.org/support/faq
> Book: http://dojotoolkit.org/docs/book
> Forums: http://dojotoolkit.org/forum
> Dojo-interest at dojotoolkit.org
More information about the Dojo-interest