51

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> For is strong-dynamical things it is convenient reactive , for more or less static - declarative. S> here I now write and is declarative and . WPF allows to write and and so. There are no problems. Well, problems are not present. I first of all when felt WPF,  GUI-COMPOSITIONS pens, and? It is too inconvenient, as was clarified. More conveniently through XAML. In the code it is convenient to install only sv-va to some already available components in a scene. V>> you think, it will be difficult will fasten on top Flutter parcer of a format of language of the description of compositions  XAML?)) S> Once again read above. In WPF, in Xamarin. Forms it is possible to create all by means of the code. Simply it in most cases is inconvenient. You did not answer a question. Once again, slowly - you think it will be difficult to wind the declarative approach over any GUI-liby?

52

Re: and Chrome OS all

Hello, Serginio1, you wrote: S>>> approaches.Net Core b Xamarin Is better. Forms V>> Who about what, and bare about a bath. S> in in and the Samsung in  decided to use.Net Core and Xamarin. Forms Decided to support. It only one of possible graphic linguistic data bases. Them already tons efficient under Tizen.

53

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> For is strong-dynamical things it is convenient reactive , for more or less static - declarative. S>> here I now write and is declarative and . WPF allows to write and and so. There are no problems. V> well, problems are not present. V> I first of all when felt WPF,  GUI-COMPOSITIONS pens, and? V> It is too inconvenient, as was clarified. V> it is more convenient through XAML. V> In the code it is convenient to install only sv-va to some already available components in a scene. Not only. It is possible to add, delete, change. In certain cases for the declarative description of literary trash will be even more. V>>> you think, it will be difficult will fasten on top Flutter parcer of a format of language of the description of compositions  XAML?) ) S>> Once again read above. In WPF, in Xamarin. Forms it is possible to create all by means of the code. Simply it in most cases is inconvenient. V> you did not answer a question. V> once again, slowly - you think it will be difficult to wind the declarative approach over any GUI-liby? Here for Xamarin. Forms wind year and without the big break. A problem that in , and there different gui - . Though for UWP  DirectX  the worthy wound.

54

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: S>>>> approaches.Net Core b Xamarin Is better. Forms V>>> Who about what, and bare about a bath. S>> in in and the Samsung in  decided to use.Net Core and Xamarin. Forms V> Decided to support. V> it only one of possible graphic linguistic data bases. V> them already tons efficient under Tizen. And unless.Net Core it is graphic ? From.Net Core it is possible to cause your tons of graphic linguistic data bases, but it is more convenient Xamarin. Forms

55

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> it is more convenient through XAML. V>> In the code it is convenient to install only sv-va to some already available components in a scene. S> not only. It is possible to add, delete, change. It is possible, but it is inconvenient.  hierarchy Visual too , the compiler does not prompt a horse-radish, only by errors in  it is possible to judge an event.)) V>> you did not answer a question. V>> once again, slowly - you think it will be difficult to wind the declarative approach over any GUI-liby? S> Here for Xamarin. Forms wind year and without the big break. And can, there a problem not the technology roadmap, and what with any  Xamarin initially rolled out the circuit XAML, having different interpretations with the circuit from WPF/Silverlight/WinRT-UWP? Perhaps the problem consists especially in  standards on itself XAML? S> the Problem that in , and there different gui - . Such problem is not present.

56

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> It only one of possible graphic linguistic data bases. V>> them already tons efficient under Tizen. S> And unless.Net Core it is graphic ? Xamarin the graphic. S> from.Net Core it is possible to cause your tons of graphic linguistic data bases, but it is more convenient Xamarin. Forms For Tizen it is primary Xamarin, instead of.Net Core. And for Linux it is primary ASP.Net, instead of.Net Core.)) Karoch, conditions dictate application-oriented needs. Technologies here on the subordinate position.

57

Re: and Chrome OS all

Hello, vdimas, you wrote: V> For the Fuchsia free has initially been selected superficial  a kernel, from all these  prejudices. What for to a mobile phone superficial  a kernel? For what tasks?

58

Re: and Chrome OS all

Hello, Sharov, you wrote: V>> For the Fuchsia free has initially been selected superficial  a kernel, from all these  prejudices. S> what for to a mobile phone superficial  a kernel? For what tasks? You tell is better, what for the heavy?

59

Re: and Chrome OS all

Hello, vdimas, you wrote: S>> What for to a mobile phone superficial  a kernel? For what tasks? V> you tell is better, what for the heavy? The emphasis was more on  a kernel? What for it to a mobile phone?

60

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> it is more convenient through XAML. V>>> In the code it is convenient to install only sv-va to some already available components in a scene. S>> not only. It is possible to add, delete, change. V> it is possible, but it is inconvenient. Well if to compare with WinForms that to itself it is quite convenient. V> Unutre hierarchy Visual too , the compiler does not prompt a horse-radish, only by errors in  it is possible to judge an event.) ) Well it how to look V>>> You at a question did not answer. V>>> once again, slowly - you think it will be difficult to wind the declarative approach over any GUI-liby? S>> Here for Xamarin. Forms wind year and without the big break. V> and can, there a problem not the technology roadmap, and what with any  Xamarin initially rolled out the circuit XAML, having different interpretations with the circuit from WPF/Silverlight/WinRT-UWP? Perhaps the problem consists especially in  standards on itself XAML? Actually and UWP differs from WPF. It is visible then thought that WPF dies. S>> a problem that in , and there different gui - . V> Such problem is not present. Then in what. UWP now as a matter of fact anything from WPF that does not differ, and here  that WPF is far.

61

Re: and Chrome OS all

Hello, Somescout, you wrote: A>> Aha, aha. And consequently on the smart phone it is impossible to deliver the axis. S> yes it is fine: at me on the first smart phone of HTC HD7 it was possible, if I am not mistaken, to stitch instead of WP7 . It is necessary to recall, whether it was possible to deliver OS on the second yours . And generally, as setting  on the smart phone looks.

62

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> It only one of possible graphic linguistic data bases. V>>> them already tons efficient under Tizen. S>> And unless.Net Core it is graphic ? V> Xamarin the graphic. S>> from.Net Core it is possible to cause your tons of graphic linguistic data bases, but it is more convenient Xamarin. Forms V> For Tizen it is primary Xamarin, instead of.Net Core. V> And for Linux it is primary ASP.Net, instead of.Net Core.)) You are mistaken.Net Core. For Linux it is primary Asp.Net Core which on.Net Core. Xamarin it Mono, and it in  is not present. https://blogs.msdn.microsoft.com/visual … 0-preview/ V> Karoch, conditions dictate application-oriented needs. V> technologies here on the subordinate position. Well here needs just in convenient both powerful language and rather comprehensible Gue for IoT

63

Re: and Chrome OS all

Hello, alpha21264, you wrote: A> It is necessary to recall, whether it was possible to deliver OS on the second yours . , on a minus the first smart phone of Acer something various insertions  A> And generally as setting  on the smart phone looks there were put. As insertion filling. Or you expect  the installer on phone?

64

Re: and Chrome OS all

Hello, Sharov, you wrote: V>> You tell is better, what for the heavy? S> the emphasis was more on  a kernel? What for it to a mobile phone? The modern mobile phone is a media combine.

65

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> And can, there a problem not the technology roadmap, and what with any  Xamarin initially rolled out the circuit XAML, having different interpretations with the circuit from WPF/Silverlight/WinRT-UWP? Perhaps the problem consists especially in  standards on itself XAML? S> Actually and UWP differs from WPF. Not strongly, also does not differ almost from a cervelat. V>> such problem is not present. S> Then in what. UWP now as a matter of fact anything from WPF that does not differ, and here  that WPF is far.  is a technology of visual editing of forms, first of all. It quitted more advanced, than the built in editors of Studio. I.e.  here it is more in the technology of a CAD, than in specific , which at  more than one.

66

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> For Tizen it is primary Xamarin, instead of.Net Core. V>> And for Linux it is primary ASP.Net, instead of.Net Core.)) S> You are mistaken.Net Core. For Linux it is primary Asp.Net Core which on.Net Core. To yourself you contradict.

67

Re: and Chrome OS all

Hello, Berserk, you wrote: Google it not Nokija to cut a hen who buckets carries eggs, nobody will be. Google it is worse than Nokija. Google is concourse . Hipstote Android bothered, and to spit on eggs.

68

Re: and Chrome OS all

Hello, vdimas, you wrote: S>> the Emphasis was more on  a kernel? What for it to a mobile phone? V> the modern mobile phone is a media combine. And?  an axis what for, than normal not that?

69

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> And can, there a problem not the technology roadmap, and what with any  Xamarin initially rolled out the circuit XAML, having different interpretations with the circuit from WPF/Silverlight/WinRT-UWP? Perhaps the problem consists especially in  standards on itself XAML? S>> Actually and UWP differs from WPF. V> it is not strong, and does not differ almost from a cervelat. There is enough. V>>> Such problem is not present. S>> Then in what. UWP now as a matter of fact anything from WPF that does not differ, and here  that WPF is far. V> Kzamarin is a technology of visual editing of forms, first of all. V> it quitted more advanced, than the built in editors of Studio. V> I.e.  here it is more in the technology of a CAD, than in specific , which at  more than one. Yet really? The same Xamarin. Android and Xamarin. IOS as that live on , and it is primary Xamarin. Forms was without the editor. All program. Or it is necessary to use other studios https://habrahabr.ru/post/188130/Development UI For each platform Xamarin gives possibility to use  means of development UI and  user interface elements. For Android creation UI can happen immediately in the code or by means of the declarative approach to the interface description in XML. For iOS it also either the code, or usage  interface design tools - separate xib-files or one big Storyboard. Editing of these files happens in customary XCode environment for the iOS-developer. And it means that it is required to you Mac. Yes, for development of iOS-appendices anyway it is required to you Mac for two reasons: At first, as I already told, for editing UI in the environment of XCode. Secondly, for debugging of applications the simulator iPhone/iPad which also is accessible only on Mac is required. And about  Xamarin. Forms it and in soles is not necessary WPF. And, as to  there it is used.Net Core which for . Xamarin left from PCL and passed on.Net Standard.

70

Re: and Chrome OS all

Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> For Tizen it is primary Xamarin, instead of.Net Core. V>>> And for Linux it is primary ASP.Net, instead of.Net Core.) ) S>> You are mistaken.Net Core. For Linux it is primary Asp.Net Core which on.Net Core. V> to yourself you contradict. Explain. Asp.Net Core it also is.Net Core https://docs.microsoft.com/ru-ru/aspnet/core/ Applications ASP.NET Core can to be fulfilled in.NET Core or a. net Framework. Applications ASP.NET Core, intended for a. net Framework, are not  - they are fulfilled only in Windows. The failure from. net Framework support in ASP.NET Core is not planned. As a rule, ASP.NET Core consists of libraries.NET Standard. The applications written for.NET Standard 2.0 are launched everywhere where there is a support.NET Standard 2.0. What  on  a. net Framework? As it generally ASP.Net will work on  without.NET Core Besides the main usage  it Azure. There it manages more cheaply. Then under your approach for Linux it is primary Azure.

71

Re: and Chrome OS all

Hello, Sharov, you wrote: S> And?  an axis what for For responsiveness and predictability of response. S> than normal not that?  also is normal for client side, and package are good for server side.

72

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> Kzamarin is a technology of visual editing of forms, first of all. V>> it quitted more advanced, than the built in editors of Studio. V>> I.e.  here it is more in the technology of a CAD, than in specific , which at  more than one. S> yet really? The same Xamarin. Android and Xamarin. IOS as that live on  This consent or objection? S> and it is primary Xamarin. Forms was without the editor. And now there is only "live" viewer, if you about plug-in VS to Kzamarinu. High-grade there will be Kzamarin Studio. S> Secondly, for debugging of applications the simulator iPhone/iPad which also is accessible only on Mac is required. You  became outdated: https://xamdev.ru/ios-simulator-for-windows/ It is possible locally on  to launch Mac and to connect to it. S> And about  Xamarin. Forms it and in soles is not necessary WPF. It seems that you were never stuck in Xamarin Studio. Thus you run on all forums and you tell about advantage Xamarin.

73

Re: and Chrome OS all

Hello, Serginio1, you wrote: V>> to yourself you contradict. S> explain. Asp.Net Core it also is.Net Core technically Asp.Net Core is.Net Sandart + ASP.Net. But as "engine" here serves Asp.Net, instead of Core. S> https://docs.microsoft.com/ru-ru/aspnet/core/ the Applications written for.NET Standard 2.0 are launched everywhere where there is a support.NET Standard 2.0. S> what  on  a. net Framework? U-u-u....NET Standard is only next version bake on.Net . Marketing  absolutely fluidifies head contents, I look... S> As it generally will work ASP.Net on  without.NET Core Went begin to flow consciousnesses... S> Besides the main usage  it Azure. There it manages more cheaply. S> then under your approach for Linux it is primary Azure. Even analogy you can not formulate. For cloud MS it is primary Azure, instead of Linux.

74

Re: and Chrome OS all

Hello, vdimas, you wrote: S>> And?  an axis what for V> For responsiveness and predictability of response. How there can be a responsiveness and  with the user? And with  a software what? S>> than normal not that? V> Realtajmovye also is normal for client side, and package are good for server side. A bucket not  an axis.

75

Re: and Chrome OS all

Hello, vdimas, you wrote: V> It on changeover develops OS Fuchsia. Anybody never spoke that it is changeover Android. It is the research project, all remaining while simply gamble.