The Oxford Guide - Differences between Version 80 and Version 28 of Comments

Version 80 Version 28
== Line 0 == == Line 0 ==
You should probably use the ticketing system now:
PhilH: this is an interesting project, i'm afraid i'm not familiar with Wiki sorry in advance for any cockups i may make ;)
== Line 2 == == Line 2 ==
* [http://dev.openguides.org/query?component=oxford.openguides.org Existing tickets]
* [http://dev.openguides.org/newticket?component=oxford.openguides.org New tickets]
* Welcome. I'd heartily recommend that you read [[House Style]]; it'll make your contributions much more valuable. --[[Dom]]
== Line 7 == == Line 6 ==
The RSS feed for recent changes seems to be invalid, according to [http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.ox.compsoc.net%2Foxfordguide%2F%3Faction%3Drss this feed validator]. Apparently it's being served with the wrong Content-Type and there's confusion as to its encoding. I believe this may be causing [http://www.livejournal.com/support/see_request.bml?id=305929 this problem with LiveJournal syndication] - [[PerfDave]]
James: Would it be possible to alter the long/lat display from the decimal representation to the more usual degrees and minutes representation? Streetmap appears to use this representation.
== Line 9 == == Line 8 ==
See http://dev.openguides.org/ticket/28 --[[Dom]]
* [http://search.cpan.org/author/PKENT/Geography-NationalGrid-1.6/lib/Geography/NationalGrid.pm Geography::NationalGrid] seems to have a method to do this, so yes. I'll add it to the next release as an option in Preferences. --[[Kake]]
== Line 13 == == Line 12 ==
Can we get the edit form to insist that the user includes a comment describing their change? I keep forgetting to include something in this field. - [[PerfDave]]
James: My spelling is bad I know. Is it possible to add some sort of spell check? Even if it's just a list of mispelled words so I can go back and re-edit the entry?
== Line 15 == == Line 14 ==
See http://dev.openguides.org/ticket/12 --[[Dom]]
* Not my itch; patches welcome :) --[[Kake]]
== Line 19 == == Line 18 ==
Should new [[Comments]] be added to the top or the bottom of this page? - [[PerfDave]]
Dom: Perhaps we need specific metadata entries for URLs to other guides/reviews?
== Line 21 == == Line 20 ==
Pass. It's ugly and I'd rather we either used the mailing list or the ticketing system :) --[[Dom]]
* Could do, yes — I mainly worry about making the edit form overcomplex and huge. But this is something the RDF people are interested in, so I'll probably add it. --[[Kake]]
== Line 25 == == Line 24 ==
Should Colleges be in [[Category The University]]? --[[Dom]]
Dom: I can't decide how streets should work, exactly. I <i>think</i> that all streets should be created as Locale links in text, along the lines of ((Locale Foo Street | Foo Street)) (those should be square brackets, but the nowiki tag doesn't seem to work). Then if the locales are important they will be clicked on/otherwise created, and used, if not, no harm done. Perhaps we should even have a macro for this. The idea is that you can easily get a list of all things in a specific street. I'm not entirely convinced by all this, though.
== Line 27 == == Line 26 ==
----
James: I think this would probably improve things, it would make it a lot easier for people to properly link their entries. Otherwise having streets as entries forces the author to actually go and edit the entry for a street to link the entry in properly. Just my 2p.
== Line 29 == == Line 28 ==
Square brackets around links to external pages look ugly. Is there any chance of preventing them from being displayed? -- [[James]]
Kake: Making people explicitly write ((Locale Foo Street|Foo Street)) is a pain though, especially when you can just make Foo Street be a redirect to Locale Foo Street (ie, you only have to do it once).
== Line 31 == == Line 30 ==
* Not that I know of. I actually disagree in any case; it's a useful way of distinguishing between internal and external links, so I'd rather the convention was kept. --[[Dom]]
Dom: Ah, yes, I like this idea even more.
== Line 33 ==
* Couldn't that be done within the stylesheet? --[[James]]

* Stylesheet sounds like the best plan. I'll look into it unless someone else does first. --[[Kake]]

See http://dev.openguides.org/ticket/38 --[[Dom]]

== Line 41 == == Line 34 ==
I was wondering if the Clubs category should be renamed Nightclubs, or if it's unlikely that any other sort of club will appear. :) --[[Art]]
James: How about offering the wanted pages ordered by the number of times they are wanted as well as by alphabetical ordering?
== Line 43 == == Line 36 ==
* It's true that Clubs is potentially confusing as it could be used to mean University type clubs (ie societies). --[[Dom]]
* Oh, nice idea. That'll require a patch to CGI::Wiki, so I'll have a think about it. --[[Kake]]
== Line 47 == == Line 40 ==
James: My spelling is bad I know. Is it possible to add some sort of spell check? Even if it's just a list of mispelled words so I can go back and re-edit the entry?
James: Are inline images disabled or is this a bug?
== Line 49 == == Line 42 ==
* Not my itch; patches welcome :) --[[Kake]]
* Use img tags &#8212; it's done like this so you can put ALT and TITLE text in. --[[Kake]]
* However, I am fairly strongly against linking large photos inline. They disrupt the use of the site. If they *must* be included, then they should at least have width and height tags. --[[Dom]]
* Yeah, can we cut down on the images? I like small, fast-loading pages. Stick in links to images by all means, though.
--[[Kake]]
== Line 51 ==
See http://dev.openguides.org/ticket/39 --[[Dom]]

== Line 47 ==
James: Can the pages please be validatable HTML of some form or another? I'm trying to write a suitable stylesheet and it would make life a little easier, it's just a few loose &lt;/P&gt; tags I believe. Should the &lt;div id="... be &lt;div class="... ?
== Line 55 == == Line 49 ==
Dom: Perhaps we need specific metadata entries for URLs to other guides/reviews?
* Can you make me a list of the specific places where things need changing? Also, 'id' is a valid attribute for the 'div' element - it's for things that you only expect there to be one of. http://www.htmlhelp.com/reference/css/structure.html might be of help. --[[Kake]]
== Line 57 == == Line 51 ==
* Could do, yes &#8212; I mainly worry about making the edit form overcomplex and huge. But this is something the RDF people are interested in, so I'll probably add it. --[[Kake]]
* I think the problem is that &lt;hr /&gt; and <&lt;form&gt; ... &lt;/form&gt; aren't valid inside paragraph tags, you can spot this on most of the pages as far as I can tell. I could be wrong, but I think that's it. Thanks for the info about the id attribute, that cleared things up for me. -- [[James]]
== Line 59 ==
See http://dev.openguides.org/ticket/40 --[[Dom]]

== Line 62 == == Line 54 ==



James
: How about offering the wanted pages ordered by the number of times they are wanted as well as by alphabetical ordering?

* Oh, nice idea. That'll require a patch to CGI::Wiki, so
I'll have a think about it. --[[Kake]]
*
Might also be nice to replicate [[Wanted Nodes]] as a special case in OpenGuides. --[[Dom]]
*
Replicate how? --[[Kake]]
* I explained myself badly. What I mean is that Wanted Nodes should be a "special" page in OpenGuides
, such that it is a place people can submit names of things they want to be added to the guide, and it would be automatically included in the Wanted Pages page, and automatically deleted from both pages when the node exists. In fact, it's probably not that important to even have a list of the pages people have "manually" requested; it would just be a case of having a special case for the "backlink". I hope that makes slightly more sense. --[[Dom]]

----
Information about businesses etc needs a "last checked" field
. Otherwise people won't know how reliable it is - this will particularly be a problem for the opening hours and (less so) phone numbers, from experience with another system that records this kind of information. --[[Ganesh]]

See
http://dev.openguides.org/ticket/1 --[[Dom]]

----
See also [[Comments Archive]]
.

Kake: I'd encourage [[Category Contributors|contributors]] to make themselves a page so people can see who else is using this, for example [[Kake]], [[Dom]], [[James]], [[Art]]. We've found on [http://grault.net/grubstreet/ grubstreet] that it makes the guide feel like more of a community thing.
== Line 82 ==
edit_type='Normal edit'
== Line 85 ==
host='217.147.80.76'
== Line 87 ==
major_change='1'
== Line 92 ==
summary=''

PhilH: this is an interesting project, i'm afraid i'm not familiar with Wiki sorry in advance for any cockups i may make ;)

  • Welcome. I'd heartily recommend that you read House Style; it'll make your contributions much more valuable. --Dom

James: Would it be possible to alter the long/lat display from the decimal representation to the more usual degrees and minutes representation? Streetmap appears to use this representation.

  • Geography::NationalGrid seems to have a method to do this, so yes. I'll add it to the next release as an option in Preferences. --Kake

James: My spelling is bad I know. Is it possible to add some sort of spell check? Even if it's just a list of mispelled words so I can go back and re-edit the entry?

  • Not my itch; patches welcome :) --Kake

Dom: Perhaps we need specific metadata entries for URLs to other guides/reviews?

  • Could do, yes — I mainly worry about making the edit form overcomplex and huge. But this is something the RDF people are interested in, so I'll probably add it. --Kake

Dom: I can't decide how streets should work, exactly. I think that all streets should be created as Locale links in text, along the lines of ((Locale Foo Street | Foo Street)) (those should be square brackets, but the nowiki tag doesn't seem to work). Then if the locales are important they will be clicked on/otherwise created, and used, if not, no harm done. Perhaps we should even have a macro for this. The idea is that you can easily get a list of all things in a specific street. I'm not entirely convinced by all this, though.

James: I think this would probably improve things, it would make it a lot easier for people to properly link their entries. Otherwise having streets as entries forces the author to actually go and edit the entry for a street to link the entry in properly. Just my 2p.

Kake: Making people explicitly write ((Locale Foo Street|Foo Street)) is a pain though, especially when you can just make Foo Street be a redirect to Locale Foo Street (ie, you only have to do it once).

Dom: Ah, yes, I like this idea even more.


James: How about offering the wanted pages ordered by the number of times they are wanted as well as by alphabetical ordering?

  • Oh, nice idea. That'll require a patch to CGI::Wiki, so I'll have a think about it. --Kake

James: Are inline images disabled or is this a bug?

  • Use img tags — it's done like this so you can put ALT and TITLE text in. --Kake
  • However, I am fairly strongly against linking large photos inline. They disrupt the use of the site. If they *must* be included, then they should at least have width and height tags. --Dom
  • Yeah, can we cut down on the images? I like small, fast-loading pages. Stick in links to images by all means, though. --Kake

James: Can the pages please be validatable HTML of some form or another? I'm trying to write a suitable stylesheet and it would make life a little easier, it's just a few loose </P> tags I believe. Should the <div id="... be <div class="... ?

  • I think the problem is that <hr /> and <<form> ... </form> aren't valid inside paragraph tags, you can spot this on most of the pages as far as I can tell. I could be wrong, but I think that's it. Thanks for the info about the id attribute, that cleared things up for me. -- James

Kake: I'd encourage contributors to make themselves a page so people can see who else is using this, for example Kake, Dom, James, Art. We've found on grubstreet that it makes the guide feel like more of a community thing.


List all versions