Giter VIP home page Giter VIP logo

Comments (6)

shekhar-shubhendu avatar shekhar-shubhendu commented on September 18, 2024

Does not makes sense to introduce and use a standard meant for Web Apps into a standard that can be used even by desktop apps.
If more fields are necessary please provide a list of them with a rationale behind each and we can discuss it here or in the forums.

from aexs.

davidyuk avatar davidyuk commented on September 18, 2024

Does not makes sense to introduce and use a standard meant for Web Apps into a standard that can be used even by desktop apps.

I see your point, Web App Manifests has some properties that are incompatible in case of the native desktop apps like display: "browser", scope, serviceworker, start_utl. But Web Manifests technically can handle that:

Note also that implementations are free to ignore any member they do not recognize or support. (https://www.w3.org/TR/appmanifest/#extensibility)

If more fields are necessary please provide a list of them with a rationale behind each and we can discuss it here or in the forums.

Let's add "icon" field. Icons are helpful because they make possible to recognize app faster than by reading its name, also most of the applications around us using them so it should be more user-friendly. In the worse case, we can communicate with aepp only by established connection, so it should be possible to pass an icon through it. Should we make possible to send icon in the response of wallet.request.connect as a base64-encoded string?

For the most popular use cases, this behavior looks strange. So I propose to describe metadata retrieving depending on the environment. Also, to suggest behavior explained above and "name" field to use in a case if none of the described cases is available.

from aexs.

davidyuk avatar davidyuk commented on September 18, 2024

Metadata in AEX-2 overlaps with #56, I think we should define it separately.

from aexs.

shekhar-shubhendu avatar shekhar-shubhendu commented on September 18, 2024

yes i guess but this can be done later too when that aex is final and should not be breaking change for aex-2.
or let me know if you have an estimate on its completion and we can try to release both together?

from aexs.

davidyuk avatar davidyuk commented on September 18, 2024

@j28 what do you think about it?

from aexs.

j28 avatar j28 commented on September 18, 2024

we should use the metadata standard from the aex draft.

from aexs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.