<h2>Sign up</h2>
 
<% form_for resource_name, resource, :url => registration_path(resource_name) do |f| -%>
  <%= f.error_messages %>
  <p><%= f.label :email %></p>
  <p><%= f.text_field :email %></p>
 
  <p><%= f.label :password %></p>
  <p><%= f.password_field :password %></p>
 
  <p><%= f.label :password_confirmation %></p>
  <p><%= f.password_field :password_confirmation %></p>
 
  <p><%= f.submit "Sign up" %></p>
<% end -%>
 
<%= render :partial => "shared/devise_links" %>

and

<h2>Sign in</h2>
 
<% form_for resource_name, resource, :url => session_path(resource_name) do |f| -%>
  <p><%= f.label :email %></p>
  <p><%= f.text_field :email %></p>
 
  <p><%= f.label :password %></p>
  <p><%= f.password_field :password %></p>
 
  <% if devise_mapping.rememberable? -%>
    <p><%= f.check_box :remember_me %> <%= f.label :remember_me %></p>
  <% end -%>
 
  <p><%= f.submit "Sign in" %></p>
<% end -%>
 
<%= render :partial => "shared/devise_links" %>

If you try to put them somewhere else you’ll run into some problem. There are some variables/methods those forms use that you’ll be lacking, specifically: resource_name, resource and for logging in also devise_mapping. I’ve recently tried to put them both in the homepage for an upcoming project of mine and this is how I’ve solved it:

module ContentHelper
  def resource_name
    :user
  end
 
  def resource
    @resource ||= User.new
  end
 
  def devise_mapping
    @devise_mapping ||= Devise.mappings[:user]
  end
end

I’m actually not sure if in that case we are more efficient (global communication infrastructure vs global transportation infrastructure and gas for the trucks and planes), we are definitely faster.

Recently my oven broke. The door is not stoping when it should and goes almost all the way to the floor when you open it. I’ve notified the management company and wanting to make the process more efficient I’ve recorded a video of the issue and sent it to them. Ah, technology, love it!

Today the repair main arrived (at 7:30hs, very Swiss). He open the door and… “Ah! It’s broken, I’ll come back next week with the spare parts.”

Honestly I wasn’t surprised, but we already have the technology to make this whole thing more efficient, I did my part and I was ignored. I bet the apartment management company never sent the guy the video.

• Airplane: RCPowers Extra 300S
• Building material: EPP 6mm RG30
• Motor: Yellow BL Proton 3S
• APC Propeller 8×3.8
• Prop saver
• Servos: Tower pro SG91R
• ESC: Arrowind 12A
• Receiver: Futaba R607FS
• Batteries: Fullymax eXtreme Power FB1000XP-3S and 2S
• Glues: Epoxy, hot glue, CA.
• Carbon fiber strips.
• Shop: hobbynet.ch (Peter, the owner, spent two or three hours helping me get everything I need, even after closing time)

Some pictures of the building process and the finished result:

So exciting! There’s still a lot of work to do, I hope it’ll be flying this weekend (if the weather allows it).

Sometimes the best information is provided by the retailers, which is already wrong, but the real issue is that when retailers are not selling something anymore, they remove the product from the public page, and the information gets lost.

I’ve decided to fix the problem so I’ve created the RadioControlPedia. A wiki for RadioControl were articles will always stay and stay at the same URL. Over time it’ll have more and more information.

gitignore.com

For now it’s just a blog, but the final goal is different:

Every time I start a new project I hesitate to make the first commit: what should I commit and what shouldn’t I? Essentially, what should I put on .gitignore.

The goal of this site is to collet snippet of .gitignore that one should use depending on what framework, software, libraries, etc. are being used. I’ll try to put the ones I’ll know, but please, if you know any, send me an email to pupeno@pupeno.com and I’ll publish (with attribution).

My final goal is to develop a small web application with a list of the frameworks (as checkboxes or something) from which you can pick and it’ll build the .gitignore. But I’ll only do it if this site gathers enough information.

Dear NetBeans User,

In the past you have taken the time to report issues that you encountered while using NetBeans software. A new version (NetBeans 6.9) has just been released,and we’d like to inform you that the following issue(s) you reported have been addressed in the new release:

Please visit the netbeans.org website to download NetBeans 6.9 and to learn more about the new release.

We appreciate your contribution to our efforts to make NetBeans software and features better for all users. And as always, we look forward to feedback from you about ways we can continue to improve.Thank you.

The NetBeans Team

Apple is not a company that can be easily influenced. They do things the way they think is right even when everybody else disagrees. Even when everybody predicts is going to cost sales. They’ve been doing it for more than 10 years and it’s working very well for them, they are not going to stop now. For Adobe, Apple is a lost cause.

I actually dislike both companies. Apple is building an extremely proprietary environment. They are much worst than Microsoft. Apple’s tax not only includes the operating system, it also includes every third party application. Not only they get a part of everybody’s cake, they decide who have cake and who doesn’t by controlling which applications get approval and which get rejected. If Apple ever dominates the industry, it’ll be the dark ages of computers.

Adobe is not much different with Flash. Flash is a proprietary and it works well on one and only one platform; if it does at all. Everybody else is left out. Flash has been making the web inaccessible for ages. I would be very glad if we can get rid of Flash.

If I were in charge of Adobe I would do something that would help the company remain a leader on the web and at the same time make Flash good: open source it.

I never understood why Adobe hasn’t open sourced Flash already. The specs are more or less open, there are alternative implementations, and they are not making any money by selling Flash. They make money by selling the tools to build Flash web sites and that’s not going to stop if they make Flash itself open source.

Before or while open sourcing I would make agreements with two companies: Google and HP. Make sure Flash is going to be included in Android, Chrome OS and Web OS. I would also put those phones and tablets in the hand of my developers (that is, Adobe’s), for free, as a gift, with the goal of making the Flash experience is absolutely thrilling.

I think that is Flash’s only hope.