On 2015-01-18 18:23, Andrei Alexandrescu wrote:

Heheh, way to use Archuduke's Ferdinand assassination :o). I'm sorry
Jacob but this one is really out there.

DDoc has nothing with this, and to the extent it does it actually helps.

No it has not, but other strange solutions you're coming up with for CSS minification and gzip.

I'm not going to touch the code for the web site as long as it's written in Ddoc. Simple as that.

So I start yesterday with searching "Css vertical menus" and the such.
After some browsing I figured a sort of hierarchical/accordion menu
would be good for us. There's plenty of them to choose from, neither of
which require Rails - apparently there are many lost souls out there. I
insisted on one that doesn't need Javascript, but at that point I
couldn't find any. So I settled for those that use jQuery, which we
already use so - nice. There are plenty of those too.

So I chose one, downloaded, and integrated it within our site. The funny
part is it was easier to work with the thing _because_ of ddoc, not in
spite of it. So our source code for menus looks like this:
http://goo.gl/QddFkh. It makes it very easy to move entries around,
change them all at once, etc. That generates http://goo.gl/ZLJisi, which
even after nice formatting is quite difficult to work with.

I don't understand this? Do you think the alternative of Ddoc is to use plain HTML? I would never use just plain HMTL. I would use a server side language to generate it. With all the flexibility it comes with it.

If we change the tooling, I'd say vibe.d is the best option for obvious
dogfooding reasons. The problem with Rails and other frameworks is that
*you* prefer it, but *I* and *others* are in for most of the work with it.

That's why I said vibe.d would be a better choice.

--
/Jacob Carlborg

Reply via email to