com/plugins/show/333
Install: svn://rubyforge.org//var/svn/dhtmlcalendar/dhtml_calendar
Bundled Resource
Info: http://agilewebdevelopment.com/plugins/show/166
Install: svn://syncid.textdriven.com/svn/opensource/bundled_resource/trunk
DatebocksEngine
Info: http://agilewebdevelopment.com/plugins/show/356
Install: http://svn.toolbocks.com/plugins/datebocks_engine/
datepicker_engine
Info: http://agilewebdevelopment.com/plugins/show/409
Install: http://svn.mamatux.dk/rails-engines/datepicker_engine
One of these could then be installed with, for example, rapt install datepicker_engine.
Piston
In Rails, plugins are perhaps the most common use of code supplied by an external
vendor (other than the Rails framework itself). This requires some special care where
version control is concerned. Managing Rails plugins as Subversion externals has several
disadvantages:
??? The remote server must be contacted on each update to determine whether anything
has changed. This can incur quite a performance penalty if the project has
many externals. In addition, it adds an unneeded dependency; problems can
ensue if the remote server is down.
??? The project is generally at the mercy of code changes that happen at the remote
branch; there is no easy way to cherry-pick or block changes that happen
remotely. The only flexibility Subversion affords is the ability to lock to a certain
remote revision.
Pages:
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131