{"action":"created","issue":{"url":"https://api.github.com/repos/edvin/fxlauncher/issues/16","repository_url":"https://api.github.com/repos/edvin/fxlauncher","labels_url":"https://api.github.com/repos/edvin/fxlauncher/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/edvin/fxlauncher/issues/16/comments","events_url":"https://api.github.com/repos/edvin/fxlauncher/issues/16/events","html_url":"https://github.com/edvin/fxlauncher/issues/16","id":162324781,"number":16,"title":"[Idea] Reworking architecture of fxlauncher","user":{"login":"SirWindfield","id":5113257,"avatar_url":"https://avatars.githubusercontent.com/u/5113257?v=3","gravatar_id":"","url":"https://api.github.com/users/SirWindfield","html_url":"https://github.com/SirWindfield","followers_url":"https://api.github.com/users/SirWindfield/followers","following_url":"https://api.github.com/users/SirWindfield/following{/other_user}","gists_url":"https://api.github.com/users/SirWindfield/gists{/gist_id}","starred_url":"https://api.github.com/users/SirWindfield/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SirWindfield/subscriptions","organizations_url":"https://api.github.com/users/SirWindfield/orgs","repos_url":"https://api.github.com/users/SirWindfield/repos","events_url":"https://api.github.com/users/SirWindfield/events{/privacy}","received_events_url":"https://api.github.com/users/SirWindfield/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":28,"created_at":"2016-06-26T12:01:22Z","updated_at":"2016-06-28T19:15:17Z","closed_at":null,"body":"As discussed in #15, reworking the architecture of fxlauncher would allow to bring new features to it such as:\r\n\r\n1. Enabling updates for the launcher itself\r\n2. Version control of the application and rollback function\r\n3. Downloading the appropriate JRE (if not present on the system)\r\n\r\nAll of those changes would result in a small native executable (exe, app, etc.) that would download all needed dependencies on the first launch. The native stub wouldn't be bigger than 1 MB for sure, meaning that the launcher would function as a 'web installer'."},"comment":{"url":"https://api.github.com/repos/edvin/fxlauncher/issues/comments/229152672","html_url":"https://github.com/edvin/fxlauncher/issues/16#issuecomment-229152672","issue_url":"https://api.github.com/repos/edvin/fxlauncher/issues/16","id":229152672,"user":{"login":"SirWindfield","id":5113257,"avatar_url":"https://avatars.githubusercontent.com/u/5113257?v=3","gravatar_id":"","url":"https://api.github.com/users/SirWindfield","html_url":"https://github.com/SirWindfield","followers_url":"https://api.github.com/users/SirWindfield/followers","following_url":"https://api.github.com/users/SirWindfield/following{/other_user}","gists_url":"https://api.github.com/users/SirWindfield/gists{/gist_id}","starred_url":"https://api.github.com/users/SirWindfield/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SirWindfield/subscriptions","organizations_url":"https://api.github.com/users/SirWindfield/orgs","repos_url":"https://api.github.com/users/SirWindfield/repos","events_url":"https://api.github.com/users/SirWindfield/events{/privacy}","received_events_url":"https://api.github.com/users/SirWindfield/received_events","type":"User","site_admin":false},"created_at":"2016-06-28T19:15:17Z","updated_at":"2016-06-28T19:15:17Z","body":"> Another approach would be to offer a build server infrastructure to build everything in the cloud.\r\n\r\nWouldn't that cost something each month? I don't think there are services that offer something like that for free. \r\n\r\n> Then users don't need to build anything, just use a Gradle or Maven plugin to augment the installers that gets put in the build folder. I wonder if that's possible..\r\n\r\nYou mean we write the 'core' of them and distribute them. Gradle or Maven will then download them and inject the needed information into the executables later on while the application is building. Am I right? I am no expert at native applications/code but theoretically something like this should be possible. Do you know install4j? It's an application that creates an exe wrapper around a jar. It basically does the same thing. It has a core exe that executes some code and calls the jar afterwards. So somehow the needed information (VM arguments, name of the jar, additional arguments) need to be injected too. It is probably a exe that is designed to get the needed information and create another exe itself (like a build job). Not sure here though."}}
{"actor":{"display_login":"SirWindfield"}}