Photographer.io is now open source
blog.photographer.io
Photographer.io is now open source
1–10 of 23 posts
Re: Photographer.io is now open source
#2I love it when I get to see first-hand how other people have made great things. I really appreciate the author opening the code up for Photographer.io.
Re: Photographer.io is now open source
#3I love it when I get to see first-hand how other people have made great things. I really appreciate the author opening the code up for Photographer.io.
Thanks! Hopefully it'll help people out a bit if they're starting off with Rails 4 too, as this was built initially on the 4.0.0.rc1 release.
It should inspire me to polish up the test suite too; it's very lacking right now!
Re: Photographer.io is now open source
#4If anyone's interested in localising the app for their native language then please let me know (@robotmay). There's near-complete support for I18n throughout the entire app and it should, in theory, be quite straightforward.
Re: Photographer.io is now open source
#5I love it when I get to see first-hand how other people have made great things. I really appreciate the author opening the code up for Photographer.io.
Couldn't agree more.
Was just going through the Gemfile, and I love how he broke out the gems in the various categories - from debugging, to databases, to search, to caching to everything else.
It just makes the code so much easier to read and understand.
As a result of this repo, I looked into Slim - but the official docs are awful, so I won't be adopting that any time soon.
But this app is very interesting to read through.
You can tell a lot of work was put into this.
Re: Photographer.io is now open source
#6I love it when I get to see first-hand how other people have made great things. I really appreciate the author opening the code up for Photographer.io.
Couldn't agree more. Was just going through the Gemfile, and I love how he broke out the gems in the various categories - from debugging, to databases, to search, to caching to everything else. It just makes the code so much easier to read and understand. As a result of this repo, I looked into Slim - but the official docs are awful, so I won't be adopting that any time soon. But this app is very interesting to read…
Slim is a bit weird as their old documentation (which I learnt on) was miles better than the current lot. I'd still recommend it though, and feel free to ask me any questions if you do give it a go as I've been using it for at least a year now.
I've only recently started organising my Gemfile like this as I was really struggling with redundant gems lying around. I'm glad you like it :D
Re: Photographer.io is now open source
#7Earlier quoted context omitted.
Couldn't agree more. Was just going through the Gemfile, and I love how he broke out the gems in the various categories - from debugging, to databases, to search, to caching to everything else. It just makes the code so much easier to read and understand. As a result of this repo, I looked into Slim - but the official docs are awful, so I won't be adopting that any time soon. But this app is very interesting to read…
Slim is a bit weird as their old documentation (which I learnt on) was miles better than the current lot. I'd still recommend it though, and feel free to ask me any questions if you do give it a go as I've been using it for at least a year now. I've only recently started organising my Gemfile like this as I was really struggling with redundant gems lying around. I'm glad you like it :D
Congrats on the wonderful job.
So I guess my first question about Slim is how does it work?
For instance, I am trying to figure out how on your home page, you have the following copy:
Upload, organise, and share your photographs alongside others, like Robert May did with this superb image.
Where 'Robert May' and 'superb image' are dynamic links - that correspond to the image below it (although maybe you may want to change the copy to "the superb image below" or something of the sort, because it took me a while to realize that image showing on the page is the same image you were talking about and linked. I thought they were 2 different images).
So, I guess just to start off...where is the actual copy of "Upload, organise, and share your photographs...." actually stored. I don't see that copy in the .slim file at all. It seems to be abstracted to 'home.blurb' - https://github.com/afternoonrobot/photographer-io/blob/maste...
But I have no idea where that is.
Sorry if this changes the topic a bit, but I am curious.
Re: Photographer.io is now open source
#8Earlier quoted context omitted.
Slim is a bit weird as their old documentation (which I learnt on) was miles better than the current lot. I'd still recommend it though, and feel free to ask me any questions if you do give it a go as I've been using it for at least a year now. I've only recently started organising my Gemfile like this as I was really struggling with redundant gems lying around. I'm glad you like it :D
Congrats on the wonderful job. So I guess my first question about Slim is how does it work? For instance, I am trying to figure out how on your home page, you have the following copy: Upload, organise, and share your photographs alongside others, like Robert May did with this superb image. Where 'Robert May' and 'superb image' are dynamic links - that correspond to the image below it (although maybe you may want to c…
Ah ha, that's actually not the doing of Slim but rather my usage of I18n, the localisation system used in Rails. Whenever you see t("something.stuff") or I18n.t("something.other.stuff") it's looking for those keys in YAML files under config/locales, primarily in en.yml at the moment. So the text you're looking for is here: https://github.com/afternoonrobot/photographer-io/blob/maste...
I'm not sure my way's the best, but I'm passing two generated links into that t() call which are then interpolated into the string in the YAML file.
If you've not used I18n before then it can make the views really confusing to read through without the text to reference! :)
Re: Photographer.io is now open source
#9Earlier quoted context omitted.
Congrats on the wonderful job. So I guess my first question about Slim is how does it work? For instance, I am trying to figure out how on your home page, you have the following copy: Upload, organise, and share your photographs alongside others, like Robert May did with this superb image. Where 'Robert May' and 'superb image' are dynamic links - that correspond to the image below it (although maybe you may want to c…
Ah ha, that's actually not the doing of Slim but rather my usage of I18n, the localisation system used in Rails. Whenever you see t("something.stuff") or I18n.t("something.other.stuff") it's looking for those keys in YAML files under config/locales, primarily in en.yml at the moment. So the text you're looking for is here: https://github.com/afternoonrobot/photographer-io/blob/maste... I'm not sure my way's the best,…
Ahhh....right.
I haven't used it much...but that's an interesting take on it.
I've seen it used for date & time localization - not for such heavy copy usage like this.
Do you profile the site - with say Rack-Mini-Profiler to see what the performance hit of using I18n like that would be? I don't see it in the Gemfile, but maybe you are using something else to see what the hit of all those choices are on your performance?
It seems that it may be an extra tax - even though it is clever and I like it...just curious what the cost is...and would love to know other non-I18n ways to achieve that, with say ERB.
Re: Photographer.io is now open source
#10Earlier quoted context omitted.
Ah ha, that's actually not the doing of Slim but rather my usage of I18n, the localisation system used in Rails. Whenever you see t("something.stuff") or I18n.t("something.other.stuff") it's looking for those keys in YAML files under config/locales, primarily in en.yml at the moment. So the text you're looking for is here: https://github.com/afternoonrobot/photographer-io/blob/maste... I'm not sure my way's the best,…
Ahhh....right. I haven't used it much...but that's an interesting take on it. I've seen it used for date & time localization - not for such heavy copy usage like this. Do you profile the site - with say Rack-Mini-Profiler to see what the performance hit of using I18n like that would be? I don't see it in the Gemfile, but maybe you are using something else to see what the hit of all those choices are on your performan…
I must admit that I haven't looked into the speed side of it too much! I suspect it's not too bad as the YAML file is loaded once on initialisation into a hash, which the t() function then retrieves the values from. I'm not sure if that differs when using a database backend.
One benefit of using Slim here is that it's a bit faster than ERB/HAML (as you can see in my token biased benchmarks: https://speakerdeck.com/robotmay/a-simple-introduction-to-ef...) so it probably negates any extra time that might be added by using locales.
There's two main reasons I use locales so heavily:
1. I like my views to be small and largely free of logic
2. I'd like to translate the site into other languages, and using locales from the start makes it much simpler!