I tried to use that crazy stuff recently and it just doesn't work, in
webkit at least.
—
Jenna
On 20/12/2011, at 4:34 PM, Steve Klabnik wrote:
> Yep! Granted, if you serve it with an XML MIME type, it must be able
> to be parsed with an XML parser, so none of that
>
>
> this is insane
>
> stu
Yep! Granted, if you serve it with an XML MIME type, it must be able
to be parsed with an XML parser, so none of that
this is insane
stuff! But still...
I actually like XML. There are some of us in Ruby...
___
Camping-list mailing list
Camping-list@
Oh I didn't realise they had a formal 'use it with xml mime-type' sort of
arrangement as well as the polyglot markup. Thanks for schooling me, Steve! :)
—
Jenna Fox
On Tuesday, 20 December 2011 at 12:48 PM, Steve Klabnik wrote:
> http://en.wikipedia.org/wiki/HTML5#XHTML5
>
> http://www.wh
Nah I'd still just think "I want camping! I'll install camping!" but then it'd
just work :P
—
Jenna Fox
On Tuesday, 20 December 2011 at 1:15 PM, David Susco wrote:
> So then I'd have to remember it's the opposite of the way it's been? :P
>
> Dave
>
> On Mon, Dec 19, 2011 at 5:53 PM, Jen
#1 gets my vote.
Dave
On Mon, Dec 19, 2011 at 6:24 PM, Philippe Monnet wrote:
> Plus people familiar with - or switching from ;-) - Rails and other
> frameworks would also feel at home.
>
>
> On 12/19/2011 3:46 PM, Jenna Fox wrote:
>
> Mmm that's true. Lets stick with that.
>
>
> —
> Jenna Fox
>
http://en.wikipedia.org/wiki/HTML5#XHTML5
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#writing-xhtml-documents
being the specific line in the spec
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyfo
So then I'd have to remember it's the opposite of the way it's been? :P
Dave
On Mon, Dec 19, 2011 at 5:53 PM, Jenna Fox wrote:
> If no hard dependancies, can we switch it around so core camping is in a
> camping-seedling gem, and the regular camping gem is actually the one with
> all the omnibus
XHTML5 is a fancy name for the way the HTML5 spec grudgingly allows the use of
XML-like syntax, allowing for XML Builders like current markaby to be
technically allowable as valid HTML. It's not 'real' in that they don't provide
validators for it and browsers aren't supposed to parse it as XML o
Plus people familiar with - or switching from ;-) - Rails and other
frameworks would also feel at home.
On 12/19/2011 3:46 PM, Jenna Fox wrote:
Mmm that's true. Lets stick with that.
---
Jenna Fox
On Tuesday, 20 December 2011 at 9:37 AM, Magnus Holm wrote:
On Mon, Dec 19, 2011 at 23:26, Jen
If no hard dependancies, can we switch it around so core camping is in a
camping-seedling gem, and the regular camping gem is actually the one with all
the omnibus? I always forget when setting up a new system and end up confused
why camping isn't working
—
Jenna Fox
On Tuesday, 20 Decembe
Small note: XHTML did survive, it's XHTML2 which didn't: there's an
XML version of HTML5 called XHTML5.
We now return to your regularly scheduled discussion.
I didn't know about XHTML5 and can't find any recent information? -
DaveE
___
Camping-l
I'd like markaby to be a hard dependancy - it's the default, if it isn't
installed beginners get terribly confused, and installing one more gem really
isn't going to cause problems for people - computers have so much free space
these days. If they really (for whatever reason) want to refuse mark
Mmm that's true. Lets stick with that.
—
Jenna Fox
On Tuesday, 20 December 2011 at 9:37 AM, Magnus Holm wrote:
> On Mon, Dec 19, 2011 at 23:26, Jenna Fox (mailto:a...@creativepony.com)> wrote:
> > 'public' is a weird word which has special meaning in the context of web
> > development for l
switch to a hard dependency on Markaby, or should we continue what
we're doing today?
no hard dependency, continue as today - DaveE
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
On Mon, Dec 19, 2011 at 23:26, Jenna Fox wrote:
> 'public' is a weird word which has special meaning in the context of web
> development for legacy reasons. I think we could find a better word.
> 'Resources', 'web', 'files'?
Phusion Passenger uses 'public' to run a Rack-application, so it
certain
'public' is a weird word which has special meaning in the context of web
development for legacy reasons. I think we could find a better word.
'Resources', 'web', 'files'?
—
Jenna Fox
On Tuesday, 20 December 2011 at 8:41 AM, Magnus Holm wrote:
> I've been thinking about adding static files
On Mon, Dec 19, 2011 at 19:38, wrote:
> Okay sure, you can make it simpler, but you still have to type a bunch of
> stuff when you are making a controller.
>
> And now that we have 'set :views' I think it comes with to add the other
> stuff because you immediately think, oh well then I can set co
Anything else?
Yeah, set :controllers, set :models and set :helpers ;)
I won't give up on that
--
Twitter: http://twitter.com/bitpuffin/
Blog: http://bitpuffin.tumblr.com/
Github: http://github.com/milkshakepanda/
___
Camping-list mailing list
Camping
Okay, people who want to extend Camping apps, how should they write their code?
Because of the many modules/classes in Camping, it can be tiresome if
all developers need to re-create all the same included-hooks:
module MyExt
module Helpers; end
def self.included(mod)
mod::Helpers.
Stick with the way we're doing it. I only use markaby when it's
easier/prettier to use then HAML (quick one-line helpers and the
like).
Dave
On Mon, Dec 19, 2011 at 4:26 PM, Magnus Holm wrote:
> On Mon, Dec 19, 2011 at 21:34, Isak Andersson wrote:
>>> My suggestion would be to make it Markaby 2
I've been thinking about adding static files support for the Camping
Server, but I'm wondering how it should work.
Alternative 1:
app.rb
public
public/style.css # example
Alternative 2:
app.rb
app/public
app/public/style.css # example
And secondly, how would it work if you have mul
- I've been rewriting the Reloader/Server code a bit to support
rackup-files too. I want to merge that.
- Resolve the Markaby-thingie.
- Figure out how to deal with static files (see other thread).
- Figure out how to handle extensions to Camping (see other thread).
Anything else?
// Magnus Holm
On Mon, Dec 19, 2011 at 21:34, Isak Andersson wrote:
>> My suggestion would be to make it Markaby 2.0 (of course, once it's
>> running and mostly backwards-compatible), keeping the old gem name,
>> and to develop on a branch in markaby repo.
>
>
> Yeah, we should more or less do a rewrite and make
My suggestion would be to make it Markaby 2.0 (of course, once it's
running and mostly backwards-compatible), keeping the old gem name,
and to develop on a branch in markaby repo.
Yeah, we should more or less do a rewrite and make it properly open source.
You are allowed to make something with t
2011/12/19 Magnus Holm :
> The real question here is: Should it be a part of camping/mab.rb or
> the Mab-gem? I'm definitely for adding many features (indentation,
> attribute-validation, flow-validation), but not in Camping. The
> Camping implementation should just be enough to get you started.
M
The real question here is: Should it be a part of camping/mab.rb or
the Mab-gem? I'm definitely for adding many features (indentation,
attribute-validation, flow-validation), but not in Camping. The
Camping implementation should just be enough to get you started
I think mab should install with C
2011/12/19 Bartosz Dziewoński :
> 2011/12/19 Magnus Holm :
>> That's actually supported. If an attribute is `true` it will use the
>> attribute name as the value. (so checked: true is the same as checked:
>> "checked"). Also, false and nil attributes won't be included.
>>>
>
> I think this is a lit
On Mon, Dec 19, 2011 at 19:10, Dave Everitt wrote:
>>
>> Magnus: this commit implements a tiny and fast Markaby-alternative (called
>> Mab) ... it's completely inline in camping/mab.rb, but it should be fairy
>> easy to create another Rubygem where we could implement for advanced
>> features (inde
2011/12/19 Magnus Holm :
> That's actually supported. If an attribute is `true` it will use the
> attribute name as the value. (so checked: true is the same as checked:
> "checked"). Also, false and nil attributes won't be included.
>>
I think this is a little inconsistent now. We're already check
Small note: XHTML did survive, it's XHTML2 which didn't: there's an
XML version of HTML5 called XHTML5.
We now return to your regularly scheduled discussion.
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/c
Okay sure, you can make it simpler, but you still have to type a bunch of
stuff when you are making a controller.
And now that we have 'set :views' I think it comes with to add the other
stuff because you immediately think, oh well then I can set controllers to
right? But you can't. That was actua
Been lurking, so offering an overview response:
Jenna: I see this problem as a chance to be reborn anew.
This *does* seem like the opportunity to remake Markaby (continuing
the _why legacy) 'for the 21st Century' that generates either
optionally indented (n spaces) or minimised:
HTML5
One of Camping's major selling points is that it's just straight
forward ruby classes and modules. No magic. Magic is anything where
you don't immediately fully grasp how it works. set :controllers is
that type of thing.
-1 for magic, and +1 for questions like this:
Is it filename based? W
On Mon, Dec 19, 2011 at 00:47, Jenna Fox wrote:
> "sit there and write a module for each one"?
>
> You mean, type 'MyApp::Controllers::'? You could make it simpler by adding a
> C = MyApp::Controllers line before your controller requires, then you could
> write 'class C::Whatever < R('/url')' sort
2011/12/18 Bartosz Dziewoński :
> I don't have time to look thru now, but it doesn't seem to support
> boolean attributes (e.g. `input checked:true` should render checked="checked" />)? I was very much missing this feature in old
> Markaby, and finally even wrote a patch, as you might remember[1].
35 matches
Mail list logo
