Re: [xmile] dashes vs underscores

[Karim Chichakly <kchichakly@iseesystems.com>]

Hi Will,

It's not case-sensitive so I don't see any issue, especially if it makes the style in the spec cleaner.  [I didn't even notice it was all caps.]  Others may want to comment.

Karim

On Mon, Jun 2, 2014 at 12:05 PM, Will Glass-Husain <wglass@forio.com> wrote:

Sorry, I meant "make all attributes dashed".  In other words, change "label_side" into "label-side".

I'm good with leaving this as it is, particularly since it's been discussed.  

But I would still like to see TOP/BOTTOM/LEFT/RIGHT made lower-case for consistency.  Do you have strong feelings on this?

WILL

On Mon, Jun 2, 2014 at 7:53 AM, Karim Chichakly <kchichakly@iseesystems.com> wrote:

Hi Will,

"label_side" is supposed to be underscored as Billy said.  That's a typo in the spec.

I'm not quite sure what you mean by "make all attributes underscore".  I don't recommend we change everything.  We had this discussion at two different committee meetings and decided both times to leave it the way it is.

Karim

On Mon, Jun 2, 2014 at 10:41 AM, Will Glass-Husain <wglass@forio.com> wrote:

Thanks, Karim.

I note the property "label-side" is defined with a dash in the spec, but Billy's example he sent to me made it an underscore "label_side".

I propose for consistency we keep all the attributes as dashes.  Most of the multi word attributes are CSS.  Then we can keep it "label-side".

On a related topic, the spec references label-side options TOP, BOTTOM, LEFT, RIGHT.   I've changed this in the schema to be all lower case "top", "bottom", "left", "right", which is consistent with all other enumerated values.

WILL

On Mon, Jun 2, 2014 at 6:30 AM, Karim Chichakly <kchichakly@iseesystems.com> wrote:

Hi Will,

That was intentional.  All the XMILE-specific names use underscore.  Anything we use from CSS matches CSS (I think for obvious reasons).

Karim

On Mon, Jun 2, 2014 at 2:08 AM, Will Glass-Husain <wglass@forio.com> wrote:

Hi,

Most of the model-related double words use in our standard use underscores to join them, e.g.

<options>

    <uses_conveyor/>

    <uses_arrays/>

</options>

and

<sim_specs>

  <start>0</start>

  <stop>10</stop>

  <dt>1</dt>

</sim_specs>

I notice that as a contrast, all the attributes in styles and the display encoding use dashes to separate multiple words.  This probably comes from the similarity to CSS.

<stock name=”Bathtub” x=”50” y=”100” width=”45” height=”35” label-side=”TOP” color=”blue” background-color=”white” z-index=”1” font-family=”Arial” font-size=”9pt” font-weight=”bold” font-style=”italic” text-decoration=”underline” text-align=”center” vertical-text-align=”center” text-padding=”2px” font-color=”blue” text-border-color=”black” text-border-thickness=”1px” text-border-style=”solid”/>

Do we care about the inconsistency?  If so, should we make them the same?

You could make an argument that for tag names we use an underscore and for attributes we use a dash...

WILL

-- 

William Glass-Husain   /forio  |  +1 (415) 440 7500 x89  |  forio.com

--

William Glass-Husain   /forio  |  +1 (415) 440 7500 x89  |  forio.com

--

William Glass-Husain   /forio  |  +1 (415) 440 7500 x89  |  forio.com