Seems right, needs more refinement

[pepe]

Did you think about helpers and rendering? Do you have any actual code, which could be tested?

Actually I have for long time some general thoughts about how should "ideal web framework" should look and I must say your concept really fits my vision.

I have vacation through most of august, but I definitely come back in September for more. Hope you will like my ideas!

[Wardrop]

I intend for everything other than the core routing (core routing being route matching, dispatching, filters, error handlers) to be implemented as helpers - modules if you like - which the user can choose to include or not. I'm going for something relative generic that can be easily tweaked and optimised on a per-application or per-developer basis.

Developers should be able to define in essence, their own application DSL. That's the idea behind the #route method for example which when used directly can seem a little verbose, but if called through a helper function (#get and #post being good examples) a lot of that verbosity can be written-once and hidden away. That's why it's called Scorched (synonym of dry). I also want developers to have a bit of fun innovating. Frameworks that are too opinionated kill the fun.

I've already spotted a couple of oversights in the example code in the README which I'll fix soon. Keep the feedback coming if you have any, it serves as good motivation.

As for code, I'll try and get something up this weekend. I don't want to put up half-baked ideas or a half-baked implementation. I'm keeping my first milestone as small and simple as possible, so hopefully I hit it if not this weekend, sometime in the next week or so.

[pepe]

Sorry for long wait, I had crazy September and then I got sick. But I would like to ask you, if you have any refinements to Readme and if any code is actually showable? I am just working on some small project, which will be suitable as testing bed for it.

I started to think about project generator:

• use thor as base for CLI
• have prepared DSL for project generation
• recipes for most common scenarios

I am really looking forward for what you have implemented!

[Wardrop]

Hey Pepe,

I also apologise as I'd moved on to other projects recently, but I do want to get back into continuing the development of Scorched. I have a bit of a vested interest actually because while I can't justify the time to development a framework for work, I do develop Ruby web applications as part of my job, and after just finishing a 6 month project using Padrino, I really want to use Scorched for my next project.

While I'm not against project generators, Scorched isn't necessarily well suited. A number of assumptions have to be made about the project for project generation to be useful, and Scorched isn't a very opinionated framework. Mind you, I haven't got much experience using project generators let alone building one (as I generally avoid them), so I may have a few misconceptions about them. Regardless, they're quite popular, and I'm open to the idea of implementing one.

Tom

[pepe]

Well I can see your point and understand it, but I am thinking more about some kind of recipes, which prepare project for me. But maybe it should not be part of this library, but something like higher level.

I will think about it more, and try to justify my reasons. You know rubyist, are pretty accustomed to generating. It is also connected to some other project, which I am dreaming of (working name: auTomato), which will be like mirror for cucumber, where you will write scenarios in gherkin and it will generate (again :) skeleton of the actions. Those will be then tested by cucumber.

But all said, I am really looking forward for your code!

pepe

[Wardrop]

Just an update. I've gotten back into Scorched and am making headway. Just about all my future projects depend on getting this done, so there's definite incentive for me to keep on it. I look forward to sharing v0.1 when it's ready.

[pepe]

Great, I am looking forward, for what you have in store :).

[Wardrop]

Hey pepe, just letting you know I've pushed up my first commit.