Discussion of article "Graphical Interfaces VIII: the File Navigator Control (Chapter 3)"
cool! offer to add these libraries to the standard set in the terminal, and documentation on them. That would be awesome
Can anyone tell me what it's for? Practically.
Apart from an exercise in programming, of course.
I'm serious.
Can anyone tell me what it's for? Practically.
Apart from an exercise in programming, of course.
I'm serious.
In order not to repeat myself, I answered a similar question here: https: create a graphical interface to manage them. Or let it be your own tester, which is better than the standard one in your opinion. Or your programme needs to specify some data from the terminal's file sandbox, but not by entering a string containing the full path to the file, but through a file navigator, which can be created with the help of this library easily and simply. Perhaps it is some kind of analytical program for conducting researches or calculations with data visualisation immediately on a graph in the terminal. Build your own charts that are not bound to the time scale of the chart where the programme is located. A graphical interface is needed to manage all this "orchestra" conveniently. Sometimes you may need to change the values of some parameters on the fly, switch to some other mode, open and visualise some data. And instead of constantly going into the code or external parameters of the programme, which in my opinion is very inconvenient, if the application is a whole complex, you can simply create a compact graphical interface.
Even if such an offer were made, I think it's too early. There is still a lot of work to be done.
There is an important question that may well be of interest to developers.
What can be the labour costs for a developer when building the interface of his application with the help of your library?
How deep and long does it take to learn it in order to use your file navigator, calendar and scrolling?
Is it necessary to read all the articles and look at the code to build a settings window with checkboxes and drop-down lists?
What should a developer do if he wants to change the style of windows and controls? How hard is it to do it and do you need to study the whole library? After all, many people will probably want to do this because they want to avoid similarities with other developers' interfaces.
There is an important question that may well be of interest to developers.
What can be the labour costs for a developer when building the interface of his application with the help of your library?
How deep and long does it take to learn it in order to use your file navigator, calendar and scrolling?
To use the library it is enough to study the examples attached to each article. You should not study every class and scheme in depth, if you don't want to learn how to make such libraries yourself. But if you study it, such experience may be useful when developing any other libraries of similar complexity.
Is it necessary to read all the articles and look into the codes to build a settings window with checkboxes and drop-down lists?
I'm preparing material for an article that will summarise the whole series. It is very concise and it is for those who need a library for creating graphical interfaces in their applications.
What should a developer do if he wants to change the style of windows and controls? How hard is it to do it and do you need to study the whole library? After all, this desire will probably arise in many people because of the desire to avoid similarity with the interfaces of other developers.
All objects from which interface elements are built are available. If you are not satisfied with the default style, you can customise your own. Gradually more possibilities will be provided.
If you need something urgently, you can already write your own class and connect it to the library engine. How to do this has been shown many times in many articles of this series.
To use the library it is enough to study the examples attached to each article. It is not worth studying each class and scheme in depth, unless you want to learn how to make such libraries yourself. But if you do, this experience may be useful when developing any other libraries of similar complexity.
I am preparing material for an article summarising the whole series. It is very concise and exactly for those who need a library for creating graphical interfaces in their applications.
All objects, from which interface elements are built, are available. If you are not satisfied with the default style, you can customise your own. Gradually more possibilities will be provided.
If you need something urgently, you can already write your own class and connect it to the library engine. How to do this has been shown repeatedly in many articles in this series.
Thank you for your detailed reply.
It is interesting to know your plans. How many more articles you plan to publish and what further goals you set.
Thanks for the detailed reply.
It is interesting to know your plans. How many more articles do you plan to release and what are your future goals.
Two more basic articles for the first version of the library.
And then I will think about implementing suggestions from interested users. I will think about yours too.
Two more main articles for the first version of the library.
And then I'll think about implementing suggestions from interested users. I'll think about yours as well.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
New article Graphical Interfaces VIII: the File Navigator Control (Chapter 3) has been published:
In the previous chapters of the eighth part of the series, our library has been reinforced by several classes for developing mouse pointers, calendars and tree views. The current article deals with the file navigator control that can also be used as part of an MQL application graphical interface.
The screenshot below shows the unfolded file navigator tree view:
Fig. 2. Unfolded structure of the file navigator tree view
Author: Anatoli Kazharski