similar to: upload problem with mimetypes

Hi All, I am making a DAM (seems to be the hip thing to do these days). It is for the company that I work for. We have some really weird domain rules that have prevented me from just using a simple directory structure file permission system. I have come up with a solution but I wanted to run it by you gurus to ensure that I am not recompiling the wheel here. Basically the domain rule is: A user

Hi is there a better way to accomplish this task? class PortfolioController < ProjectController layout ''portfolio'' def boing redirect_to :action=>:index end alias_method :new , :boing alias_method :destroy , :boing alias_method :edit , :boing alias_method :update , :boing end My portfolio controller implements view only

I have a mysql database that I am trying to use migrations on. The problem that I am having is that when I create a blob field in my migration file like so: t.column "data", :binary, :limit => 15.megabytes, :null => false rails changes it to this in the schema: t.column "data", :binary, :default => "", :null => false not only is this not what I wanted

Am i a total idiot to try and parse out a rails object for javascript in this way? <% for i in interface_items[0].attributes %> var <%= i[0] %> = "<%=h( i[1] )%>" <% end %> Am I missing something really obvious? Thanks, Mark -- -------------------------------------------------------------------- I am Mark Daggett and I approve this message.

Hi I know there is no real requirements tag but I was unsure what to label this message, please don''t flame me :-). I am using the Javascript Integration Kit with Macromedia Flash to make a local connection to the rendered Rails view. I am then using Flash to render my page components (sort of like you do with Lazlo or Flex etc.) though Javascript acts as a proxy for me. Ideally I would

>> Just one small question, 10.3: "In particular, .ogg is used for Ogg >> files that contain only a Vorbis bitstream, while .spx is used for Ogg >> files that contain only a Speex bitstream." >> >> Should that be a "Vorbis I" bitstream, or is it intentionally left open? > > Technically it is a Vorbis I bitstream, but I think we should leave

On Thu, Aug 14, 2008 at 9:14 PM, Silvia Pfeiffer wrote: > The IETF has a final draft of our RFC at > ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes > from 3534 to 5334 - funny!). Didn't we decide YUV4MPEG should be 8 octets as well? -r

Excellent, thanks for noticing - will add that. Also: question about the Dirac codec identifier in Ogg. It is currently char[5]: 'BBCD\0' - but in your spec it is char[4]: 'BBCD'. Which one should we put in? Cheers, Silvia. On Sat, Aug 16, 2008 at 5:31 PM, David Flynn <davidf+nntp at woaf.net> wrote: > On 2008-08-16, Ralph Giles <giles at xiph.org> wrote:

On Sat, Aug 16, 2008 at 12:23 AM, Silvia Pfeiffer wrote: > Have we got a spec? If not, we may want to remove it altogether and > make the fixes in our wiki as the spec develops. We have a draft spec with no implementation. I can't imagine the magic changing, so I think it's ok to leave it in, but I'm ok to remove it if you think that's best. I do think there's little

On 8/17/08, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > OK, then yuv4mpeg will have the magic number: char[8]: 'YUV4MPEG'. Which was previously for those not paying attention char[9]: 'YUV4MPEG2'. > Also, can you put the link to the spec into > http://wiki.xiph.org/index.php/MIMETypesCodecs ? AFAIK, that is just a matter of putting a [[OggUVS]] in

On 17-Aug-08, at 1:11 AM, Silvia Pfeiffer wrote: > OK, then yuv4mpeg will have the magic number: char[8]: 'YUV4MPEG'. > Is that ok? Yes, I'm good with that. > Also, can you put the link to the spec into > http://wiki.xiph.org/index.php/MIMETypesCodecs ? Thanks! Sorry, I thought I'd dumped the spec into the wiki. It's there now, and linked from the

2008/8/18 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: > On Mon, Aug 18, 2008 at 9:59 PM, Ian Malone <ibmalone at gmail.com> wrote: >> 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >>> On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com >>> <ogg.k.ogg.k at googlemail.com> wrote: >>>>>> Just one small

just found http://www.ietf.org/rfc/rfc4281 and it looks like a good way to indicate which content ogg streams have, to my understanding one would use things like these: Content-Type: application/ogg; codecs="theora, vorbis" Content-Type: application/ogg; codecs="theora, speex" Content-Type: application/ogg; codecs="vorbis" what would be a good place to

Hi all, The IETF has a final draft of our RFC at ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes from 3534 to 5334 - funny!). If you have anything in need of change, speak up now. I have one question in particular: Ogg.k.ogg.k: is the kate codec parameter now down to 8 bytes? If so, it's ok, since I've already made that change. Cheers, Silvia.

On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: >>> Just one small question, 10.3: "In particular, .ogg is used for Ogg >>> files that contain only a Vorbis bitstream, while .spx is used for Ogg >>> files that contain only a Speex bitstream." >>> >>> Should that be a "Vorbis

On Fri, Aug 15, 2008 at 8:42 PM, Ian Malone <ibmalone at gmail.com> wrote: > 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> Hi all, >> >> The IETF has a final draft of our RFC at >> ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes >> from 3534 to 5334 - funny!). >> >> If you have anything in need of change,

On Mon, Aug 18, 2008 at 9:59 PM, Ian Malone <ibmalone at gmail.com> wrote: > 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> On Fri, Aug 15, 2008 at 9:03 PM, ogg.k.ogg.k at googlemail.com >> <ogg.k.ogg.k at googlemail.com> wrote: >>>>> Just one small question, 10.3: "In particular, .ogg is used for Ogg >>>>> files

Hi there, I have a file upload form on my page that is for images. In the model I have this: def file_data=(file_data) @file_data = file_data write_attribute ''extension'', file_data.original_filename.split(''.'').last.downcase write_attribute("content_type", file_data.content_type) write_attribute("current_name",

Hi there, I''m writing a little application that parses an image file and extracts the camera settings from the file (the EXIF data) and saves all the fields to the database. The idea is that after awhile people will be able to search based on camera make, model, lens settings, etc... and all the pictures that meet those requirements will be displayed. The picture is stored on the file

I created an integrations test that attempted to uploade a file as follows: def uploaded_file(path, content_type="application/octet-stream", filename=nil) filename ||= File.basename(path) t = Tempfile.new(filename) FileUtils.copy_file(path, t.path) (class << t; self; end;).class_eval do alias local_path path define_method(:original_filename) {