[wp-hackers] WP 3.1 admin bar

[Chris Carter]

and you know -- it's just an admin bar really

I written edit_post_link() so many times; I could probably type it in my
sleep...

makes my life easier from the jump...

On Thu, Feb 17, 2011 at 2:25 PM, SWORD Studios <info at swordstudios.net>wrote:

> Chris is right that most people don't update (in my experience) usually
> they are too afraid to because they don't know what it means or what will
> happen.
>
> Also I think Chip is correct that people don't like change.  Look at
> Facebook they force change on their users UI and everyone hates it (at
> first) then they get used to it.
>
> Change scares people.  All of this can be equated to fear.
>
> Jesse
>
>
> On Thu, Feb 17, 2011 at 3:23 PM, Chris Carter <chris at 314media.com> wrote:
>
>> IMHO everyone ignores the yellow update bar anyway unless I specifically
>> tell them to click it :)
>>
>> -CCA
>>
>> On Thu, Feb 17, 2011 at 2:19 PM, Chip Bennett <chip at chipbennett.net>
>> wrote:
>>
>> > I don't believe that *most* users would do any such thing.
>> >
>> > I believe that *most* users, when they learn about a new feature due to
>> > that
>> > new feature changing something about the appearance or output of their
>> > site,
>> > are going to be quite unhappy that said new feature was enabled - and
>> thus,
>> > changed their site - without permission.
>> >
>> > New features that change the public-facing appearance or output of
>> users'
>> > sites should not be enabled by default.
>> >
>> > But, again: this argument was had months ago, and those who espouse my
>> > opinion lost that argument. There's really not much sense in re-hashing
>> it
>> > now.
>> >
>> > Chip
>> >
>> > On Thu, Feb 17, 2011 at 1:46 PM, Iain Cambridge <backie at backie.org>
>> wrote:
>> >
>> > > If it happened like that most people would either never find out about
>> > new
>> > > features, complain it wasn't enabled by default or claim their is a
>> bug
>> > > because it wasn't enabled.
>> > >
>> > > Iain
>> > >
>> > > On 17 February 2011 19:22, Blue Chives <info at bluechives.com> wrote:
>> > >
>> > > > Like it but it won't happen.
>> > > >
>> > > >
>> > > > On 17 Feb 2011, at 18:56, Mark E wrote:
>> > > >
>> > > > > +1 on that.
>> > > > >
>> > > > > On 02/17/2011 11:27 AM, Chris Williams wrote:
>> > > > >> I like that approach.
>> > > > >>
>> > > > >> On 2/17/11 9:39 AM, "Chip Bennett"<chip at chipbennett.net>  wrote:
>> > > > >>
>> > > > >>> I think there is merit, though, in the suggestion that the
>> feature
>> > be
>> > > > >>> turned
>> > > > >>> ON by default for NEW installations, and turned OFF by default
>> for
>> > > > >>> upgrades.
>> > > > > _______________________________________________
>> > > > > wp-hackers mailing list
>> > > > > wp-hackers at lists.automattic.com
>> > > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> > > >
>> > > > _______________________________________________
>> > > > wp-hackers mailing list
>> > > > wp-hackers at lists.automattic.com
>> > > > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> > > >
>> > > _______________________________________________
>> > > wp-hackers mailing list
>> > > wp-hackers at lists.automattic.com
>> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> > >
>> > _______________________________________________
>> > wp-hackers mailing list
>> > wp-hackers at lists.automattic.com
>> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> >
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>