Author Topic: BibTexApp in development  (Read 190 times)

HSE

  • Member
  • *****
  • Posts: 1549
  • <AMD>< 7-32>
BibTexApp in development
« on: February 04, 2021, 08:35:29 AM »
Hi all!

This little application begin to work, and uploaded is the 32bit binary.

Now I discovered that @string instruction must be processed to obtain a perfect list output  :biggrin: (not solved yet)

In yellow you can see command entries, and in blue  undefined fields (take me some hours to remember RichEdit jokes  :rolleyes:).

Could be interesting if someone can test original BibTEX format files (some ".bib" are not true BibTEX but derivatives, and have some problems).

Thanks in advance, HSE

PD:  2. Updated with BibTex routines v7. Retrieve non standard entries, in that case all fields are considered additionals and showed in green (see IEEEexample.bib)
       3. Updated with BibTex routines v8. Load sequences of BibTEX files.
« Last Edit: February 17, 2021, 05:59:26 AM by HSE »

Biterider

  • Moderator
  • Member
  • *****
  • Posts: 629
  • ObjAsm Developer
    • ObjAsm
Re: BibTexApp in development
« Reply #1 on: February 04, 2021, 04:55:30 PM »
Hi HSE
The binary works fine here.
A nice feature would be if you could drag and drop a file instead of opening it.  :cool:

Biterider

HSE

  • Member
  • *****
  • Posts: 1549
  • <AMD>< 7-32>
Re: BibTexApp in development
« Reply #2 on: February 04, 2021, 11:56:07 PM »
Hi Biterider!

Good idea  :thumbsup:

Thanks, HSE

HSE

  • Member
  • *****
  • Posts: 1549
  • <AMD>< 7-32>
Re: BibTexApp in development
« Reply #3 on: February 17, 2021, 06:13:46 AM »
Hi all!

   Updated in first post with new routines to load sequences of files (arbitrarily *.bsq).
   To show how sequences must work, window The Expanse show some string replacements (@String entry is some kind of "textequ" directive).
   You can see easily what text is going to be replaced because they are one word strings without brackets nor quotes in originals files. In Text Edition window that text is represented exactly if related @String entry is declared in same file or in a previous file in the sequence.

    A couple of problems with interface, just because we infrequently destroy windows, waiting that OS make that at program end. But with dynamics interfaces, if you create, you must destroy  :biggrin:

Regard, HSE.
 
« Last Edit: February 17, 2021, 11:15:24 AM by HSE »