26

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

MasterZiv wrote:

On all questions - the answer "Yes".

Well tell to me, the magician how it is possible to collect easily RPM-ku, capable to update?

27

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

mayton wrote:

AlekseySQL, there are releases with  XFCE. They start by the machine with 128. A drawing - cut down
But packets should be up to date.

xfce on house  also costs.

makhaon wrote:

Know, misters, you, sense in perversions smile

The system fulfills ALL necessary actions (and very quickly!). What for to me time in 5 years to replace all iron with the new?

28

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

Dimitry Sibiryakov wrote:

Perhaps someone developed unified API for GUI?

Many programs are written on Qt (if I correctly understood a question). To me and as to the developer this library is pleasant, and as to the user (for example, my favourite torrent - the client - qBittorrent).

29

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

AlekseySQL wrote:

To me and as to the developer this library is pleasant, and as to the user

To me it is not pleasant neither as to the developer, nor as to the user because of foolish aspiration
To draw  it is independent that, at first, it is intolerable brakes, secondly,
It is broken out from the general style of system, and in the third, inflates it to impossibility.

30

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

AlekseySQL wrote:

it is passed...
Many programs are written on Qt (if I correctly understood a question). To me and as to the developer this library is pleasant, and as to the user (for example, my favourite torrent - the client - qBittorrent).

And how many layers graphic API in it are incapsulated? Normally of it you think when arises .
Here about 15 years ago studied Gnome/Gtk. Was not useful. Almost forgot.  it is very similar on Win32Gdi-lifecycle
application. But I still then was surprised with a stack. I will try to recall
C <-> glib/X <-> GDK <-> GTK + <-> Gnome <-> Application
Also it is simple . To it it is far to modern Qt/Wpf/Unity/WebGL. And how many at them layers?
And all these layers - separate software solutions with the  and with the matrix
Compatibility.

31

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

mayton wrote:

And how many layers graphic API in it are incapsulated? Normally of it you think when arises .
Here about 15 years ago studied Gnome/Gtk. Was not useful. Almost forgot.  it is very similar on Win32Gdi-lifecycle
application. But I still then was surprised with a stack. I will try to recall
C <-> glib/X <-> GDK <-> GTK + <-> Gnome <-> Application
Also it is simple . To it it is far to modern Qt/Wpf/Unity/WebGL. And how many at them layers?
And all these layers - separate software solutions with the  and with the matrix
Compatibility.

It is possible to theorize abstractly, of course, but upon I did not note brakes Qt - applications, and here when I load Windows simple interface actions start to irritate from - behind the . Besides the interface of operation with the user should be in time behind operation of the user, therefore its optimization towards convenience of development (and as a consequence - a victim in speed) I consider as the reasonable decision.
I never tracked an interface stack, simply I use convenient Qt - buns, and it suits me. For all history of operation on Linakse did not meet any application where the interface would brake.

32

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

AlekseySQL wrote:

For all history of operation on Linakse did not meet any application where the interface would brake.

You simply compensate a software a hard. Be not confused, it is a mainstream.

33

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

AlekseySQL wrote:

I never tracked an interface stack, simply I use convenient Qt - buns, and it suits me. For all history of operation on Linakse did not meet any application where the interface would brake.

In 2000 I experimented and put in a year of 2-3 different distribution kits beginning from Linux Black Cat.
I remember that the greatest number of problems (in normal user operation) me delivered
KDE. You probably noted that in Windows since 3.0 buffering of UI-events works.
even if application  in a part wndproc - that  it will not be lost
And comes when application droops and "will be processed. It is clever and  strategy.
What was at me horror when I saw that OpenSuse/KDE the sample of 2005 is not capable
To process such situation. Fairly. You could smash a mouse but braking
Processes in window cycles lost events. But it so. Trifles. Iceberg peak. Probably
Already it  but  remained. And the length of a stack too is important. Especially when
The bug is got on non-standard behavior . Creators SWING for example generally refused
From GDI OS. They from GDI take only primary window and title creation. And
clientarea means Java. It gives warranties that display will be maximum
Expected also does not collapse at passage with Windows on what thread Nexenta OS.

34

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

Dimitry Sibiryakov wrote:

You simply compensate a software a hard. Be not confused, it is a mainstream.

I so do not do, and about it wrote even in this subject (about setting of Linaksa on an old notebook).
I will repeat that when I on the same iron switch on Windows I receive notable brakes by operation with the interface (and I work on "heavy" KDE which is written on Qt). I also met such expression at forums from other people.

35

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

mayton wrote:

In 2000....

Today 2018, and already it is time to recognize that at the expense of Android Linaks the most widespread OS. The more the market of computers will drift towards small devices, the more company of Microsoft with the thick inaccurate products will leave in a non-existence.

36

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

Dimitry Sibiryakov wrote:

it is passed...
To me it is not pleasant neither as to the developer, nor as to the user because of foolish aspiration
To draw  it is independent that, at first, it is intolerable brakes, secondly,
It is broken out from the general style of system, and in the third, inflates it to impossibility.

And how you still  will receive? In any way, so alas...

37

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

AlekseySQL wrote:

it is passed...
Today 2018, and already it is time to recognize that at the expense of Android Linaks the most widespread OS. The more the market of computers will drift towards small devices, the more company of Microsoft with the thick inaccurate products will leave in a non-existence.

Today the MSEC is still strong. Not so it is strong as 10 years ago but all the same it has software solutions
Such as AutoCad, Photoshop, 3dStudio, a heap of software solutions for music and sound handling.
Ruler of office software and standards. And while there is a class of users
Which pay for , Windows to them will be necessary. And a segment of users - thick. . With a wide pocket.
Therefore and to support Win/Qt products still it is necessary. Is not present better  than a coin ring.
And concerning a non-existence. Is still Azure...

38

Re: Perspective of mastering of a Visual C ++ in environment Studio 2017

mayton wrote:

... But all the same it has software solutions
Such as AutoCad, Photoshop, 3dStudio, a heap of software solutions for music and sound handling.

Very frequent argument but when I would not hear it at once reflected: and what share of users works with the same photoshop or AutoCard? And why - that the answer always floated: a maximum of 1-2 %. And if to consider only to what are necessary nonexistent in Linaks - analogs of possibility this share in 10 times is less. For example, I as the user with small requests at audio editing always used  Audacity because me its functions above roof, and to understand a product in times easier (than with the heaped up professional audio - editors).