Mvu file

Please clarify for me that this isn't what you understand MAUI to be or if it is. I really like the way this issue and it's comments are going. Thanks for everyone participating. Maybe together we can get all the different architectures as possible flavors for MAUI established and named properly. Just a note from my own experience with CSharpForMarkup: it's a bit lower level than MVVM - more of a set of extension methods and utilities to make C markup more streamlined and nicer looking.

You can certainly implement an MVVM pattern with it as it has helpers to make ViewModel bindings easier but what I ended up doing is implementing all of my view logic in Redux instead of ViewModels. Not quite unidirectional data flow but I didn't have a mature way of doing UI object tree diffs and view functions like Fabulous does now. I would need to say that your original MVU blog is one of the best article that explains the concept very clear and precise.

I have learned a fair bit from it. Thank you. You started to enumerate things that are actually in one category and ignored the ones that are not.

The are similarities with MVU implementations, like an immutable view. But there are clear differences like, there are is no message loop and no explicit update function. The model is mutated directly in the View. This is something people explicitly didn't want when they came up with MVU. In some languages it would even be impossible to do that - that's why MVU emerged. And why it became popular. Now we should be careful if we remove those properties from our definition of MVU.

Infact it's those points that you brought up in the last comment that we need to discuss as a community and not title on a blog post. That's my point. That's a positive thing to discuss and the framework will gain from it.

I agree that the name is a little detail that should not distract from more important aspects. However, the reason I brought it up is that I personally do not see MAUI as a community effort where common sense eventually will lead to a commonly agreed solution. It's a Microsoft product where final decisions are being made behind closed doors.

I am here in my capactiy as a customer to raise my concerns. But I am sure, we all agree that the closest architectural pattern for all these frameworks are MVU.

No, names are important. They are difficult, both to establish and to retain their meaning. REST is so abused that it is no longer meaningful except as a marketing jargon term. Just like with REST, you don't have to do the definitional thing to make something useful and good. Just please don't muddy the name with alternatives that clearly deviate from a well-defined and established pattern.

Just like with REST, you don't have to do the definitional thing to make something useful and good, just please don't muddy the name with alternatives that clearly deviate from its definition.

Both work and is closer to what is presented in the blog post than MVU. Edit add: I am even not sure where the proposed version lives. Is there going to be a View where everything lives in?

Or does it all live in just some class named by the Domain Model what serves the view, logic and model? Are models supposed to be separate classes types or records? I think this is for me the major pain point here, I have no clue how it is "presented" and therefor I can't see there to be an update, model and view function. Out of the box, it seems to me that MAUI is a little lower level than the patterns discussed so far - really just the Model or State and the View portion of those other patterns.

Something you could perhaps build on to implement those other patterns although state management is a bit opinionated. As a rough first pass, I'm thinking maybe if you created a separate class that exposes "actions" to the view function. The MAUI view would forward click events from the view to the controller, which would either generate a new model or mutate the existing model.

JeroMiya I agree, definitely using Redux pattern can make it closer to MVU and keeps architecture a lot less opiniated. Here's my attempt at a C example. I don't have MAUI available to try this as a real example. There's no preview, is there? Anyway, this is a rough translation of the idea. Would this incur more of a performance cost for updates than in the Microsoft sample? In this model, if I understand, a new view would be instantiated containing all of the UI elements, as opposed to, in the MS sample, leaving the existing view elements in place and merely updating the value of the label an incurring whatever re-sizing cost this could have.

This difference seems to be one of the core differences driving this discussion around naming, and so I'm curious if in the traditionally defined MVU architecture there are other technqiues for efficiently updating UI, and if so, are they implemented at the level of the rendering engine?

This is usually very very efficient, especially if you work with immutable data structures. I'm going to close this issue for now.. If anyone wants to continue this conversation please create a discussion item and then references this issue. As i see this and what the snippet look like to me is something I first found in React, then Flutter, then in SwiftUI. I'ts fine having any name for it. Its a "functional programming" paradigm. Avoiding the problems that MVVM has in my experience , in layouts with complex inter-dependencies.

Any inter-dependencies are resolved by the app developer in writing the tree. The renderer has a straightforward task. IMHO, Its easier to debug tree-writing code, than figuring out what went wrong where in the data binding. I'd rather do it that way, even if at first it takes more coding. I've got years of often painful experience pushing Xamarin Forms to the limit. That's the closest tech that I am familiar with.

Skip to content. Star New issue. Jump to bottom. Copy link. How would you expect to see C MVU in. What new language features would you see needed, if any? In order to process messages, pattern matching is helpful if not required. I think the current state of C switch expressions is already good enough for that, as the shape of messages will be simple.

Last but not least, the most important feature I see is immutability by default and enabled structural equality comparisons. As far as I remember the current proposal of records in C 9 aka data classes , those will deliver exactly that.

I didn't anticipate how much weight the code snippet would bear But that's the meat, right? And I'm sorry it did not match the label. In this case I think using wrong wording needs to be fixed and for that to happen I'd love for this project to a understand that MVU is the wrong name for what we are talking about here and b to find the right term to describe what we are trying to establish here and then c update everyone and start using that new name I think we are still at a point we're we can still go back and fix it.

Edit: miss communication dropped out of the contest. Isn't our natural thinking against these paradigms [MVU]? Do you have anything else to tell us? Please tell us what you were looking for. Do not include sensitive information, such as Social Security or bank account numbers. Your feedback will not receive a response. Thanks, your message has been sent to Massachusetts Department of Revenue!

Survey Tell us more about your experience How much do you agree with the following statements in the scale of 1, Strongly Disagree, to 5, Strongly Agree? Strongly Disagree. This page is helpful. This page, Request a motor vehicle sales or use tax abatement, is offered by Massachusetts Department of Revenue show more. Request a motor vehicle sales or use tax abatement If you bought a motor vehicle, you might be eligible to receive a sales or use tax refund.

Learn how to request an abatement. Request a motor vehicle sales or use tax abatement with MassTaxConnect. MassTaxConnect Log in to file and pay taxes. Receive email updates Subscribe to receive updates from DOR. What you need. How to request. You will need the following information about the vehicle: Year Make Model Identification Number Title number Date of Sale You will also need: Copy of Bill of Sale Copy of registration certificate showing the amount of tax you paid to the RMV If applicable: Date of Return Tax exemptions - Related affidavit or exemption certificate form Challenges to the book value used by the RMV - Odometer reading at time of purchase Penalty assessment - An explanation detailing the reasonable cause for the late filing and tax payment.

The assessment of interest is not discretionary and the Department of Revenue does not have the authority to abate interest accrued on unpaid or late paid tax.

Feedback Did you find what you were looking for on this webpage? Do you have anything else to tell us?