OpenGuides-Dev November 2005

openguides-dev@lists.openguides.org

13 participants
28 discussions

Geocoder.us Support
by crschmidt＠crschmidt.net 20 Nov '05

20 Nov '05

OGDev - A couple weeks ago I hacked support for Geocoder.us into OpenGuides. Admittedly, this is only useful for US guides, but it has made my life infinitely easier when adding guides - before I was keeping two tabs open and checking out Geocoder for each address, now that's taken care of in the backend for me. I'm merging my forked version of 0.47 to 0.51 today, and this is one of the changes that other people running US-based guides might want or need. I've attached a patch. It's not the cleanest solution in the world, but it's something. It should merge nicely against most versions, since the code surrounding it hasn't changed much. I don't know if this is desirable for the main branch, simply because most of the guides right now can't be helped by it at all, and the code is simplistic enough that it could be reproduced by anyone with a small amount of effort. However, it's here anyway. -- Christopher Schmidt Ning Developer

1 0

[OpenGuides] #11: Edit page category/locale selection
by crschmidt＠crschmidt.net 20 Nov '05

20 Nov '05

Now that trac is up and running, I went through all the open tickets and added my two cents to a fair number of them. One of them was ticket 11, regarding adding a javascript mechanism for selecting categories/locales. You can see the result of my work at http://boston.openguides.org/?id=Home;action=edit , under the Locales and Category sections. My comment below provides a brief summary of the way that I did it. #11: Edit page category/locale selection Comment: Okay, so I've tossed something for this together on the Boston OpenGuides site. * Created CGI::Wiki::Plugin:: Summariser, for generating metadata summary lists, http://crschmidt.net/projects/Summariser.pm * Added some code to wiki.cgi in edit_node(): {{{ my $summariser = CGI::Wiki::Plugin::Summariser->new; $wiki->register_plugin( plugin => $summariser ); my @categories = $summariser->metadata_list( type => 'Category' ); my @locales = $summariser->metadata_list( type => 'Locale' ); my %tt_vars = ( global_categories => \@categories, global_locales => \@locales, ... }}} * Added some code to edit_form.tt: {{{ [% FOREACH category = global_categories %] <a href='#' onclick="javascript:d=document.getElementById('categories');d.value = d.value + '[% category %]\n'; return false;"> [% category %] </a> * [% END %] }}} and the same for locales. It's not a *clean* solution by any means, but it works, and should get anyone else who's interested in attacking the problem a running start. -- Ticket URL: <http://dev.openguides.org/ticket/11> OpenGuides <http://openguides.org/> The OpenGuides city guides project

1 0

New dev site using Trac
by Dominic Hargreaves 19 Nov '05

19 Nov '05

I'm pleased to announce the availability of the new OpenGuides development site, <http://dev.openguides.org/>. This site integrates several resources we've been using before and should improve the workflow of the project. Dev wiki: Trac includes a wiki which we'll use as a replacement for <http://openguides.org/dev/> (which has broken). I've integrated most of the content of the old wiki, though I've dropped a few nodes that were no longer relevant. <http://dev.openguides.org/> is the front page of the wiki. Bugs: Instead of rt.cpan.org (which has proved rather cumbersome in the past) we'll use trac's ticketing functionality: I've integrated all the open RT tickets (and closed them with a reference to their trac URL) and you can see a report of all active tickets at <http://dev.openguides.org/report/1>. You can report new bugs at <http://dev.openguides.org/newticket>. SVN browser: We didn't have any nice web view of the source before; now we have <http://dev.openguides.org/browser> which is a good way of viewing changesets and file histories, and so on. The SVN repository itself remains at <https://urchin.earth.li/svn/openguides/> Timeline: <http://dev.openguides.org/timeline>, and its associated RSS feed, provides a good overview of OpenGuides development activity. If you use RSS I recommend you subscribe to the feed. Email notifications: Changes to tickets get emailed to the mailing list <http://urchin.earth.li/mailman/listinfo/openguides-tickets> which you may want to subscribe to (as a companion to <http://urchin.earth.li/mailman/listinfo/openguides-commits>. All these things link in rather nicely, so you'll see references in changeset logs, tickets and wiki pages referring to reach other. Please take a few minutes to browse through the Trac user documentation at <http://dev.openguides.org/wiki/TracGuide> for how to use Trac most effectively. Currently, all day-to-day aspects of trac can be used without logging in. However I recommend that regular users of the site register for an account by emailing me an htpasswd password hash or plain text password, and their preferred username. Then they can be referred to as a simple username rather than an email address. In time I reserve the right to restrict certain operations to registered users, if spammers get hold of the site. Note that people with commit access to SVN should be using the same usernames but different passwords. This is due to the increased security on the SVN site compared to Trac (ie it's SSL-protected). Please address any comments about Trac to me or to the mailing list, and enjoy! Thanks are due to Earle and Ivor for suggesting the use of this fine package, and to Edgewall Software for developing Trac. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

1 0

OpenGuides 0.51 released
by Dominic Hargreaves 15 Nov '05

15 Nov '05

OpenGuides 0.51 has been released, with a number of bug fixes and improvements. It is a recommended upgrade. It will shortly be available from your favourite CPAN mirror, or if you're impatient http://www.larted.org.uk/~dom/computing/code/openguides/OpenGuides-0.51.tar… or, indeed, http://www.larted.org.uk/~dom/debian/openguides/. md5sum: aa72d47516445694c72d43f28cedae49 OpenGuides-0.51.tar.gz (files in this distribution are also signed with cpansign; run "cpansign -v" to verify.) Changelog: 0.51 15 November 2005 Important changes: * The preferred way to get RecentChanges is now to pass the CGI the parameter "action=rc", rather than just using the page name "RecentChanges". However, this method will still work for the time being. Similarly, the URL parameter for the RecentChanges RSS feed has changed from "action=rss" to "action=rc;format=rss". Requests for the former will be redirected to the latter. New features: * When trying to view a non-existent node, you will now be presented with a message asking if you want to create that node, rather than a blank page. * New "summary" metadata field for one-line summaries of nodes: - Add summary field to RDF as dc:description. - Show node summary in search results. * New "format=raw" option for outputting wiki text of a node. * RSS feed now contains DOAP (http://usefulinc.com/doap) metadata. RDF bugfixes: * Locales, address and summary fields now XML-escaped properly. * Add "address" field that was missing from the RDF node view. * Update URL for Dublin Core elements in RDF index view. * Fix URL in the RSS <channel> element to point to the RSS URL, not the RecentChanges page URL. Search bugfixes: * Fix bug that was breaking coordinate entry fields on search page if lat/lon was being used. * Fix bug in OpenGuides::SuperSearch that wasn't passing "latitude" and "longitude" values to the search template when a distance search was being done. Minor improvements: * Replace underscores in node names in "redirected from" message with spaces. * "Redirected from" message now links to a rendered version of the old page rather than the editing view. Miscellaneous bugfixes: * Fix problem with newer Text::Wikiformat and blank nodes. * Fix bug in navbar template that caused warnings in the tests. Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

1 0

Changes in 0.51
by Earle Martin 11 Nov '05

11 Nov '05

Here is the current Changes entry for OpenGuides 0.51. Please feel free to comment. (Note: the latest version of Changes is always available at https://urchin.earth.li/svn/openguides/trunk/Changes .) -- Earle -------- Important changes: * The preferred way to get RecentChanges is now to pass the CGI the parameter "action=rc", rather than just using the page name "RecentChanges". However, this method will still work for the time being. Similarly, the URL parameter for the RecentChanges RSS feed has changed from "action=rss" to "action=rc;format=rss". Requests for the former will be redirected to the latter. New features: * When trying to view a non-existent node, you will now be presented with a message asking if you want to create that node, rather than a blank page. * New "summary" metadata field for one-line summaries of nodes: - Add summary field to RDF as dc:description. - Show node summary in search results. * New "format=raw" option for outputting wiki text of a node. * RSS feed now contains DOAP (http://usefulinc.com/doap) metadata. RDF bugfixes: * Locales, address and summary fields now XML-escaped properly. * Add "address" field that was missing from the RDF node view. * Update URL for Dublin Core elements in RDF index view. * Fix URL in the RSS <channel> element to point to the RSS URL, not the RecentChanges page URL. Search bugfixes: * Fix bug that was breaking coordinate entry fields on search page if lat/lon was being used. * Fix bug in OpenGuides::SuperSearch that wasn't passing "latitude" and "longitude" values to the search template when a distance search was being done. Minor improvements: * Replace underscores in node names in "redirected from" message with spaces. * "Redirected from" message now links to a rendered version of the old page rather than the editing view. -- Earle Martin http://downlode.org/ http://purl.oclc.org/net/earlemartin/

3 2

The OpenGuides Project and Change Management
by IvorW 04 Nov '05

04 Nov '05

Observing a dialogue between hex and Dom yesterday on #openguides has set me thinking. We need to get our house in order. Kake predicted this a year ago, see http://openguides.org/mail/openguides-dev/2004-October/thread.html#575 I agree with Dominic that changes to 0.50 have been coming in too fast and furious to manage them effectively. Anyway, I have some practical suggestions and ideas: 1. Subversion has a good branching mechanism that works, let's use it! 2. The trunk is for releases. Don't check things in here unless they are ready for release. In fact, Dom or whoever is release managing, should be the only one touching the trunk. 3. For someone hosting a guide running different software from the latest release, it would be useful if this was in a branch. This would make bug reporting much easier. 4. Create separate branches for each chunk of work. The RT ticket number provides a good central reference point for this. 5. Post comments to RT indicating progress on each change. Every change should be tied back to an RT number. 6. Changes need tests. I've been as guilty as anyone for negleting this. Each RT branch should include either new tests or modifications to existing tests that would fail if run before applying the change. 7. Changes need airing. If you can either present the change on a guide you are hosting (mirrors help here :)), or if you can persuade someone else to patch a guide they are hosting, it would be desirable to expose the change to people in the OG community for rigourous exercising. We need more beta sites for this. I will be hosting such in the near future - watch this space. 8. Even if you don't have commit access to the master OpenGuides repository, you can always run a local repository. In fact, I recommend mirroring the repository even if you do have commit access. svk is your friend here :). clkao++ svk rocks! see http://svk.elixus.org/ These are my thoughts on change management; the list is probably not complete, but enough ideas to make a start. Ivor.

2 2

Nominet and bogus openguides donation
by Justin Davies 04 Nov '05

04 Nov '05

Hey guys, I run www.buddyping.com and will probably be integrating Openguides into it to essentially mobilise your content to our users (if that is ok with you?). Let me know. The other thing is that if you want to pursue the Nominet claim, I would like to stump up a contribution of £200 to get you started in the process of getting the funds together. This is regardless of whether it is ok for me to integrate openguides with buddyping by the way. J - - -- ---- ----------------------------------------- --- -- - - Justin Davies :: CEO/CTO email: justin(a)buddyping.com web: www.buddyping.com - - -- ---- -------- ----------------------------------------------- ------- --- -- - -

2 1

OpenGuide to Boston
by crschmidt＠crschmidt.net 02 Nov '05

02 Nov '05

A discussion on LiveJournal earlier today led to me actually spending some time with The Open Guide to Boston earlier today. The result of this came to be: * Redesign, adding some information to CSS and adding a header. * Adding support for Geocoder.us to look up addresses when a node is edited * Adding support for a "Map" view of all the nodes in the guide. This service (like so many others of its kind) uses Google Maps to display the data. Map view is avaialble via ;format=map on all index-list type pages, a la http://boston.openguides.org/?action=index;format=map * Adding Map View Support to the node pages, a la http://boston.openguides.org/?Full_Moon * Adding a significant number of nodes to the guide as starter content, mostly metadata only. As a result, I'm now willing to call the Open Guide to Boston open for business, and anyone who would like to contribute is welcome to do so. Over time I hope to incorporate a number of more advanced/complex features, but for the time being, I'm happy with the accomplishments of today, and would love to see more data added to the Guide. -- Christopher Schmidt

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 November 2005