December 2009 - openSUSE Ruby - openSUSE Mailing Lists

[opensuse-ruby] HelpNeeded: ActiveResource and transitive inheritance
by Josef Reidinger 21 Dec '09

21 Dec '09

Hi, I create own wrapper over ActiveResource and found quite interesting problem which blocking my work. If I create ancestor of ActiveResource::Base then everything works, but when I create ancestor of ancestor then it stop working (exactly it return nil on method which should not return nil, because it is accessor with default and I assign value so it should return assigned value or default but not nil). I attach example code which demonstrate this problem. thanks for help Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp)

3 6

[opensuse-ruby] javascript and static assets
by Duncan Mac-Vicar Prett 20 Dec '09

20 Dec '09

Hi One of the first problems we hit by using the Rails 2.3 engine was the usage of the static files directory. Engines do not support their own public/ directory. This is because rails does not serve it, but the http server directly. This means that even if our engines are under plugins/$foo, the static files like images and _javascript_files_ have to go under the main app public/ braking this structure. As we are a packaged application, where files should not be touched manually, and the application files should be read only and immutable (so the original engines sync task was not an option), we still needed to provide the vendors with the ability to override any file to alter the look and feel. Like for example, dropping a new css file with the same name somewhere to be used instead of the main one. This was achieved by a small hack: # In order to overwrite,exchange images, stylesheets,.... for special vendors there # is the directory "vendor" in the "public" directory. Each file in the public # directory can be exchanged by putting a file with the same path in the vendor # directory. # Please take care that all links in the views have to be defined by the AssetTagHelper like # image_tag, stylesheet_link_tag, javascript_include_tag, ... config.action_controller.asset_host = Proc.new do |source, request| path = "#{config.root_path}/public/vendor#{source}".split("?") if path.length >0 and File.exists?(path[0]) "#{request.protocol}#{request.host_with_port}/vendor" else "" end end The ability for plugins to have their own public directory was solved by using a rack middle-ware, but this only worked in development mode, because in a normal setup, the http server was the first in the rack chain. # look for all existing loaded plugin's public/ directories plugin_assets = init.loaded_plugins.map { |plugin| File.join(plugin.directory, 'public') }.reject { |dir| not (File.directory?(dir) and File.exist?(dir)) } init.configuration.middleware.use YaST::Rack::StaticOverlay, :roots => plugin_assets This problem hits bad on javascript files. Right now if we want to have a separate javascrpt file that decorates/validates/autocompletes a view, it needs to go in the main app public directory. Which means you can have it together with the other files. When packaging it, it can be installed there, but while running in development mode you just want to edit the file and reload. So I am looking for ways to solve this problem. Right now most of the views javascript is just inlined, which is not good. There are even nice plugins like this one: http://blog.media72.net/2008/05/13/javascript-auto-include-rails-plugin/ Which auto includes javascript files based on the name of the view (convention over configuration) so you don't even need to include the files from your views explicitly, but this still requires those files to be in public/ The only idea that is going around my head is actually serving those files from rails, having a kind of asset controller that could look into the filesystem and read the files. For us the performance of the http server is not that critical like it is for a heavy multiuser site. Is the problem understood? (I can try to explain more). Does anyone has experiences or ideas on this? -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org

2 1

[opensuse-ruby] Another presentation which is good to see
by Josef Reidinger 15 Dec '09

15 Dec '09

Hi, I see some videos and find two good which is good to see - both are from Scotland Ruby conference (and added to our learning source http://en.opensuse.org/YaST/Web/Development/TrainingKit/Learning_Ruby_and_R… ) http://scotland-on-rails.s3.amazonaws.com/2A04_DaveThomas-SOR.mp4 http://scotland-on-rails.s3.amazonaws.com/2A08_JoeOBrianJimWeirich-SOR.mp4 (whole list of scotland presentation is there ( I see other three videos, but I think it is not so useful) - http://www.rubyinside.com/scotland-on-rails-presentations-now-online-27-awe… ) The first one is about ruby object model, which describes how objects works in ruby and how you can benefit from it. It is good to see if you still has problem what means '<<' or 'class << self' or other tricks with objects and modules. The second one is about refactoring code and how to avoid common mistakes. It is imaginary dialog and it is quite funny (geek fun :). Good to see especially if you want use too much meta-programming after watching the first video (or how to write more robust test, how to improve bad test covered code etc.) Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org

1 0

[opensuse-ruby] Webyast: ancestor for models in rest-service merged to master
by Josef Reidinger 14 Dec '09

14 Dec '09

Hi, I implement ancestor which have some usable utilities for rest-service models. Reason to have it is in bug http://bugzilla.novell.com/show_bug.cgi?id=543423 . I call it BaseModel and it is inspired by ActiveModel from rails3.0. It is general usability and I think that all models which is not based on database or REST service could benefit from it. ( just inform me, I can help you to use it in your project). Main features is: * callbacks (before_save etc.) * validations ( validates_format_of etc.) * serialization ( to_xml and to_json and also restore it) * mass assignment (load instance from hash, also whitelisting and blacklisting attributes for mass assignment). For details see documentation: http://yast.suse.de:3334/view/webyast/job/webyast-service-head- i586/javadoc/webservice/index.html classes in BaseModel namespace (sorry internal only, as we still doesn't have public place where we synchronize documentation ). Or you can generate it in git by rake doc:app in webservice directory. For example usage see time plugin, which use validations, after_save hook, mass assignment and also serialization ( It is also example of xml limitation as for hash is key used as tags and tags is quite restricted, so time module must transform hash before serialization ). Welcome your comments, suggestions or ideas what could be improved or added ( especially if more then one plugin could benefit from it). Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org

1 0

[opensuse-ruby] ActiveModel
by Josef Reidinger 08 Dec '09

08 Dec '09

Hi, It will be nice if we have some active-record(-resource) like models in rest- service (same methods etc. to easy understand usage by other rails developers). We use as backend DBus. After some investigating I found that there is ActiveModel for rails (also in 2.3.4 and 2.3.5), but marked as experimental. Do you have any experience with it? Also how it should be packaged? As separated gem? thanks Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ruby+help(a)opensuse.org

3 3