I know about code-behind files, but what is the best real-world way of Designers that are using DreamWeaver or other Design Tools to work with Visual Studio programmers?
我知道代码隐藏文件,但使用DreamWeaver或其他设计工具与Visual Studio程序员合作的设计师最好的现实方式是什么?
For example, say you have a basic website with user interface forms hitting the database... the database work is definitely done by the developer but how to tie the designed forms with the database coding or client-side logic that may involve events on controls, or other GUI related tie-ins. Are the graphic designers also controlling application flow? There seems to be a large disconnect that needs addressed - especially when it comes time to tweak the design after it's been implemented.
例如,假设您有一个基本网站,用户界面表单访问数据库...数据库工作肯定是由开发人员完成的,但如何将设计的表单与数据库编码或客户端逻辑绑定,可能涉及控件上的事件或其他与GUI相关的搭配。图形设计师是否也在控制应用程序流程?似乎存在需要解决的大型断开连接 - 特别是在实施后调整设计的时候。
4 个解决方案
#1
#2
1
The best way is to make sure that your designers have some knowledge of what kind of HTML they will be working with.
最好的方法是确保您的设计人员了解他们将使用哪种HTML。
Every ASP.NET developer is aware of MS-HTML, that lovely nesting of HTML tables, but designers aren't. Designers have their own requirements to meet and they'll do them in the best manner possible. Sadly it's not often good for us.
每个ASP.NET开发人员都知道MS-HTML,HTML表的可爱嵌套,但设计师不是。设计师有自己的要求,他们会以最好的方式做到这一点。可悲的是,这对我们来说并不常见。
I am always frustrated when I receive a design from our UI team which shows radio-buttons nicely layed out in a grid using floating div's. Then I have to shatter their dreams that no, I can't generate you that HTML (ok, I can with the use of ControlAdapters, but every time they are different designs!).
当我从我们的UI团队收到一个设计时,我总是很沮丧,这个设计显示了使用浮动div在网格中很好地布置了无线电按钮。然后我必须粉碎他们的梦想,不,我不能生成那个HTML(好吧,我可以使用ControlAdapters,但每次他们是不同的设计!)。
Try and have a 90%/ 10% rule, where 90% of the design is done before the ASP.NET starts and the 10% is done once the ASP.NET is completed, and done against ASP.NET generated HTML.
尝试并拥有90%/ 10%规则,其中90%的设计在ASP.NET启动之前完成,10%在ASP.NET完成后完成,并针对ASP.NET生成的HTML完成。
And make sure you're using source control! Code doesn't exist unless it's in source control! And thanks to the latest TFS PowerTools there's a lovely Windows Shell integration component so you don't need to use VS to check in and out now more :D
并确保您使用源代码管理!代码不存在,除非它在源代码管理中!并且由于最新的TFS PowerTools,它有一个可爱的Windows Shell集成组件,因此您现在不需要使用VS来检查和退出:D
#3
1
This may sound really cheezy, but when I was working with Dreamweaver / Visual Studio, I'd do my layouts, and then conveniently put [RADIO BUTTON HERE], [INPUT TEXT HERE], etc. in the places where my form elements/controls would go, and I'd save the page as a basic HTML document.
这可能听起来真的很讨厌,但是当我使用Dreamweaver / Visual Studio时,我会做我的布局,然后方便地将[RADIO BUTTON HERE],[INPUT TEXT HERE]等放在我的表格元素的地方/控件会去,我将页面保存为基本的HTML文档。
That way Dreamweaver wouldn't nest its own form tags in and I'd have easy to locate places to drop in my ASP.NET controls when I went to merge things in. It was easy enough to create a fresh web form page in Visual Studio and then copy and paste everything over. If for some reason I mucked things up, I'd have a basic HTML "template" to start over wtih.
这样Dreamweaver就不会嵌套自己的表单标签了,当我去合并内容时,我很容易找到放在ASP.NET控件中的地方。很容易在Visual中创建一个新的Web表单页面Studio然后复制并粘贴所有内容。如果由于某种原因我搞砸了,我会有一个基本的HTML“模板”重新开始。
#4
0
Unfortunately this is an all too common problem. Dreamweaver typically doesn't write html that is friendly to a .net developer. If at all possible, get someone who can actually read, and write HTML,not just use the Dreamweaver WYSIWYG editor.
不幸的是,这是一个非常普遍的问题。 Dreamweaver通常不会编写对.net开发人员友好的html。如果可能的话,找一个可以实际阅读并编写HTML的人,而不仅仅是使用Dreamweaver WYSIWYG编辑器。
I often found that if I'm working with a designer that doesn't know html, that I actually save a lot of time be just having them mock up everything in photoshop, then give me sliced up images. I find that my writing the actual HTML in a .net friendly format saves a ton of time, instead of having to go back and forth with the designer in this situation.
我经常发现,如果我和一个不懂html的设计师合作,我实际上节省了很多时间,只是让他们在photoshop中模拟一切,然后给我切片图像。我发现以.net友好格式编写实际HTML可以节省大量时间,而不必在这种情况下与设计师来回。
#1
1
Use another approach like MVC, separate your design from your logic. Like this every member (designer / developer) of the team can focus on what they do best.
使用另一种方法,如MVC,将您的设计与逻辑分开。像这样,团队中的每个成员(设计师/开发人员)都可以专注于他们最擅长的事情。
MVC implementations: link / link
MVC实现:链接/链接
#2
1
The best way is to make sure that your designers have some knowledge of what kind of HTML they will be working with.
最好的方法是确保您的设计人员了解他们将使用哪种HTML。
Every ASP.NET developer is aware of MS-HTML, that lovely nesting of HTML tables, but designers aren't. Designers have their own requirements to meet and they'll do them in the best manner possible. Sadly it's not often good for us.
每个ASP.NET开发人员都知道MS-HTML,HTML表的可爱嵌套,但设计师不是。设计师有自己的要求,他们会以最好的方式做到这一点。可悲的是,这对我们来说并不常见。
I am always frustrated when I receive a design from our UI team which shows radio-buttons nicely layed out in a grid using floating div's. Then I have to shatter their dreams that no, I can't generate you that HTML (ok, I can with the use of ControlAdapters, but every time they are different designs!).
当我从我们的UI团队收到一个设计时,我总是很沮丧,这个设计显示了使用浮动div在网格中很好地布置了无线电按钮。然后我必须粉碎他们的梦想,不,我不能生成那个HTML(好吧,我可以使用ControlAdapters,但每次他们是不同的设计!)。
Try and have a 90%/ 10% rule, where 90% of the design is done before the ASP.NET starts and the 10% is done once the ASP.NET is completed, and done against ASP.NET generated HTML.
尝试并拥有90%/ 10%规则,其中90%的设计在ASP.NET启动之前完成,10%在ASP.NET完成后完成,并针对ASP.NET生成的HTML完成。
And make sure you're using source control! Code doesn't exist unless it's in source control! And thanks to the latest TFS PowerTools there's a lovely Windows Shell integration component so you don't need to use VS to check in and out now more :D
并确保您使用源代码管理!代码不存在,除非它在源代码管理中!并且由于最新的TFS PowerTools,它有一个可爱的Windows Shell集成组件,因此您现在不需要使用VS来检查和退出:D
#3
1
This may sound really cheezy, but when I was working with Dreamweaver / Visual Studio, I'd do my layouts, and then conveniently put [RADIO BUTTON HERE], [INPUT TEXT HERE], etc. in the places where my form elements/controls would go, and I'd save the page as a basic HTML document.
这可能听起来真的很讨厌,但是当我使用Dreamweaver / Visual Studio时,我会做我的布局,然后方便地将[RADIO BUTTON HERE],[INPUT TEXT HERE]等放在我的表格元素的地方/控件会去,我将页面保存为基本的HTML文档。
That way Dreamweaver wouldn't nest its own form tags in and I'd have easy to locate places to drop in my ASP.NET controls when I went to merge things in. It was easy enough to create a fresh web form page in Visual Studio and then copy and paste everything over. If for some reason I mucked things up, I'd have a basic HTML "template" to start over wtih.
这样Dreamweaver就不会嵌套自己的表单标签了,当我去合并内容时,我很容易找到放在ASP.NET控件中的地方。很容易在Visual中创建一个新的Web表单页面Studio然后复制并粘贴所有内容。如果由于某种原因我搞砸了,我会有一个基本的HTML“模板”重新开始。
#4
0
Unfortunately this is an all too common problem. Dreamweaver typically doesn't write html that is friendly to a .net developer. If at all possible, get someone who can actually read, and write HTML,not just use the Dreamweaver WYSIWYG editor.
不幸的是,这是一个非常普遍的问题。 Dreamweaver通常不会编写对.net开发人员友好的html。如果可能的话,找一个可以实际阅读并编写HTML的人,而不仅仅是使用Dreamweaver WYSIWYG编辑器。
I often found that if I'm working with a designer that doesn't know html, that I actually save a lot of time be just having them mock up everything in photoshop, then give me sliced up images. I find that my writing the actual HTML in a .net friendly format saves a ton of time, instead of having to go back and forth with the designer in this situation.
我经常发现,如果我和一个不懂html的设计师合作,我实际上节省了很多时间,只是让他们在photoshop中模拟一切,然后给我切片图像。我发现以.net友好格式编写实际HTML可以节省大量时间,而不必在这种情况下与设计师来回。