I hate when this happens to me, so I apologise, but I think we doubled-up here:
http://drupal.org/project/markup_snippets

Your module actually sounds cooler than mine, but if you haven't created any code yet (you haven't committed any, I see) it would be better for you to co-maintainer markup_snippets. I'm happy to give you access.

Comments

dagmar’s picture

Category: bug » support
Status: Active » Fixed

So, after a nice IRC conversation, we decide to mark this issue as fixed and keep both modules online.

(15:23:17) gregharvey: hi there
(15:23:39) dagmar: you know, I just created the project five minutes ago
(15:24:01) gregharvey: I know... I saw it roll past on Twitter and was curious ;)
(15:24:28) gregharvey: read the description and thought "that's markup_snippets, but better!"
(15:24:40) dagmar: well, lets see if our modules are similar
(15:24:47) gregharvey: ok
(15:25:25) gregharvey: shall I explain why we created markup_snippets and see if it's a similar use case?
(15:25:42) dagmar: Canned texts works in this way: You create a view, add a canned text display and this view will be rendered as a selec box in the node forms that you specify. Then, when a item is selected, the body of the node is loaded and pasted into the current selected area
(15:25:56) dagmar: it works also for body comments
(15:26:47) gregharvey: and the canned text is nodes?
(15:26:54) dagmar: yes
(15:27:05) gregharvey: title for selection purposes and body for loading in?
(15:27:20) gregharvey: ok, markup_snippets is very similar except it stores the "canned text" in its own database table
(15:27:25) dagmar: not really, you can define in the view which title do you want to see
(15:27:25) gregharvey: I like your way MUCH better :)
(15:27:36) gregharvey: ok, cool
(15:27:37) dagmar: something like My Text (by admin)
(15:28:00) dagmar: where are you snippets saved?
(15:28:04) gregharvey: did you see this? http://drupal.org/node/521074
(15:28:19) dagmar: yes I did
(15:28:39) dagmar: here is mine http://drupal.org/node/753036
(15:29:18) gregharvey: snippets are saved in a markup_snippets custom table ... just mid (to give them an ID), name and snippet
(15:29:26) gregharvey: very basic
(15:30:17) gregharvey: never occurred to me to use nodes as the storage medium, for some reason :/
(15:30:24) gregharvey: dur
(15:31:09) gregharvey: I'm not sure whether it's better to close markup_snippets and just have the canned_text module, or start a 6.x-2.x branch of markup_snippets
(15:31:29) gregharvey: I don't mind really... but it seems silly to run both projects and your module is definitely an improvement on mine
(15:32:15) dagmar: well, maybe your module is more appropiate for development tasks
(15:32:29) dagmar: I created this module to use in a ticket system
(15:33:05) dagmar: to make easy the task to answer the same thing many times
(15:33:37) gregharvey: that was our goal too, except it was for an events management site where many events have the same "boiler plate" description text
(15:33:49) gregharvey: just paste it in and change a few words
(15:34:16) gregharvey: it was actually written for this: http://www.economistconferences.co.uk (sorry about the Flash, that wasn't us! ;)
(15:35:03) gregharvey: though looking at admin, they've never actually used this feature! typical! ;)
(15:35:40) dagmar: mmm, well, I was thinking in views because you can use flag + views + canned text and make a dinamic list of canned text flaged by the current user
(15:36:02) dagmar: so, what do you suggest?
(15:36:07) gregharvey: nice, so different users can maintain their own sets of canned text
(15:36:46) gregharvey: I think I should close markup_snippets actually... since according to the stats there's ONE user (which would be us!)
(15:37:12) gregharvey: I can't think of any features it has which your module won't match
(15:37:30) dagmar: well, a table is more light than a node
(15:37:37) dagmar: a row table I mean
(15:37:56) gregharvey: I suppose so...
(15:38:07) dagmar: so, for a lot snippets managed by a single user your module may be a better choice
(15:39:09) dagmar: I don't know..
(15:39:24) gregharvey: well I could extend markup_snippets  to integrate with Views
(15:39:34) gregharvey: so get rid of the admin page and make it a provided view instead
(15:40:07) gregharvey: which would pave the way to merging the markup_snippets code with yours and simply offering two operating "modes"
(15:40:14) gregharvey: or do you think that over-complicates things?
(15:41:11) dagmar: mmm, in that case we have to decide which module will survive :D
(15:41:57) dagmar: In my opinion both modules can live if you keep your module more faster than mine
(15:42:12) gregharvey: ok, that makes sense...
(15:42:34) gregharvey: maybe I'll write a comparison table between the two and put it on my project page
(15:43:05) gregharvey: I still like the idea of making my admin page and selector widgets views instead of custom code
(15:43:16) gregharvey: do you think that's a good idea, or do you think it's just fine how it is?
(15:43:20) dagmar: great. ok, Do you have problems to paste this conversation as the answer of the issue?
(15:43:32) gregharvey: no, that's fine

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.