Yeah, what Jenna said. Also, can you show us the error you're getting?
-- Eric
On Thu, Apr 23, 2009 at 7:16 AM, Jenna Fox bluebe...@creativepony.com wrote:
Why are you using the 'p' function in your controller? this is strange.
You give it a string containing ruby code... maybe closer to what
hi :)
i'm not has error.
but click the button,
show white page.
i want action is easy,
first, submit button click!
and some action from post function in 'Newsctrl' controller.
some action is save(sqlite3) that 2 inputbox's input
i thing not connect that views and controller
thank you for
Something like this should work for the old version of Camping:
class Upload R '/upload'
def get
render :upload
end
def post
upload = @input.upload
filename = File.basename(upload.filename)
puts @input.upload[:tempfile].path
puts filename
hi all!
i can't speak english well..
i want know that file upload...
Search has a lot of time.
i can find just one Example
this link..
http://www.oreillynet.com/ruby/blog/2007/01/the_joy_of_rolling_your_own_wi_1.html
And it was typed.
but, error occurs.
error code(Fold) is...
Camping
In the current version of Camping, we use Rack. Rack has a slightly
different upload system.
To read the contents of an uploaded file, where the upload was done
using input type=file name=upload you must now do:
input.upload[:tempfile].read
This also applies to file uploads done
oh... sorry.
i can't use current version.
I had a lot of code writing.
i used 1.5.180 camping version.
when i upgrade to the latest version is a lot of errors.
but, I want to use the latest version.
Anyway,
how do upload file in 1.5.180
2009/4/2 Jenna Fox bluebe...@creativepony.com
In
I was able to get camping 1.9 to work with rack 0.9 by using a copy
pulled from the repository for rack listed on github.
git clone git://github.com/rack/rack.git
Paul
On Sat, Mar 28, 2009 at 10:06:57PM -0700, Garret Buell wrote:
Ok, scratch that last. Turns out camping works just fine with
On 29 Mar 2009, at 07:06, Garret Buell wrote:
Would we gain anything by making the switch?
Everybody would gain. Content-length is a requirement of the latest
Rack spec, presumaby to allow for easier caching, and you have to set
it _unless_ you send out chunked - but then you have to state
Well, this issue is actually solved in the latest master :-)
Maybe it's time to release this thing... I'm way to lazy :/
//Magnus Holm
On Sun, Mar 29, 2009 at 20:45, Julik Tarkhanov
julian.tarkha...@gmail.comwrote:
On 29 Mar 2009, at 07:06, Garret Buell wrote:
Would we gain anything by
What about using the github gem server?
http://github.com/blog/51-github-s-rubygem-server
That way the most current camping could be installed with a
gem install judofyr-camping
Instead of having to download and build it (marginally more difficult)
-Garret Buell
2009/3/29 Magnus Holm
Ok, scratch that last. Turns out camping works just fine with Rack 0.4
so it seems the change was with 0.9. I'm not too familiar with Rack --
what changes would we need to make to get camping working with Rack
0.9? Would we gain anything by making the switch?
-Garret
On Sat, Mar 28, 2009 at
hi all
i'm can't speak english well
i has something problem.
i used gems list is..
mongrel-1.1.5
camping-1.5.180
and update now..
camping-1.9.300
so, My blog looks like an error on the server.
my old code is ..
615 if __FILE__ == $0
616 require 'mongrel/camping'
617
618
Okay, boys and girls: Let's get ready for the release!
First of all, in case you missed it: I now have full access to the RubyForge
project and why's repo at GitHub. I guess this makes me some sort of a
project leader, but don't worry: The community will still maintain Camping.
I will continue
Magnus,
First, you are right, you are not _why but you are doing an
amazing job. You can throw away the little wheels.
I would be happy to contribute updating the Wiki at GitHub,
starting next saturday. Not sure what timeframe are you thinking for
the release...
Best regards,
On Sat, 2009-02-14 at 15:43 +0100, Magnus Holm wrote:
Okay, boys and girls: Let's get ready for the release!
When it comes to bug tracking, I really like ditz
(http://ditz.rubyforge.org) + sheila (written in Camping;
example: http://masanjin.net:9000/). What do you think?
Sounds great! I
+1 Little wheels, and down the hill :-)
Aníbal Rojas
http://hasmanydevelopers.com
http://rubycorner.com
http://anibal.rojas.com.ve
On Thu, Feb 12, 2009 at 1:30 AM, Jenna Fox bluebe...@creativepony.com wrote:
Yay little wheels!
Okay, first task! Whatever
I don't genuinely enjoy using any issue/bug trackers (who does?), but
Lighthouse is my least among evils. It's a lot nicer than Trac,
anyway. What do you guys think?
On Thu, Feb 12, 2009 at 11:40 AM, Magnus Holm judo...@gmail.com wrote:
Okay, let's roll!
I did some testing with `git checkout`
On Feb 12, 2009, at 6:56 PM, Eric Mill wrote:
I don't genuinely enjoy using any issue/bug trackers (who does?), but
Lighthouse is my least among evils. It's a lot nicer than Trac,
anyway. What do you guys think?
I rather like the oldskool idea of the bugtracker being powered by
Camping
On Thu, Feb 12, 2009 at 8:42 PM, Julik Tarkhanov
julian.tarkha...@gmail.com wrote:
Why not just 2.0.0 with a tag, then 2.0.1 with a tag and so on? Then you
also know everytime you release something you have a tag for it. And things
like rebases will not ruin your schemes
+1
On Feb 10, 2009, at 8:11 PM, Magnus Holm wrote:
Hm... I've always thought 1.5 == 1.5.180... Well, only _why has
access to the project, so there's not so much we can do :-(
I thought so too basically, but it 's not ==, its obviously . Ok,
I'll contact him off-list.
--
Julik Tarkhanov
On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote:
Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to
the project, so there's not so much we can do :-(
I'm sorry everyone, let's get this all worked out, okay?
Magnus, I've added you as an admin on both Rubyforge
Yay little wheels!
Okay, first task! Whatever Magnus has right now, lets call it 2.0 and
release it everywhere! We can bugfix later if we have to. :)
On 12/02/2009, at 1:35 PM, _why wrote:
On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote:
Hm... I've always thought 1.5 ==
On Feb 10, 2009, at 8:41 AM, Magnus Holm wrote:
Yes, we should release 2.0 soon...
Meanwhile you can always download 2.0 using my repo:
gem install camping --source http://gems.judofyr.net/
I can, but people who might need my apps can't and won't look for non-
official gem servers.
Is
Hello folks!
Just checking - I understand that Camping 2.0 entered the phase of
perpetual polishing and will not likely happen,
anytime soon, but would there be a possibility to at least have
1.5.180 on Robyforge for official installs instead of _why's repo?
I just tried to deploy my blog
Another option, which Rails has a lot of good documentation on, is to
create a row in your database which represents the image file, and
contains all the related meta data as well as a unique id number, and
then just keep the actual images in the filesystem named #.jpeg or
some such thing,
Roland just showed you how to inline it.
Here's a little article on the technique he's using:
http://jimbojw.com/wiki/index.php?title=Data_URIs_and_Inline_Images
However, as Jenna said, this technique doesn't work in IE. Her first
suggestion is probably the path of least resistance.
--beppu
Make a controller with a get method to retrieve the image, then, have
some code like this in it, supposing image_data is a string or
something:
headers['Content-Type'] = 'image/png'
headers['Content-Length'] = image_data.length.to_s
return image_data
On 03/02/2009, at 10:58 AM, Cornelius
Mmm, indeededly, though data: uri's don't work at all in internet
explorer, quite the bummer if you care :)
On 03/02/2009, at 12:15 PM, Roland Crosby wrote:
Well, you could sorta do img(:src = file_data), using the data: URI
scheme.
def data_uri(file_data, mime_type=image/png)
Camping::H hasn't longer indiffenrent access:
h = Camping::H.new
h.title = Sweet!
h[:title] != h[title]
Should we (1) don't make it indifferent at all, but rather say you should
always use method_missing (2) add indifferent access?
Here is one such implementation in 86 bytes, in case we
Hi Magnus,
I prefer using method_missing, with string access for fallback when
key names are not compatible with ruby method names.
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Yes, I want my method access too!..
Perhaps it'd be extra worthy of the '2.0' if you also did something
akin to:
def [](k);super(k.to_s);end
def []=(k,v);super(k.to_s,v);end
it's some bytes, but I think it's worth it!
What ever happened to Mash?
On 25/01/2009, at 1:50 AM, Aria Stewart
Yes! give me indifferent access! :D
On 25/01/2009, at 7:35 AM, Magnus Holm wrote:
Doh, the snippet I wrote was actually really stupid. Forgot we can
safely call super without thinking of recursive calls. What do you
guys think? Is it worth it?
Method access won't go away, and Mash was
Hi,
I've been noticing some disturbance in #camping lately, and I would
like to remind everyone about the Group Camp Agreement.
http://dnr.wi.gov/forestry/stateforests/SF-BlackRiver/pdf/BlackRiver-GroupCampAgreement.pdf
Please study it carefully. Also, point 2 about threaded applications
Well done, but I thought Perl would do better...
//Magnus
On 4. des.. 2008, at 10.37, John Beppu [EMAIL PROTECTED] wrote:
Behold! http://gist.github.com/31363
4004 bytes!
The non-obfuscated version can be found at:
http://github.com/beppu/squatting/tree/master
--beppu
PS: I'm not
Unfortunately, I am not a master of obfuscation. I don't know where the
masters went, either. Back in the day, there were some talented ASCII
artists working in Perl, but it's like they've gone extinct.
On Thu, Dec 4, 2008 at 2:57 AM, Magnus Holm [EMAIL PROTECTED] wrote:
Well done, but I
I think I could easily trim 20-30 bytes from the obfuscated version, but 3K
seems so far away.
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
On Sun Nov 30 21:39:53 2008, Singalicious365 wrote:
Cool to find some people that love the outdoors as much as I do!
Has anyone ever camped on the Tye River?
Yes, it was beautiful until the raft I had pitched my tent on got
overturned by sexually frustrated hippos.
--
Fred O. Phillips
Awesome! I've already thought of doing it myself, but I'm way to lazy!
Very nice, indeed!
Magnus Holm
On Sun, Nov 16, 2008 at 20:56, julik [EMAIL PROTECTED] wrote:
Hello everyone! Just a quick heads-up - ppplz willing to use Mosquito for
testing Camping 2 can track my Mosquito trunk on
Hello everyone! Just a quick heads-up - ppplz willing to use Mosquito
for testing Camping 2 can track my Mosquito trunk on github. I hope
for a rubyforge release soon. Camping 1.5 compat stays the same.
http://github.com/julik/mosquito/tree/master
Huh? I just pasted that code, ran camping test.rb and it worked just like
expected: Camping say Hello World!...
--
Magnus Holm
On Wed, Nov 12, 2008 at 6:29 PM, Eric Mill [EMAIL PROTECTED] wrote:
You want
def get
render :index, :hello = Hello World!
end
in your view. Unlike Rails,
On Mon, Oct 27, 2008 at 11:09:10PM +0100, Magnus Holm wrote:
Documentation is probably what's missing for a release. Both cleaning up
some part in the current docs and write some sort of how-to-switch-to-2.0.
And the wiki needs some work too!
Yes, we need to clear up the rdoc and write howtos
I've deployed a couple Camping apps in a FastCGI environment on shared
hosting, and written wiki pages on it. I feel like this must be a
pretty common scenario, since shared hosting itself is a common
scenario.
-- Eric
On Thu, Oct 30, 2008 at 11:01 AM, _why [EMAIL PROTECTED] wrote:
On Mon, Oct
On Oct 30, 2008, at 4:01 PM, _why wrote:
I don't know, what do
most people deploy camping on?
Oh yeah to imagine the scale: I have like 6 apps on FCGI now.___
Camping-list mailing list
Camping-list@rubyforge.org
On Oct 30, 2008, at 9:01 AM, _why wrote:
On Mon, Oct 27, 2008 at 11:09:10PM +0100, Magnus Holm wrote:
Documentation is probably what's missing for a release. Both
cleaning up
some part in the current docs and write some sort of how-to-switch-
to-2.0.
And the wiki needs some work too!
Okey. Today I cherry-picked some commits from zimbatm, Bluebie and
my experimental-branch so we can get a bit closer to 2.0:
- Making Camping::ARSession work with AR 2.1 -
d1db4f3c50815c93e370b696fb5b6c814bd1a7c4http://github.com/judofyr/camping/commit/d1db4f3c50815c93e370b696fb5b6c814bd1a7c4
-
Hi Garret,
check out why's repository on : http://github.com/why/camping
2008/9/5 Garret Buell [EMAIL PROTECTED]:
So I'm looking to get the latest, most very bleeding edge version of
camping. The question is, who's got it? It seems I can get it from
why, Magnus, or zimbatm on github. Why's
Garret,
I'm using _why's version for ruxtape, it works perfectly. I think his could
be considered the master and zimbatm or Magnus' are a little more
'experimental'.
Regards,
Josh
On Mon, Sep 15, 2008 at 3:17 PM, zimbatm [EMAIL PROTECTED] wrote:
Hi Garret,
check out why's repository on :
So I'm looking to get the latest, most very bleeding edge version of
camping. The question is, who's got it? It seems I can get it from
why, Magnus, or zimbatm on github. Why's seems to be the oldest but it
seems neither Magnus or zimbatm have merged changes recently. Should I
just merge the
It's a little early, but I wanted to announce a project that I'm
working on called Ruxtape. It's a pseudo-clone of Opentape (http://opentape.fm
), but written in Camping, of course. The reason that it's a little
early is that I'm having trouble getting the flash player to work, but
that
That's why I have monkey-patched it:
Apps = [].instance_eval do
def (i)
delete_if { |f| f.to_s == i.to_s}
super
end
self
end
Ex1 = Class.new
Apps Ex1 # = [Ex1]
Object.send(:remove_const, :Ex1)
Ex1 = Class.new
Apps Ex1 # = [Ex1] # the old one has been deleted.
Yes, I realize we
This is a nice little trick to defer some block execution in a multi-pane layout
module Views
def layout
html do
#...
body do
div.main { yield }
div.right! @_right_pane if @_right_pane
end
end
end
def _right_pane(block)
@_right_pane = block
That's pretty damned cool. Good technique!
--beppu
On Thu, Aug 28, 2008 at 3:46 AM, zimbatm [EMAIL PROTECTED] wrote:
This is a nice little trick to defer some block execution in a multi-pane
layout
module Views
def layout
html do
#...
body do
div.main { yield }
Camping::Apps is back! I don't know the *exact* reason it was being removed,
but now it's a monkey-patched array which at least doesn't leak memory when
using together with the reloader (were there more problems with this?).
I really think we need this, since there's no guaranty that only
Hi Magnus,
If I remember well, I am the one who introduced AND removed
Camping::Apps. I'm not sure anymore but I think it wasn't really used
and that solutions never really satisfied me. Do you have any use for
it ?
Cheers,
zimbatm
___
Camping-list
Is there a good blog post, article tutorial, anything on doing a file
upload in Camping? I've been looking around, but I haven't found
anything yet.
Regards,
Josh
___
Camping-list mailing list
Camping-list@rubyforge.org
If you're using Camping 2.0 stuff off github, file uploads work
exactly as they do in regular rack, so search around for rack upload
examples. :)
In camping 1.5, it works quite similarly, like this:
input.fieldname.tempfile.length #= how many bytes long it is
input.fieldname[:type] #=
No prob, I took a look at it using Opera, just wanted to let you know.
By the way please feed free to register, both you and your blog
(http://geraldbauer.ca) at RubyCorner.com a directory for blogs
related to the Ruby Programming Language or any of the related
technologies.
Best regards,
--
Gerald,
Doesn't work in Firefox 2.0.0.16 :-( (anyway I will be upgrading
my Ubuntu laptop in the next few days)
Best regards,
--
Aníbal
On Tue, Aug 19, 2008 at 10:26 AM, Gerald Bauer [EMAIL PROTECTED] wrote:
Hello,
I've created a S6/S9 version of Jeremy McAnally's GoRuCo slide
True to my word, I have created a page for using Camping 2.0 on shared hosts:
http://github.com/why/camping/wikis/camping-on-shared-hosting
Thanks to Magnus and Jenna especially for helping figure it all out.
-- Eric
On Sat, Jul 19, 2008 at 11:50 PM, Eric Mill [EMAIL PROTECTED] wrote:
Ah, hot
I've pointed to the fact that its not a problem of activerecord but
the stubbornness of the camping session module (insisting on natural
primary key) that keeps it from working
--
Julian Julik Tarkhanov
On 29-jul-2008, at 17:13, Bluebie, Jenna
[EMAIL PROTECTED] wrote:
Also worth noting
ActiveRecord::Base.partial_updates = false
and you should be good to go
--
Julian Julik Tarkhanov
On 29-jul-2008, at 16:11, Magnus Holm [EMAIL PROTECTED] wrote:
For some reason, AR 1.2 can't save serialized data. At least in the
tests I have done with Camping's Session model.
For now we
Is it that AR 2.1 only has problems in conjunction with Camping? Or
is table-based session support totally broken in Rails 2.1 right now?
-- Eric
On Tue, Jul 29, 2008 at 1:10 AM, Alpha Chen [EMAIL PROTECTED] wrote:
This happened to me... I saw an email on this list earlier about AR
2.1.0
For some reason, AR 1.2 can't save serialized data. At least in the
tests I have done with Camping's Session model.
For now we have to stick with 2.0.2, but I know the problem has been reported.
2008/7/29, Eric Mill [EMAIL PROTECTED]:
Is it that AR 2.1 only has problems in conjunction with
On Mon Jul 28 22:10:44 2008, Alpha Chen wrote:
This happened to me... I saw an email on this list earlier about AR
2.1.0 having problems, and reverting back to 2.0.2 got session support
working again.
On the command line:
$ gem install --version '=2.0.2' activerecord
In Camping:
gem
I have a sqlite3 database with the sessions table and schema set up
correctly. Sessions are created fine and put in the table, the cookie
is set with the correct hash and the hash is found again but when
using @state the values aren’t updated in the table.
I know that Session::service is called
This happened to me... I saw an email on this list earlier about AR
2.1.0 having problems, and reverting back to 2.0.2 got session support
working again.
On the command line:
$ gem install --version '=2.0.2' activerecord
In Camping:
gem 'activerecord', '=2.0.2'
Alpha
On Mon, Jul 28, 2008 at
They havent't changed the method. They probabely should.
When you run Mash.new it transforms all keys to strings (and turns
Hash'es to Mash'es), Mash[] doesn't do anything like that. And it
isn't Mash[:test = 1, :cool = 2] which raises errors, it's when you
call #inspect on it (it tries to sort
Yum. Did you try just setting YourApp::H = Mash ? If it works like
this out of the box
then we can keep the simpler solution and provide a recipe to work with mash ?
2008/7/23 Magnus Holm [EMAIL PROTECTED]:
I'm playing with Mash (http://mash-hash.rubyforge.org/) which has some really
nifty
I'm playing with Mash (http://mash-hash.rubyforge.org/) which has some really
nifty stuff. Here's the branch: http://github.com/judofyr/camping/tree/mash.
It requires 0.0.6 (which is only on GitHUb), but will work with 0.0.3
if you drop
the latest patch.
I don't know if it's worth another
This bug is actually Apache's fault. The problem occurs when you use
mod_rewrite to hide that you're using dispatch.cgi. When you use
RewriteRule ^(.*)$ dispatch.cgi the following happens:
* SCRIPT_NAME is set to /dispatch.cgi (since that's the actual script
which gets ran)
* REDIRECT_SCRIPT_NAME
Magnus, this is terrific information, thank you for looking into this.
I'm trying to follow your example - you use ApacheFixer to make a
TestingFixed class, but never use that class anywhere else. Do you
mean for the lines in dispatch.* to use TestingFixed instead of
Testing?
I'm trying to use
Simply replace Testing with TestingFixed in dispatch.cgi:11 and
dispatch.fcgi:13 to see the diffenrence :-)
On Wed, Jul 16, 2008 at 11:28 PM, Eric Mill [EMAIL PROTECTED] wrote:
Magnus, this is terrific information, thank you for looking into this.
I'm trying to follow your example - you use
Unfortunately this isn't working. I'm checking my ENV and
REDIRECT_SCRIPT_NAME isn't set to anything. I'm using the Rack spec
to try to figure out an alternative.
Right now, requests to / go to a Camping error page which says
/index.html not found! and requests to /login (which should go to
a
On 16 jul 2008, at 23:40, Eric Mill wrote:
Unfortunately this isn't working. I'm checking my ENV and
REDIRECT_SCRIPT_NAME isn't set to anything. I'm using the Rack spec
to try to figure out an alternative.
Rails resolves this somehow, they mount dispatch.fcgi as /
dispatch.fcgi and use it
The 500-handling I'm used to appears to be gone. What's the best approach here?
-- Eric
On Wed, Jul 16, 2008 at 6:08 PM, Eric Mill [EMAIL PROTECTED] wrote:
I think I've got it working, with this as the 'fixer' call:
def call(env)
env['SCRIPT_NAME'] = '/'
env['PATH_INFO'] =
I think I've got it working, with this as the 'fixer' call:
def call(env)
env['SCRIPT_NAME'] = '/'
env['PATH_INFO'] = env['REDIRECT_URL']
@app.call(env)
end
I think you might have meant REDIRECT_URL and not REDIRECT_SCRIPT_NAME?
Thank you Magnus!
-- Eric
On Wed, Jul 16, 2008
What about dropping the idea of config.ru and just create a dispatch.cgi
like this?
#!/usr/bin/env ruby
require 'app'
Rack::Handler::CGI.run(App)
On Fri, Jul 11, 2008 at 7:33 AM, Eric Mill [EMAIL PROTECTED] wrote:
Some progress: I put most of the code from dispatch.cgi into a
Could you show us the .htaccess please? :)
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Also, is it possible that you could simply rename dispatch.cgi to
something like 'appname' and use htaccess to grant that file cgi
execution type permissions? Or does this need to be on the root of a
domain?
___
Camping-list mailing list
can you please try adding to htaccess SetEnv SCRIPT_NAME /path/to/app
Assuming your dispatch is in /path/to/app/dispatch.cgi
Let us know what happens!
___
Camping-list mailing list
Camping-list@rubyforge.org
No wait, this is even better, at the end of your RewriteRule, put:
[env=SCRIPT_NAME:/path/to/app]
Let us know what happens!
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
I'm not able to get this working, I can't seem to affect the
environment, either using the SetEnv approach, or by including that at
the end of RewriteRule. How does Camping use the env in forming its
understanding of its base URI?
Forming URLs using the R method does not pre-pend /dispatch.cgi/,
I really do think we should build in the SCRIPT_URL || SCRIPT_NAME
thingo. This is going to be a relatively common situation. Totally
worth the bytes.
___
Camping-list mailing list
Camping-list@rubyforge.org
On Jul 15, 2008, at 12:58 AM, Bluebie, Jenna wrote:
I really do think we should build in the SCRIPT_URL || SCRIPT_NAME
thingo. This is going to be a relatively common situation. Totally
worth the bytes.
You might, but this is a can of worms. See, right now for example, if
you need to
We are talking about cgi here, not fast cgi. Specifically CGI's
interactions with mod_rewrite in apache.
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Hi all,
I have a little camping micro-blog that's working well with the cookie
session store, but falls over when I try to use the AR session store.
The changes I made were:
require 'camping/session' becomes require 'camping/ar/session'
module Blog; include Camping::Session; end becomes module
Specifically, Dreamhost. I'm trying to figure out how to get this to
work the standard dispatch.cgi or dispatch.fcgi setup. I've been
using the instructions that Magnus sent out when he first announced
his plan for Camping 2.0, but they either no longer apply, or I'm an
edge case.
I've been
Some progress: I put most of the code from dispatch.cgi into a
config.ru, and dispatch.cgi now uses backticks to literally call
'/usr/bin/env rackup'. This works, yet now calls to / redirect to
/dispatch.cgi/ (this is truly the path in my browser location bar),
and it messes with my routing.
On Jun 25, 2008, at 3:18 PM, zimbatm wrote:
One contra argument is that markaby is pretty old. Last time I checked
the trunk it was in a weird state. If I remember well,
it has been made Camping incompatible in favor of some Rails (!)
goodness.
Yeah, I removed Markaby from one of our Rails
R isn't gone! Feel free to use both (and if you use R, it would not
add more routes:
module Camping::Controllers
class Index;end
class Advanced R '/(some regex';end
# /advanced will NOT route to Advanced
end
On Tue, Jun 24, 2008 at 3:09 PM, Julik Tarkhanov
[EMAIL PROTECTED] wrote:
Does
Then I'm +1.
Can't wait to see my tests fail with 2.0 (I will obviously have to
update Mosquito for the new version, although if we still have .run
it should
work unmodified).
On Jun 24, 2008, at 3:14 PM, Magnus Holm wrote:
R isn't gone! Feel free to use both (and if you use R, it would
Nice! You should also go through the documentation, it's pretty bad at
the moment...
On Tue, Jun 24, 2008 at 5:07 PM, _why [EMAIL PROTECTED] wrote:
On Tue, Jun 24, 2008 at 01:05:54PM +0200, Magnus Holm wrote:
Man, that's way better than removing 135 bytes! I *love* the implementation!
I have
On Fri, Jun 6, 2008 at 6:07 AM, Magnus Holm [EMAIL PROTECTED] wrote:
It looks like everyone has tried to fix the cookies lately, and no-one
managed
to get it 100% correctly...
Thanks for the code, that seems to work really well and prettily. I admit
that, though I love writing apps in it, I
Judofyr: This isn't a question to ask _why. It simply cannot be done.
Stealing cookies is not the same thing as XSS, and locking cookies to
an IP address will not stop XSS at all. Locking cookies to an IP
address (as I wrote in my git commit where I removed it) will lock out
AOL users, and
Hi all,
Friday. Noon. I'm tasked with writing a small web front end. LDAP
validation required. Form data validation required.
I have to post form data to an external URL because of retarded
licensing issues. And validate the result using screen scraping.
I had the initial version done and
I forgot to mention though, the signing just stops users from changing
the session data without the server knowing, it doesn't stop them from
reading it. Any data in the session when using the cookie sessions
store only needs to be base64 decoded and unmarshaled with ruby to
find out
On 25 mei 2008, at 00:25, Magnus Holm wrote:
* insert your wish
* Are deeply nested query arguments and tricky bits like checkbox
arrays/param arrays handled properly (and in a Camping-compatible
manner, AFAIK in Camping
the first parameter wins as opposed to Rails) by Rack? What happens
On Sun, May 25, 2008 at 4:25 PM, Julian Tarkhanov
[EMAIL PROTECTED] wrote:
On 25 mei 2008, at 00:25, Magnus Holm wrote:
* insert your wish
* Are deeply nested query arguments and tricky bits like checkbox
arrays/param arrays handled properly (and in a Camping-compatible manner,
AFAIK in
I don't want to be the leader. I just want to contribute to one of the sweetest
framework that exists in the Rubyverse!
I'm going to contribute with what I can, and I suck at writing documentation and
I have no intention to learn RDoc (ATM, maybe another day).
(I still think that _why is the
If you can point to areas to document or changes you are making that
need documentation, I'd be happy to write it for you.
--Jeremy
On Sat, May 24, 2008 at 12:51 PM, Magnus Holm [EMAIL PROTECTED] wrote:
I don't want to be the leader. I just want to contribute to one of the
sweetest
framework
901 - 1000 of 1200 matches
Mail list logo
