Tag Info

Hot answers tagged

4

As jackJoe said, the browse button will translate into the users locale installation of the browser. If they don't have an Hebrew browser, I would guess they either know English (or whatever language that browser has) or are used to seeing "Browse" everywhere they are asked to upload something. I would say it is more worth it to explain what this button ...


4

These controls translate to the user's browser language automatically (may not happen in some cases). Unless you plan to have it on a multi-language site, in that case, js + css will have to be used...


4

Maybe: simply just "Add folder to..."


4

I propose some improvements, based on the usability heuristics. The main issue here is the absence of clear focal point which leads to the convertion task execution. Also the task itself could be fully automated, there no man needed. Just provide FTP address and access parameters to a database. And let it run as batch process.


3

Your UX is all about "change the template". The required template may be (a) the default or (b) local file. In future say a selection from most recently used file list or a resource from a shared template library is useful. You could display this domain model this flat in the UI much as you have. But if extra capability or clarity is needed, then could ...


3

I like the term "Select parent folder", but one thing to consider would be whether or not the concept of folder creation needs to be communicated to the user. The user doesn't care that you're "creating a folder" for the project in another folder. The important high level idea is location of data. Try something like "Select location for project data." or ...


3

"Where would you like this project's folder created?" or "Location of project folder:" make it clear that I don't have to create my own sub-folder for the project, which is always a temptation for me to do. (You ever done that, or not done that when you should have? Like when extracting compressed files; I never know if I need to make a subfolder first, and ...


3

I would keep the two separate, but in the same group, because of the different location concepts the user has to grasp. Mockup example: ux.stackexchange.com is also a good example of this separation of concepts:


3

I would be inclined to keep them separate. They are different functions and the down arrow does not explain the distinct functionality very well. Also: overlap between 'upload file' and 'select file', which one could argue amount to the same thing, namely, 'selecting a file to attach with a post'. I would do this: and even then you might want to play ...


2

Personally, if that is your requirement, then there is nothing wrong with doing that. But please keep in mind any users (they might be very very less) who do not have their CSS and JavaScript enabled. What I mean is, that on disabling the JavaScript and CSS, your page should not display 2 textboxes and buttons. I'm pretty sure you would have taken care of ...


2

I haven't seen to many apps that ask a user to select where they want a folder to be created, but the one I have seen (dare I say, Microsoft Visual Studio) has two fields everytime you create a new project: name and location. It creates a folder of the same name of the value the user enters into the "name" field at the given location. Though this doesn't ...


2

Rather than 'Open' and 'Save', it sounds like your need a bit of a rewording. I believe 'Source' and 'Destination' may be a better fit for the function of your app. download bmml source – Wireframes created with Balsamiq Mockups A quick wizard like this may alleviate confusion for the user. I did modify the workflow you described; I put the ...


1

Should the Save/Cancel buttons determine whether changes made to the file attachments are saved or discarded? Or would users expect that these changes are automatically and independently saved, since they entail file operations? It actually depends on how you will display these changes. Apply/Cancel behaviour should differentiate applied changes from ...


1

I support the answer from Myrddin Emrys. In this case an assistant or wizard-approach is a good way to lead the user through the configuration. This approach has many advantages such as: you can easily add more items to configure you can add explanation texts if some options need to be explained you can add extra options or modifiers (as example: "Same as ...


1

I would refer to the parent folder where project folders are created as the "working folder". Is there a valid use case for different project folders to be stored in different working folders? If not, or if this is a rare use case, I would have users select their working folder once as part of their user preferences and then as much as possible remove it ...


1

If the end result is for the entire project to be contained in one folder that will be maintained by your application, then why even mention that a folder is being created? That's something that the user doesn't need to know at the point you're describing, because it sounds like the project has to be contained within a folder. Therefor, I'd use the simplest ...



Only top voted, non community-wiki answers of a minimum length are eligible