Declarative ViewModels and Taborder
No edit summary
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<message>Write the content here to display this box</message>
A good friend of mine, Lars Olofsson, complained about the Taborder between controls in the ViewModels. The project he is working on uses ViewModels A LOT. As the work of developing this system continues, small changes are applied to the ViewModels, and the Taborder becomes messier and messier.
A good friend of mine, Lars Olofsson, complained about the Taborder between controls in the ViewModels. The project he is working on uses ViewModels A LOT. As the work of developing this system continues, small changes are applied to the ViewModels, and the Taborder becomes messier and messier.


He suggested that the Taborder be made visible so that anyone working on the ViewModel definition could see if it was okay or not. That was a brilliant idea – why has it not always been that way:
He suggested that the Taborder be made visible so that anyone working on the ViewModel definition could see if it was okay or not. It was a brilliant idea – why has it not always been this way?


[[File:Taborder -1.png|frameless|541x541px]]
[[File:Taborder -1.png|frameless|837x837px]]
[[Category:View Model]]
[[Category:View Model]]
{{Edited|July|12|2024}}

Latest revision as of 05:33, 21 June 2024

A good friend of mine, Lars Olofsson, complained about the Taborder between controls in the ViewModels. The project he is working on uses ViewModels A LOT. As the work of developing this system continues, small changes are applied to the ViewModels, and the Taborder becomes messier and messier.

He suggested that the Taborder be made visible so that anyone working on the ViewModel definition could see if it was okay or not. It was a brilliant idea – why has it not always been this way?

Taborder -1.png

This page was edited 10 days ago on 06/21/2024. What links here