up-to-date syntax highlighting about less-docs HOT 12 CLOSED

@brian-frichette, this is only semi-related to this issue, but are you still interested in helping out with the lesscss.org website?

Since we didn't get a chance to connect, what I'd like to do is implement side-by-side examples that users can actually edit in real-time. Some thoughts/questions first, in case you are willing to help out:

• Is a server required for the actual code examples, or are you running the server for other reasons? (admittedly I didn't look at the server code). I would prefer to keep the site static if possible, but you have some awesome stuff going on over there, so I'm keeping an open mind.
• If you do help get this implemented, we would be happy to link to less2css.org from each code example. None of the examples will have any options, so if visitors want to play around with options we'll let them know that less2css.org is the place to go.

Any other ideas you have would be great. I have another really cool, related idea.. but I'll wait and see if this stuff is doable before I get ahead of myself...

from less-docs.

Yeah, we need to talk. Frankly, I prefer phone / voice / Google Hangout, if you're open to any of those.

To answer your questions:

• Server-side isn't required to process the code. That said, I run the server b/c
  1. Express is fast
  2. It allows me to XHR the options (for easy config) and LESS scripts (IE 9/10 won't do an XHR from raw.github since the Content-Type is text/plain and it pull it in as a script. I'm sure there's a workaround but it's easier and fast to use my server).
  3. I want to implement saving / link-sharing sometime in the next 10 to 5,234 days. 👅
  4. I like playing with servers since I do front-end in my day job
• Regarding implementations for this, I could think of a few. What I would LIKE to do is integrate a stripped down version of the live editor into lesscss.org for the code examples. It could link the code back to less2css.org if people want more options. Or not. Whatever makes the most sense.

Before integration there is one issue that needs to be solved, and frankly it's fairly simple, I just haven't got around to it. This issue with error text. I just want to capture the last non-error state (which is trivial since the output is already being saved in real-time) and keep that displayed, and then put the error text in a visible but unobtrusive location.

From a UX perspective this is low-hanging fruit and should be done before we proceed with anything else. I'll see what I can do this weekend.

Let's talk at some point.

from less-docs.

I prefer phone / voice / Google Hangout

I'll try, I have a 2-yr old with me most of the time. So nights and weekends are best.

from less-docs.

Hey Jon,

I just wanted to follow up with this, since it seems like it might be tough to get a clear window to flesh this out on the phone. But for communication, add me to Skype or Hangouts. You have my email somewhere, and my Skype is @bfricka.

So I thought about this a bit, and really the core of the solution on my end is to pull out the core pieces that I have developed for the site into re-usable components. With the last major refactor I did, I really have gone a long way to actually getting this done already. @heff and I had a brief talk about the fork he did of my project to build his real-time video player editor. All together, it seems like the core components that make this front-end piece of the puzzle happen should be pulled out into their own components, and further, their own GH projects so they can be accessed in a more abstract way w/out all the other implementation-specific baggage.

Since most of this is on the verge of being done, I'll spend some time this weekend creating these projects as independent AngularJS components, structured in much the same way that Angular-UI does. From there, it'll be clear which components are required, and the components used won't be encumbered by the less-preview-specific implementation.

Let me know what you think.

from less-docs.

@brian-frichette I'm a big fan of that architectural philosophy in general, so I think it sounds great. @doowb and I are using angular on a semi-related project and it's pretty awesome to work with.

What are good times for you to chat normally? Thursday is out, but I can try to make something work tomorrow, Friday or this weekend.

from less-docs.

@lukeapage fwiw I created a new repo for hiless since it was created by @cloudhead and there really aren't very good options for LESS syntax highlighting in the community. now we can just redirect people who want that over to the hiless repo https://github.com/less/hiless

from less-docs.

Wow, this update just reminded me about this. I'm so sorry for not getting back to you on this. Please find me on Skype as I'm almost always on nowadays. I need to update less2css anyways.

from less-docs.

no worries. there is still time to make something happen.

from less-docs.

Btw. highlightjs/highlight.js/pull/558
I'll probably try to integrate it into less-docs myself, but I'm not sure how soon I get to it so I'm mentioning it just in case someone is interested to try to do this earlier.

from less-docs.

@seven-phases-max this is merged, correct? looks awesome btw!

from less-docs.

@jonschlinkert Thanks, yes, it was merged yet in previous site update (so it's already at the live site for two weeks or so).

from less-docs.

then done! thanks

from less-docs.