Customiser descriptions

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

Customiser descriptions

nophead
Do customiser variable descriptions need to be on the line before the variable, rather than on the same line where the ranges are defined. If so, why?


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Customiser descriptions

tp3
On 01.10.20 01:08, nop head wrote:
> Do customiser variable descriptions need to be on the
> line before the variable, rather than on the same line
> where the ranges are defined.

Yes.

> If so, why?

Because that's how Thingiverse/MakerBot defined it:
https://customizer.makerbot.com/docs

ciao,
  Torsten.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Customiser descriptions

nophead
I see. Shame they didn't allow it after the ranges.

On Thu, 1 Oct 2020 at 00:22, Torsten Paul <[hidden email]> wrote:
On 01.10.20 01:08, nop head wrote:
> Do customiser variable descriptions need to be on the
> line before the variable, rather than on the same line
> where the ranges are defined.

Yes.

> If so, why?

Because that's how Thingiverse/MakerBot defined it:
https://customizer.makerbot.com/docs

ciao,
  Torsten.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
tp3
Reply | Threaded
Open this post in threaded view
|

Re: Customiser descriptions

tp3
On 01.10.20 01:25, nop head wrote:
> I see. Shame they didn't allow it after the ranges.

I guess that would make it much more difficult to parse.

Even a "better?" or native style, similar to attributes
in other languages would put the extra information in
front of the variable. Why would you want to have it
on the same line? For minimizing line count?

Rust attributes:

#[allow(non_camel_case_types)]
type int8_t = i8;

Java annotations:

@Persistent
protected String s = null;

As those are actually part of the normal language
it's possible to put them on the same line, at
least in some languages:

@Persistent protected String s = null;

ciao,
  Torsten.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-- Torsten
Reply | Threaded
Open this post in threaded view
|

Re: Customiser descriptions

nophead
> Why would you want to have it on the same line? For minimizing line count?

Yes exactly. The range is defined in a comment on the same line so I expected anything after the range to be the description. Not exactly hard to parse.

But I can see you wouldn't want to break compatibility with Thingiverse

On Thu, 1 Oct 2020 at 00:50, Torsten Paul <[hidden email]> wrote:
On 01.10.20 01:25, nop head wrote:
> I see. Shame they didn't allow it after the ranges.

I guess that would make it much more difficult to parse.

Even a "better?" or native style, similar to attributes
in other languages would put the extra information in
front of the variable. Why would you want to have it
on the same line? For minimizing line count?

Rust attributes:

#[allow(non_camel_case_types)]
type int8_t = i8;

Java annotations:

@Persistent
protected String s = null;

As those are actually part of the normal language
it's possible to put them on the same line, at
least in some languages:

@Persistent protected String s = null;

ciao,
  Torsten.

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org