I'd prefer to keep the content simple so that it even works on "less capable" browsers.
So sticking with "plain HTML" or "plain text" is desirable in my view. With that said, I'm open to being convinced otherwise. 2008/6/27 Tom Mueller <[EMAIL PROTECTED]>: > How about an XML document with a reference to a XSLT stylesheet. > See: http://www.w3schools.com/xml/xml_xsl.asp > > Tom > > Shawn Walker wrote: >> >> The line between a depot operation and "web interface" is a bit blurry >> to me. To me, anything the depot server provides is a "web interface." >> >> I've completed Stephen's initial work on the RSS/Atom feeds for the >> depot repository to the point where I can get a live bookmark to show >> up for my local depot when publishing packages to the repository. >> >> However, one of the things that I need for that to work is to be able >> to link to something for each of the rss update entries. >> >> At the moment, I've just set it up to link to the /manifest/0/ for the >> package that was published. But that isn't very user friendly. >> >> As such, I'm considering adding /info/0/ to the depot server. So, >> visiting this URL: >> >> http://hostname/info/0/[EMAIL PROTECTED],5.11-0.91:20080620T101740Z >> >> Would return: >> >> Name: SUNWipkg >> Summary: >> State: Installed >> Authority: opensolaris.org (preferred) >> Version: 0.5.11 >> Build Release: 5.11 >> Branch: 0.91 >> Packaging Date: Fri Jun 20 10:17:40 2008 >> Size: 1.2 MB >> FMRI: pkg:/[EMAIL PROTECTED],5.11-0.91:20080620T101740Z >> >> As such, if a user subscribed to the rss feed provided by a depot >> server, they could just click a "live bookmark" entry (in FireFox) and >> be taken to that output. >> >> Should this output be rich output? (HTML) or raw in nature? (text >> identical to that which the client produces) >> >> Thoughts? >> >> > > -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
