Hello! > thanks for the interesting contribution! Have a look at the patch > I hopefully don’t forget to append.
Thank you! I will take a look and learn... ;-)
>> [...]
>> I use \startbuffer and \stopbuffer, and also Lua. As I said, I don't
>> really know how to write a module... comments are very welcome.
>
> Honestly, it doesn’t work, but that’s a minor flaw!
Sorry! I forgot to mention. Only a little subset of it works. I have
(already - so I don't forget to) attached a "tex" file that works.
> [**lots of advices I will study carefully latter**]
> [...]
> I could not figure out how exactly the section block thingy is
> supposed to work. It does not create the \startframe macro at all
> -- is this something custom?
I don't know how to use this "startframe" yet. So, I am doing like
this right now: (numbers like 2-3 or 2- don't work yet)
=== START code snip ===
\startbuffer[simplesteps]
\startitemize
\item First item
\uncover[2,3,4]{\item Second item}
\uncover[3,4]{\item Second item}
\uncover[4]{\item Second item}
\stopitemize
\stopbuffer
\simplestepsplaybuffer
=== STOP code snip ===
The "simplestepsplaybuffer" macro simply calls the
simplesteps.playbuffer() lua function. This function plays the buffer
and determines if it has to be played again or not. If it does, then
it tex.print('\simplestepsplaybuffer').
The macros "uncover" determine how far the specification is from being
played. If it is being played now, then show. If it is played "next",
then show in gray. And so on.
> I infer it’s about the slide title
> so I have \startframe call \section but that should be taken as a
> placeholder at most. In my own slide module I use
> \{start,stop}section with the option placehead=no and rely on the
> page header to display the slide title (i.e. current section
> running head). That was the laziest way I could imagine :P
I guess that's what I want to do. I just don't have the necessary
knowledge yet. ;-)
> Some remarks:
>
> - you should rename simplesteps.mkiv to t-simplesteps.mkiv,
> indicating that it is a thirdparty module
I will. I think I will have a bitbucket repository exclusively for
modules. Then I will have the proper directory structure, the proper
naming scheme and hopefully proper documentation, xml, etc. (lots of
things to learn!)
> - if you plan on expanding the code you eventually will come to
> love this bit: http://wiki.contextgarden.net/System_Macros
> - Context has a namespacing system which you might consider
> switching to in the long term:
> http://tex.stackexchange.com/q/58654
> but it’s arguably an advanced method
Well, I do want to do it the right (recommended) way!
> - maybe switch to mkvi as named parameters make rewriting
> macros a breeze
Would you elaborate a bit further?
>> Is it ok if I send a PDF sample to the list?
I hope you can use the TEX file attached.
Cheers,
André Caldas.
simpletest.tex
Description: TeX document
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
