Feedback #1

Closed
addyosmani opened this Issue Mar 17, 2013 · 3 comments

Projects

None yet

2 participants

@addyosmani
  • Really like SIML. Fantastic work :)
  • Could you expand on the docs to cover expected behavior when using tabs? It wasn't entirely clear what to expect when tabbing after creating a new set of nested elements (i.e that the closing tag appears to move to the end of a block) - is this just tag indentation?
  • As it isn't a templating language, can we expect to see some sort of Sublime/editor plugin for support similar to Emmet?
  • I wasn't completely sold on the more explicit CSS selector approach to writing markup (i.e using braces). Are there clear advantages of doing this:
form {
    fieldset {
        label {
            for: "your-name";
            text: "Enter something..."
        }

over

form
    field
        label[for="your-name"] 'Enter something'

? My guess is that it's easier to parse visually for those used to nested SASS but I could just be guessing :)

  • Are there plans for a SIML conversion tool? i.e something which works in reverse to convert existing markup to this form?
@addyosmani

In the SIML editor, there appears to be a bug when mixing the above two types:

form
    fieldset{

}

The closing brace (I would guess) should auto-indent to:

form
    fieldset{

    }

but doesn't. This could be a very very minor bug. Just a nit :)

@padolsey
Owner

Thanks so much for the feedback Addy!

Could you expand on the docs to cover expected behavior when using tabs? It wasn't entirely clear what to expect when tabbing after creating a new set of nested elements (i.e that the closing tag appears to move to the end of a block) - is this just tag indentation?

I can expand on this, definitely. I think I'll create a wiki for the indentation stuff.

As it isn't a templating language, can we expect to see some sort of Sublime/editor plugin for support similar to Emmet?

That's a great idea -- I'll look into Sublime. I'm not sure how much effort is involved in creating a plugin. What I would really like is for SIML to gain sufficient interest so that people are creating their own plugins/addons. Of course, this'll only happen if SIML proves to be sufficiently useful.

ATM I am very conscious of my decision not to make it a templating language... I wonder if it would perhaps be wiser to go in that direction.

I wasn't completely sold on the more explicit CSS selector approach to writing markup (i.e using braces). Are there clear advantages of doing this

I guess, as you mentioned, some people may find it easier to parse visually. Also it allows you to be absolutely explicit in what kind of nesting you want. Using the magical tabbing technique can lead to weird results if you don't use consistent tab characters/spacing. E.g. It's very unclear what this should become:

a
  b
      c
    d
     e
 f

Are there plans for a SIML conversion tool? i.e something which works in reverse to convert existing markup to this form?

Very cool idea -- I will look into it.

And in regard to the indentation bug in the SIML editor. At this point the SIML editor is kinda SIML agnostic. It's just an Ace editor. It won't manage your indentation for you. I may improve it but I am wary of the difficulty involved in creating a full fledged editor just for a single language.

Thanks once again for the feedback -- It's very helpful! :)

@addyosmani

No worries at all! I'm glad the feedback was helpful :) fwiw, I think taking this is the same direction (i.e as an editing workflow helper) would offer the greatest impact. Maybe best to release and see what the community will use it for the most :)

@padolsey padolsey closed this Mar 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment