Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explanation for non-Ruby users #8

Closed
rowild opened this issue Sep 10, 2014 · 7 comments
Closed

Explanation for non-Ruby users #8

rowild opened this issue Sep 10, 2014 · 7 comments

Comments

@rowild
Copy link

rowild commented Sep 10, 2014

Hi, I am not a Ruby user. Where can I get information on how to generate the HAML?

Thanks!

@sbstjn
Copy link
Owner

sbstjn commented Sep 11, 2014

You don't need Ruby/HAML to get it working.

Use the JS and CSS file inside the dist/ folder and take a look at http://semu.github.io/timesheet.js/

@rowild
Copy link
Author

rowild commented Sep 11, 2014

I am confused... there has to be some html, right?

I can get grunt running, that's no problem. But trying to process the haml files - which should work, right? - is, where I am stuck. Also, using the grunt-contrib-haml plugin throws an error:

Exception on line 14: undefined method `javascript_include_tag' for #Object:0x007ffb8a3dd6e0
Use --trace for backtrace.

Any help would really be appreciated! Thanks!

@sbstjn
Copy link
Owner

sbstjn commented Sep 11, 2014

try

bundle install
middleman

or

bundle install
middleman build

After that you have the site available at http://semu.github.io/timesheet.js, but that's not needed for using Timesheet.js. All HTML code is generated for you using JavaScript …

@rowild
Copy link
Author

rowild commented Sep 11, 2014

Thank you, that worked!

Are the websocket and swf reference included by the ruby-live-reload-thingy? And why is the actual html not saved anywhere?

No offense, but for a newcomer, this is all vey confusing... I really think such a nice project should provide more info on how to get it running and also generate the HTML output (which must be somewhere... not everything is in the JS, right?)

Sorry for the critique - it is a wonderful script that you share here. It would be even greater if it was more "accessible" :-)

BTW: why don't you use grunt's haml module? That would keep things consistent and within one "technology frame"...

All the best and thanks again!
Robert

@sbstjn
Copy link
Owner

sbstjn commented Sep 11, 2014

No offense

none taken ;)

Are the websocket and swf reference included by the ruby-live-reload-thingy?

yes.

which must be somewhere... not everything is in the JS, right?

That's the idea behind Timesheet.js. You do not have to create HTML structure for your data. Just include the JavaScript file, provide a structured set of data and everything is generated for you.

why don't you use grunt's haml module?

Because HAML/ruby/middleman is only needed to generate the GitHub info page.

@rowild
Copy link
Author

rowild commented Sep 11, 2014

:-) Yes, for the data (the .timesheet section). But you provide more than that with your example here. It is just my feeling that a project transports a sense of completeness, if the show case can be duplicated.

I am a somewhat tenacious, maybe even stubborn character as you might have guessed by now already ;-) So I'd like to give it one more try to ask you whether it is possible to convince you to provide a grunt haml solution the get the html processed, too??

Would be great - but I do understand that this is of course your product and I still could forge it...

Million thanks for your help and patience!
Robert

@sbstjn
Copy link
Owner

sbstjn commented Sep 11, 2014

It is just my feeling that a project transports a sense of completeness, if the show case can be duplicated

Jep, you're are right on that. But Timesheet.js is work-in-progress and not something to be considered a failsafe 1.0 release. And as mentioned before, you can easily run the showcase with bundle install && middleman

provide a grunt haml solution the get the html processed

I don't see that in the near future, I'm sorry. But I will keep it on the list for a rainy sunday :)

@sbstjn sbstjn self-assigned this Sep 14, 2014
@sbstjn sbstjn assigned sbstjn and unassigned sbstjn Mar 2, 2015
@sbstjn sbstjn closed this as completed Mar 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants