shannah78

9 ms·

1.
JDeploy 5.0: Deploy Java Desktop Apps to ARM64 Windows and Linux with One Click
4 points by shannah78 1y ago|0 comments
2.
by shannah78 2y ago
What do you mean be centralized service? It allows you to publish to GitHub releases or npm. Do you mean "central" like "GitHub"?
3.
by shannah78 2y ago
I think Swing is a non-goal of this project. It provides good interop with the DOM and core JS methods, and it makes it easy to create your own interop for JS apis that aren't in the core. There are at least two GUI toolkits that run
4.
by shannah78 2y ago
A little over 10 years ago, I ran across TeaVM for the first time (probably) on GitHub. We had been looking for a way to port Codename One to the web, but we needed thread support, which wasn't supported by any existing solutions. I em
5.
by shannah78 4y ago
Nice. I haven't used Flavour for anything yet, but TeaVm is awesome sauce! This past year or so, I've noticed an uptick in activity surrounding TeaVM. More contributions from people other than Alexey. Some of this is seems to
6.
by shannah78 5y ago
"at the cost of some npm shenanigans" jDeploy developer here. No shenanigans, I swear. npm just simplified things. Some have expressed interest in adding self-hosting options, so I'll likely add support for that. It&#x27
7.
by shannah78 5y ago
"Swing suffered from two central weaknesses: the tutorials provided by Oracle were... often insufficient. And you could pick up some bad habits by following them. And then there were the UI builders where anybody could draw up somethin
8.
by shannah78 5y ago
My experience with many Swing apps is the same. I think a large part of the problem lay with the development tools. When you create a new Cococa project in Xcode, it generates a full app with all the necessary parts to feel native. You bu
9.
by shannah78 5y ago
I always found this very confusing. I still do. At one point in time I think I could have explained why there were three tags. But I don't remember the specifics anymore.
10.
by shannah78 5y ago
I never really understood why, but I can guess. Could have been political/strategic, to try to force developers onto Objective-C. Or his keen attention to detail might have just bristled at some of the performance an UI issues that m
11.
by shannah78 5y ago
Neat. I hadn't heard of either of those before (though I'm not a Clojure developer). Thanks for sharing.
12.
by shannah78 5y ago
100% agree. The "distribution" step has always taken way more time than I expected. And, I almost always had to compromise on certain platforms just because it couldn't get the square peg in to the round hole. The goal of
13.
by shannah78 5y ago
That sounds about right to me. AJAX - or more broadly, what we call HTML5 could have been the gamechanger.
14.
by shannah78 5y ago
The FileDialog is the only AWT widget I still use regularly. It gives you the native file chooser. Unfortunately it isn't terribly flexible when it comes to, for example, only selecting directories. In those cases, I have been known
15.
by shannah78 5y ago
I started from the other side of that fence, and I remember feeling jealous of how smooth the GUI editor was in Visual Studio. Even in 2022, I still don't think I've seen any Java GUI builders that are as easy to use as Visual St
16.
by shannah78 5y ago
I can't disagree with anything you say here, except the thing about "the article seems quite off". lol. This piece covers the state of the technology at that time. In the early 2000's Java was slow. I wasn't famil
17.
The decline and fall of Java on the desktop(jdeploy.substack.com)
247 points by shannah78 5y ago|357 comments
18.
by shannah78 5y ago
> It was a little odd that the new download had the same version number as the old The build number refers to your app version. The download page creates the bundle on the fly (but does cache) using the latest jDeploy release, so when I
19.
by shannah78 5y ago
This is fixed now. If you download the demo again it should work for you.
20.
by shannah78 5y ago
I have reproduced this issue, and have posted and update that should fix it. Please try downloading either of the demos again and let me know if it still gives you issues.
21.
by shannah78 5y ago
> Any plans for commercial features in the future? I'll have to find out what kinds of features are of interest to commercial clients. I'd like to find some way to support continued development. Commercial features are certai
22.
by shannah78 5y ago
I agree. Once you fight through the initial project setup, and solve the deployment difficulties (jDeploy), Java is a remarkably good platform for Desktop development. The sheer number of libraries available to you with a simple copy&#x2F
23.
by shannah78 5y ago
I have received a few reports on Linux. I'm working on it. Literally this is the reason why jDeploy is helpful. I've spent 2 years working out many details. Every OS/Version/distribution has needed some special care.
24.
by shannah78 5y ago
> Very naive question but is it different from what npm, pip, etc. let you do already? npm, pip, etc.. are CLI install tools. jDeploy supports CLI app distribution using npm also. But the key difference is that jDeploy provides double-
25.
by shannah78 5y ago
The launcher is about 3 megs compressed. The actual jar files and JVM are downloaded on demand in the $HOME/.jdeploy directory.
26.
by shannah78 5y ago
> I need to not use public npm. In a previous iteration everything was designed to be self-hosted, but decided to focus on npm support because it made things much simpler. I'll be re-exposing the self-hosting, and private npm opti
27.
by shannah78 5y ago
> Interesting idea, though I thought the orig. goal of Java was to avoid this in the first place. IMO this is moving back in the direction of the original WORA philosophy of Java. jDeploy is designed to be cross platform. No platform-s
28.
by shannah78 5y ago
> But hats off, cool project! Thanks!
29.
by shannah78 5y ago
Thanks. I saw the issue (presumably) you posted, and am setting up a VM to try to reproduce. Should have this fixed shortly.
30.
by shannah78 5y ago
Hard to tell if this is sarcasm. However, I totally agree that learning about operating system packaging is a rewarding exercise. In developing jDeploy I had to learn a lot of details about OS packaging. Very interesting most of the time

More ›