3 ms·
I think the WYSIWYG WPF and Silverlight tools were pretty close to VB6 level of usability. The tools are great for building a quick UI, but I think they fall s
by hahamrfunnyguy 4y ago
I think the WYSIWYG WPF and Silverlight tools were pretty close to VB6 level of usability. The tools are great for building a quick UI, but I think they fall short for more complex applications.
This is why designers have their own preferences when it comes to designing the UX, to give them the flexibility to create the UI as they see fit. When different teams are working on a shared goal, there can always an element of "throw it over the fence".
As a developer, I always saw part of my job as getting plugged in with the other teams as much as possible. Providing continuous advisement and feedback on UX patterns as projects progress really helps things move smoothly.
- AnIdiotOnTheNet 4y agoI would argue that "more complex applications", when it comes to UI, are an anti-pattern. Use standard widgets, and don't be creative. Of course "standard widgets" don't really exist anymore because of where UI design has gone, but they did provide a consistency that users could rely on. That is gone now. Buttons don't even look like buttons anymore.
- EdiX 4y agoThe GUI builder of VB6 fell apart the moment you wanted to do a resizable window. Here "more complex applications" = "window that you can resize or maximize".
- mappu 4y agoVB.NET/WinForms (and competitors like Qt Designer) had a pretty good solution for widget placement on resize, all within the GUI builder. So i don't think this was fatal, if Classic VB had survived a bit longer it likely would have been added too. (Although to date they don't have a great solution for responsive layouts.)