Earlier quoted context omitted.
If the creator wants an ad there, let him put an ad there or just simply stop using the app.
Ok, what about the vision impaired? Or any other point I mentioned?
Vue Native (2018)
181–190 of 190 posts
Re: Vue Native (2018)
#182Earlier quoted context omitted.
Ok, what about the vision impaired? Or any other point I mentioned?
I didn't know about this. Is Flutter web ignoring accessibility when rendering to HTML? If so that is a no no.
Re: Vue Native (2018)
#183Earlier quoted context omitted.
i'm not a js hater but i'd be curious to hear what you think is so great about ts
It is pretty damn powerful and quite elegant. What do you find bad about it?
Re: Vue Native (2018)
#184Earlier quoted context omitted.
Shoutout for Framework7. I built a test app in both Ionic and Framework7 and vastly enjoyed the experience of F7 over Ionic. For Ionic Vue is still in beta, poorly documented and had some vague errors with obtuse solutions. It didn't have all the components you might want in an app either, so less boiler plate. Framework7 has full Vue documentation, and the handful of components that aren't Vueified (Calendar, Toasts…
Ionic vue is no longer in beta, though it will take ~a year before it reach full parity support vs other VDOMs
https://ionicframework.com/blog/announcing-ionic-vue/
Will give it another spin. Because UI wise, it was faster.
Re: Vue Native (2018)
#185Earlier quoted context omitted.
> The problem is that it's bad. I say this as someone who comes from the outside, and isn't an expert ("barely competent" in HTML/CSS is probably accurate). Basic layout of things in a way that copes with different screen sizes/orientations is a surprisingly black art sometimes. There's a lot of history confusing the issue and three ways of doing each thing. How can you say this with a "barely competent" level of exp…
> How can you say this with a "barely competent" level of expertise? I get that, and that's why I declared it. I have two reasons why I think the opinion is still valid: I'm not completely incompetent. I have produced useful web frontend work. After having spent more time on web technologies than a lot of others I still find it to be slower and harder. This point is about learning - I have done some learning in both…
But the complexity arises from wanting to make apps with something meant for simple documents. That being said, even building the simplest website nowadays requires a mind-boggling knowledge of the idiosyncrasies of the "languages".
I want to lose my job; I want the next best thing to be completely different but still allow for creativity and productivity.
Re: Vue Native (2018)
#186Earlier quoted context omitted.
Yup thank you. Web is only now coming to terms with desktop application development world of doing things. While I support the movement, however there are too many legacy stuff in the web and how front end developer use JS like jquery type of thing to manage a document base page. Maybe there should be a mode like 'stric mode' to support two way data binding.
The problem, if there is one, with the web stuff discussed here is not that it is not strict enough to facilitate two way data binding but the opposite. Modern web frameworks use stricter one way data binding because they posit two way data binding is too dangerous / hard to reason about. It could easily be added and vue does in fact have some of it.
Re: Vue Native (2018)
#187Flutter web is also becoming a viable option for web apps. I recently wrote a new app in Flutter and it works surprisingly well on the web, not just in native iOS and Android. It has some quirks though but I did not find anything serious.
I have a large Flutter codebase and I don't have the same opinion, Flutter web is still an alpha quality and it would take way too much work to make my codebase work with the web version. For desktop though, it's pretty good.
Re: Vue Native (2018)
#188is there any project that would us the same js - native bridge as react native, except with wasm. The idea would be to let us write cross-platform business level code in any language targeting wasm, while using a native UI framework
Not exactly the implementation you described but Kotlin Multiplatform is targeting this workflow. Shared business logic in Kotlin and Native UI on each platform. You can currently compile to iOS/Android/Web and Desktops. I imagine the could support wasm at some point too. Edit: Kotlin Multiplatform not Kotlin Native
Re: Vue Native (2018)
#189I love functional concepts such as stateless systems, but young folks should acknowledge that two way event binding is something graphical desktop toolkits are doing since decades. For instance, Qt signal-slot mechanism https://doc.qt.io/qt-5/signalsandslots.html or https://libsigcplusplus.github.io/libsigcplusplus Furthermore, MVC is , when done correctly, a sane two way data-GUI binding. However, I have never seen…
Hopefully one day we can get to where Visual Basic was in the 90's.
Re: Vue Native (2018)
#190Earlier quoted context omitted.
Can you elaborate? Undo/redo in what contexts? What applications had undo/redo besides for editing things?
Is "editing things" (i.e. data) not central in the majority of apps?
Text editor? Those have undo.
Image editor? Also have undo.
Video Games? Depends. Should you be allowed to "undo" in a game of minesweeper? Probably not- it kind of ruins the game. Should you be allowed to "undo" in Chess? Probably not. Should you be allowed to undo in Solitaire? Maybe.
Chat client? What would you undo? Can't unsend a message.
Web Browsers have back buttons, to the extent that those can undo.
I could see file managers maybe having undo. I honestly don't know if the popular ones today do or not.
What apps are missing undo functionality for you?