Yurii Rashkovskii's Blog

While I have discovered RSpec on Rails for a while ago, I haven’t really used it yet.

But today I have moved Frontcamp tests to RSpec specifications, finally. Even without test2spec (it failed to translate my tests for some reason), transition to specs did not took too much time. I’ve accomplished it in 2-3 hours or so.

What should I say? I like it. My tests were completely bad organized before, I’ve found that I’ve missed few bugs in an implementation and I’ve found that my test aren’t covering some important aspects. And for all this, thank you, RSpec team.

To not to change my habit to type `rake’ to run tests I’ve written very simple lib/tasks/rakespec.rake:

1
2
3

task :default do
        Rake::Task["spec"].invoke
end

Also, I’m very excited about `spec -f s’ and `spec -f h’ output.

I have been warned that running tests without rails_spec_server (now it seems to be called rails_spec_runner) could be not very fast. But since I’ve found that I need to restart rails_spec_runner mostly after each rails_spec invocation (probably some bug, or may be I’m missing something), I’ve tried to run `spec’ and I’ve found its speed reasonable and acceptable.

More to report later. Anyway, my specifications are in a trunk already.

What is important for us in our Frontcamp projects—it is a high simplicity of web publishing with it. We’re working hard each day on it, dropping unnecessary features and inventing conventions in order to make things easy.

Yesterday we made next step on Frontcamp simplification. We’ve defined very ease naming scheme and defaults for templates.

Let me show it briefly.

(Please note that these screenshots make use of preliminary version of syntax and conventions used in Frontcamp; they are subject to change before launch)

First, we create an index page in a category named ”/” :

It’s a page that will be rendered on a ”/” request.

Then, we define template for it (message named / in a “Templates” category_):

After this, let’s define a template for Blog Entry

Then, we submit a message to Blog Entries:

Let’s see what we’re getting:

Yes, it has rendered index in / with a template for it. No more explicit templates in each page!

Let’s see how it can work for a bit more complicated structure.

Let’s define two pages in /articles:

test:

and list:

Obviously, they should be rendered with different templates:

Let’s look what Frontcamp is able to generate now:

As you can see, we’ve got two different templates. Voila!

We’re going to have a limited preview launch in October. Subscribe to get notified today!

Today I will show an early preview of what Frontcamp is about.

(Please note that these screenshots make use of preliminary version of syntax and conventions used in Frontcamp; they are subject to change before launch)

First, we create an index page:

Then, we define Main template

and template for Blog Entry

Then, we submit a message to Blog Entries:

Finally, Frontcamp can automatically render the following web page:

I hope that this peek will help you to understand, what Frontcamp is for!

Subscribe to get notified about launch today!

Here are you some updates.

• We’ve almost finalized developing an easy-to-learn template language. Publishing with Frontcamp should be really easy. I’d rather prefer to tease you ;) before I will show an ease of this template language. I want to keep some secrets until private beta launch.
• Now you can chat with Frontcamp authors before launch (Campfire-based).

Stay tuned!