Matt,
Thanks much!!!!
All the dryml is now in logical locations and being interpreted correctly.
I have started to use a technique that I used with my original RoR
implementation of this site. I modified the rails code generators to
include the equivalent of:
<% if RAILS_ENV == 'development' %> <p class="dryml_file">"#{__FILE__},
#{__LINE__}"</p> <% end %>
at the end of each html.erb file. (I had so many that I had trouble
keeping track of them), Now I manually add this to appropriate places
in application.dryml and any dryml files I create myself. If it doesn't
show up, I have to suspect one of the rapid files, otherwise I know
where to look to update the appropriate dryml. It would really help if
this link could be (optionally) generated automagically, especially in
the rapid files which keep getting overwritten.
Paperclip made the upload implementation almost instantaneous (had to
change some of the recipe commands to match Rails 1.3), and made a lot
of my old code obsolete (a good thing TM). It took a long time to hunt
down where the data were being saved - my original assumption was that
it went into a db column somewhere :-[ - then how to download the data.
My app needs the users to be able to view the data in separate tabs -
which is the default behavior of send_data - but I couldn't figure out
how to get <a href=...> to do that. I am now using <nav-item-external>
which works as needed, but puts a little extra dot before the link :-D .
One big question, will storing the data in /pubic/system... (per
paperclip) work if I eventually host this on Heroku? If not, is there
any way of putting the data into a db column as in my first assumption
rather than s3 which seems to be the only other option with paperclip?
Thanks again,
Don Z
On 1/3/2011 5:09 PM, Matt Jones wrote:
<extend tag="form" for="Announcement">
<old-form merge multipart>
<field-list: fields="title, description, audio" />
</old-form>
</extend>
<def tag="input" for="Paperclip::Attachment">
<%= file_field_tag param_name_for_this, attributes %>
</def>
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hobousers?hl=en.
