Hi Dave :) On Tue, Mar 27, 2012 at 9:34 PM, Dave Everitt <dever...@innotts.co.uk>wrote:
> > it is, it's just not immediately documented although there are some (a bit > out-of-date) posts on MySQL and Camping. The idea is that you can use what > you like, but perhaps an example for each case would be in order... > Yes what I mean for example is that somewhere clearly on the camping book we should have something like "Database: by default and in this example... camping creates an sqlite database called camping.db located by default in your home folder under .camping.db .... This is done for simplicity but you can easily define your own db engine ......" I don't want to compare this to other solutions but for example in php pear libraries (few of which I developed including Sqlite tools) It is very straightforward to any user (with PHP experience or not) what is going on. Perhaps this is not the aim of a ruby framework like camping where, if you have experience with MVC and ruby, you can figure out things pretty easily. If that is the case I might be totally off track ! I am giving you the view of someone with some programming experience in php, perl, bash but not a lot in ruby or rails. Hopefully the screencasts will clear many of these doubts to new users and be of help. I am somehow convinced that documentations/screencasts are as important as good code to get some decent usage and expansion in a project. This because programmers are exposed to so many options that you need to have a compelling story to tell :) > > > no, I think camping has a separate user base (wild claim, no stats) and > although (being Ruby) many are familiar with/also use RoR, this isn't taken > for granted and shouldn't appear as if it is... > > Thanks for this it is very clear. Again it could be that I am weak on this point so what is obvious to you or many camping users is a bit less obvious to me. > not at all, it's good to have new users! As for unifying things... well, > that's been tried before :-) the thing is, although we all get on, the > varying ideas about Camping's 'public face' each have a unique take on > things. http://camping.rubyforge.org/ is the main starting-point, and (as > you know) Philippe Monnet's site also has a lot of useful tutorials e.g. > this one on OAuth http://blog.monnet-usa.com/?p=293 But if you'd like to > list what you've found useful (or compile a set of ideas for brief guides > to Camping) at some point I'm sure there'll be a way to get it added > somewhere findable... I might even do it myself :-) > > I think it is fair for users like Philippe Monnet to have their own tutorials on their website :) Getting back to the database issue: when I came to camping the description was a micro web framework which is great. Now If you ask me micro and simple should let you set your db on the fly, easily like definedb or something to overwrite the existing DB or, on the fly, use another db engine. From the post http://stackoverflow.com/questions/9086590/where-does-camping-store-my-databaseit seems pretty easy but it has to be obvious. If you have an example about building a db backed simple website and don't tell me where the db is well, that is a bit too much hidden for my taste :) I think that if we want people to use camping in real projects (even dead simple ones like blogs, simple websites which I think should be the aim given that camping wouldn't be suitable, I think, for huge projects) a small chapter on "using databases" is pretty much needed ! :) Will get sure that Isak has a screencasts about this because, to me, it is actually the very first thing I would look from a framework! Best Regards David
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
