Community
Participate
Working Groups
Build ID: n/a Steps To Reproduce: 1. Join #eclipse 2. Type ~list 3. Nothing happens! More information: A Better option: 1. Join #eclipse 2. Type ~list 3. KOS-MOS responds via private msg with list of available commands. Alternatively, command could be ~commands (or both ~list and ~commands could work). Note: ~commands is currently mapped to point to the wiki with the promise of a list of commands, except <https://bugs.eclipse.org/bugs/show_bug.cgi?id=201751> prevents the wiki from being a useful provider of mapped commands.
It'd have to do this at a very slow pace or something. Attempting to send too many messages at a time will get the bot kicked off of the server. The 'commands' command has been removed for the time being to prevent confusions.
what about a request to copy the latest version of the source properties file into the webserver root on ecf.eclipse.org, then have the bot spit back a link to that page? We could get fancy and add a properties-file-to-wiki-markup converter which would not only copy the file but reformat it so it would be easy to just cut n' paste that into the wiki. Of course at that point there's no need since the file on ecf.eclipse.org could just be linked to from the wiki, negating the need to clone the information in two places / two formats. If you give me details about how the webserver is structured on ecf.eclipse.org (I assume the web root is in /var/www/html/) and where on the server the properties file lives, I can cobble together a patch for this.
The web root is in /var/www/html as you guessed, which loads http://ecf.eclipse.org. The properties file is currently in /home/rcjsuen/bot/plugins/org.eclipse.ecf.presence.bot.kosmos_1.0.0.200709281923/messages.properties.
Created attachment 81002 [details] patch to add ~list command copies messages.properties to /home/rcjsuen/public_html/IRC_bot_messages.txt, then echoes a pointer to that URL to the requesting user.
Created attachment 81003 [details] same patch again w/ linux line endings (much smaller patch)
Y'know, a simpler approach would be to just symlink the messages.properties file from inside your ~/public_html folder ... ;-) might still be better to dump the contents as HTML instead of just a verbatim copy. thoughts? eg., instead of keyword=some bit of text we could dump <li><b>keyword</b>: some bit of text</li> or <tr><td><b>keyword</b></td><td>some bit of text</td></tr> just so it's more legible...
(In reply to comment #6) > might still be better to dump the contents as HTML instead of just a verbatim > copy. thoughts? Right. The file right itself is not very readable in its raw form since there is no spacing whatsoever.
Created attachment 81548 [details] generate html output this version outputs a simple HTML table instead of just copying the properties file to a text file; also turns URLs into links and makes ~commands appear red so they're more visible
Fixed in CVS HEAD. Thanks Nick, for the patch, I had to do some tweaking, but whatever.
Yes, as discussed it makes more sense to update the HTML file with every change to the properties file rather than just when people fire a ~list command. Next time I'll make sure I get all the NLS markers in place and format multi-line strings according to the ECF style guide. ;-)
closing
