MacGapProject / MacGap2

MacGap 2
MIT License
1.19k stars 85 forks source link

Is MacGap2 dead? #64

Open behrangsa opened 8 years ago

behrangsa commented 8 years ago

Last commit is from 5 months ago. Is MacGap dead? Is it renamed to something else?

Is there a thorough documentation available for it? Any screencasts? Books?

Thanks, Behrang

jeff-h commented 8 years ago

Hi — it's not dead, more a case of "it works well enough for 90% that we don't get pushed hard to implement something new".

Also, since it's aimed at Javascript developers (who usually don't also write Objective-C), there are very few users able to commit new features. Those that can commit new features typically aren't that interested in what MacGap does, since they could code their own native solution in most use-cases.

It's a case where the typical open source "scratch-your-own-itch" motivation doesn't quite fit the equation, unfortunately. There are a few recent issues which have remained without a good solution for exactly this reason e.g. https://github.com/MacGapProject/MacGap2/issues/62

To my knowledge there is no better solution for close-to-native web apps on OS X.

behrangsa commented 8 years ago

HI @jeff-h,

Thanks for your reply. Liveness of the project aside, are there any good tutorials, screencasts, articles, etc. for getting started with MacGap and building an app? Does MacGap have an API docs similar to Java, Cocoa, or, say, Angular JS? For People who are familiar with PhoneGap, it might be easy to get started and write MacGap apps, but I haven't used PhoneGap before so I am looking for a MacGap: The Beginners Guide kind of introduction/book/article.

Also while the functionality of MacGap might be complete enough it is still lackadaisical on the documentation side of things. And no progress being made in this area, makes MacGap more or less an unmaintained project.

puccaso commented 5 years ago

Hey there guys, Love the app. I can completely under the 90% working user case, but with recent changes to Mojave and xcode, plus safari12's new security requirements, I wonder if a tiny update might be required? or at least that what i'm requesting.

Xcode gives a plethora of things to be changed, MenuItems dont conform, loads of stubs etc - to be honest, i dont even know what a stub is - but xcode wants to put it in the project, and things break.

love the code!

jeff-h commented 5 years ago

Strange — it compiles just fine for me (Mojave 10.14.1, Xcode 10.1). It did throw a bunch of warnings but that's not too unexpected. It did suggest adding one stub but gave me nothing about MenuItems. Are you on an older version of Xcode perhaps?

Regardless, I just updated the code to remove most of the warnings.

In terms of the future of MacGap, would you mind sharing a few thoughts on why MacGap appeals? For me it was primarily to avoid the enormous & unnecessary weight of Electron, but that feels like a lost battle in 2018.

blakewatson commented 5 years ago

@jeff-h The file size issue is still the main appeal of MacGap to me. I think that it's even more important in 2018/19 that we figure the "Electron problem" out. It's clear that there's a big market for desktop apps built on web technology. It's no big deal for a user to be running one Electron app. But when you've got half a dozen Electron apps running at once it becomes a significant performance problem. I made a dice roller for RPG tabletop games in Electron and it's published on the Mac App Store. I'm embarrassed that my app is so large, given its relatively low complexity. But, I’m a web developer by day and it would take a lot of time I don’t have to learn native app development.

I think this project and others like it are more relevant now than ever.

tcaer commented 5 years ago

I personally agree that the weight of Electron is a big problem for me. It is something I can feel when running them on my machine. MacGap really helps address that issue while still providing a lot of the same functionality.

jeff-h commented 5 years ago

The huge advantage Electron brings is cross-platform capability. Is that not necessary for you guys? Just playing devil's advocate here :)

Overall, MacGap2 is based on two technologies that are showing their age (Objective-C and WebView). Ideally we'd embark on a v3 written in Swift and using WKWebView. The biggest problem is just that I don't personally use MacGap and it would be quite a time-consuming project!

blakewatson commented 5 years ago

@jeff-h Yeah my use case doesn't require cross-platform capability (in which case I should probably be using native code instead of HTML/CSS/JS). I just want to make desktop apps on the Mac with web tech—which, admittedly, isn’t a compelling reason for you to continue work on it. :-)

blakewatson commented 5 years ago

I still say a lightweight alternative to Electron would be great though. For developers and users.

jeff-h commented 5 years ago

Yeah — I definitely believe in MacGap and its place in the world. I just wish someone else would write it lol I'd love to dive into it, but I've learnt enough to know that once the fun fades and it becomes hard work it's going to get "procrastinated"...