I have this idea for a small-medium web application that I would like to build, probably with a combination of Velocity and Spring MVC. My problem is that I have never dealt with issues such as user registration, or with design issues such as CSS, layout, etc.
我有一个想要构建的中小型Web应用程序的想法,可能结合了Velocity和Spring MVC。我的问题是我从未处理过诸如用户注册或CSS,布局等设计问题等问题。
I'm pretty confident I can build the application/domain layer of this application, but how should I get started on the user interface side of it? Are there any resources on how to manage users, and on how to, well, make the app look good? I don't necessarily need references to the classics on user interaction design, but rather pointers to how to implement these ideas with the most popular frameworks.
我非常有信心可以构建这个应用程序的应用程序/域层,但是我应该如何开始使用它的用户界面呢?有没有关于如何管理用户的资源,以及如何使应用看起来很好?我不一定需要引用关于用户交互设计的经典,而是指向如何使用最流行的框架实现这些想法。
4 个解决方案
#1
If you're familiar with Spring MVC and Java you might want to look at Grails which is built on top of spring amongst other things. There are a number of plugins including at least a couple which handle user registration for you (ie http://grails.org/plugin/acegi based on Spring Security). Scaffolding from your domain model might well not get you a good looking interface but at least gets you a starting point you can then build on.
如果您熟悉Spring MVC和Java,您可能需要查看基于Spring构建的Grails。有许多插件,包括至少一对为您处理用户注册的插件(即基于Spring Security的http://grails.org/plugin/acegi)。来自您的域模型的脚手架可能不会让您看起来很漂亮,但至少可以为您提供一个可以构建的起点。
Having said that you could get scuppered trying to learn grails before you get any work done. Perhaps take a look at the user management plugins for some inspiration. As for the interface, if it's just about how to make it look good I'd suggest having a look at www.oswd.org which has a lot of example open source css designs.
话虽如此,在完成任何工作之前,你可能会试图学习grails。或许可以看看用户管理插件的一些灵感。至于界面,如果它只是关于如何使它看起来很好我建议看看www.oswd.org,它有很多开源css设计的例子。
#2
You sound like you are suffering from project-planning-paralysis. I would suggest that you just start working on the parts you are certain of (like the application and data layers) and leave the parts you are unsure of alone.
你听起来像是在遭受项目规划 - 瘫痪。我建议你开始研究你确定的部分(比如应用程序和数据层),并留下你不确定的部分。
Depending on the size of the project it may be worthwhile to get someone else involved who has the knack for creating UIs.
根据项目的规模,可能值得让其他人参与创建UI的诀窍。
#3
Getting web applications to look good is no easy task.
让Web应用程序看起来很好并非易事。
As Andrew said it would be worth doing what you feel most comfortable with, and asking someone to help out with the UI.
正如安德鲁所说,值得做你觉得最舒服的事情,并要求别人帮助你。
Other than that, all I can really suggest is looking at some existing web applications and see how they do things. There's just way too much variety to really give any hard and fast rules about making a web application UI.
除此之外,我真正建议的是查看一些现有的Web应用程序,看看它们是如何做的。对于制作Web应用程序UI来说,真正提供任何硬性规定的方法太多了。
#4
Hire an design expert... from the start.
从一开始就聘请设计专家。
If your specialty is programming, your design will likely hinder your success regardless of your intent. If you aren't comfortable farming out, then hire a consultant to provide feedback on how your app will work. Do this throughout the design and development process.
如果您的专业是编程,那么无论您的意图如何,您的设计都可能会阻碍您的成功。如果您不熟练,请聘请顾问,就您的应用程序的运作方式提供反馈。在整个设计和开发过程中执行此操作。
As someone who does both development and design, when I'm handed a project in which one or the other is completed, I usually have to make them go back and change things since they didn't consider the big picture.
作为同时进行开发和设计的人,当我交给一个完成其中一个项目的项目时,我通常不得不让他们回去改变一些事情,因为他们不考虑大局。
Best case scenario: you avoid common pitfalls, interface problems and your app is drastically improved.
最佳案例场景:您可以避免常见的陷阱,界面问题以及您的应用程序大幅改进。
Worse case scenario: you ended up knowing what you were doing and you ended up having that work validated and moved out of a "design team of one".
更糟糕的情况是:你最终知道自己在做什么,最后你的工作得到了验证,并从一个“设计团队”中撤出。
#1
If you're familiar with Spring MVC and Java you might want to look at Grails which is built on top of spring amongst other things. There are a number of plugins including at least a couple which handle user registration for you (ie http://grails.org/plugin/acegi based on Spring Security). Scaffolding from your domain model might well not get you a good looking interface but at least gets you a starting point you can then build on.
如果您熟悉Spring MVC和Java,您可能需要查看基于Spring构建的Grails。有许多插件,包括至少一对为您处理用户注册的插件(即基于Spring Security的http://grails.org/plugin/acegi)。来自您的域模型的脚手架可能不会让您看起来很漂亮,但至少可以为您提供一个可以构建的起点。
Having said that you could get scuppered trying to learn grails before you get any work done. Perhaps take a look at the user management plugins for some inspiration. As for the interface, if it's just about how to make it look good I'd suggest having a look at www.oswd.org which has a lot of example open source css designs.
话虽如此,在完成任何工作之前,你可能会试图学习grails。或许可以看看用户管理插件的一些灵感。至于界面,如果它只是关于如何使它看起来很好我建议看看www.oswd.org,它有很多开源css设计的例子。
#2
You sound like you are suffering from project-planning-paralysis. I would suggest that you just start working on the parts you are certain of (like the application and data layers) and leave the parts you are unsure of alone.
你听起来像是在遭受项目规划 - 瘫痪。我建议你开始研究你确定的部分(比如应用程序和数据层),并留下你不确定的部分。
Depending on the size of the project it may be worthwhile to get someone else involved who has the knack for creating UIs.
根据项目的规模,可能值得让其他人参与创建UI的诀窍。
#3
Getting web applications to look good is no easy task.
让Web应用程序看起来很好并非易事。
As Andrew said it would be worth doing what you feel most comfortable with, and asking someone to help out with the UI.
正如安德鲁所说,值得做你觉得最舒服的事情,并要求别人帮助你。
Other than that, all I can really suggest is looking at some existing web applications and see how they do things. There's just way too much variety to really give any hard and fast rules about making a web application UI.
除此之外,我真正建议的是查看一些现有的Web应用程序,看看它们是如何做的。对于制作Web应用程序UI来说,真正提供任何硬性规定的方法太多了。
#4
Hire an design expert... from the start.
从一开始就聘请设计专家。
If your specialty is programming, your design will likely hinder your success regardless of your intent. If you aren't comfortable farming out, then hire a consultant to provide feedback on how your app will work. Do this throughout the design and development process.
如果您的专业是编程,那么无论您的意图如何,您的设计都可能会阻碍您的成功。如果您不熟练,请聘请顾问,就您的应用程序的运作方式提供反馈。在整个设计和开发过程中执行此操作。
As someone who does both development and design, when I'm handed a project in which one or the other is completed, I usually have to make them go back and change things since they didn't consider the big picture.
作为同时进行开发和设计的人,当我交给一个完成其中一个项目的项目时,我通常不得不让他们回去改变一些事情,因为他们不考虑大局。
Best case scenario: you avoid common pitfalls, interface problems and your app is drastically improved.
最佳案例场景:您可以避免常见的陷阱,界面问题以及您的应用程序大幅改进。
Worse case scenario: you ended up knowing what you were doing and you ended up having that work validated and moved out of a "design team of one".
更糟糕的情况是:你最终知道自己在做什么,最后你的工作得到了验证,并从一个“设计团队”中撤出。