|
#realJSOP wrote: Not possible, because VS is a WPF application. "because shooting twice is just silly"
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
yeah... nah...
A year back looked at going this rout, didn't get as far as vs because first tried a few other simpler things (tools, utils I use) with wine that were gold rated and:
- at best I would say only "mostly" worked - sometimes caveats were noted, sometimes not.
- be prepared for at any time (even idle) for it to simply stop (freeze, spectacular or just disappear)
with a lot of tinkering I got things "more" mostly working but it was like per hour:
- 35 minutes tinkering,
- maybe 10 minutes actual work,
- 15 minutes preparing for the next inevitable fail
remember wine at best barely achieves stability at "windows xp" level, win 7?
wine is not something I would daily use for anything I rely on: firstly there's always the feeling it's going to fail 60, 15, 1 minute later,
and that's only after making all the compromises and adjustments to your usage of the app to "achieve better stability" (i.e. they say "use these settings, avoid using X, ...
remember dev of wine itself is low, still years behind, poorly managed. In terms of dev towards app compatibility that's totally ad-hoc at best - only if someone needs something and they got the energy to do it does it happen, and only as far as their own needs for that app.
stick to VM's
- it works, it's easy, you can actually concentrate on getting work done
- not losing time tinkering the platform, installing / practising workarounds and compromises
- in case you're worried it's legal.
<< Signature removed due to multiple copyright violations >>
|
|
|
|
|
Thanks for the heads up. I wasn't going to assume WINE was still unstable - it has been years since I've played with it, and I had heard some good things, but I guess I should remain skeptical.
My only issue using the VM is I only have 8GB of ram in my dev machine for now (long sordid tale, i really need to upgrade this old i5)
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I need at least a bottle and a half, just to get started.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I've been working on and off for the past year in trying to write a small mobile app to help my training at the gym. It's stupid simple what I'm after, but I've been trying to avoid going the easy (aka hard) route of separate iOS and Android apps. Because I like to complicate things and yet I'm lazy and super short on time.
I have a Windows Form version, which I ported to a Vue/Typescript web app. I'd like to stick to either .NET or TypeScript as my language of choice.
It seemed Xamarin would be sensible given that it allows me to stay in C#. Except my experience with Xamarin hasn't been great and it seems Microsoft is pushing React Native for UWP apps. So why not Reach Native? Porting Vue to React/RN is simple enough and I'll simply stick with TypeScript as my core language and I'm done.
Except that I cannot, for the life of me, get anything to work. I've forked GitHub repos that have "complete apps". I've walked through, line by line, the official docs on Facebook. I've spent the hour installing the Android SDKs, node, gradle, chocolatey, yarn, react native, etc etc etc. GB worth of installs. Endless command lines. Opening a powershell window in Admin mode to run the ps1 scripts. Manually adding the environment variables.
Insane.
I can't believe that 13 years after the iPhone was released we're still in the string and ducttape era of cross platform mobile development.
Once I get this working and boiled down to something sensible I'll write an article.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Except my experience with Xamarin hasn't been great Sorry to hear that. I've had nothing but success with Xamarin. Admittedly, I currently build native Android apps only.
/ravi
|
|
|
|
|
I've dealt with a few android apps using Android Studio, and each was a mess. Emulators either didn't function, or were pathetically slow/limited. Countless re-installations later, I opted to do live debugging on my phone and ditch emulation.
The one experience with Android apps that went smoothly involved a game I made in Unity3D. Got to keep the C# love, and it compiled for Android and ran without hassle.
|
|
|
|
|
im guessing you were running on windows. ihad an i7 8GB machine and it wasnt enough under windows
i recently upgraded my machine entirely so i could run Android Studio and emulator.
However i went back to the older machine and installed Ubuntu and Andrioid Studio and found that bec Linux OS uses so much less RAM (1.2GB base v windows 4-5 GB base) that i could run Studio and emulator on Linux.
The emulator constantly ran out of RAM on windows.
|
|
|
|
|
Yeah, it was a Win PC. I don't recall the specific issue in my case, but it ran like hot garbage on both my i3 and i7 laptop, 8g and 16g respectively. Once it ran so well on the live device, I just gave up on the troubleshooting.
|
|
|
|
|
In my limited mobile development I used Basic4Android (B4A). It is very simple, similar to VB6. They also have versions for iOS, Linux, and several others. b4x.com is the website.
|
|
|
|
|
Chris Maunder wrote: Once I get this working
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
|
|
|
|
|
Genuinely curious as I don't do that kind of stuff...
Is the problem ios development tools ? or cross-platform development ?
I'd rather be phishing!
|
|
|
|
|
|
I could code my mobile apps in Visual Basic?
Oh that's awesome.
cheers
Chris Maunder
|
|
|
|
|
Yes, a new year, a new language
|
|
|
|
|
|
Yes, many! However, I need a mobile app that can access sensor data so a pure web app isn't going to cut it.
If I stuck with Xamarin then I'd certainly be thinking about Blazor because of it's speed, and because I'd truly be working in a single language.
cheers
Chris Maunder
|
|
|
|
|
Those pesky details.
You fooled me by mentioning react.
|
|
|
|
|
Jörgen Andersson wrote: Those pesky details
I know, right?
cheers
Chris Maunder
|
|
|
|
|
ive developed a couple apps natively on Android (java via Android Studio) and iOS (swift via XCode).
XCode / iOS dev is such an odd beast, slow and unwieldy, with odd constructs.
Android Dev is so much nicer.
i often dream of writing apps in one language (especially C# ) but alas for anything except straight data driven apps that display data in basic forms Xamarin doesnt buy you much.
i keep trying Xamarin but it's yet another paradigm to learn and you really cant do extended things like connect to iot etc very easily.
The dream of code once build everywhere still doesnt quite exist. google is trying it based upon HTML5 via Flutter (flutter.io)
|
|
|
|
|
Start simple.
"Hello World"
|
|
|
|
|
I was thinking even simpler. Something like "Build succeeded".
In any case, it all works fine on my mac. Windows? Still no luck and I'm assuming it's a tool version mismatch.
cheers
Chris Maunder
|
|
|
|
|
With one UWP project, I'm available on "PC, Xbox, Mobile, HoloLens, and Surface Hub" (X86, x64, ARM).
My "mobile" is a Surface GO (though technically a PC).
The ARM "mobiles" are (apparently) starting to come into their own.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
What's a mobile app?
|
|
|
|
|
Yeah, mobile can be a pain.
NativeScript looks interesting. I think there are other Frameworks / Tools like this as well. E.g. PhoneGap, Cordova, React Native. Almost too many to choose from.
Flutter also looks cool, although you'll need to learn Dart.
|
|
|
|