Wednesday, January 30th, 2008

Lipsiadmin: Rails 2.0 Ext Admin

Category: Rails, Sencha

<>p>

Lipsiadmin is a framework that generates Ext 2.0 views on top of your Rails 2.0 application, a compelling duo indeed.

You can strap into your migrations to add menus such as:

  1. # I will create also my menu
  2. menu = Menu.create(:name => "Articles", :admin => true, :position => 1)
  3. # And my
  4. menu.menuitems.create(:name => "New Article", :url => "/admin/articles/new",
  5.   :position => 1, :style => "icon-no-group")
  6. menu.menuitems.create(:name => "List Articles", :url => "/admin/articles/list",
  7.   :position => 1, :style => "icon-show-all")

If you stay in REST land it all just starts to work. Very Naked Objects-esque.

Check out the live demo (u: info@lipsiasoft.com, p: admin).

Speaking of Ext, the team has been expanded its offerings.

Posted by Dion Almaer at 5:47 am
7 Comments

++++-
4.4 rating from 45 votes

7 Comments »

Comments feed TrackBack URI

The button is labeled “Delte” :)

Comment by Gordon — January 30, 2008

Not only that. Look at the “Delete Confirmation Window”, it says: “Do you really want to permanently 3?”

I just opened up the Interface Demo. I find it really slow. The navigation on the left is interactive, but when you klick on a link you loose all your preferenaces. It does not use any AJAX? Everything generates a page reload! I would be OK with that if it would not be here on Ajaxian.com :)

Comment by polysign — January 30, 2008

@Polysign: The reason for the post is because it uses Ext 2.0, one of the top JS/Ajax libs available

Comment by Rey Bango — January 30, 2008

the use of Ext in this admin is very poor… This is not an Ajax interface at all. This is a good idea, but you need more xp with ExtJS ;)

Comment by devil1591 — January 30, 2008

Hm. The list search results always seem to be one keystroke behind your typing. I tried to leave a bug report and saw just one issue tracked in the system. I’m afraid there’s not a lot of people using or contributing to this framework at the moment.

Comment by dubnium — January 30, 2008

@dubnium

What is the problem with issue tracker?

This framework is very new, so at the moment there are few contributions, but I hope in future…

For any question use this: http://rails.lipsiasoft.com/projects/lipsiadmin/boards

Comment by DAddYE — January 31, 2008

Hi Dion!

I´m starting to use Lipsiadmin with Associations and doesn´t work. The problem is the same that reproduced by Gabrio.
Probabily I´m doing something terrible. :)

Well, I have do this:

Ruby script/generate model state
Ruby script/generate model city

create_states.rb
class CreateStates 2, :null => false
t.column :name, :string, :limit =>50, :null => false
end
end
def self.down
drop_table :states
end
end

create_cities.rb
class CreateCities 50, :null => false
t.integer :state_id, :null => false,
:options => “CONSTRAINT fk_cit_sta REFERENCES state(id)”
end
end
def self.down
drop_table :cities
end
end

In my model, I put this:

class City < ActiveRecord::Base
belongs_to :state
end

class State < ActiveRecord::Base
has_many :city
end

When I tried to insert a new city, only the name appear for me and if I save, the application frozen.

Did you have the same problem?

Thanks

Reply

Comment by RicardoLeme — December 4, 2008

Leave a comment

You must be logged in to post a comment.