search

jonase / cljsfiddle

http://cljsfiddle.net
Eclipse Public License 1.0
93 stars 16 forks source link

adding clear output button. adding ability to grow/shrink the editor #7

Closed shaunxcode closed 11 years ago

shaunxcode commented 11 years ago

I think the changes are pretty straight forward and I tried to make them in a way that was consistent with the existing codebase. However I did notice emacs decided to fix some trailing white space etc. without my direct consent - hopefully that is not an issue.

jonase commented 11 years ago

This looks awesome, thanks!

I'll take a closer look at this later today or tomorrow.

jonase commented 11 years ago

Great work!

How difficult would it be to grow/shrink the editor both horizontally and vertically? Also, is it possible to make the console stick to the bottom so it also grows/shrinks with the editor?

If you're interested in exploring these suggestions I'll be happy to accept more pull requests. Otherwise, I certainly will when I get some free time.

Thanks again!

shaunxcode commented 11 years ago

Not hard at all I will take a look tonight. It might mess up the bootstrap stuff unless we have it snap to specific bs col widths?

I have some other ideas like having multiple namespaces open as different tabs in one fiddle that I am playing with too. On Nov 13, 2013 11:52 AM, "Jonas Enlund" notifications@github.com wrote:

Great work!

How difficult would it be to grow/shrink the editor both horizontally and vertically? Also, is it possible to make the console stick to the bottom so it also grows/shrinks with the editor?

If you're interested in exploring these suggestions I'll be happy to accept more pull requests. Otherwise, I certainly will when I get some free time.

Thanks again!

— Reply to this email directly or view it on GitHubhttps://github.com/jonase/cljsfiddle/pull/7#issuecomment-28427721 .

jonase commented 11 years ago

Don't worry about bootstrap. I only used it to .. ehm .. bootstrap the UI :)

Open/close additional namespace tabs is a good idea (and something I've also been thinking about). It might require some backend changes depending on how we want to implement it.