Fulcrum Devel Google Group

Shutting down the fulcrum-devel group

m...@wholemeal.co.nz (Malcolm Locke) — Tue, 23 Oct 2012 00:35:08 UT

Hello everyone,

Given the extremely low level of traffic on fulcrum-users and
fulcrum-devel, I'm going to shut down this group and keep only
fulcrum-users running.

If you'd like to be kept up to date with announcements please subscribe
to the fulcrum-users list if you haven't done so already.

Re: [fulcrum-devel] New fork, greek localization and a bit of CSS work

m...@wholemeal.co.nz (Malcolm Locke) — Thu, 27 Sep 2012 21:35:08 UT

Thanks.

Cherry picked, and all green again ;)

Malc

Re: [fulcrum-devel] New fork, greek localization and a bit of CSS work

ad...@betmasters.gr (humbucker) — Thu, 27 Sep 2012 12:08:57 UT

This should do the trick:
[link]

From here on, I ll be working on branches and will issue pull request when
new features are completed and tested

Re: [fulcrum-devel] New fork, greek localization and a bit of CSS work

ad...@betmasters.gr (humbucker) — Thu, 27 Sep 2012 10:23:13 UT

Hey Malc, thanks for welcome.

No worries regarding the new features, I will do them in branches.

Regarding the errors, it is a utf-related issue, as 1.8.* and 1.9.* are
quite different in the way they handle UTF sources.
I will post a fix in a few hours.

thanks,
ac

Re: [fulcrum-devel] New fork, greek localization and a bit of CSS work

m...@wholemeal.co.nz (Malcolm Locke) — Thu, 27 Sep 2012 09:49:14 UT

The changes in `config/initializers/inflectio ns.rb` seem to have broken
the Ruby 1.8.7 build, see
[link]

The error is:

unmatched (: /(�)\271στορία$/

Any ideas on a quick solution to this? I think I'm probably OK at this
point with dropping 1.8.7 support if it's necessary, but I'd like to

Re: [fulcrum-devel] New fork, greek localization and a bit of CSS work

m...@wholemeal.co.nz (Malcolm Locke) — Thu, 27 Sep 2012 09:12:10 UT

Excellent work, thanks Humbucker (Achilles?).

I've merged the i18n and 'de-bolding' commits from your fork, many
thanks.

All sound good to me. If you work on each as a feature branch it will
make the pull request process a lot easier and increase the chance of a
swift and pain free merge into the mainline.

New fork, greek localization and a bit of CSS work

ad...@betmasters.gr (humbucker) — Wed, 26 Sep 2012 14:33:44 UT

Hi all, just chiming in to introduce our Fulcrum fork.
[link]
We have added greek locale files, a few view tweaks to facilitate a
smoother localization experience, and a few CSS tweaks - basically, we
considerably reduced the amount of *bold* text, as we found it difficult to

Re: [fulcrum-devel] Coffee-script usage

st...@aelogica.com (Steven Talcott Smith) — Tue, 24 Apr 2012 15:27:07 UT

Forgot to mention, one of the top devs here in the phillipines produced a js2coffee conversion tool that really helps when youre just starting out.
[link]
Try just pasting your js in there. It's easy.
Sent from my iPhone

Re: [fulcrum-devel] Coffee-script usage

tom.harrison...@gmail.com (Tom Harrison) — Tue, 24 Apr 2012 13:12:51 UT

Hey Malcolm --
Saw this thread and thought I would share a couple thoughts -- I think we
may have similar views.
I share your concern that meta-langauges on top of JS may not
survive/thrive. But I keep seeing it pop up in non-Rails places. While
it's true that it's not directly debuggable, it quickly becomes clear how

Re: [fulcrum-devel] Coffee-script usage

st...@aelogica.com (Steven Talcott Smith) — Tue, 24 Apr 2012 12:03:09 UT

Hi Malcolm, thank you for creating fulcrum and open sourcing it. Fulcrum is a nice project that is at once quite useful and functional and demonstrates some important newer technologies and techniques yet also small enough and contained enough to be able to hack on.
Having moved quickly from hacking on fulcrum to learn a little backbone to now going full bore with coffee script and backbone on a new project, I vote for encouraging David to go ahead with the conversion. It will be a chance for you to learn coffeescript which once you get over the newness becomes rather indispensable. It's not going away any time soon. More likely the ideas will get incorporated into some future javascript. The new hotness phenomena is part of our craft and we are always in the business of mastering something new. Let's not let fear of the new shut us down or restrain someone else's progress. Enthusiasm is a delicate thing. I welcome David's conversion to CoffeeScript. People may look to fulcrum for examples of real coffeescript. That would be cool!

Re: [fulcrum-devel] Coffee-script usage

m...@wholemeal.co.nz (Malcolm Locke) — Tue, 24 Apr 2012 11:22:54 UT

Hi David,
There may come a point in the future when the project converts to
CoffeeScript, or something similar, but I'm not quite ready for it at
the moment. My main motivations are:
- I'm still learning Javascript, and am not comfortable moving to a meta
language at this point. This is a pretty weak argument, and taking it

Re: [fulcrum-devel] Coffee-script usage

imacaterpil...@gmail.com (Eumir Gaspar) — Sun, 22 Apr 2012 23:41:53 UT

Just saw your reply to the html vs haml thing and i find it weird that it's
easier for you to debug coffeescript than javascript and then say the other
thing for haml and html. being a beginning web developer, i would suggest
that you stick with the basics(html and javascript) first because any
abstraction would just add to the complication. If you didn't know what

Coffee-script usage

rabbit.edi...@gmail.com (DavidA) — Sun, 22 Apr 2012 16:31:28 UT

Hi, I'm a beginning web developer and I noticed that fulcrum uses a
lot of Javascript. Tracking bugs in Javascript is kinda hard so I'm
teaching myself coffee script and I'm practicing converting
fulcrum .js files to .coffee files.
I'm no expert, but I was wondering if there was interest in doing

Re: [fulcrum-devel] Re: Rails 3.1 branch

tom.harrison...@gmail.com (Tom Harrison) — Mon, 05 Mar 2012 22:42:37 UT

Following the current approach, this sounds like a "settings" thing to me,
perhaps even in the database, or something to set in one of the
initializers. It's far from onerous to have to set this
up ([link]), and anyone deploying
the app may not necessarily use Heroku...

Re: [fulcrum-devel] Re: Rails 3.1 branch

m...@wholemeal.co.nz (Malcolm Locke) — Mon, 05 Mar 2012 20:46:54 UT

Looks like that's not set on Heroku cedar or bamboo. That one must have
slipped past me without being verified, unless it used to be defined on
heroku but they have since removed it, which I doubt.
I think options like that need to be extracted out to a config file that
isn't in source control, I'll put it in the backlog.