On Mon, 2012-03-12 at 08:49 +0000, Robin H. Johnson wrote:
> On Mon, Mar 12, 2012 at 08:52:20PM +1300, Kent Fredric wrote:
> > On 11 March 2012 22:09, Brian Dolbec <email@example.com> wrote:
> > >
> > > eg:
> > >
> > > <irc>Channel #gentoo-guis on the freenode network</irc>
> > > or
> > > <irc>#gentoo-guis on the freenode IRC network, irc://irc.gentoo.org/gentoo-guis</irc>
> > >
> > Though a freeform text field is probably better for humans, I'd
> > suggest having more explicit data available as an option, ie:
> > <irc network="irc.freenode.org" channel="#gentoo-guis">Channel
> > #gentoo-guis on the freenode network</irc>
> +1 on this.
... and just when I was beginning to think no one actually cared
The proper form of an irc url is in my example
"irc://irc.gentoo.org/gentoo-guis" and I took it from gentoo's irc
channel page at http://www.gentoo.org/main/en/irc.xml .
That would mean limiting a single <irc></irc> field to just valid url's
just like the <homepage></homepage> field.
The other thing I find with your example is that layman no longer uses
that old style of xml. It still supports it, if you have that format
for some overlay definitions. But does not fit the current
Personally I would find it quite simple to use a reg expression to
extract a valid irc url from a mixture of written text and url.
<irc>#gentoo-guis on the freenode IRC network, irc://irc.gentoo.org/gentoo-guis</irc>
So far there is not a gui for working with layman, so is all command
line, including the output of layman -i some-overlay. Don't get me
wrong, I have nothing aginst a layman gui. I actually ended up taking
over layman's development because of it's lack of a good api for other
apps to use. Namely porthole. Plus I fully intend to create a
standalone gui for layman.
Would it be better that I create 2 irc sub data types then?
<description>#gentoo-guis on the freenode IRC network</description>
So far it seems many/most systems do not come setup to recognize and
take proper action for irc:// mime types like they do for http://
Brian Dolbec <firstname.lastname@example.org>