OpenGuides-Dev May 2012

openguides-dev@lists.openguides.org

6 participants
3 discussions

OpenGuides 0.67 released.
by Bob Walker 14 Feb '13

14 Feb '13

I uploaded the latest release of OpenGuides to CPAN this morning. https://metacpan.org/release/BOB/OpenGuides-0.67/ There have been lots of changes this release the most important of which are: Leaflet support for maps removes the need to rely on Google Maps. On map index pages you can now find Categories within Locales. JSON output has been added or improved on several types of pages. A long standing bug in recent changes has been fixed. There have also been numerous bug fixes. See https://metacpan.org/source/BOB/OpenGuides-0.67/Changes and http://dev.openguides.org/changeset?old_path=%2Ftags%2Frel0_66&old=1395&new… for more info. As you can see the tests have also been renumbered. This was done by adding a 0 inbetween the 2 existing digits. We now require Wiki::Toolkit 0.80 and introduced a new dependency on Template::Plugin::JSON::Escape. -- bob walker everything should be purple and bendy http://randomness.org.uk

4 21

"Last verified" dates
by Kake 01 Jun '12

01 Jun '12

Hello! On the train the other day I had some ideas about the way data input could work for a "last verified" field for OpenGuides. I drew a thing: http://www.flickr.com/photos/kake_pugh/7278918078/ This would result in three pieces of data, which will be stored if and only if the "re-confirm existence?" tickybox is ticked: - the date on which the existence of the business described was last checked (it should be possible to give either a specific day or just the month) - the method by which it was checked (free text, e.g. "phoned them up", but with a tickybox or two to make it easy to give standard reasons such as "went past and saw it open" - a tick in this box would be turned into text by the code before storing in the database) - the person who checked it (not explicitly entered on the form, but taken from the username of the person performing the edit - see above, this only happens if they explicitly choose to "re-confirm existence") Anyone got any thoughts on the above? Regarding the backend, here is some previous discussion on the point: http://lists.openguides.org/pipermail/openguides-dev/2007-June/001872.html Dom points out in that post that there are two ways of doing it: - as Wiki::Toolkit metadata - as a new field in the node/content tables Advantages of doing it as metadata: - No need to change Wiki::Toolkit databases in a way that is irrelevant to some wikis. - The "method of checking" data is really OpenGuides-specific, so should go in the metadata table, and then it would be nice to have the "date of checking" in there as well. Also, the "person who checked" data needs to go somewhere (this isn't always the same as the "person who last edited"). Then again, we already have a small inconsistency in that "date last edited" and "person who last edited" are in different tables. Advantages of doing it in the node/content tables: - We can store it as a proper date type, which saves some fiddling around in terms of actually using the data. Actually it strikes me that a third possibility would be to use plugins: https://metacpan.org/module/Wiki::Toolkit::Plugin though the Wiki::Toolkit plugin system never really got fully developed, and this might be an overcomplicated way of doing it for little benefit. Thoughts? Kake

5 9

OpenGuides 0.68 released
by Bob Walker 21 May '12

21 May '12

OpenGuides 0.68 has been released to CPAN. https://metacpan.org/release/BOB/OpenGuides-0.68/ This main purpose of this release to fix a bug introduced in 0.66. https://metacpan.org/source/BOB/OpenGuides-0.68/Changes -- bob walker everything should be purple and bendy http://randomness.org.uk

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

OpenGuides-Dev May 2012