Excerpts from MenTaLguY's mail of 23 Aug 2005 (EDT): > That doesn't sound like a bad idea, but I'm not sure how it could be > implemented easily (or what the commandline interface should look > like). Suggestions?
Entries can already have a 'modified' timestamp field. I'm not entirely sure how this is used now---I see it sporadically in my entries. If we coopt this field and have 'hobix post' insert it, set to the current time, in the YAML before opening any pre-existing entry, we can use this to determine whether to push it up the list or not. Quick-summaries order by the value of this field || the Storage timestamp, and the author removes this field from the YAML at re-edit time if he doesn't want the post pushed up to the top of the list. Some portions of this behavior may already be the case. I forget. Do we want the same behavior across all quick-summaries, not just "syndication" ones? (Fuzzy distinction IMO.) -- William <[EMAIL PROTECTED]> _______________________________________________ Hobix-is-the-way mailing list [email protected] http://rubyforge.org/mailman/listinfo/hobix-is-the-way
