Реter Konow: Alexey, don't make the main mistake of my opponents. They all think that my technology is a total slag, and every time they see its results they get cognitive dissonance. Why walk on the same rake?
I'm sick of laughing. I feel sorry for you... it hurts...
Peter, none of your opponents have said that your design or your technology is rubbish. You are making this up.
All participants of the discussion in one voice, but in different ways, are trying to tell you that you can get the same result is much more elegant, efficient and with less effort.
We're trying to make it clear that everything you're trying to come up with was already invented by others a long time ago and you just have to accept and learn it.
That's why nobody accepted your "markup language", because it does not fit in the framework of habitual actions of any programmer.
Everyone is eager to learn something new, and gets bogged down when people try to return to the past.
The decision to create a graphical interface editor is in itself a really useful tool, which will allow even a novice programmer to quickly create the desired interface.
But the only thing is that in the end the linking of this interface with the rest of the logic has to be done in the code!
There's a development pattern called MVVM, which allows you to develop the interface itself separately from the logic. The same pattern is used to develop all android apps....
If your builder allowed you to create a standalone interface that would fit into MVVM technology, then nobody would even discuss what the interface consists of.....
But that's all lyrics... wait for.... We have waited 2 years and we will wait another... March 3rd doesn't seem to be long now...
I'll present the minimum on the 3rd. Creating and connecting a simple panel. I've only had three weeks to go from a markup language to a visually editor. There has been a lot of work. By the end of March, the editor will be much more complete.
My goal is for people to use the editor. You can go into it and argue about its design for fun. It will perform its function to the best of its ability.
The connection you're worried about is the easiest and most convenient. You'll see how wrong you were in your assumptions.
Of course, there will be bugs in the beginning... but we'll fix them.
Реter Konow: I will present the minimum on the 3rd. Creating and connecting a simple panel. I've only had three weeks to go from a markup language to a view editor. There has been a lot of work. By the end of March, the editor will be much more complete.
Реter Konow: I'll present the minimum on the 3rd. Creating and connecting a simple panel. I had only three weeks to go from a markup language to a visually editor. There has been a lot of work. By the end of March, the editor will be much more complete.
My aim is for people to use the editor. You can go into it and argue about its design for fun. It will perform its function fully and with quality.
The connection you're worried about is the simplest and most convenient. You'll see how wrong you were in your assumptions.
Of course, there will be bugs in the beginning... but we'll fix them.
I certainly hope so!
There are familiar and understandable, generally accepted ways of interacting and I'd hate to see something obviously irrational.
In the end, of course, I'd like to be able to send data directly to and receive data from the interface:
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Alexey, don't make the main mistake of my opponents. They all think that my technology is a total slag, and every time they see its results they get cognitive dissonance. Why walk on the same rake?
Peter, none of your opponents have said that your design or your technology is rubbish. You are making this up.
All participants of the discussion in one voice, but in different ways, are trying to tell you that you can get the same result is much more elegant, efficient and with less effort.
We're trying to make it clear that everything you're trying to come up with was already invented by others a long time ago and you just have to accept and learn it.
That's why nobody accepted your "markup language", because it does not fit in the framework of habitual actions of any programmer.
Everyone is eager to learn something new, and gets bogged down when people try to return to the past.
The decision to create a graphical interface editor is in itself a really useful tool, which will allow even a novice programmer to quickly create the desired interface.
But the only thing is that in the end the linking of this interface with the rest of the logic has to be done in the code!
There's a development pattern called MVVM, which allows you to develop the interface itself separately from the logic. The same pattern is used to develop all android apps....
If your builder allowed you to create a standalone interface that would fit into MVVM technology, then nobody would even discuss what the interface consists of.....
...
But that's all lyrics... wait for.... We have waited 2 years and we will wait another... March 3rd doesn't seem to be long now...
I will present the minimum on the 3rd. Creating and connecting a simple panel. I've only had three weeks to go from a markup language to a view editor. There has been a lot of work. By the end of March, the editor will be much more complete.
There's no such thing as a second-fresh fish.
I'll present the minimum on the 3rd. Creating and connecting a simple panel. I had only three weeks to go from a markup language to a visually editor. There has been a lot of work. By the end of March, the editor will be much more complete.
I certainly hope so!
There are familiar and understandable, generally accepted ways of interacting and I'd hate to see something obviously irrational.
In the end, of course, I'd like to be able to send data directly to and receive data from the interface:
Don't talk nonsense, please. Bugs will be fixed and features will be added.
I really hope so!
There are familiar and understandable, generally accepted ways of communicating, and I would hate to see something obviously irrational.
In the end, I would like to be able to send data directly to the interface and receive data from the interface:
TakiWhat does "much more complete" mean?
TakiWhat do you mean by "much more complete"?
Let's not engage in pettifoggery, we're not in court, Artem.
All the more so because Peter, unlike empty talkers like Baskakov, is proposing something.
You have me confused with someone else, Dimitri. I break any rules within the law - what kind of moderator am I?)
I didn't insist, on the contrary, I had my doubts. If I had been sure, I wouldn't have asked.