137 0 false 2008-07-21T18:06:35+01:00 137 2009-01-10T00:00:00+00:00 14059 21 comments-should-be-formatted 9 11797 new comments markdown renderer textile 2008-07-21T18:06:35+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/21 0.5 This could be markdown, or textile, or something else. But it shouldn't let the format be set arbitrarily, as they could lead to Ruby execution. This could be markdown, or textile, or something else. But it shouldn't let the format be set arbitrarily, as they could lead to Ruby execution. <div><p> This could be markdown, or textile, or something else. But it shouldn't let the format be set arbitrarily, as they could lead to Ruby execution. </p></div> 137 0 true 2008-07-17T17:52:09+01:00 137 20 let-browsers-render-the-raw-response 19702 11797 resolved raw renderer 2008-07-17T18:11:47+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/20 Perhaps we can do that by setting the mime type? I don't know why Firefox wants it to be a RAW camera image file. Perhaps we can do that by setting the mime type? I don't know why Firefox wants it to be a RAW camera image file. <div><p> Perhaps we can do that by setting the mime type? I don't know why Firefox wants it to be a RAW camera image file. </p></div> 137 0 true 2008-06-05T00:15:10+01:00 137 2009-09-04T00:00:00+01:00 14060 16 i-want-syntax-highlighting 2 11797 resolved code renderer ruby syntax 2008-07-17T17:48:53+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/16 0.6 Maybe we could have a 'code' renderer, using the Syntax gem or something, that renders snips with syntax highlighting. The language the snip is written in could be an attribute of the snip? Maybe we could have a 'code' renderer, using the Syntax gem or something, that renders snips with syntax highlighting. The language the snip is written in could be an attribute of the snip? <div><p> Maybe we could have a 'code' renderer, using the Syntax gem or something, that renders snips with syntax highlighting. </p><p> The language the snip is written in could be an attribute of the snip? </p></div> 137 0 true 2008-07-02T22:56:01+01:00 137 2009-01-10T00:00:00+00:00 14059 19 the-pre-snip-should-show-the-raw-snip-contents 8 11797 invalid dynasnips parsing snip 2008-07-03T23:27:00+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/19 0.5 If pre is given a snip name, it should prevent any further processing of the snip contents. I.e. {blah} should not trigger an attempted snip inclusion. If pre is given a snip name, it should prevent any further processing of the snip contents. I.e. {blah} should not trigger an attempted snip inclusion. <div><p> If pre is given a snip name, it should prevent any further processing of the snip contents. I.e. {blah} should not trigger an attempted snip inclusion. </p></div> 137 0 false 2008-06-01T14:06:06+01:00 137 2009-01-10T00:00:00+00:00 14059 6 adding-additional-attributes-doesn-t-work 7 11797 new edit javascript snip 2008-07-02T21:43:34+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/6 0.5 If you need to add additional snip attributes (via the 'add' link on the form), the elements created don't work. It should be that when you enter a name in the text field (within the dt tag), it gets set as the name of the text area, but this behaviour isn't triggered for new pairs of text field and area created by the 'add' button. If you need to add additional snip attributes (via the 'add' link on the form), the elements created don't work. It should be that when you enter a name in the text field (within the dt tag), it gets set as the name of the text area, but this behaviour isn't triggered for new pairs of text field and area created by the 'add' button. <div><p> If you need to add additional snip attributes (via the 'add' link on the form), the elements created don't work. </p><p> It should be that when you enter a name in the text field (within the dt tag), it gets set as the name of the text area, but this behaviour isn't triggered for new pairs of text field and area created by the 'add' button. </p></div> 137 0 false 2008-06-02T00:29:37+01:00 137 2009-01-10T00:00:00+00:00 14059 12 upgrading-dynasnips-overwrites-any-changed-attributes 6 11797 new 2008-07-02T21:43:21+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/12 0.5 Like, for instance, editing the snip_template attribute of the kind dyna - running the rake upgrade:dynasnips will overwrite that mercilessly. Perhaps this indicates that customisation should happen in different snips? Like, for instance, editing the snip_template attribute of the kind dyna - running the rake upgrade:dynasnips will overwrite that mercilessly. Perhaps this indicates that customisation should happen in different snips? <div><p> Like, for instance, editing the snip_template attribute of the kind dyna - running the rake upgrade:dynasnips will overwrite that mercilessly. </p><p> Perhaps this indicates that customisation should happen in different snips? </p></div> 137 0 false 2008-06-04T01:58:27+01:00 137 2009-09-04T00:00:00+01:00 14060 15 dynasnips-should-be-able-to-take-arguments-from-the-url 3 11797 new dynasnips kind 2008-07-02T21:43:05+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/15 0.6 Wirhin the body of a dynasnip, I should be able to call something like @@@ def handle(name=nil) name = arg(:name) # ... end @@@ And have the value in 'name' be set either via snips parameters: @@@ {dyna my-name} @@@ Or have the value come from the URL: @@@ http://site/dyna?name=my-name @@@ An example this would be useful for is paginating the 'kind' dyna for going back into blog history. Wirhin the body of a dynasnip, I should be able to call something like @@@ def handle(name=nil) name = arg(:name) # ... end @@@ And have the value in 'name' be set either via snips parameters: @@@ {dyna my-name} @@@ Or have the value come from the URL: @@@ http://site/dyna?name=my-name @@@ An example this would be useful for is paginating the 'kind' dyna for going back into blog history. <div><p> Wirhin the body of a dynasnip, I should be able to call something like </p> <pre><code class="">def handle(name=nil) name = arg(:name) # ... end </code></pre> <p> And have the value in 'name' be set either via snips parameters: </p> <pre><code class="">{dyna my-name} </code></pre> <p> Or have the value come from the URL: </p> <pre><code class=""><a href="http://site/dyna?name=my-name">http://site/dyna?name=my-name</a> </code></pre> <p> An example this would be useful for is paginating the 'kind' dyna for going back into blog history. </p></div> 137 0 false 2008-06-01T14:40:02+01:00 137 2009-01-10T00:00:00+00:00 14059 8 it-should-be-possible-to-give-quoted-arguments-to-dynasnips 5 11797 new dynasnips parsing 2008-07-02T21:42:34+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/8 0.5 For instance, i should be able to do this: @@@ {link_to 'link text with spaces','snip name with spaces'} @@@ Or even @@@ {link_to 'link text with any.char! in it',snip_name} @@@ For instance, i should be able to do this: @@@ {link_to 'link text with spaces','snip name with spaces'} @@@ Or even @@@ {link_to 'link text with any.char! in it',snip_name} @@@ <div><p> For instance, i should be able to do this: </p> <pre><code class="">{link_to 'link text with spaces','snip name with spaces'} </code></pre> <p> Or even </p> <pre><code class="">{link_to 'link text with any.char! in it',snip_name} </code></pre></div> 137 0 false 2008-06-01T23:48:35+01:00 137 2009-01-10T00:00:00+00:00 14059 11 markdown-interacts-badly-with-dynasnips-using-underscores 4 11797 new markdown renderer 2008-07-02T21:42:14+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/11 0.5 Essentially, if a paragraph occurs like this: @@@ Here's a {link_to a-snip} and a {link_to another-snip}. @@@ then markdown will see the underscores and make the central portial italic. That's no good. The default render order is 1. pass the text through the special render stuff (i.e. Markdown) 2. process any references to snips ... but it seems like this should be the other way round. In this case. Or Markdown should be taught to ignore things in curly braces. As I recall, we can't flip the order because then markdown ends up processing content badly. Essentially, if a paragraph occurs like this: @@@ Here's a {link_to a-snip} and a {link_to another-snip}. @@@ then markdown will see the underscores and make the central portial italic. That's no good. The default render order is 1. pass the text through the special render stuff (i.e. Markdown) 2. process any references to snips ... but it seems like this should be the other way round. In this case. Or Markdown should be taught to ignore things in curly braces. As I recall, we can't flip the order because then markdown ends up processing content badly. <div><p> Essentially, if a paragraph occurs like this: </p> <pre><code class="">Here's a {link_to a-snip} and a {link_to another-snip}. </code></pre> <p> then markdown will see the underscores and make the central portial italic. That's no good. </p><p> The default render order is </p><p> 1. pass the text through the special render stuff (i.e. Markdown) </p><p> 2. process any references to snips </p><p> ... but it seems like this should be the other way round. In this case. Or Markdown should be taught to ignore things in curly braces. </p><p> As I recall, we can't flip the order because then markdown ends up processing content badly. </p></div> 137 0 false 2008-06-01T14:41:48+01:00 137 2009-01-10T00:00:00+00:00 14059 9 clicking-on-a-link-to-a-missing-snip-should-prompt-for-creation-of-that-snip 3 11797 new 2008-07-02T21:41:46+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/9 0.5 When going to a missing snip url, we should see a 'create' link. When going to a missing snip url, we should see a 'create' link. <div><p> When going to a missing snip url, we should see a 'create' link. </p></div> 137 0 false 2008-06-04T01:40:09+01:00 137 2009-01-10T00:00:00+00:00 14059 14 i-should-be-able-to-delete-snips 2 11797 new administration snip 2008-07-02T21:41:31+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/14 0.5 luke, for example, bad comments, old snips, outdated dynas and so on. luke, for example, bad comments, old snips, outdated dynas and so on. <div><p> luke, for example, bad comments, old snips, outdated dynas and so on. </p></div> 137 0 false 2008-06-01T14:43:03+01:00 137 2009-01-10T00:00:00+00:00 14059 10 snip-should-be-a-shortcut-to-link_to-snip 1 11797 new dynasnips parsing 2008-07-02T21:41:19+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/10 0.5 It's nice to be able to link very quickly when writing snips It's nice to be able to link very quickly when writing snips <div><p> It's nice to be able to link very quickly when writing snips </p></div> 137 0 false 2008-06-06T11:08:06+01:00 137 2009-09-04T00:00:00+01:00 14060 18 use-a-faster-markdown 1 11797 new markdown 2008-07-02T21:40:34+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/18 0.6 http://tomayko.com/writings/ruby-markdown-libraries-real-cheap-for-you-two-for-price-of-one Apparently the BlueCloth markdown is slow, although I don't see it being as broken as Ryan describes. Regardless, if we're doing lots of Markdown rendering (which my blog at least will), why not have it be fast? http://tomayko.com/writings/ruby-markdown-libraries-real-cheap-for-you-two-for-price-of-one Apparently the BlueCloth markdown is slow, although I don't see it being as broken as Ryan describes. Regardless, if we're doing lots of Markdown rendering (which my blog at least will), why not have it be fast? <div><p> <a href="http://tomayko.com/writings/ruby-markdown-libraries-real-cheap-for-you-two-for-price-of-one">http://tomayko.com/writings/ruby...</a> </p><p> Apparently the BlueCloth markdown is slow, although I don't see it being as broken as Ryan describes. </p><p> Regardless, if we're doing lots of Markdown rendering (which my blog at least will), why not have it be fast? </p></div> 137 0 false 2008-06-05T16:37:33+01:00 137 17 use-the-xml-base-attribute-for-relative-links 13336 11797 new atom kind 2008-06-05T16:37:33+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/17 See here: http://www.w3.org/TR/xmlbase/ See here: http://www.w3.org/TR/xmlbase/ <div><p> See here: <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a> </p></div> 137 0 true 2008-05-25T23:56:03+01:00 137 1 i-should-be-able-to-upgrade-an-existing-install-of-vanilla 13321 11797 resolved administration dynasnips snip upgrade 2008-06-04T23:51:32+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/1 The vanilla system should be easy to update on a running server. It should also upgrade any snips/dynasnips in the soup, but without: * losing any snips I've created * losing any customisations to snips that are installed by default The vanilla system should be easy to update on a running server. It should also upgrade any snips/dynasnips in the soup, but without: * losing any snips I've created * losing any customisations to snips that are installed by default <div><p> The vanilla system should be easy to update on a running server. It should also upgrade any snips/dynasnips in the soup, but without: </p> <ul><li> losing any snips I've created </li><li> losing any customisations to snips that are installed by default </li></ul></div> 137 0 true 2008-06-01T12:52:46+01:00 137 5 it-should-be-possible-to-create-comments 13325 11797 resolved comments dynasnips kind 2008-06-03T23:57:29+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/5 I want people to be able to comment on snips that I make. Probably either by adding a comment dyna to the bottom of the snip, or on a per-kind basis. I'm thinking something like this: @@@ Here's the snip contents Blah blah blah... {comments} @@@ The comments dyna should show any existing comments, and a form to add new ones. It should probably check them via a spam service. It should let anyone create a snip, effectively, but store their IP, author, email, site, content. It shouldn't let them choose the name of the snip that will hold their comments. I want people to be able to comment on snips that I make. Probably either by adding a comment dyna to the bottom of the snip, or on a per-kind basis. I'm thinking something like this: @@@ Here's the snip contents Blah blah blah... {comments} @@@ The comments dyna should show any existing comments, and a form to add new ones. It should probably check them via a spam service. It should let anyone create a snip, effectively, but store their IP, author, email, site, content. It shouldn't let them choose the name of the snip that will hold their comments. <div><p> I want people to be able to comment on snips that I make. Probably either by adding a comment dyna to the bottom of the snip, or on a per-kind basis. I'm thinking something like this: </p> <pre><code class="">Here's the snip contents Blah blah blah... {comments} </code></pre> <p> The comments dyna should show any existing comments, and a form to add new ones. It should probably check them via a spam service. It should let anyone create a snip, effectively, but store their IP, author, email, site, content. It shouldn't let them choose the name of the snip that will hold their comments. </p></div> 137 0 false 2008-06-02T10:05:37+01:00 137 13 we-should-avoid-recursive-rendering-if-possible 13333 11797 new dynasnips renderer template 2008-06-02T10:05:37+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/13 For instance, rendering the main template without 'text' or 'raw' formats causes recursion like crazy. The same is possible for a dyna that renders a call to itself. For instance, rendering the main template without 'text' or 'raw' formats causes recursion like crazy. The same is possible for a dyna that renders a call to itself. <div><p> For instance, rendering the main template without 'text' or 'raw' formats causes recursion like crazy. The same is possible for a dyna that renders a call to itself. </p></div> 137 0 true 2008-06-01T14:22:31+01:00 137 7 vanilla-should-respect-explicitly-set-created_at-and-updated_at-values 13327 11797 resolved edit snip 2008-06-01T14:27:41+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/7 While it's great that Vanilla gives us these free attributes, we should also be able to explicitly set them via the web interface (for example, for backdating old blog posts). While it's great that Vanilla gives us these free attributes, we should also be able to explicitly set them via the web interface (for example, for backdating old blog posts). <div><p> While it's great that Vanilla gives us these free attributes, we should also be able to explicitly set them via the web interface (for example, for backdating old blog posts). </p></div> 137 0 true 2008-06-01T12:48:55+01:00 137 4 dynasnip-attributes-changes-should-be-reflected-without-restarting-the-server 13324 11797 resolved 2008-06-01T13:57:51+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/4 At the moment, it looks like dynasnip attributes (ones set on the class and made available via method_missing) get cached, such that the class must be unloaded/reloaded for any changes to be made available. It would be much better if this didn't need to happen, so that (for example) people could change the snip_template in the kind dyna. At the moment, it looks like dynasnip attributes (ones set on the class and made available via method_missing) get cached, such that the class must be unloaded/reloaded for any changes to be made available. It would be much better if this didn't need to happen, so that (for example) people could change the snip_template in the kind dyna. <div><p> At the moment, it looks like dynasnip attributes (ones set on the class and made available via method_missing) get cached, such that the class must be unloaded/reloaded for any changes to be made available. </p><p> It would be much better if this didn't need to happen, so that (for example) people could change the snip_template in the kind dyna. </p></div> 137 0 false 2008-06-01T12:33:21+01:00 137 3 a-snip-should-be-able-to-set-the-feed-in-the-headers 13323 11797 new 2008-06-01T12:33:21+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/3 If a snip provides a feed, it should be automatically made available in the headers, so that browsers can detect its presence If a snip provides a feed, it should be automatically made available in the headers, so that browsers can detect its presence <div><p> If a snip provides a feed, it should be automatically made available in the headers, so that browsers can detect its presence </p></div> 137 0 false 2008-05-26T00:00:02+01:00 137 2 it-should-be-simpler-to-get-an-rss-atom-feed-for-a-set-of-snips 13322 11797 new 2008-05-26T00:00:02+01:00 137 James Adam James Adam James Adam http://lazyatom.lighthouseapp.com/projects/11797/tickets/2 Does that mean every snip needs a unique ID? Well, we could get that. But how to specify a set of snips? Well, we could easy get a set of snips via Soup. Perhaps there just needs to be an easy 'snip-to-atom-entry' transformation? Does that mean every snip needs a unique ID? Well, we could get that. But how to specify a set of snips? Well, we could easy get a set of snips via Soup. Perhaps there just needs to be an easy 'snip-to-atom-entry' transformation? <div><p> Does that mean every snip needs a unique ID? Well, we could get that. </p><p> But how to specify a set of snips? Well, we could easy get a set of snips via Soup. Perhaps there just needs to be an easy 'snip-to-atom-entry' transformation? </p></div>