On 28.03.2012 14:11, Fania Bremmer wrote:
* change title to Activity Settings (settings being less tech than
configuration and shorter, at least in english; use title capitalization)
+1. I would even prefer a title that integrates a verb, like edit activity.
But that's a wording question. I
* change Lock as private to just Private. the phrase Lock as
private is
a bit awkward (it is not a natural phrasing one would use in
conversation) and
specifying Lock speaks to the mechanism rather than the intention
of the
user. the intention is this is private; the mechanism we use is
On 28.03.2012 14:37, Fania Bremmer wrote:
I don't really like Lock as private, but if that's the one that fared best
with the users, I think we should still keep it. Don't know what it looks like
if it's placed next to the name, though. Might make the row a bit too long.
Keep in mind that we
Hi Dean,
Yes, sure, we could do an interview. I am working on the User Interface
Design side of things, so if the Interaction Part is interesting as
well, I could contribute that part.
Regards,
Fania
Am 27.03.2012 17:06, schrieb Dean Howell:
Plasma Active Team,
We at The Powerbase
On Tuesday 27 March 2012, Dean Howell wrote:
Plasma Active Team,
We at The Powerbase http://www.thepowerbase.com are probably the most
excited blog on the Internet when it comes to Vivaldi, Plasma-Active and
everything related to it. We want to bring some attention to the core team
and
Em Wednesday 28 March 2012, Marco Martin escreveu:
On Wednesday 28 March 2012, Thomas Pfeiffer wrote:
Ah, I see.
So what is the internal, technical workflow for switching an activity to
private (everything that happens from the point where the user taps
Save in the Activity configuration
Am 28.03.2012 17:27, schrieb Ivan Čukić:
instant apply is really not a possibility here for technical reasons. we
can get rid of the Close button though by making an outside tap close
and cancel the dialog.
Okay okay, so no instant apply. But can we still open the password setting
dialog
Sorry, but that comment just made me laugh: we would write why it can not
be like that; that shouldnt be the focus in a multi-disciplinary team, that
designers propose something and the techies just say no, not working.
Honestly, I don't see anything amusing there. If a designer asks for
we would write why it can not be like that.
the key word being 'why' - reason for not implementing something,
since we are devels, the reason usually is technical. I know, I need
to be less zen and more verbose sometimes :)
Whenever UX people write something, the developers
always say that
Hello ,
I am Arjun (ultimatrix on irc) .This is a follow up to the mail I posted
some days back. I was looking for a mentor who could guide me on the
project Write a QML based client to GHNS(Get Hot New Stuff) . My earlier
mentor can't mentor me anymore on account of being overloaded with
10 matches
Mail list logo
