Op dinsdag 11 september 2018 06:03:28 CEST schreef David Cousens:
> This link (http://www.sagehill.net/docbookxsl/Db5Tools.html) provides the
> mechanism for linking between different docbooks. It would probably a good
> idea to mark any docbook links with a do not delete message for example. so
Op dinsdag 11 september 2018 09:15:43 CEST schreef David Cousens:
> David,
>
> Just some comments on a couple of other points:
>
> Embedding even the context help in the program code is not a really good
> idea. It means that text cannot be edited /altered easily separately from
> the program
David,
Just some comments on a couple of other points:
Embedding even the context help in the program code is not a really good
idea. It means that text cannot be edited /altered easily separately from
the program and without rebuilding the program. My understanding is that it
can be done from
Thanks Frank,
I didn't know about the Lonely pages . that helps a lot.
David Cousens
-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
On Tue, 2018-09-11 at 08:46 +0200, Frank H. Ellenberger wrote:
> Am 11.09.2018 um 06:03 schrieb David Cousens:
> > One other problem with a WIki for a maintenance
> > point of view is thatt a link to a page can be deleted and the page becomes
> > an orphan with no way to logically access it. A
Hello,
> On Sep 11, 2018, at 4:45 AM, Geert Janssens
> wrote:
>
> Op dinsdag 11 september 2018 09:15:43 CEST schreef David Cousens:
>> David,
>>
>> Just some comments on a couple of other points:
>>
>> Embedding even the context help in the program code is not a really good
>> idea. It means
> On Sep 11, 2018, at 5:12 PM, David Cousens wrote:
>
> Hi John,
>
> I do understand that alternatives to docbook are being considered.
>
> I keep referring to it primarily because it is the current format, rather
> than necessarily the best or even what may be used in future. Perhaps with
Hi John,
I do understand that alternatives to docbook are being considered.
I keep referring to it primarily because it is the current format, rather
than necessarily the best or even what may be used in future. Perhaps with
an assumption that whatever format is decided on, it will at least
> On Sep 11, 2018, at 1:45 PM, Geert Janssens
> wrote:
>
> Somewhere in the long thread about future documentation directions the issue
> of translating documentation was raised. Rightfully so, because this is
> currently a very challenging task.
>
> The initial translation, while a huge
John,
Point taken. I rarely use the yelp viewer from inside Gnucash at all and
mainly use the online HTML documentation. It could be to separate context
sensitive help into it's own structureis one way to go. I would have thought
for the more tutorial aspects currently in the guide it would
Hi Geert
"I know you can define these links in docbook. However my remark earlier in
this thread is how will they work in practice ? How can one document on the
system know where the other is stored ? I presume this means we should have
strict rules about the relative locations of documents.
> On Sep 11, 2018, at 8:13 AM, David Cousens wrote:
>
> Hi Geert
>
> "I know you can define these links in docbook. However my remark earlier in
> this thread is how will they work in practice ? How can one document on the
> system know where the other is stored ? I presume this means we
Then I misunderstood some earlier discussions about the UI, at least with
respect to Linux. What toolkit is envisioned to be used? What layout
principles? Or are those questions so far in the future as to not be worth
spending time allowing room for?
Regards,
Adrien
> On Sep 11, 2018, at
> On Sep 11, 2018, at 8:13 AM, David T. via gnucash-devel
> wrote:
>
> Hello,
>
>
> I envision that the context help would consist of short _functional_
> descriptions of one or two sentences. I believe that the rate of change in
> the functions of the UI elements is exceedingly small. In
I don't know about allowing room for it, but it's pretty far in the future
because we still have too many Gnome dependencies in the core and too many MVC
violations to be able to implement a different toolkit.
Regards,
John Ralls
> On Sep 11, 2018, at 10:23 AM, Adrien Monteleone
> wrote:
>
> On Sep 11, 2018, at 10:09 AM, Adrien Monteleone
> wrote:
>
>
>
>> On Sep 11, 2018, at 8:13 AM, David T. via gnucash-devel
>> wrote:
>>
>> Hello,
>>
>>
>> I envision that the context help would consist of short _functional_
>> descriptions of one or two sentences. I believe that the
Adrien,
> On Sep 11, 2018, at 1:09 PM, Adrien Monteleone
> wrote:
>
>
>
>> On Sep 11, 2018, at 8:13 AM, David T. via gnucash-devel
>> wrote:
>>
>> Hello,
>>
>>
>> I envision that the context help would consist of short _functional_
>> descriptions of one or two sentences. I believe
Op dinsdag 11 september 2018 15:13:51 CEST schreef David T.:
> Hello,
>
> > On Sep 11, 2018, at 4:45 AM, Geert Janssens
> > wrote:>
> > Op dinsdag 11 september 2018 09:15:43 CEST schreef David Cousens:
> >> David,
> >>
> >> Just some comments on a couple of other points:
> >>
> >> Embedding
Yes, sorry. I misspoke on that last point.
Regards,
Adrien
> On Sep 11, 2018, at 1:10 PM, David T. wrote:
>
> Adrien,
>
> I’ll note here that you seem to have the documentation model backwards,
> insofar as you suggest that interface changes wouldn’t affect the Guide. I
> believe that such
Op maandag 10 september 2018 17:26:44 CEST schreef David T. via gnucash-devel:
> The idea of use-case recipes sounds rather like the “walkthrough" described
> in the pronovix article, which they clearly see as a specific, separate,
> experience. Such resources have their place, but not in the
Perhaps
• Bazaar
• BreezyBadgerInstallation
• Main Page
could be deleted by someone with those tights on the wiki?
David T.
> On Sep 11, 2018, at 2:46 AM, Frank H. Ellenberger
> wrote:
>
> Am 11.09.2018 um 06:03 schrieb David Cousens:
>> One other problem with a WIki
Somewhere in the long thread about future documentation directions the issue
of translating documentation was raised. Rightfully so, because this is
currently a very challenging task.
The initial translation, while a huge job, is relatively straight forward: one
takes the English docbook files
22 matches
Mail list logo
