I have to agree with this.
On Thu, May 26, 2011 at 11:01 AM, GonzO wrote:
> How about "keep things where I frakkin' put them"? ;-)
>
> I can't think of a single good reason why my scroll location on the
> bar *has to* reset itself once I leave. I scrolled to *this spot*
> because I wanted to b
On Thu, May 26, 2011 at 10:14 AM, ello wrote:
>
> With the theme I've got now - Orta -
Looks nice, I might have to try it.
> The
> problem with scrolling down the bar is difficult to solve - perhaps make
> the mouse "stickier" there, so it needs a determined movement by the
> user to free it?
On Wed, 2011-05-25 at 17:06 -0500, S. Christian Collins wrote:
> >
> I think this is a terrific idea. Allowing the user to choose the
> profile on first desktop login or during installation might be nice as
> well.
I agree with the idea of different profiles, but I don't know about
asking the u
> Although, truth be told, the more I think about it, the more I like
> the "Opera Idea" (title of app is an obvious button that exposes the
> pull-down menus vertically). While it does have two drawbacks I *do
> not* like -
>
> 1) The pull-down menus are semi-hidden by default (the button is vi
On Wed, May 25, 2011 at 5:17 PM, ello wrote:
> How about this: the lenses are moved to the bottom so they are above
> Trash) and all three do not collapse, so they're always there? (Or the
> user, can remove them (without taking the guts of the dash with them))
I like it.
> > This problem is a
I think you just sent this to me. Let's see if a little cc magic gets
it back . . .
In answer to your clarification, you're completely right, it would be
confusing to new users. As I say in my response to the mailing list, my
suggestion was more about those users who don't like moving all the wa
> I don't really care where they go, as long as they're separated and
> the lenses are in a fixed position.
How about this: the lenses are moved to the bottom so they are above
Trash) and all three do not collapse, so they're always there? (Or the
user, can remove them (without taking the guts o
On 11-05-25 01:20 PM, GonzO wrote:
How about this:
- Make Unity configurable enough so that it can be a great interface
for small touchscreens, netbooks, and full-grown monitors
- Save these configuration changes as profiles ("Touchscreen",
"Netbook/Laptop", "Desktop")
- Upon first run, ha
HOORAY. I can finally post to the list without it showing up as "Message
Unavailable". :-)
On Wed, May 25, 2011 at 2:54 PM, ello wrote:
> 1) Putting the launchers at the bottom/lense at the top impedes the
> function of the bar (as I see it): You want the things you want close at
> hand. So,
Nice mockup. However . . .
1) Putting the launchers at the bottom/lense at the top impedes the
function of the bar (as I see it): You want the things you want close at
hand. So, if you invoke the bar by moving the mouse, you don't want to
move too much to launch the things you want. A user uses
On Wed, May 25, 2011 at 7:38 AM, Adrian Maier wrote:
> My feeling is that the goal of developing a universally good desktop
> environment for all kinds of screens (including touch) is too bold and
> ignores the principle "use the right tool for the job". Screen size
> matters a lot ; a user
Hello ,
Visually these mockups seems to go towards a good direction ,
particularly reverting to a sane way of handling the menus (no more
autohiding global menu at the top of screen) .
The "ubuntu" menu looks ok as a default . Additionally it would be
extremely nice to be able to configure it
That is true of course ;) I too enjoy working with Photoshop/GIMP to
visualize ideas, it's great fun. I will probably make a complete Unity
sketch when I know what I want from Unity 2.0 :)
2011/5/24 Henrik Peytz
> For the sake of integration, would be my answer.
> Singular ideas on how to change
For the sake of integration, would be my answer.
Singular ideas on how to change the interface or accomplish stuff might suck
when viewed in isolation, yet turn out to be brilliant ideas when put
together with others and viewed as a whole. This was one of my gripes with
Brainstorm, it catered only
I'm sorry for not seeing the reason behind these mockups, all of these ideas
are exactly the same as have been stated in other ayatana threads, the only
difference is the position of the menu toggle button which was discussed in
the "Global menu in Oneiric Ocelot (11.10)" thread.
2011/5/24 Henrik
2011/5/24 GonzO Rodrigue
> On Tue, May 24, 2011 at 12:20 PM, Henrik Peytz
> wrote:
>
>
>
>> As for "always-visible-vs-menu-toggler", well, I just happen to like
>> getting rid of menus that go unused; consider it an extra feature, you
>> wouldn't have to use it, just keep the menus enabled.
>
>
If you look at the mockup you'll see that the idea does not mess with the
indicators/tray-icons.
As for "always-visible-vs-menu-toggler", well, I just happen to like getting
rid of menus that go unused; consider it an extra feature, you wouldn't have
to use it, just keep the menus enabled.
If you
The purpose would be more space to move around on, place windows there etc.
If the Global menu is made redundant by a menu-toggler, then there's no
reason to waste about 25x(x-resolution) of pixels drawing a panel that is
only used when an application is maximized. From a purely personal view I'd
r
Here's my third round of mockups based on some of the ideas floating around.
--
Particular ideas visualized:
http://fav.me/d3h14ui <-- Global-menu has turned into Maximode-menu, it is
only visible when a window is maximized, and it only shows the menus of the
maximized window, NEV
19 matches
Mail list logo
