dwp-forge / refnotes

4 stars 6 forks source link

Configuration and back references #4

Closed dwp-forge closed 9 years ago

dwp-forge commented 9 years ago
Let me add couple more questions.

I) First, more important, back-ref-format: it says
"Actual values of these identifiers are controlled by the multi-ref-id style."
If I set multi-ref-id = 'Note counter', then it does change the reference
numbers in the text, but does not change in footnotes. So, for example, if
I have [(note 1)] [(note 2)] [(#1)] I get 1) 2) 1) in text, but footnotes
look like this:
1),3)
2)
Is this by design? (Because, in help it says that for notes it is
controlled by this variable as well.)

II) back-ref-format = "None" seems not working. In fact, in help it says
that "Note" is the default option, but in my case "None" is the default,
and it still renders back references. So, if I change between these two --
nothing changes.

III) It seems that all fields on control page in Namespaces section are in 
two colors: light green and light blue. It is really hard to distinguish
between them (LCD display), only when they are close to each other, and
also I don't see the point of having two colors there -- for some fields
inherit makes it blue, for some inherit makes it green.

I may have posted too much "bugs", questions and suggestions, but your
plugin is kind of fresh, so, I am just trying to pay your attention, and
get all things right.

Original issue reported on code.google.com by vadimcher on 2009-08-28 00:59:57

dwp-forge commented 9 years ago
I) No, it's not by design. It's a bug. Though, there are lots of parameters to tweak
and not all combinations make sense. So I never tested "multi-ref-id : note" together
with "back-ref-format : note". The expected:

  1),1)
  2)

wasn't appealing, so I used something like "back-ref-format : a" instead.

II) Yeah, that was a typo in JS. I fixed it in revision 239 (not released yet).

III) Well, if you don't see the point of having two colors, there shouldn't be a
problem with distinguishing one from another. Just treat the fields as colored versus
non-colored ;)

Seriously though, I can't recall why did I do this. I just thought it's kinda looks
nice. For you it doesn't. So apparently it's just a matter of taste -- some people
like it some don't. Not a bug.

> I may have posted too much "bugs", questions and suggestions, but your
> plugin is kind of fresh, so, I am just trying to pay your attention, and
> get all things right.

What you doing is really great! You know, it's not easy to find a free tester :)

Though, I would appreciate if you wouldn't bundle a number of problems/suggestions
into a single issue. Create a new issue for every topic. That way it will be easier
to keep the discussion straight on the subject and make it more convenient to close
the issue.

Original issue reported on code.google.com by dwp-forge on 2009-08-28 07:09:09

dwp-forge commented 9 years ago
:)  I am a "free tester" as long as I get all things work for me... As for III), if
there is no point of having two colors, then why don't make them all one color -- I
mean, when I have back-ref-separator light blue, and scoping light green I really
start thinking that there is something in it... and others would worry about this as
well, I think. At the top it says: green == inherited, so, what does 'blue' mean, and
how to make 'scoping' green? :) You may not agree, but that's just my feeling about
this as an user.

Original issue reported on code.google.com by vadimcher on 2009-08-28 16:24:45

dwp-forge commented 9 years ago
> if there is no point of having two colors

The colors actually mean different things: the blue is the DokuWiki way, the green
is
inherited value.

> You may not agree

Cool! Then I will use my right not to agree :) That is until more people will start
complain about it :)

Original issue reported on code.google.com by dwp-forge on 2009-08-28 16:35:36

dwp-forge commented 9 years ago
BTW, if it's *really* that annoying, you can change the colors to be the same at the
bottom of admin.css file.

Original issue reported on code.google.com by dwp-forge on 2009-08-28 16:39:24

dwp-forge commented 9 years ago
OK, no problem on my side. Just to make it clear: blue and green both mean inherited,
right?

Original issue reported on code.google.com by vadimcher on 2009-08-28 16:43:03

dwp-forge commented 9 years ago
> Just to make it clear: blue and green both mean inherited, right?

Well, I don't know how to state it more clear than I did in #3.

   Blue -- similar to DokuWiki, none of the parent namespaces changed this style
   Green -- inherited from parent, whatever parent namespace currently has

Hope that clears any remaining confusion :)

Original issue reported on code.google.com by dwp-forge on 2009-08-28 17:06:44

dwp-forge commented 9 years ago
OK, thanks!

Original issue reported on code.google.com by vadimcher on 2009-08-28 17:13:52

dwp-forge commented 9 years ago
I) Fixed in revision 242.
II) Fixed in revision 239.
III) Rejected.

Original issue reported on code.google.com by dwp-forge on 2009-08-28 17:56:55