I finally transferred my book to LyX

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

I finally transferred my book to LyX

Steve Litt
Hi all,

I wrote most of the first draft of my next book right within VimOutliner. The
outline was up to 72,000 words -- a reasonably sized book.

Today I ran the outline through a title-case script, and then through
otl2lyx.awk, to produce a LyX document of the book.

Because VO doesn't have a provision for home-grown styles, I'm having to apply
styles to the LyX doc. It took me about an hour to convert all the numbered
and bulleted lists to LyX's enumerate and itemize styles (environments).

My next step will be to create a LyX layout file to implement a document
class, based on LyX's Book document class, into which I can put homegrown
styles such as story, article, myEmph, outline, Note, Tip, Warning, Caution
and the like. That should take about a day (and would have even if I'd begun
the writing in LyX. After the new document class is complete and running,
I'll apply the proper styles to things I'd capitalized or tagged within the
outline.

This is substantial extra work, but I liked the idea that I was able to easily
rearrange the structure long into the authoring process. I'll keep you
informed.

SteveT

Steve Litt
Recession Relief Package
http://www.recession-relief.US

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: I finally transferred my book to LyX

Bill Powell
Hi Steve,

> I wrote most of the first draft of my next book right within VimOutliner. The
> outline was up to 72,000 words -- a reasonably sized book.

That's exciting!

> After the new document class is complete and running, I'll
> apply the proper styles to things I'd capitalized or
> tagged within the outline.

Could you elaborate a bit on the tags you used? E.g., some
kind of wiki-like markup that you parse into Lyx syntax?

Could we use something like Markdown or another wiki parser
to do a lot of this kind of post-processing for VO?

Bill

--
_____________________________________________________________

http://pennyjustice.com  : How do you spend your penny?
http://wineskinmedia.com : Books and sites crafted with care.
http://billpowellisalive.com : Man found alive with two legs.  
_____________________________________________________________

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Re: I finally transferred my book to LyX

Steve Litt
On Thursday 26 February 2009 03:36:27 pm Bill Powell wrote:

> Hi Steve,
>
> > I wrote most of the first draft of my next book right within VimOutliner.
> > The outline was up to 72,000 words -- a reasonably sized book.
>
> That's exciting!
>
> > After the new document class is complete and running, I'll
> > apply the proper styles to things I'd capitalized or
> > tagged within the outline.
>
> Could you elaborate a bit on the tags you used? E.g., some
> kind of wiki-like markup that you parse into Lyx syntax?

Nothing so exciting. I just had <story> </story> or <outline> </outline>, and
then I manually converted such things in LyX after creating those styles in
the document class. I marked things mean't to be emphasis character style by
making them all caps, and I'll convert them to lowercase and the right
character style during proofing and editing.

I figured, and I think rightly so, that the effort in making markup
technologically meaningful would be more than the effort of manually cleaning
it up during proofreading and editing.

At least this time.

If we REALLY wanted to accommodate user created styles within VO, one way we
could do it is have a file containing the various styles, and have a menu
item for start style, which would pull up a list of the styles, and a menu
item for stopping the style. If either is used during highlighting, the
styles are applied at the ends of the selection. The file listing the styles
could then be turned into a list of styles for the destination format.

Personally, I think that would be overkill. But I'll have a more definite
opinion as I clean up the LyX document.

Thanks

SteveT

Steve Litt
Recession Relief Package
http://www.recession-relief.US

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: I finally transferred my book to LyX

Bill Powell
> > > After the new document class is complete and running, I'll
> > > apply the proper styles to things I'd capitalized or
> > > tagged within the outline.
> >
> > Could you elaborate a bit on the tags you used? E.g., some
> > kind of wiki-like markup that you parse into Lyx syntax?
>
> Nothing so exciting. I just had <story> </story> or <outline> </outline>, and
> then I manually converted such things in LyX after creating those styles in
> the document class. I marked things mean't to be emphasis character style by
> making them all caps, and I'll convert them to lowercase and the right
> character style during proofing and editing.

Hmm. I wonder how VO would interact with standard converters
like pandoc? It seems like wiki markup like _this_ or
**this** could be parsed by a tool like pandoc _before_
being sent to the post-processor specifically geared at the
VO formatting. So you could hand off a VO file to your
otl2lyx with everything already like \emph{this}.

In short, VO syntax is simple enough that it might be really
good at staying out of the way of other parsers. But
probably some folks are already doing this.

Bill




--
_____________________________________________________________

http://pennyjustice.com  : How do you spend your penny?
http://wineskinmedia.com : Books and sites crafted with care.
http://billpowellisalive.com : Man found alive with two legs.  
_____________________________________________________________

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

How do VimOutliners bill their time?

Bill Powell
In reply to this post by Steve Litt
Hi folks,

This is a subject that came up a few months back, sort of,
but there's been activity on the list lately so I thought
I'd ask: what tools do y'all use to bill your time? It seems
we have a fair number of freelancers/independent
contractors/etc. here, who need to track billable hours. Any
favorite tools?

And what features do you like in a billing tool?  E.g., do
you bill to the minute, or in larger blocks? Do you need to
save the data to a database, or do you like a plain text
file you can edit? How do you generate invoices?

I've been using some macros of my own (which rest on
VimOutliner) and I think Noel might have mentioned VO files
and a perl script (which perhaps might be posted?) awhile
back. But I'm all ears for any suggestions.

Thanks,
Bill

--
_____________________________________________________________

http://pennyjustice.com  : How do you spend your penny?
http://wineskinmedia.com : Books and sites crafted with care.
http://billpowellisalive.com : Man found alive with two legs.  
_____________________________________________________________

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: How do VimOutliners bill their time?

Steve Litt
On Tuesday 03 March 2009 02:28:19 pm Bill Powell wrote:

> Hi folks,
>
> This is a subject that came up a few months back, sort of,
> but there's been activity on the list lately so I thought
> I'd ask: what tools do y'all use to bill your time? It seems
> we have a fair number of freelancers/independent
> contractors/etc. here, who need to track billable hours. Any
> favorite tools?
>
> And what features do you like in a billing tool?  E.g., do
> you bill to the minute, or in larger blocks? Do you need to
> save the data to a database, or do you like a plain text
> file you can edit? How do you generate invoices?
>
> I've been using some macros of my own (which rest on
> VimOutliner) and I think Noel might have mentioned VO files
> and a perl script (which perhaps might be posted?) awhile
> back. But I'm all ears for any suggestions.
>
> Thanks,
> Bill
Hi Bill,

I bill by the book sold, by the student courseware license sold, and by the
day when I'm training.

:-)

But I know what you mean. Once upon a time all my income came from contract
programming.

If you mean what do my invoices look like, they're plain text with my company
name, the items provided and price breakdown (usually hours, sometimes
expenses) and a total. I bill net 15. Because they're all text, I can read my
1987 invoices just fine. When emailing an invoice to a customer I use
enscript and then ps2pdf to turn it into a PDF which the customer can easily
read or print.

If you mean time tracking, I have a little app to do that:

http://www.troubleshooters.com/projects/tslips/index.htm

I'm attaching the README.otl from that project. What I never did was write a
program to summarize and report on the log (zts.txt). It would have been easy
to do, but I just went on to other things. Instead, I just view the log
(zts.txt) in a read-only Vim.

The following is a snippet from an old log (zts.txt)

45eefaff::BEGIN:: 2007/03/07 12:48:47:: Lloyd Ferguson Parking Lot:: Project
setup
45eefaff::END  :: 2007/03/07 14:38:46:: 1:49:59:: 6599

45ef14c6::BEGIN:: 2007/03/07 14:38:46:: Lloyd Ferguson Parking Lot::
Programming basic data
45ef14c6::END  :: 2007/03/07 20:28:13:: 5:49:27:: 20967

477e68d5::BEGIN:: 2008/01/04 12:11:49:: New Rapid Learning::
Checking/responding to email

The preceding word wrapped. What it looks like in real life is that the END
line immediately follows the BEGIN line of the same task, and then a blank
line separates that END from the next task's BEGIN.


This program (tslips.pl) is good and fast for simple stuff where you're
billing for only one thing at a time.

The project web page doesn't explain a whole heckofalot, but I front-ended
tslips.pl with UMENU. Front ending it with a keystroke menu program makes it
one heck of a lot faster to use -- begin and end projects with maybe three
keystrokes. The beauty is that when you get a new client, you just put them
in your menu, and bang, a couple keystrokes can start or stop their time.
Below is the relevent UMENU EMDL from my computer, which is pretty self
explanatory:

Timekeeping ::: Timekeeping Menu
        Always Persistent Timekeeping Menu
                param
                        C: xterm -e ./umenu.pl st
                        B: 1
                        D: ~/.umenu/program
        End current task
                param
                        D: /d/at/perl/tslips
                        C: ./tslips.pl END null null
                        S: 1
        Start new task ::: Start New Task Menu
                Lloyd Ferguson
                        param
                                D: /d/at/perl/tslips
                                C: ./tslips.pl BEGIN "Lloyd Ferguson Parking Lot" "%1%Task desc please%%"
                                S:
                AT ::: American Troublebusters Timekeeping
                        Website
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "T.C" "%1%Task desc please%%"
                                        S:
                        Books ::: Book Timekeeping Submenu
                                New RL
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "New Rapid Learning" "Checking/responding to email"
                                                S:
                                TS Self help
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "TS Selfhelp" "Checking/responding to email"
                                                S:
                                Woman's guide to repairmen
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "WomansGuide" "Checking/responding to email"
                                                S:
                                Manager's guide
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "ManagersGuide" "Checking/responding to email"
                                                S:
                                Other
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "Books, Misc" "Checking/responding to email"
                                                S:
                                ^Quit
                        Email
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Email" "Checking/responding to email"
                                        S:
                        Programming ::: Programming (AT) menu
                                Timekeeping program
                                        param
                                                D: /d/at/perl/tslips
                                                C: ./tslips.pl BEGIN "Programming timekeeping" "%1%Task desc please%%"
                                ^Quit
                        Todo list
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Todo List" "%1%Task desc please%%"
                                        S:
                        Other business
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Misc Business" "%1%Task desc please%%"
                                        S:
                        ^Quit
                Toastmasters ::: Toastmasters Timekeeping
                        Foliage
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Toastmasters Foliage" "%1%Task desc please%%"
                                        S:
                        Speech writing and rehearsal
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Toastmasters speech writeing and
rehearsal" "%1%Task desc please%%"
                                        S:
                        Attend meeting
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl BEGIN "Toastmasters attend meeting" "%1%Task desc
please%%"
                                        S:
                        ^Quit
                Sylvia
                        param
                                D: /d/at/perl/tslips
                                C: ./tslips.pl BEGIN "Sylvia" "%1%Task desc please%%"
                                S:
                Personal
                        param
                                D: /d/at/perl/tslips
                                C: ./tslips.pl BEGIN "Personal" "%1%Task desc please%%"
                                S:
                Not working
                        param
                                D: /d/at/perl/tslips
                                C: ./tslips.pl BEGIN "Not working" "Not working"
                                S:
                stronGarm project ::: Strongarm menu
                        Xerox
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl CREATE Xerox "%1%Task desc please%%"
                                        S:
                        Personal
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl CREATE Personal "%1%Task desc please%%"
                                        S:
                        Other
                                param
                                        D: /d/at/perl/tslips
                                        C: ./tslips.pl CREATE "%1%Client please%%" "%2%Task desc please%%"
                                        S:
                        ^Quit
                ^Quit
        View/Modify task log
                param
                        D: /d/at/perl/tslips
                        C: gvim -R zts.txt
        ^eXit


_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner

README.otl (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How do VimOutliners bill their time?

Bill Powell
Steve -- thanks so much for your reply! (So much quicker
than my response.) I should have known to have a look at
your site. :)

>
> If you mean time tracking, I have a little app to do that:
>
> http://www.troubleshooters.com/projects/tslips/index.htm
>
> I'm attaching the README.otl from that project. What I never did was write a
> program to summarize and report on the log (zts.txt). It would have been easy
> to do, but I just went on to other things. Instead, I just view the log
> (zts.txt) in a read-only Vim.

tslips looks neat, especially since you included your UMENU
code to show how to make it quick.

I'm still curious, though, how you got from these records to
your final invoice. Did you write a one-off script to
summarize your data that you wouldn't want to share? Or
import the times into a spreadsheet?

It's uncanny how similar this is to the time tracking part
of my "VimPim" project (the part I didn't include in the
public files yet). I think I like your lines better, though.
Mine are like:

+guideline  +stmarys 00:25 2009-03-18 14:41:35 2009-03-18 15:06:47
+email      +bpalive 00:07 2009-03-18 15:06:51 2009-03-18 15:14:39

(Here I used spaces instead of tabs to try to get it to line
up right.) In Vim, even with syntax highlighting, these
lines get a bit annoying.

Particularly, the project and parent names ("guideline" and
"stmarys") are limited to however long a tabstop you can
stand. Vim auto-complete can help prevent some misspellings,
but it's nothing like having a real database behind it to be
sure you're marking time on the right project.

Also, the "interval" doesn't have seconds in the original
implementation, which led to some minor underbilling until I
redid the summarizing program in perl.

Anyhow, I like how you use UMENU to serve as a kind of
database to keep your projects straight. I guess I could
implement something similar within Vim using abbreviations.
Though I'd have to memorize them. :)

And though I keep a dedicated Vim open just for time
tracking, it's still probably faster to access it from the
command line.

The nice part about editing the log within Vim is that I
also have the VO plugin loaded, so I can make VO notes under
my billing entries, then remove them later when summarizing
the data.

Anyhow, thanks again. I wonder if everyone else on the list
is already at the stage of billing by the book. :)

Bill

--
_____________________________________________________________

http://pennyjustice.com  : How do you spend your penny?
http://wineskinmedia.com : Books and sites crafted with care.
http://billpowellisalive.com : Man found alive with two legs.  
_____________________________________________________________

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Re: How do VimOutliners bill their time?

Steve Litt
On Wednesday 18 March 2009 04:38:38 pm Bill Powell wrote:

> Anyhow, I like how you use UMENU to serve as a kind of
> database to keep your projects straight. I guess I could
> implement something similar within Vim using abbreviations.
> Though I'd have to memorize them. :)

You can always make a menu out of a VimOutliner outline, simply by ,,1 and
then drilling down at each level. The only advantage of UMENU is a single
keystroke per level, rather than jjjjjzo

By the way, I gave up hand-coding UMENU .mnu files back in 2001. Now I use
Easy Menu Definition Language (EMDL), which is, taadaa, a tab indented
outline (http://www.troubleshooters.com/projects/emdl/index.htm). I found a
really cool editor with which to create and modify EMDL. It's called
VimOutliner :-)

StevET
 
Steve Litt
Recession Relief Package
http://www.recession-relief.US

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: How do VimOutliners bill their time?

Bill Powell
+++ Steve Litt [18/03/09 15:54 -0400]:

> On Wednesday 18 March 2009 04:38:38 pm Bill Powell wrote:
>
> > Anyhow, I like how you use UMENU to serve as a kind of
> > database to keep your projects straight. I guess I could
> > implement something similar within Vim using abbreviations.
> > Though I'd have to memorize them. :)
>
> You can always make a menu out of a VimOutliner outline, simply by ,,1 and
> then drilling down at each level. The only advantage of UMENU is a single
> keystroke per level, rather than jjjjjzo
>
> By the way, I gave up hand-coding UMENU .mnu files back in 2001. Now I use
> Easy Menu Definition Language (EMDL), which is, taadaa, a tab indented
> outline (http://www.troubleshooters.com/projects/emdl/index.htm). I found a
> really cool editor with which to create and modify EMDL. It's called
> VimOutliner :-)
>

Thanks, Steve. This looks cool, too. :)

Bill


--
_____________________________________________________________

http://pennyjustice.com  : How do you spend your penny?
http://wineskinmedia.com : Books and sites crafted with care.
http://billpowellisalive.com : Man found alive with two legs.  
_____________________________________________________________

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Re: How do VimOutliners bill their time?

Steve Litt
In reply to this post by Bill Powell
On Wednesday 18 March 2009 04:38:38 pm Bill Powell wrote:

> Anyhow, I like how you use UMENU to serve as a kind of
> database to keep your projects straight. I guess I could
> implement something similar within Vim using abbreviations.
> Though I'd have to memorize them. :)

We have different perspectives. You see my use of UMENU as a database because
different clients are included in the menu. I see UMENU as the universal
front end. You code up a quick and dirty script to make something happen,
like a quick and dirty timekeeping program. The quick and dirty script is
controlled by its command line arguments, current directory, and environment
variables.

Then you front end the script with UMENU, and the quick and dirty script
changes from something arcane, hard to remember and a hassle to type, to
something requiring a couple keystrokes and maybe a couple queries. I even
have filepickers and recordpickers that work between UMENU and the script.

See these for usage of UMENU and pickers to quickly front end just about
anything:

http://www.troubleshooters.com/lpm/200801/200801.htm
http://www.troubleshooters.com/lpm/200802/200802.htm

SteveT
 
Steve Litt
Recession Relief Package
http://www.recession-relief.US

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Re: How do VimOutliners bill their time?

Steve Litt
In reply to this post by Bill Powell
On Wednesday 18 March 2009 04:38:38 pm Bill Powell wrote:

> I'm still curious, though, how you got from these records to
> your final invoice. Did you write a one-off script to
> summarize your data that you wouldn't want to share? Or
> import the times into a spreadsheet?

I just manually take the week's time on a project and copy it to the invoice,
rounding up to the nearest 15 minutes.

SteveT

>
> It's uncanny how similar this is to the time tracking part
> of my "VimPim" project (the part I didn't include in the
> public files yet). I think I like your lines better, though.
> Mine are like:
>
> +guideline  +stmarys 00:25 2009-03-18 14:41:35 2009-03-18 15:06:47
> +email      +bpalive 00:07 2009-03-18 15:06:51 2009-03-18 15:14:39
>
> (Here I used spaces instead of tabs to try to get it to line
> up right.) In Vim, even with syntax highlighting, these
> lines get a bit annoying.
>
> Particularly, the project and parent names ("guideline" and
> "stmarys") are limited to however long a tabstop you can
> stand. Vim auto-complete can help prevent some misspellings,
> but it's nothing like having a real database behind it to be
> sure you're marking time on the right project.
>
> Also, the "interval" doesn't have seconds in the original
> implementation, which led to some minor underbilling until I
> redid the summarizing program in perl.
>
> Anyhow, I like how you use UMENU to serve as a kind of
> database to keep your projects straight. I guess I could
> implement something similar within Vim using abbreviations.
> Though I'd have to memorize them. :)
>
> And though I keep a dedicated Vim open just for time
> tracking, it's still probably faster to access it from the
> command line.
>
> The nice part about editing the log within Vim is that I
> also have the VO plugin loaded, so I can make VO notes under
> my billing entries, then remove them later when summarizing
> the data.
>
> Anyhow, thanks again. I wonder if everyone else on the list
> is already at the stage of billing by the book. :)
>
> Bill



--
Steve Litt
Recession Relief Package
http://www.recession-relief.US

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner