« Return to Thread: Preparing Ryppl Developer Preview based on 0install
Re: Preparing Ryppl Developer Preview based on 0install
by Tim Cuthbertson-2
::
Rate this Message:
On Thu, Apr 19, 2012 at 9:52 PM, Bastian Eicher <bastian@...> wrote:
>> <entry-point>
>>
>> What are these, and do we need them on an index?
>> It may be used for distinguishing libraries from commands, which is a
>> good idea. But if that's the purpose I would expect to just see a list
>> of the <command> tags (probably omitting the path and runner
>> information for brevity, but I'm not bothered if it stays in)
>
> <command> tags are located within specific implementations. Not all versions
> of an application necessarily provide the same commands.
> The intention of <entry-point>s is to provide a feed-level list of available
> commands along with optional icons and localizable descriptions. (The
> binary-name tag is used as a hint for a suitable alias name.) They are
> mainly used by the Windows desktop integration system but I believe the data
> would be equally applicable to 0desktop.
> In short: An <entry-point> describes what an application can do and a
> <command> describes how to get it to do just that.
I'd prefer to combine this with the <command> tag (by adding a few
optional tags/attributes like "binary-name" and descriptions), so we
don't have to repeat ourselves. I don't think the problem of commands
differing across implementations can't actually be be avoided either
way - if you add, remove or change an entry-point as of a certain
release, older implementations will not actually support it - so you
might as well just get the list of commands from the latest
implementation as a *guide* to what commands an interface most likely
supports, which I think is the best you can do regardless of whether
you use implementation-level or feed-level elements.
> The Zero Install for Windows GUI uses the <entry-point>s to populate a
> "Select command" dialog box. In order to be able to display this dialog box
> in the "New applications" list before retrieving individual feeds and since
> the <entry-point>s do not describe anything implementation-specific I
> decided to add them to the catalog.
What happens if you pick an entry point that isn't actually supported
by the impl that is later selected?
Cheers,
- Tim.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Zero-install-devel mailing list
Zero-install-devel@...
https://lists.sourceforge.net/lists/listinfo/zero-install-devel
>> <entry-point>
>>
>> What are these, and do we need them on an index?
>> It may be used for distinguishing libraries from commands, which is a
>> good idea. But if that's the purpose I would expect to just see a list
>> of the <command> tags (probably omitting the path and runner
>> information for brevity, but I'm not bothered if it stays in)
>
> <command> tags are located within specific implementations. Not all versions
> of an application necessarily provide the same commands.
> The intention of <entry-point>s is to provide a feed-level list of available
> commands along with optional icons and localizable descriptions. (The
> binary-name tag is used as a hint for a suitable alias name.) They are
> mainly used by the Windows desktop integration system but I believe the data
> would be equally applicable to 0desktop.
> In short: An <entry-point> describes what an application can do and a
> <command> describes how to get it to do just that.
I'd prefer to combine this with the <command> tag (by adding a few
optional tags/attributes like "binary-name" and descriptions), so we
don't have to repeat ourselves. I don't think the problem of commands
differing across implementations can't actually be be avoided either
way - if you add, remove or change an entry-point as of a certain
release, older implementations will not actually support it - so you
might as well just get the list of commands from the latest
implementation as a *guide* to what commands an interface most likely
supports, which I think is the best you can do regardless of whether
you use implementation-level or feed-level elements.
> The Zero Install for Windows GUI uses the <entry-point>s to populate a
> "Select command" dialog box. In order to be able to display this dialog box
> in the "New applications" list before retrieving individual feeds and since
> the <entry-point>s do not describe anything implementation-specific I
> decided to add them to the catalog.
What happens if you pick an entry point that isn't actually supported
by the impl that is later selected?
Cheers,
- Tim.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Zero-install-devel mailing list
Zero-install-devel@...
https://lists.sourceforge.net/lists/listinfo/zero-install-devel
« Return to Thread: Preparing Ryppl Developer Preview based on 0install
| Free embeddable forum powered by Nabble | Forum Help |
