A single flag for "UI/UX" would be my first choice, with just "UI" being
second. Differentiating the two isn't going to produce a lot of useful
information at this juncture. Certainly fine with me to go ahead and add
something for it, though.
- Gabriel
--
You received this message because
On Wed, Jun 8, 2011 at 9:36 AM, Idan Gazit wrote:
> UI: "The sorting icon is ugly."
> UX: "Sorting is confusing."
>
> That being said, I agree that most people won't be able to make the
> distinction.
>
> I'd say that we should just add a single boolean flag. I don't want to call
> it "Design" so
UI: "The sorting icon is ugly."
UX: "Sorting is confusing."
That being said, I agree that most people won't be able to make the distinction.
I'd say that we should just add a single boolean flag. I don't want to call it
"Design" so as not to confuse people with DDN tickets. "UI/UX"? "DesignHelp"
On Jun 8, 12:25 am, Luke Plant wrote:
> On 07/06/11 11:32, Idan Gazit wrote:
> > I'd like to propose adding two flags to Trac, "UI" and "UX".
> So would it be better to have just "UI/UX"?
I totally agree that Trac needs something specific for this, as it's a
shame we have to remove admin-related
On 07/06/11 11:32, Idan Gazit wrote:
> Greetings, Earthlings.
>
> I'd like to propose adding two flags to Trac, "UI" and "UX".
Fine with me, with one query:
Is there a sharp enough distinction between these two for it to be
useful for there to be both "UI" and "UX" flags? Is the typical
contrib
Greetings, Earthlings.
I'd like to propose adding two flags to Trac, "UI" and "UX".
The impetus for adding these new fields is twofold: I'd like some hooks that I
can use to keep track of tickets related to design issues, but more importantly
this will allow me to say "Designers: here's where
