search

jedfoster / SassMeister

The Sass playground
http://sassmeister.com
198 stars 25 forks source link

Suggestions for potential "pro" features #63

Closed lunelson closed 9 years ago

lunelson commented 10 years ago

I tweeted to @sassmeister today that I'd pay for pro features if they built them. This is a follow-up to outline what I had in mind. Basically: features which might require a development investment—and possibly ongoing overhead—such that they would require a subscription.

  1. gist importing, as with libraries. This was my main thought: I do a lot of debugging in sassmeister and have to paste in sometimes hundreds of lines of library code first before I can debug the stuff I'm after. It would be great if I could keep that stuff in separate gists and just pull it in. I imagine a syntax similar to the way we can already include libraries: e.g. @import "gist/654321";
  2. ability to name gists, and acess and retrieve them by name. One of the downsides with gists and sassmeister is that I have many many gists now that are all called "Sassmeister Input", when I view them on github. But conceivably, sassmeister could keep track of gists that I create through the SM interface, and potentially also store a name for each one (perhaps in a banner block comment), such that from within SM I could see my sm gists by name.
  3. custom banner. This is a kind of corrollary to the two points above: if I could set a preference on sassmeister to always start a new file—such as you get when you hit 'reset'—with a custom banner, I could set some defaults for the naming, description and also custom @import statements on my files. Something like a boilerplate I guess.
  4. user-selectable version of sass (i.e. ruby vs. libsass). Due to the growing interest in libsass, it would be great to actually work with that compiler. I'm migrating some code from ruby 3.3.x to libsass and in order to emulate what that version can support I have to use a local clone of the sassmeister sandbox, checked out at a pre-3.3 state (this being the closest replication of the current state of libsass' functionality). I don't have this hooked up with github access or anything so I don't get any of that other functionality, making it a bit less convenient (though a local sassmeister is faster ;)). Would be great if one could switch versions/compilers on the fly.
jedfoster commented 10 years ago

Feature number 4 above has been released.

rodrigoAbril commented 10 years ago

I would also gladly pay for the first 3 features :moneybag: hell... I would pay even for the first one :grey_exclamation:

KatieK2 commented 10 years ago

Asset hosting.

jedfoster commented 10 years ago

@KatieK2 What do you mean by "asset hosting"? What assets?

lunelson commented 10 years ago

Similar to whats' meant by "asset hosting" at Codepen.io probably -- drag and drop to upload, unique URL is generated for reference in html... a bit complex since there's no discrete "Pen" in this case just what's defined by the gist. Can you upload assets to a gist? Never tried that

jedfoster commented 10 years ago

Technically, a gist is just a git repo with a simple web interface; you can add any kind of file if you clone the gist locally. And the API allows for adding binary files, so there's no reason we couldn't add other resources to a gist. Wiring up the references is might be tricky.

Guess I'm just not clear on the use case. Other than image sprites, I don't know what kind of files would need hosting.

Spriting with Lemonade requires file system access, which doesn't really exist in our environment; I don't think sprites will ever be supported by SassMeister.

KatieK2 commented 10 years ago

It would be nice to have SM host front-end assets like fonts, images and SVG files, rather than having to hot-link off-site. This would help us make richer demos.

Also, it would be nice to be able to download a .zip file of code from a Sassmeister gist which included file.css, file.sass/scss, file.html, file.haml, and a license. This would make it easier for visitors to grab demos to play with, and to prep some code for a off-line scenarios like conferences or airplanes.

jedfoster commented 9 years ago

I would LOVE to have all these features, but the work to build even just the foundation of a "pro" version of SassMeister is simply too great.

After several months working on a service to handle user accounts (essential for being able to charge for additional features) I've come to the conclusion that SassMeister Pro just isn't feasible on my own. At least not in the foreseeable future.

lunelson commented 9 years ago

Totally understood, thanks for all your work @jedfoster