We have the first entry of this new publication! Subscribe!
We have the first entry of this new publication! Subscribe!
MVC for desktop, mobile and web applications. With Delphi & FireDAC!
http://ow.ly/YAPjH
(Sorry for publishing twice)
http://ow.ly/YAPjH
MVC for desktop, mobile and web applications. With Delphi & FireDAC!
http://ow.ly/YAPjH
(Sorry for publishing twice)
http://ow.ly/YAPjH
Interesting.. Wanna hear more.
ReplyDeleteYou should really consider adding your blog to DelphiFeeds/BeginEnd
ReplyDeleteI really like the post!! Really. Until i came to tools. An MVC framework should NOT require tools that generate tables/sourcecode/dfm's/DOM models or anything that needs to be prepared befor compile time. IMHO. Another thing - FMX dependency? FMX is still in it's infancy and if it does not get big enough the ecology it tries to leverage will always run far faster than FMX. VCL's "ecology" is maintained by Microsoft alone (good or bad... eh) but to maintain VCL is a task that's orders of magnitude less complex that the multiplatform initiative that constitutes FMX.
ReplyDeleteDany Marmur only the views should depend on fmx in a true MVC
ReplyDeleteAgustin Ortu could you not separate the View "units" (or whatever) like the rest of Dephi? System.OurView (platform independent), VCL.OurViewBase, FMX.OurViewBase? FMX is just so... convoluted.
ReplyDeleteWe push code into forms because 3rd party libs forces us to. Devexpress once aimed at a complete model but things was not so. Mostly because of Delphi common system Lund and vcl architecture.
ReplyDeleteDany Marmur Subscribe you to the blog and let us show you how we do. This is not a perfect solution, but its a very good solution. I think.
ReplyDeleteDany Marmur
ReplyDeleteNo one forces you to push code into the forms!!!
What is a Form? It's an Object than can be instantiated at design time, with a different behavior. True?
What is a Component inserted into a Form? It's the same thing but it belongs to the form.
What's an "Event"? It's a property that holds a pointer to a method. True too?
If all of this is true, and I know that really it is, why when the IDE creates and empty Event Handler, by double clicking on the "Event" property, by example to handle the behavior of a click over a button, it creates the code owned by the Form and not by the Button?
This is an arbitrary decision. This is, without doubt, part of the genius of Mr. Anders and his team. But... if the IDE would allow us to tell, in what object, instantiated or not, it should create the empty code of this "event handlers"? In this case, you can have a Controller class that holds all the event handlers of a view.
This, creates a new necessity: Shall be this class, the controller, who creates the View, to be sure that all the event handler are available when the view comes up.
But, be sure of this: No one forces you to push code into the form!!! It's the IDE who makes this. Not the language or the classes. It is a convenience, not an imposition.
Dany Marmur
ReplyDeleteYour affirmation: "An MVC framework should NOT require tools that generate tables/sourcecode/dfm's/DOM models or anything that needs to be prepared befor compile time." This include too the IDE?
If you don't like this tools, you can work in the conversion of this tools into experts integrated in the IDE. But, be part of the IDE don't make it different.
When you use the property editor, by example you are using an external tool. Integrated into the IDE, Ok, but external. His mission is modify the file of resources that initialize the form and the components owned by it. When you use the form designer... It's or not is an external tool?
When you push Alt+F11 to include a unit into the uses clause, It's or not is an external tool?
Juan C. Cilleruelo my statement was not meant as criticism of your project. Just put my $0.05 into a comment.
ReplyDeleteI can clarify though that if you use DevExpress Grid and want to extent filtering and drop-down logic there's a lot of things that is managed by code that prevents a clean design.
I almost never create forms "design time", with persistence and added complexity i find it better to create stuff dynamically.
And i absolutely agree that the IDEs idea of event handlers are too meek.
I simply just wanted to say that another VisualBinding scenario won't be of any use to me.
Just published the Second Part
ReplyDeletesenCille MVC: The Database & Stub.