[MTOS-dev] Template Listing Screen

Chris Hall chris at fozboot.com
Wed Apr 16 15:17:45 PDT 2008 

The latter issue is already captured as a fbz case:

http://bugs.movabletype.org/default.asp?74632

currently in triage. As for the former request, it seems like a valid  
use case, so I'll file a feature case for it.

- chris


On Apr 16, 2008, at 3:12 PM, Jay Allen wrote:

> *bump*  See below.
>
> -- 
> Jay Allen
> Endevver Consulting
> 415-200-6985
>
> On Fri, Apr 11, 2008 at 8:34 AM, Jay Allen <jay at endevver.com> wrote:
>> Byrne, I have but two simple questions:
>>
>>   1) What happened to Manual, asynchronously?  That is, I like to  
>> send
>>  everything through the publish queue but there are still some
>>  templates I don't even want to burden it with all the time.  So I'd
>>  like to turn them off, but when I build them, use PQ
>>
>>   2) I've seen nothing mentioned about caching yet.  Not having  
>> caching
>>  status indicated on the listings makes me very nervous for my  
>> clients
>>  and, relatedly, myself.  I can already hear the frantic calls from
>>  someone saying that their site isn't updating and then having to  
>> make
>>  a progressive drinking game out of checking every template's caching
>>  options.
>>
>>  That is all,
>>  --
>>
>> Jay Allen
>>  Endevver Consulting
>>  415-200-6985
>>
>>
>>
>> On Thu, Apr 10, 2008 at 1:07 PM, Byrne Reese <byrne at sixapart.com>  
>> wrote:
>>
>>
>>> Ok - we are going to need to clearly lay out this change, and  
>>> this relates
>>>  the nomenclature of the various publishing options in general.
>>>
>>>  First - the intention is for the publishing option column to  
>>> replace the
>>>  need for "rebuild with indexes". Let me explain the various  
>>> publishing
>>>  options and what they mean. Then let me proposes a revised set  
>>> of labels for
>>>  these options and then get your feedback.
>>>
>>>  * "Statically" - publish normally and synchronously. For index  
>>> templates, it
>>>  means "publish with other index templates."
>>>  * "Asynchronously" - publish in the background via publish queue.
>>>  * "Dynamically" - publish dynamically.
>>>  * "Manually" - this applies to index templates only and  
>>> correlates to the
>>>  setting of an index template that is NOT published with index  
>>> templates
>>>  * "Disabled" - this applies to archive maps only and prevents  
>>> that map from
>>>  being published at all.
>>>
>>>  Question #1 - does this make sense to everyone?
>>>
>>>  OPTION 1 (simple):
>>>
>>>  * "Normally"
>>>  * "In the background"
>>>  * "Dynamically"
>>>  * "Manually" (for indexes)
>>>  * "Do not publish" (for maps)
>>>
>>>  OPTION 2 (technical):
>>>
>>>  * "Synchronously"
>>>  * "Asynchronously"
>>>  * "Dynamically"
>>>  * "Manually" (for indexes)
>>>  * "Disabled" (for maps)
>>>
>>>  OPTION 3 (specific):
>>>
>>>  * "Statically (synchronously)"
>>>  * "Statically (asynchronously)"
>>>  * "Dynamically"
>>>  * "Manually" (for indexes)
>>>  * "Disabled" (for maps)
>>>
>>>  Question #2: Thoughts?
>>>
>>>
>>>
>>>
>>>  On 4/10/08 7:03 AM, "Mark Carey" <mark at mt-hacks.com> wrote:
>>>
>>>> I agree with all of Jay's comments, and I have one more to add:
>>>>
>>>> (Note: I haven't tried the beta yet, so comment is based only on  
>>>> screen
>>>> snaps.)
>>>>
>>>> There doesn't appear to be a way from the listing screen to tell
>>>> whether an index template is set to "build with indexes".  Such an
>>>> indicator is VERY, VERY, important IMO (and more important than the
>>>> 'linked to file' indicator).  Some sites (rightly or wrongly)  
>>>> have a
>>>> large number of index templates and some of them are not not set to
>>>> rebuild with indexes (usually for performance reasons).  Being  
>>>> able to
>>>> see at a glance which indexes get built with indexes is a "must  
>>>> have"
>>>> feature in my view....
>>>>
>>>> -Mark
>>>>
>>>> On Wed, Apr 9, 2008 at 9:44 PM, Jay Allen <jay at endevver.com> wrote:
>>>>> On Wed, Apr 9, 2008 at 5:00 PM, Beau Smith <beau at sixapart.com>  
>>>>> wrote:
>>>>>> What do y'all think of the new template and widget listing  
>>>>>> screens?
>>>>>>
>>>>>>  http://www.movabletype.org/2008/04/ 
>>>>>> movable_type_415_beta_1_now_av.html
>>>>>
>>>>>  Hey Beau,
>>>>>
>>>>>  Thanks for asking.  As someone who lives in these screens, I  
>>>>> do have
>>>>>  some feedback.  Actual *constructive* feedback.  :-)
>>>>>
>>>>>  Frankly, I'm mixed.  I definitely DO like having access to all  
>>>>> of the
>>>>>  templates from one screen and I love seeing the output file/ 
>>>>> archive
>>>>>  path right there in the listing.  It's a very nice efficiency
>>>>>  improvement. However, there are a few things big and small  
>>>>> that bother
>>>>>  me in using it:
>>>>>
>>>>>   1) I would like to be able to act on templates of different  
>>>>> types
>>>>>  together via the buttons and/or itemset action dropdown.
>>>>>   2) The Quickfilters aren't as quick as I'd like, requiring a  
>>>>> page
>>>>>  load instead of simply filtering the list with Javascript.
>>>>>   3) Once I use the QuickFilter, I can't figure out how to get  
>>>>> BACK to
>>>>>  the full all templates listing without going to Design >  
>>>>> Templates in
>>>>>  the top nav.
>>>>>   4) I'm worried that the listings might be missing some really  
>>>>> crucial
>>>>>  pieces of data in the template options which could make debugging
>>>>>  certain template issues maddening, but I will admit that I  
>>>>> have not
>>>>>  enabled caching for ANY templates so perhaps you guys handled  
>>>>> this
>>>>>  well with the "Publishing" column.
>>>>>
>>>>>  My hopes for this combination of pages would best be described by
>>>>>  looking at, for example, iTunes.  I was hoping for one big old  
>>>>> list of
>>>>>  templates with various columns display relevant and important  
>>>>> metadata
>>>>>  for each.  All of the templates could be acted on as one  
>>>>> (except in
>>>>>  cases where it didn't make sense, like deleting system  
>>>>> templates) and
>>>>>  the listing could be filtered dynamically by name, type or other
>>>>>  metadata without having to do the whole page reload (like the  
>>>>> iTunes
>>>>>  search bar filter and/or browser functionality).
>>>>>
>>>>>  I certainly understand that there are OTHER usability issues  
>>>>> to deal
>>>>>  with when you combine the templates into one large listing but  
>>>>> I was
>>>>>  pretty confident that those could be solved to make the  
>>>>> experience
>>>>>  easy to understand AND super-efficient.  I do think that this  
>>>>> is an
>>>>>  improvement assuming that the navigation BACK to the unfiltered
>>>>>  listing can be made obvious.  I just wish the filtering were a  
>>>>> little
>>>>>  more dynamic overall.
>>>>>
>>>>>  --
>>>>>  Jay Allen
>>>>>  Endevver Consulting
>>>>>  415-200-6985
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>  MTOS-dev mailing list
>>>>>  MTOS-dev at sixapart.com
>>>>>  http://www.sixapart.com/mailman/listinfo/mtos-dev
>>>>>
>>>> _______________________________________________
>>>> MTOS-dev mailing list
>>>> MTOS-dev at sixapart.com
>>>> http://www.sixapart.com/mailman/listinfo/mtos-dev
>>>
>>>  _______________________________________________
>>>  MTOS-dev mailing list
>>>  MTOS-dev at sixapart.com
>>>  http://www.sixapart.com/mailman/listinfo/mtos-dev
>>>
>>
> _______________________________________________
> MTOS-dev mailing list
> MTOS-dev at sixapart.com
> http://www.sixapart.com/mailman/listinfo/mtos-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.sixapart.com/pipermail/mtos-dev/attachments/20080416/accddf31/attachment-0001.html

More information about the MTOS-dev mailing list