issue 5
(Can't get tooltip to work) commented on by capalini.richard
-
the same problem here..
firebug:
$ is not defined
$('tooltip_link_26').observe('mouseover'...{hideTooltip(event, $('tooltip_26'))});\n
new# (row 39)
I dont know JS.
Widgets seems realy useful. Thanks for help.
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090805 Sabayon
Firefox/3.5.1
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.5
Rack version 1.0
Rails version 2.3.4
Active Record version 2.3.4
Active Resource version 2.3.4
Action Mailer version 2.3.4
Active Support version 2.3.4
Environment development
Database adapter mysql
the same problem here..
firebug:
$ is not defined
$('tooltip_link_26').observe('mouseover'...{hideTooltip(event, $('tooltip_26'))});\n
new# (row 39)
I dont know JS.
Widgets seems realy useful. Thanks for help.
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090805 Sabayon
Firefox/3.5.1
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.5
Rack version 1.0
Rails version 2.3.4
Active Record version 2.3.4
Active Resource version 2.3.4
Action Mailer version 2.3.4
Active Support version 2.3.4
Environment development
Database adapter mysql
Feb 17, 2009
issue 9
(Rails 2.2 warn about binding argument of concat) reported by vicente.mundim
- When using rails-widgets plugin in a Rails 2.2 application, it complains
that the binding argument of concat is no longer necessary. I've searched
the code and have found two places where the concat method is used.
The first one is in lib/widgets/tabnav_helper.rb, and the second is in
lib/widgets/navigation_helper.rb
I was able to fix it by changing the method "out" to something like this:
def out(string); Rails::VERSION::STRING < "2.2" ? concat(string, @_binding)
: concat(string); end
This way it still works in Rails 2.1 (and older) and Rails 2.2 (and newer).
When using rails-widgets plugin in a Rails 2.2 application, it complains
that the binding argument of concat is no longer necessary. I've searched
the code and have found two places where the concat method is used.
The first one is in lib/widgets/tabnav_helper.rb, and the second is in
lib/widgets/navigation_helper.rb
I was able to fix it by changing the method "out" to something like this:
def out(string); Rails::VERSION::STRING < "2.2" ? concat(string, @_binding)
: concat(string); end
This way it still works in Rails 2.1 (and older) and Rails 2.2 (and newer).
issue 1
(Please provide documentation) commented on by paolo.dona
- Guys, I know there's a lack of documentation on this. I have no time right now to do
do it. The project is on github as well (http://github.com/paolodona/rails-widgets).
Feel free to fork it, document it someway (rdoc?) and I'll pull your changes.
Guys, I know there's a lack of documentation on this. I have no time right now to do
do it. The project is on github as well (http://github.com/paolodona/rails-widgets).
Feel free to fork it, document it someway (rdoc?) and I'll pull your changes.
Sep 26, 2008
issue 1
(Please provide documentation) commented on by primary0
- haha. the developers don't actually want anyone to figure out how to use this :P
haha. the developers don't actually want anyone to figure out how to use this :P
Aug 22, 2008
issue 7
(Provide Multiple highligh urls) reported by mathias.joachim.fiedler
- Allow navigation links to be highlighted for mutiple sub pages.
Example: When having a "Buy" navigation point it should be highlighted
during whole buy-process which contains of the two pages /checkout/payment
and /checkout/confirm.
Solution:
in "NavigationItem.initialize" add the lines:
cust_highlights = opts[:highlights]
if !cust_highlights.nil? && cust_highlights.is_a?(Array)
for highlight in cust_highlights
self.highlights << highlight
end
end
In the remplates you can then create additional highlights like this:
add_item :name => 'Buy',
:link => {:action => 'payment', :controller => "checkout"},
:highlights => Array[{:action => "confirm", :controller =>
"checkout"}]
Allow navigation links to be highlighted for mutiple sub pages.
Example: When having a "Buy" navigation point it should be highlighted
during whole buy-process which contains of the two pages /checkout/payment
and /checkout/confirm.
Solution:
in "NavigationItem.initialize" add the lines:
cust_highlights = opts[:highlights]
if !cust_highlights.nil? && cust_highlights.is_a?(Array)
for highlight in cust_highlights
self.highlights << highlight
end
end
In the remplates you can then create additional highlights like this:
add_item :name => 'Buy',
:link => {:action => 'payment', :controller => "checkout"},
:highlights => Array[{:action => "confirm", :controller =>
"checkout"}]