tag:c21.lighthouseapp.com,2009-09-20:/projects/37825-staticmatic/eventsc21 / StaticMatic Events2009-11-01T19:58:39Ztag:c21.lighthouseapp.com,2009-09-20:Event/400163392024-03-06T11:35:30Z2024-03-06T11:35:30ZHbomax.com TvsigninStaticMatic: Built in Compass configuration [#11]<li>Tag cleared.</li>
<div><p>To access HBO Max on your TV via <a href="https://www.tvactivatecode.com/hbomax-com-tvsignin/">Hbomax.com
Tvsignin</a>, first launch a web browser on your computer or mobile
device and navigate to the provided URL. Once there, you'll be
prompted to sign in to your HBO Max account or create one if you
haven't already. Follow the on-screen instructions to complete the
sign-in process. After signing in, enter the activation code
displayed on your TV screen to link your device to your <a href="https://www.hbomaxtvsignin.net/">www.hbomax.com/tvsignin</a>
account. Once confirmed, you'll have full access to HBO Max's
extensive library of content on your TV.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/400163382024-03-06T11:35:20Z2024-03-06T11:35:30ZHbomax.com TvsigninStaticMatic: Built in Compass configuration [#11]<li>Tag cleared.</li>
<div><p>To access HBO Max on your TV via <a href="https://www.tvactivatecode.com/hbomax-com-tvsignin/">Hbomax.com
Tvsignin</a>, first launch a web browser on your computer or mobile
device and navigate to the provided URL. Once there, you'll be
prompted to sign in to your HBO Max account or create one if you
haven't already. Follow the on-screen instructions to complete the
sign-in process. After signing in, enter the activation code
displayed on your TV screen to link your device to your <a href="https://www.hbomaxtvsignin.net/">www.hbomax.com/tvsignin</a>
account. Once confirmed, you'll have full access to HBO Max's
extensive library of content on your TV.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/400163372024-03-06T11:35:20Z2024-03-06T11:35:30ZHbomax.com TvsigninStaticMatic: Built in Compass configuration [#11]<li>Tag cleared.</li>
<div><p>To access HBO Max on your TV via <a href="https://www.tvactivatecode.com/hbomax-com-tvsignin/">Hbomax.com
Tvsignin</a>, first launch a web browser on your computer or mobile
device and navigate to the provided URL. Once there, you'll be
prompted to sign in to your HBO Max account or create one if you
haven't already. Follow the on-screen instructions to complete the
sign-in process. After signing in, enter the activation code
displayed on your TV screen to link your device to your <a href="https://www.hbomaxtvsignin.net/">www.hbomax.com/tvsignin</a>
account. Once confirmed, you'll have full access to HBO Max's
extensive library of content on your TV.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/400163362024-03-06T11:34:20Z2024-03-06T11:35:30ZHbomax.com TvsigninStaticMatic: Built in Compass configuration [#11]<li>Tag cleared.</li>
<div><p>To access HBO Max on your TV via <a href="https://www.tvactivatecode.com/hbomax-com-tvsignin/">Hbomax.com
Tvsignin</a>, first launch a web browser on your computer or mobile
device and navigate to the provided URL. Once there, you'll be
prompted to sign in to your HBO Max account or create one if you
haven't already. Follow the on-screen instructions to complete the
sign-in process. After signing in, enter the activation code
displayed on your TV screen to link your device to your <a href="https://www.hbomaxtvsignin.net/">www.hbomax.com/tvsignin</a>
account. Once confirmed, you'll have full access to HBO Max's
extensive library of content on your TV.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/95247822010-09-29T21:11:32Z2010-09-29T21:11:32ZMark RobinsonStaticMatic: Stylesheets not handled correctly [#14]<div><p>Sorry, just reread that. There shouldn't be :ie after
=stylesheets</p>
<p>And yes, you've fixed the bit I suggested in my first comment
but not the problem above if you want to take a look at it.</p>
<p>Thanks</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/95246402010-09-29T21:07:02Z2010-09-29T21:07:02ZMark RobinsonStaticMatic: Stylesheets not handled correctly [#14]<div><p>I just tried with the latest pre-release 0.11.0 and still not
working.</p>
<p>in layout I have<br>
= stylesheets :ie</p>
<p>that produces:<br></p>
<pre>
<code><link href="/stylesheets/screen.css" media="all" rel="stylesheet" type="text/css"/><link href="/stylesheets/ie.css" media="all" rel="stylesheet" type="text/css"/><link href="/stylesheets/print.css" media="all" rel="stylesheet" type="text/css"/></code>
</pre>
<p>What I would like is:</p>
<pre>
<code><link href="/stylesheets/print.css" media="print" rel="stylesheet" type="text/css"/>
<link href="/stylesheets/screen.css" media="screen" rel="stylesheet" type="text/css"/>
<!--[if lt IE 8]>
<link href="/stylesheets/ie.css" media="all" rel="stylesheet" type="text/css"/>
<![endif]--></code>
</pre></div>tag:c21.lighthouseapp.com,2009-09-20:Event/93936482010-09-22T20:18:59Z2010-09-22T20:18:59ZStephen BartholomewStaticMatic: Stylesheets not handled correctly [#14]<div><p>This should be working in the pre-release. Can you try and let
me know?</p>
<p>If it's still not working, can you post code samples?</p>
<p>Cheers!</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/92478192010-09-14T20:14:34Z2010-09-14T20:14:34ZMark RobinsonStaticMatic: Stylesheets not handled correctly [#14]<div><p>I just hacked it to work by adding this line around line 61:</p>
<p>File.exist?(File.join(@staticmatic.src_dir, 'stylesheets',
"#{file}.scss"))</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/92430242010-09-14T17:11:56Z2010-09-14T17:11:56ZMark RobinsonStaticMatic: Stylesheets not handled correctly [#14]<div><p>The stylesheets helper outputs print and screen stylesheets in
wrong order without appropriate media statement. Specifying media
and sheet order doesn't work because .scss aren't handled when
specifying sheets.</p>
<p>lib/staticmatic/helpers.rb</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/75278622010-05-24T13:04:04Z2010-05-24T13:04:04ZStephen BartholomewStaticMatic: Variables should not persist between pages [#13]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/75265522010-05-24T10:11:43Z2010-05-24T10:11:43ZStephen BartholomewStaticMatic: Variables should not persist between pages [#13]<div><p>Variables set in one page are being persisted to subsequent page
requests/generations.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/70642232010-04-20T10:10:53Z2010-04-20T10:10:53ZStephen BartholomewStaticMatic: Specify CSS framework options on setup [#12]tag:c21.lighthouseapp.com,2009-09-20:Event/70642192010-04-20T10:10:12Z2010-04-20T10:11:38ZStephen BartholomewStaticMatic: Built in Compass configuration [#11]tag:c21.lighthouseapp.com,2009-09-20:Event/70642072010-04-20T10:09:56Z2024-03-06T11:35:30ZStephen Bartholomew[Milestone] StaticMatic: 0.11.0tag:c21.lighthouseapp.com,2009-09-20:Event/70571922010-04-19T20:38:10Z2010-04-19T20:38:10ZStephen BartholomewStaticMatic: Incorrect use of || breaks helpers in Ruby 1.9 [#10]<li>State changed from <em class="change">“open”</em> to <em class="change">“resolved”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/70299202010-04-16T16:23:52Z2024-03-06T11:35:30ZStephen Bartholomew[Milestone] StaticMatic: 0.11.0tag:c21.lighthouseapp.com,2009-09-20:Event/67571462010-03-26T09:00:38Z2010-03-26T09:00:39ZJoe ChengStaticMatic: Specify build file extension [#7]<div><p>I took a stab at this. I also sent you a github pull request
with some additional comments.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/59498682010-01-25T11:48:08Z2010-01-25T11:48:08ZStephen BartholomewStaticMatic: Incorrect use of || breaks helpers in Ruby 1.9 [#10]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
<div><p>Wow - that's a pretty dumb bug - I'll get that sorted for the
next release.<br></p>
<p>Thanks for the patch.</p>
<p>Steve</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/58701612010-01-18T13:38:17Z2010-01-18T13:38:17ZBenedict EastaughStaticMatic: Incorrect use of || breaks helpers in Ruby 1.9 [#10]<div><p>It might, of course, be preferable to stop setting the names of
instance variables to strings altogether, but I don't know whether
there's some underlying reason it's done like this.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/58701462010-01-18T13:36:31Z2010-01-18T13:36:31ZBenedict EastaughStaticMatic: Incorrect use of || breaks helpers in Ruby 1.9 [#10]<div><p>The problem with the following line ought to be obvious:
<code>'@staticmatic'</code>, being truthy, will always be the
result of the disjunction.</p>
<pre>
<code>@scope.instance_variable_set(var, nil) unless var == ('@staticmatic' || :@staticmatic)</code>
</pre>
<p>This is a problem on Ruby 1.9, where instance variables names
are always set to symbols, even if strings are used in the setters
(as they are in Staticmatic). Consider this example script:</p>
<pre>
<code>obj = Object.new
obj.instance_variable_set("@myvar", "Test.")
obj.instance_variables.each do |var|
puts var.class
end</code>
</pre>
<p>Ruby 1.8.x will print <code>String</code>; Ruby 1.9.x will print
<code>Symbol</code>.</p>
<p>Patch is attached.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763872009-11-01T20:18:22Z2009-11-01T20:18:23ZStephen BartholomewStaticMatic: Centralise asset path generation [#5]<li>Tag changed from <em class="change">“<span class="tag">feature</span>”</em> to <em class="change">“<span class="tag">bug</span>”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/50763812009-11-01T20:14:31Z2009-11-01T20:14:31ZStephen BartholomewStaticMatic: Errors in Sass aren't reported gracefully [#4]<li>Tag changed from <em class="change">“<span class="tag">improvement</span>”</em> to <em class="change">“<span class="tag">bug</span>”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/50763792009-11-01T20:14:16Z2009-11-01T20:14:16ZStephen BartholomewStaticMatic: Specify build file extension [#7]<li>Tag set to <em class="change">“<span class="tag">feature</span>”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/50763772009-11-01T20:14:00Z2009-11-01T20:14:00ZStephen BartholomewStaticMatic: Page URL helper [#9]<div><p>To allow linking without the need to specify the extension
e.g:</p>
<p>path "about_us"</p>
<p>=> "about_us.html"</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763752009-11-01T20:12:25Z2009-11-01T20:12:25ZStephen BartholomewStaticMatic: Allow absolute paths to be used for assets & linking [#8]<div><p>As a configuration variable.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763742009-11-01T20:11:20Z2009-11-01T20:11:20ZStephen BartholomewStaticMatic: Specify build file extension [#7]<div><p>This will be specified in the template filename itself:</p>
<p>index.html.haml -> index.html</p>
<p>or even:</p>
<p>index.php.haml -> index.php</p>
<p>Filenames without secondary extensions will acts as they do
now:</p>
<p>index.haml -> index.html</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763662009-11-01T20:08:54Z2009-11-01T20:08:54ZStephen BartholomewStaticMatic: Centralise asset path generation [#5]<li>Tag set to <em class="change">“<span class="tag">feature</span>”</em></li>
tag:c21.lighthouseapp.com,2009-09-20:Event/50763452009-11-01T20:00:20Z2009-11-01T20:00:20ZStephen BartholomewStaticMatic: Configuration for asset paths [#6]<div><p>Allow users to configure where javascripts & images are
stored.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763422009-11-01T19:59:32Z2009-11-01T19:59:32ZStephen BartholomewStaticMatic: Centralise asset path generation [#5]<div><p>Currently asset paths are generated in multiple places including
helpers.</p></div>tag:c21.lighthouseapp.com,2009-09-20:Event/50763392009-11-01T19:58:39Z2009-11-01T19:58:39ZStephen BartholomewStaticMatic: Errors in Sass aren't reported gracefully [#4]<li>State changed from <em class="change">“new”</em> to <em class="change">“open”</em></li>
<li>Tag set to <em class="change">“<span class="tag">improvement</span>”</em></li>
<li>Milestone set to <em class="change">“<span class="milestone" data-id="54471">0.11.0</span>”</em></li>
<li>Assigned user set to <em class="change">“Stephen Bartholomew”</em></li>
<div><p>Agreed.</p></div>