![]() However, once you are proficient with the methods, you still might not have the desire to multiple 634*592 by hand. If you rely on it too much as a kid then you might not ever get good at your times tables. On the other hand, if you (and your team) know about all the artefacts generated by a visual editor, then maintainability might not be an issue for you.ĭragging visual images around is just one of many development tools to make your life easier - same as a debugger, or something that auto-generates getter and setter functions - and there's nothing inherently wrong with that. If you're used to code an interface by hand, you'll be faster and more efficient going that way. Of course, take it all with a grain of salt. The second method requires more discipline, but is more useful for critical applications that might need to be maintained for a long time. The first method is very useful for fast-moving projects, where you want to have a quick visual feedback. Therefore, both approaches have some merit: While those tools can provide design speed and instant visual feedback of what your application can look like, the code can take a big maintainability hit, especially if you do not know the tools inside and out. However, you have to be able to trust your tools and be aware of the code generated by your actions.Īre methods automatically generated? Is the positioning used absolute or relative? I've used Flex Builder and some Silverlight tools, as well as some good old Swing generators and the behavior of such tools can vary widely. As many have mentioned here, using visual tools does not make you any less of a programmer and can be a time saver. ![]() Honestly, it's mostly about the project scope. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |