New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

WOW YOU REALLY ARE SUPER, @SuperJMN!! :) :) :) #2

Closed
Mike-EEE opened this Issue Jun 21, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@Mike-EEE

Mike-EEE commented Jun 21, 2017

WOWWWW.... this is a ping-ping to your pings at Microsoft/xaml-standard#20 (comment) and Microsoft/xaml-standard#193 (comment) and thought I would post in here instead as it tends to get a little stuffy in there. 馃槃 馃槅

I've also sent out a little ping to the Create a Ubiquitous .NET Client Application Development Model vote as that has turned into a semi-news hub of .NET client models (feel free to post a note there too if you feel so inclined).

So what's the scoop yo? Totally doing your own thing here? I am in complete agreement with your approach, of course. As you know, a consistent user experience is what I consider a necessary ubiquitous quality and one that Xamarin.Forms -- as impressive as it is -- takes a 馃挬 all over, LOL.

How does this square with Avalonia? Supplements it? Totally your own thing now? Details please. :) :) :)

(Also, @birbilis... looks like ANOTHER entry for my list of client models. Sigh. Gotta brush the dust off that thing. 馃)

@Mike-EEE

This comment has been minimized.

Show comment
Hide comment
@Mike-EEE

Mike-EEE Jun 21, 2017

OK @SuperJMN I got some <3 for you here:
http://blog.developers.win/2015/10/existing-net-client-application-models/#omnigui

(Unfortunately the quality matrix at the bottom requires an FTP so that is not updated just yet and probably won't be for a while.)

Mike-EEE commented Jun 21, 2017

OK @SuperJMN I got some <3 for you here:
http://blog.developers.win/2015/10/existing-net-client-application-models/#omnigui

(Unfortunately the quality matrix at the bottom requires an FTP so that is not updated just yet and probably won't be for a while.)

@SuperJMN

This comment has been minimized.

Show comment
Hide comment
@SuperJMN

SuperJMN Jun 21, 2017

Collaborator

Oh my God! You alone in one day have achieved more notoriety than me in a year 馃槷

Big, big thanks, Mike! by the way, I must say I would like to have some conversation with you, with some messenger program. You are one of the most enthusiastic people I've ever watched (because haven't met, yet!)

Collaborator

SuperJMN commented Jun 21, 2017

Oh my God! You alone in one day have achieved more notoriety than me in a year 馃槷

Big, big thanks, Mike! by the way, I must say I would like to have some conversation with you, with some messenger program. You are one of the most enthusiastic people I've ever watched (because haven't met, yet!)

@SuperJMN

This comment has been minimized.

Show comment
Hide comment
@SuperJMN

SuperJMN Jun 21, 2017

Collaborator

Mike, yes, I'm doing it all on my own. I already told some colleagues about, but it seems I'm the only one interested in something like this 馃構 BTW, I have pinged @migueldeicaza (https://github.com/migueldeicaza) and he seemed to like it!

Also, I won't bother @grokys because Avalonia has already migrated to Portable.Xaml and it's a pretty mature UI framework with a lot of collaborators. I understand they had to switch from OmniXAML to Portable.Xaml because they expect a XAML parser that works, with all the features packed, something that OmniXAML cannot provide just yet).

Collaborator

SuperJMN commented Jun 21, 2017

Mike, yes, I'm doing it all on my own. I already told some colleagues about, but it seems I'm the only one interested in something like this 馃構 BTW, I have pinged @migueldeicaza (https://github.com/migueldeicaza) and he seemed to like it!

Also, I won't bother @grokys because Avalonia has already migrated to Portable.Xaml and it's a pretty mature UI framework with a lot of collaborators. I understand they had to switch from OmniXAML to Portable.Xaml because they expect a XAML parser that works, with all the features packed, something that OmniXAML cannot provide just yet).

@SuperJMN

This comment has been minimized.

Show comment
Hide comment
@SuperJMN

SuperJMN Jun 21, 2017

Collaborator

Just to clarify things a bit about the project:
OmniGUI sits over simplicity. It's thought to be a component that fits into existing applications. In each platform it supports, OmniGUI will render inside a UIView, View, Control... or whatever a "UI component" is called in the target platform.

It will take the client area assigned to it and render like any other component, using drawing primitives available in the platform.

The interaction with it is also made possible because there are abstraction layers that provide the signals OmniGUI needs to make its components act in consequence to user actions.

For drawing, in iOS it uses CoreGraphics, in Android it uses Canvas, in UWP it uses Win2D and in WPF it uses a DrawingContext.

Collaborator

SuperJMN commented Jun 21, 2017

Just to clarify things a bit about the project:
OmniGUI sits over simplicity. It's thought to be a component that fits into existing applications. In each platform it supports, OmniGUI will render inside a UIView, View, Control... or whatever a "UI component" is called in the target platform.

It will take the client area assigned to it and render like any other component, using drawing primitives available in the platform.

The interaction with it is also made possible because there are abstraction layers that provide the signals OmniGUI needs to make its components act in consequence to user actions.

For drawing, in iOS it uses CoreGraphics, in Android it uses Canvas, in UWP it uses Win2D and in WPF it uses a DrawingContext.

@Mike-EEE

This comment has been minimized.

Show comment
Hide comment
@Mike-EEE

Mike-EEE Jun 21, 2017

Hehehe... yeah I find there's not a lot of luv in the trenches. So I will admit I sort of add to it a bit to make up for it. It's a cold world out there, what can I say. 馃懠

That's great to hear about Portable.Xaml and Avalonia. I have nothing but respect for that team and vision. They are also "with it." XF was a good stab, but I just don't see a lot of good things about it unless I am reading a Xamarin blog post. ;P

I haven't forgot about your IM request! I was going to get around to it when I started to hash all the (growing) issues in our repo at ExtendedXmlSerializer. It would be awesome to team up in some way with Omni*. I've been thinking about it. :) I will add you on Skype now, my man. Thanks again for being a passionate visionary. 馃憤

Mike-EEE commented Jun 21, 2017

Hehehe... yeah I find there's not a lot of luv in the trenches. So I will admit I sort of add to it a bit to make up for it. It's a cold world out there, what can I say. 馃懠

That's great to hear about Portable.Xaml and Avalonia. I have nothing but respect for that team and vision. They are also "with it." XF was a good stab, but I just don't see a lot of good things about it unless I am reading a Xamarin blog post. ;P

I haven't forgot about your IM request! I was going to get around to it when I started to hash all the (growing) issues in our repo at ExtendedXmlSerializer. It would be awesome to team up in some way with Omni*. I've been thinking about it. :) I will add you on Skype now, my man. Thanks again for being a passionate visionary. 馃憤

@grokys

This comment has been minimized.

Show comment
Hide comment
@grokys

grokys Jun 21, 2017

@SuperJMN just for the record, we've not switched to Portable.Xaml yet, though we hope to soon!

This looks really interesting, I will be keeping an eye on it! ;)

grokys commented Jun 21, 2017

@SuperJMN just for the record, we've not switched to Portable.Xaml yet, though we hope to soon!

This looks really interesting, I will be keeping an eye on it! ;)

@SuperJMN

This comment has been minimized.

Show comment
Hide comment
@SuperJMN

SuperJMN Jun 21, 2017

Collaborator

Hey @grokys!! Welcome! Thanks for coming 馃槃 I'm really sorry because OmniXAML couldn't keep the track of AvaloniaUI while it started to gain traction. Now it rocketed and needs to fly free! Well, it seems that my beloved XAML parser was too basic and intricate. I redesigned it n-times to face some big challenges. I hope Portable.Xaml is a booster for your project, instead of a flat tire.

BTW, I created OmniGUI just as proof-of-concept, to learn what I always wanted to learn, and I'm actually enjoying it.

What should I say? Without your inspiration and Avalonia it's very unlikely that this would have ever existed. I had a (very) bad time seeing that my real-life job took away my chances to be an important part in your project and finally understood that I had lost Avalonia's train.

I don't know where this will lead, I don't have high hopes, but from here I would like to tell you: Steven, thanks for everything.

Collaborator

SuperJMN commented Jun 21, 2017

Hey @grokys!! Welcome! Thanks for coming 馃槃 I'm really sorry because OmniXAML couldn't keep the track of AvaloniaUI while it started to gain traction. Now it rocketed and needs to fly free! Well, it seems that my beloved XAML parser was too basic and intricate. I redesigned it n-times to face some big challenges. I hope Portable.Xaml is a booster for your project, instead of a flat tire.

BTW, I created OmniGUI just as proof-of-concept, to learn what I always wanted to learn, and I'm actually enjoying it.

What should I say? Without your inspiration and Avalonia it's very unlikely that this would have ever existed. I had a (very) bad time seeing that my real-life job took away my chances to be an important part in your project and finally understood that I had lost Avalonia's train.

I don't know where this will lead, I don't have high hopes, but from here I would like to tell you: Steven, thanks for everything.

@Mike-EEE

This comment has been minimized.

Show comment
Hide comment
@Mike-EEE

Mike-EEE Jun 28, 2017

Gonna close this issue now to keep your issue slate clean. :)

Mike-EEE commented Jun 28, 2017

Gonna close this issue now to keep your issue slate clean. :)

@Mike-EEE Mike-EEE closed this Jun 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment