dragora-members
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dragora-members] Relation of Qi and Qire


From: Matias Fonzo
Subject: Re: [Dragora-members] Relation of Qi and Qire
Date: Mon, 15 Jun 2020 09:20:36 -0300
User-agent: Roundcube Webmail/1.4.4

El 2020-06-14 09:20, Michael Siegel escribió:
Am 13.06.20 um 00:35 schrieb Matias Fonzo:

I understood that you want Qire's ability in Qi, but I also understood
that for a better understanding of both things we should unify or extend
with appropriate languages since the package managing is something
complex, as Qi currently works well, maybe there is no need to rewrite
Qi now (and I hope not :-).

Why add more code when you can invoke qire, besides being better off referring to the extension directly.

Well, I wasn't meaning to imply that Qi should explicitly include the
ability to do what Qire does. I was just trying to say that I think Qi
should be the way the user invokes those things. I.e., Qi should be able
to make use of Qire seamlessly if that is possible.

The point of having only one command leads to think that Qi could invoke
the "extensions" of Qire, by this I meant part of Qire, not the whole
interface, taking into account everything Qi already has, including the
documentation format.

This has the advantage that parts of "Qi" will be in Fennel/Scheme/Lips or whatever, while in the future parts or modes of Qi could be replaced
in the same language (if needed).

On the other hand, we still don't know how users will interact using qi
and qire, it might be positive (I hope).

Sorry, but this confuses me even more.

Could you explain the relation of Qi and Qire how you currently envision
it for Dragora 3 once again as if you were trying to explain it to
someone who has no prior knowledge of those things? That will surely
help to cure my confusion.

I agree with you on using only one command, hence I think it is better to have the remote extensions in one command. If you don't have them in one, then I think it's better to learn them separately, with their respective documentation. We don't yet know how this will work out for the user in practice, it may well work out how it doesn't. I still think that incorporating some of Qire's code into Qi is a good idea. But I also understand that Kevin has his reasons for not doing so, so I assume he prefers to keep it that way. I don't have a problem with both, but I still think that making it easier for the user is the "single" option...




reply via email to

[Prev in Thread] Current Thread [Next in Thread]