Feeds:
Posts
Comentários

Posts Tagged ‘plugin’

(See this post in english)

Eu acabei de corrigir alguns bugs no plugin Rails Footnotes e agora temos suporte completo para Ubuntu Linux  (Deveria funcionar em outras distros também, porém apenas usando o Gnome e o Gedit são suportados até agora).

Agora você poderá abrir qualquer arquivo listado nos stack traces exibidos no browser (Firefox) além de obter todos os demais benefícios dos Footnotes no final de suas páginas durante o desenvolvimento.

Veja os screenshots para ter uma idéia dos benefícios:

Footnotes Filters

Na imagem acima estamos mostrando a cadeia de filtros (Filter chain) do controller atual, mas podemos facilmente abrir o arquivo do controller, view, layout, estilos, javascripts direto no Gedit apenas clicando em um link, e, podemos também ver os Selects executados no banco de dados, log, Informações do ambiente, logs, routes e muito mais.

Footnotes Stack Trace

Na imagem acima estamos vendo um stack trace, então ao clicar em um dos links criados pelo plugin Footnotes, o Gedit já abre tal arquivo com o cursor posicionado corretamente sobre a linha onde o erro ocorreu.

Você pode fazer o download do plugin com suporte para linux aqui (Github master tree)

Para obter instruções sobre o processo de instalação, veja o arquivo README que está no pacote do plugin ou acesse a Página do projeto no Github.

Você pode também ler mais sobre este plugin no meu primeiro post sobre ele, e ainda assistir a um pequeno screencast mostrando sua funcionalidade.

Read Full Post »

(Ver este artigo em português)

I have just fixed some issues on Rails Footnotes plugin, and now we have full support for Ubuntu linux (this should work with other distros too, but only Gedit and Gnome are supported for now.

Now you can open any files listed on stack trace, and get all bennefits of Footnotes just bellow your pages during development.

Se the screenshots to get an Idea of beneffits:

Footnotes Filters

In image above we are showing the Filters chain of current controller, but we can easily, open the controller, view, layout, styles or javascripts files in Gedit by just one click in the link, and we can also see the database queries performed, log, Environment, Routes and much more.

Footnotes Stack Trace

In the image above we are seeing a stack trace, then we clicked on  a link created by Footnotes plugin, and Gedit just opened that file and switched the cursor to the correct line.

You can download the  plugin with linux support directly from here (Github master tree)

To get instructions about installation process point to README file on package or go to Footnotes Project Page on Github

You can also read more about this plugin on my first post about it (In Portuguese), and also watch a little screencast showing the plugin in action.

Read Full Post »

Some months ago since I started using jEdit I also started improving the gtksouceview language definition for ruby and Rails code for use with Gedit, because in most of cases Gedit is faster than jEdit, Now I have some improvements to show.
I used as base for show improvements some screenshots that I made from Railscasts, so I got some episodes that have the “little things” I’ve changed.
This first is a screnshot of Railscasts Episode 33, here we can see the function name properly highlighted and also some Rails specific methods. We can compare the Gedit Screenshot to TextMate screenshot and see that all:

 

Here we have a rhtml (html.erb) shippet from Episode 37, all tags are highighted properly, including xml markup and erb markup “<%= %>”:

In this (Episode 62) we have a classmethod correctly highlighed (here I prefered to let “self” keyword in the same color of methodname, but is possible to change in future), and the method definitions including method names ending with ?, ! (= signal in the first screenshot):

And last an example of string interpolation (Episode 69), that already exists in original language definition but doesn’t work(I don’t know exactly why), the approach of original attemp is to change the context of string back to main context, by this way the code “should” be highlighted as normal ruby code, and in theory could be other interopated strings in many levels, but, that doesn’t work and I changed to just colorize (I mean this should be the default and correct way) and interpolation is highlighted properly:

 

You can download a package I made, containing some useful plugins, code snippets and
the language definition. this pack is very useful also if you just installed linux (I use ubuntu) and need quick setup to a Rails development environment

The package also include Extract partial plugin and a Smart indent plugin

How to install.

download the package here in some place
open a terminal go to the place of download and type

$tar -zxvf [name of downloaded tarball]
$./install.sh

WARNING: Some commands need sudo password, so you will be asked.

Open gedit chose your preferred color, enable your preferred plugins and enjoy.
(The package also include the TODO-List plugin and you will need to follow plugin README to install)

Gmate Project Page

Read Full Post »