Sorry if it seems like I’ve abandoned this thread. I haven’t been getting notified about the replies. :(
Let me first say: I haven’t touched Carabiner in a long time. My life is pretty much all Ruby and JavaScript at this point, and I haven’t used CI for some time. Having said that, I’m still more than happy provide support in these forums. Having said that, I still see Carabiner as pretty much feature complete. The last thing I wanted to add (support for adding “extensions” to Carabiner) has been completed and in the codebase (in the extend branch in GitHub) since November of last year. I haven’t released it, as I haven’t had the time or motivation to adequately test it. Anyone can feel free to clone, fork, test or submit code. I’d be happy to give anyone an overview of the current extension philosophy, though it should be pretty well commented in the code. I do still plan to get to it at some point, I just can’t say when.
Now, I’ll try to answer all the questions I missed from the past several months. Anything older than that is probably not worth answering.
@zombaya and @mikedfunk Those are solid additions. If you want, fork me on github and submit pull requests with the changes.
@vertmonkee Not with Carabiner. As mentioned, there are other ways.
@webPragmatist You had a bunch of questions that didn’t really get answered. I’ll answer them in reverse: First, feel free to fork: http://github.com/tonydewan/Carabiner. I’d be happy to still maintain the codebase if you want to submit Pull requests. In terms of “queueing” groups, I think what you want is the display_string method. It will return a string of the display result, rather than just echoing. The display method is meant to be used in views, which is why it works the way it does. display_string will allow you to call it in controllers and use the resulting string as you see fit. Third, your best bet is to use the parent folder as the config value, and just deal with longer paths.
@TigerWolf I’m not totally sure what you mean. Are you saying you want to add a group as an item in another group? If so, then no, that won’t work.
@Bulletz I haven’t ever tried this, but it should work. You might have issues with the caching conflicting with the internationalization output. However, as long as the “filenames” you reference are unique (for example “internationalize.php?lang=en” versus just “internationalize.php”) it should work okay. You’ll probably run into issues if the php files are running through the whole CI stack, rather than just bare php. Let us know if it works.
I hope that helps people. Thanks everyone for using Carabiner! I’m glad it’s been useful.