Idea

+priority

 

 

+solution

show:typemenu ?

 

+example

Just added an inclusion in a +discussion - {{_L+screenshot2}} - intending to upload an image, but couldn't set it's type. Thought I would save, re-edit and set it's type, but it was (default) content view, so no menu. :-P

 

 

Is there a reason not to have this most of the time? I'm thinking that in any case where the type isn't input as a parameter or a *default setting

  --Gerry Gleason.....2013-03-13 20:13:29 +0000


reason is not to expose Wagneer decisions to Editors and reduce visual noise. discussed in related support ticket (linked to above)

  --Ethan McCutchen.....2013-03-13 20:21:38 +0000


Ok, I understand the reduce visual noise, but not the Wagneer decision part.

  --Gerry Gleason.....2013-03-13 20:43:44 +0000


I've gotten a lot of feedback that casual users of sites are confused when they see type: <BASIC> Think about it as a non-Wagn person. It makes you go "what the heck does that mean".  That's why I say it's in the Wagneering space.  Anything that requires knowledge of Wagn structures (types, sets, rules, references ... even cards) belongs in Wagneering space.

  --Ethan McCutchen.....2013-03-13 20:49:24 +0000


going to paste the current code to help explain current functionality:

      show_type_menu = if !params[:type]
        ( main? || card.simple? || card.is_template? ) and
          Card.new( :type_id=>card.type_id ).ok? :create #otherwise current type won't be on menu
      end

 

so basically:

1. don't show on forms specifically intended for specific types  (eg /new/Company)

2. do show otherwise when card is the main card, when the name is simple, or when you're working with a template, PROVIDED:

3. the default type would actually show up on the menu

 

  --Ethan McCutchen.....2013-03-13 20:50:05 +0000


Just played with it a bit, hunh! I either never knew or forgot that we could essentially override the data type of a card of one type with another type. Nifty.

  --John Abbe.....2013-03-14 03:48:17 +0000


Hmm, not sure I understand above?

 

re the example, in current functionality, "show:typemenu" is no easier than "type:Image". But I do kind of want to get rid of "type" as an inclusion option now that we've made the "right" way more accessible.

  --Ethan McCutchen.....2013-03-27 16:47:51 +0000


I wondering whether we might have an icon on the upper right corner of new forms that will give us a "full" form. it would basically let you override the default name and type where permitted. The "where permitted" is the key part. Need to generate ideas for how to reduce exposure of non-Wagneers to type interface

  --Ethan McCutchen.....2013-03-27 16:51:44 +0000

+relevant user stories