I decided to mock up my concept for LittleIpsum’s proposed selection interface in situ. I am assuming that the existing menu items aren’t going anywhere.
over 2 years ago
I like this allot better. I use it on every project, and while the current interface is unique, it's awkward to wait/pounce-on what I want.
I did not get it earlier, this makes allot of sense, love the concept.
I like it. Though not usually used with groups of same menu items, it might help to have the divider lines between each 'block' just so you can quickly scan how much text you're getting...maybe?
Why not just use text labels instead?
On the main dropdown, show the following options: Words, Sentences, and Paragraphs. Hovering over any one of those options would count up the numbers just like it does with the current UI. Seems like the text labels would be easier to quickly understand, making it easier to find the right option you want.
Such a condensed group of lines is harder to discern compared to three distinct words. It'd take more time and effort to hover over the right block (and the right number of blocks) than I want to put into such a tool. At present, it's as easy as counting to 5 a few times—not so here.
Adding menu options for Words, Sentences, and Paragraphs would improve that workflow by saving me at least 5 seconds every time I use the app.
It takes a second to wreck it, it takes time to build! -BBoys
I like all of these concepts. Why not make it an option to do any of these?
Also, a number 1-4 next to each graphic option might help alternatively.
Makes good sense to me. I hope it get's implemented.
@Seth Dividers are an interesting idea. Without having a working prototype, it’s hard to determine whether the user would need more delineation between that different blocks or larger targets. I’ll mock something up for that.
@Mark See @alan’s comment and Dustin’s original video post.
One of the reasons for moving to a more direct interaction with the representative ‘blocks’ is to eliminate the delay when waiting to “count up the numbers”. The spacing and target area of the blocks could be changed to increase the user’s success in hitting the right spot. I’d argue that this method would not “… take more time and effort to hover over the right block” than the current interface. It’s more like sliding quickly through a list of menu items.
by Faruk Ateş
The idea in this variant is that you drag across the bar and click to copy; while not as charming as Grant’s version, it doesn’t suffer from tiny clickable areas for the words and lines.
over 2 years ago
by Dustin Senos
Proposing another interaction for the upcoming UI change to LittleIpsum.
As you move your mouse downwards from the top menu the window expands and increases the amount of Latin generated upon click.
Coloured blocks represent words, then sentences, then paragraphs.
The light grey line represents the total distance the mouse would have to move to go from generating one word, to four paragraphs.
This mock up skips stages (3 words, 3 sentences, 3 paragraphs) for illustrative purposes.
Full Version: http://dl.dropbox.com/u/403968/ui_v1_littleipsum.png
@dustin your concept is innovative for sure, but I feel like maybe it overcomplicates a really simple UI need.. I think Grant's design is elegantly simple, and provided the hit-areas work like you'd imagine they would, then this really hits the nail on the head.. quick scan, visually identify the approximate amount of text you need, click, you're done.
It’s very hard to gauge how complex or simple the interaction will be without building a working prototype. Frankly, I’d love to be able to “time trial” my concept beside Dustin’s.
Don’t miss Kyle Pickering’s “Feeling Lucky” rebound. Har.
The handy Mr Senos has mocked up this menu concept using Flash and posted it to the LittleIpsum blog. Please give it a whirl and send him your feedback.
The only problem I see with this is that if you want words you have to move left to right but for paragraphs and sentences you go downwards. It's a clever idea though.
Matt, did you give the interactive mockup a try? It’s not very difficult to get the feel of how the menu would work in practice.
I like it! If there's debate, i wouldn't mind seeing more ideas in mockup like that, but otherwise, I'd approve this idea. Nice job Dustin and Grant!
@Grant I did give it a try before my comment. The way I would adjust it is to make a downwards mouse movement gradually select the 1 - 5 words. So if you go straight down, it doesn't jump from 1 word to 1 sentence. I would also get rid of “Preferences” and “Quit’ at the bottom and have them accessible via right click, like Coversutra.
I do like it though and don't mean to sound overly critical.
personally I can't stand requiring control/contextual clicks on the menubar. having prefs and quit below everything feels more comforting to me.
I guess it depends on the app really. With LittleIpsum it seems really pointless and a waste of space to display Quit and Preferences, when they will hardly ever be used. Apptivate does the same thing.
@matt Menu items are not a “waste of space” if they are requisite and perform a needed (albeit irregular) function. Should Safari have it’s “Print…” menu item removed because the majority of people never print a web page? Probably not. By keeping those two menu items (which arguably do not get in the way of the primary functionality of LittleIpsum) you are keeping things as straightforward and obvious as possible.
There will always be a need to manually quit the application and access the preferences. If these menu items did not exist in the menu itself, you would have to access the functionality via “option key on launch” or some other unintuitive means. The Coversutra method of accessing hidden functionality falls into this category.
But the Print function in Safari is appropriately relegated to a menu and is not in the main window of the app. LittleIpsum's main window is the menu or (pop-over). There are good arguments for leaving them there (ease of access/not hiding features), but I think there are also good arguments for relegating them. It simplifies the UI and means that you can click on the icon to select text, and only get the text selection menu. Or you can right click to get options, you only get displayed options.
Ok, I have a better idea of what you were going for … I still think that key modifiers are not something you should introduce into a reasonably tidy UI, given the amount of secondary elements affected. Perhaps if the app had a dozen (or more) additional menu items.
I'd be interested to hear your thoughts on the animated mockup I posted? I tried to take on board your comments and make those features more accessible than they would be via right or ctrl click
I left a comment, but forgot to link to it.
keyboard shortcuts: ← previous shot → next shot L or F like
Show and tell for designers
What are you working on? Dribbble is a community of designers sharing screenshots of their work, process, and projects.
Copyright © 2009–2013 Dribbble LLC. All screenshots © their respective owners. Shipped from Salem, Mass. USA.
Follow Dribbble on Twitter