search

qrush / motion-layout

A nice way to use iOS6+ autolayout in your RubyMotion app. Use ASCII-art inspired format strings to build your app's layout!
MIT License
215 stars 29 forks source link

Add options #7

Open wejn opened 11 years ago

wejn commented 11 years ago

Yet another way of setting options (turns out I'm not the only one needing this).

My approach allows for string/symbol shortcuts for option names.

Oh, and no, I'm not going to be adding readme and whatnot; mainly because @qrush ignores pull requests for 3 months so it'd be waste of time.

I'm just posting this in case someone looks in open pull requests and finds this helpful. I'll be using my local add-options branch, thankyouverymuch.

raganwald commented 11 years ago

I'm not going to be adding readme and whatnot; mainly because @qrush ignores pull requests for 3 months so it'd be waste of time.

So, if @qrush addresses this in two months, it would be a 33% improvement in response time?

wejn commented 11 years ago

So, if @qrush addresses this in two months, it would be a 33% improvement in response time?

If a tree falls in a forest and no one is around to hear it, does it make a sound?

lrz commented 11 years ago

As far as I know, he does not owe you a damn thing.

wejn commented 11 years ago

As far as I know, he does not owe you a damn thing.

Hm, it might be because english is not my mother's tongue but I don't see this implication anywhere.

I'd be happy if you could enlighten me where I made it. Seriously.

lrz commented 11 years ago

Sorry. What I meant is that this is an open-source project. People tend to work on them after their daily job, on a voluntary basis. When people don't reply it's usually because they don't have time, not because they ignore you. And making fun of the maintainer is not really helpful. A personal "hey, can you look at my patch" email would have been a better idea (maybe you did that, I don't know).

wejn commented 11 years ago

OK, I get your point -- I did not expect the message to be taken like this. Oops.

I certainly don't think @qrush is obliged to merge my pull req (there are two other pull reqs with similar functionality already under way).

I just wanted to make clear I'm sending this pull req in case someone finds my approach helpful and I'm not crossing my fingers for any merge; early or otherwise. And on the other hand, I don't intend to contribute more than I did, mainly because it might be in vain.

Hope this clears it up. Certainly no harm was intended.