On Sun, Jul 18 2010, Hans Hagen wrote:
then they could easily all be merged into a single command table
during loading or even via 'cat'.
I'd rather go for this (see lfg file for examples):
return {
name = placefloat,
version = 1.00,
comment = Insert a floating element.,
}
On Sun, Jul 18 2010, Taco Hoekwater wrote:
If you start your files like this:
command = command or {}
command['placefloat'] = {
comment = Insert a floating element.,
...
}
then they could easily all be merged into a single command table
during loading or even via 'cat'.
On Sat, Jul 17 2010, Mojca Miklavec wrote:
A few random comments from externalfigure:
- Despite the fact that the command name is known from filename,
wouldn't it be nice to have externalfigure string defined somewhere?
Ok, see response to Taco.
- It is not really needed, but it helps when
On Sun, Jul 18 2010, Taco Hoekwater wrote:
arguments = {
[label_arg] = {
type = label,
},
[filename_arg] = {
type = file,
},
[settings_arg] = {
type = settings,
On Sun, Jul 18, 2010 at 09:38, Peter Münster wrote:
On Sat, Jul 17 2010, Mojca Miklavec wrote:
- It is not really needed, but it helps when cross-referencing: I
would nevertheless leave the [1] = {...}, [2] = {...} for arguments
- The following:
settings = {
inherit =
On Sun, Jul 18 2010, Peter Münster wrote:
- If all the three arguments are optional, it's a bit difficult to
tell what combination of arguments is allowed, so it might make sense
to be a bit more verbose in that (to tell somehow that for example
only 123 and 23 and 3 is allowed, but not
On Sun, Jul 18 2010, Taco Hoekwater wrote:
variants = { -- just an example
{ filename_arg },
{ label_arg, filename_arg },
{ label_arg, filename_arg, settings_arg },
{ filename_arg, parent_arg },
Now I see the big benefit!
Instead of having 2
On 18-7-2010 8:09, Taco Hoekwater wrote:
On 07/17/2010 09:32 PM, Peter Münster wrote:
On Sat, Jul 17 2010, luigi scarso wrote:
Why don't put them into a table as is in
http://www.lua.org/pil/10.1.html
Ok, now one file defines exactly one command table.
I added also other minor enhancements.
On 07/16/2010 04:41 PM, Peter Münster wrote:
Hello,
Here some new ideas:
http://pmrb.free.fr/tmp/context-commands/
All feedback is welcome!
FWIW, I actually like this: I find it more readable
than the XML version, and the inline descriptions and
comments are clearly helpful.
Best wishes,
On Fri, Jul 16, 2010 at 4:41 PM, Peter Münster pmli...@free.fr wrote:
Hello,
Here some new ideas:
http://pmrb.free.fr/tmp/context-commands/
All feedback is welcome!
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
On Sat, Jul 17 2010, luigi scarso wrote:
Why don't put them into a table as is in
http://www.lua.org/pil/10.1.html
For exampl e placefloat.lua should be
placefloat ={
props = {
[...]
Because I like to avoid redundancy.
It's easy to do things like this automatically:
local placefloat = {}
On Fri, Jul 16, 2010 at 16:41, Peter Münster pmli...@free.fr wrote:
Hello,
Here some new ideas:
http://pmrb.free.fr/tmp/context-commands/
Wow! I like it very much.
Mojca
___
dev-context mailing list
dev-context@ntg.nl
On Sat, Jul 17 2010, luigi scarso wrote:
Why don't put them into a table as is in
http://www.lua.org/pil/10.1.html
Ok, now one file defines exactly one command table.
I added also other minor enhancements.
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
On 17-7-2010 7:39, Mojca Miklavec wrote:
On Fri, Jul 16, 2010 at 16:41, Peter Münsterpmli...@free.fr wrote:
Hello,
Here some new ideas:
http://pmrb.free.fr/tmp/context-commands/
Wow! I like it very much.
i'll come back to this later, just a few comments now:
- props - properties (or
14 matches
Mail list logo
