journal thing definition?

[Kairos]

It may be I've been at this too long today and this is a stupid question, but I can't seem to find the thing definition for the "journal" thing referenced in tab_journal.dat:

  <portal
    id="journal"
    style="tblNormal">
    <table_auto
      component="Journal"
      showtemplate="jrPick"
      autothing="journal">
      <additem><![CDATA[
        @text = "Add New Journal Entry"
        ]]></additem>
      </table_auto>
    </portal>

and bootstrap.1st.

  <autoadd thing="journal" portal="journal"/>

A "Find in Files" in Notepad++ returns bupkis. I was thinking of adding a gizmo to it.

Thanks in advance.

 

[Kairos]

Looks like the answer is here, but the documentation is incomplete. I'll assume that the "journal" thing is not editable then.

 

[Mathias]

No, the journal thing is auto-generated by Hero Lab.

Everything I saw on your honor entries can simply be fields on the component, all visible on the normal pick template. Or, you can create a form launching button that simply shows fields on that compset, rather than a form that shows the gizmo. (I'd recommend just making the journal pick template taller, so you can fit everything in it).

If the only customization options you want to add to something are fields that the user can fill in, that doesn't require a gizmo - gizmos are needed only in cases where the user will be selecting from various modifications, and those modifications are so diverse that you need to code them as their own <thing>s, and those things are being added to the customized thing.

 

[Kairos]

No, the journal thing is auto-generated by Hero Lab.

Everything I saw on your honor entries can simply be fields on the component, all visible on the normal pick template. Or, you can create a form launching button that simply shows fields on that compset, rather than a form that shows the gizmo. (I'd recommend just making the journal pick template taller, so you can fit everything in it).

If the only customization options you want to add to something are fields that the user can fill in, that doesn't require a gizmo - gizmos are needed only in cases where the user will be selecting from various modifications, and those modifications are so diverse that you need to code them as their own <thing>s, and those things are being added to the customized thing.

Got it. I appreciate the clarification.

 

[Kairos]

Thanks again for the suggestion, Mathias. That was the right move.

The journal entries are a bit busy, but I think I just need to tweak the layout a little. Also, I think I'm going to modify the date to reflect the calendars in the books, but that's later.

I'm now tracking Renown as a usagepool and resource rather than as a trait, which makes a ton more sense.

 

[Mathias]

I'd move the cash and XP section left, above the dates, scooting the renown up to where that had been, and then place the two checkboxes below that. Since the checkboxes are associated with renown, they should be near each other.