Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osx ? #15

Open
joeblew99 opened this issue Mar 12, 2017 · 2 comments
Open

osx ? #15

joeblew99 opened this issue Mar 12, 2017 · 2 comments

Comments

@joeblew99
Copy link

all the work on packaging and releasing is awesome, and i would like ot help.

I am wondering about OSX.
Have a look at this
https://github.com/murlokswarm/macpack
It can make a OSX app and gen the Plist.
What i find really interesting is that they have a OS agnostic schema description, so it can be used for all OS's.

I am also working on making url schemes work for apps so that devs can link up apps to listen for other urls and also send urls. Allows composition.
They just put in the their first version of it for OSX.
https://github.com/murlokswarm/mac/commit/82cfcdae33ec9aeb04eaade142098ef7b9c7a2f2

@mh-cbon
Copy link
Owner

mh-cbon commented Mar 12, 2017

Hi! Yes that s a great package,
have you tried to build an app on travis macos ?
https://docs.travis-ci.com/user/osx-ci-environment/

What do you mean by:

What i find really interesting is that they have a OS agnostic schema description, so it can be used for all OS's.

The json file i read is containing a lot of very specific directive, in my understanding.

This electron builder handles a lot of output,
https://www.npmjs.com/package/electron-builder

@joeblew99
Copy link
Author

joeblew99 commented Mar 13, 2017

Travis

not tried building yet. But good point.

OS Agnostic

What i mean is that each OS has differences in how url scheme can be implemented.
So, i think that a manifest in YAML for all OS's can help here.
There would be a few levels for which this composition is needed:

  • Between Applications that do not know about each other at compile time.
    • Url schemes are a standard way to do this. For example: openUrl(Url("mailto:?subject=File from our app.&attach=" + fileName));
  • Between components that do not know about each other in the same App.
    • Each component publishes its url schemes, and others consume them.
    • We can make this more strongly typed too
      • Go generate at compile time the golang code from the Url schemes each app publishes in their manifest.
        • Golang constants for all Components to consume at compile time.
        • PList and Android manifests for the whole app.
    • A third party app can send an Url scheme event, and the App can then reroute it to the appropriate Component screen.

Manifest

At the moment he is not modelling the url-scheme hooks it seems, but i think he should.
https://github.com/murlokswarm/examples/blob/master/mac/hello/mac.json

I guess lots of logic can be pulled out the electron builder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants