Loading ...
Sorry, an error occurred while loading the content.

Re: Deprecating mvim.app. WAS: What's the rationale behind not using a normal PATH?

Expand Messages
  • Matt Tolton
    Perhaps it might be fruitful to shoot an email to the author of said not-so-free app and ask for permission? On Thu, Nov 13, 2008 at 8:31 PM, Ben Schmidt ...
    Message 1 of 39 , Nov 13, 2008
    • 0 Attachment
      Perhaps it might be fruitful to shoot an email to the author of said
      not-so-free app and ask for permission?

      On Thu, Nov 13, 2008 at 8:31 PM, Ben Schmidt
      <mail_ben_schmidt@...> wrote:
      >
      >>> I probably don't have much of a legal mind, but...it would seem odd
      >>> to me if a list of file extensions could really be copyrighted.
      >>
      >> It still was a significant amount of work that someone else did that I
      >> totally stole. It would have taken me a long time to:
      >>
      >> a) Come up with that list
      >>
      >> b) Convert it to the pref format that OS X needs
      >
      > IANAL. I'm also in Australia, and have no idea under what legal
      > jurisdiction MacVim falls, or the aforementioned not-so-free app, or
      > whether it really matters. But...I do know, or think I know, that
      >
      > - The amount of work put into it is irrelevant.
      > - Nonetheless copyright may well subsist in the 'compilation' of those
      > associations, i.e. the selection and arrangement of them (so, yes the
      > 'coming up with the list' part does make it copyright; not because it
      > was a lot of work, but because it was essentially creative work).
      > - Copyright wouldn't subsist in the individual associations themselves,
      > which is the kinda obvious thing: just because one person associates a
      > filetype to an app doesn't mean nobody else can do the same!
      >
      > So, yeah, I believe basically you can come up with your own list which
      > incidentally will have similar associations to a lot of other people's
      > lists, but you can't just rip someone else's list unless it has a
      > compatible license.
      >
      > Ben.
      >
      >
      >
      >
      > >
      >

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_mac" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    • Steven Michalske
      That is fantastic. Steve ... --~--~---------~--~----~------------~-------~--~----~ You received this message from the vim_mac maillist. For more information,
      Message 39 of 39 , Nov 26, 2008
      • 0 Attachment
        That is fantastic.

        Steve

        On Nov 24, 2008, at 7:42 PM, Nico Weber wrote:

        >
        > Hi Steve,
        >
        > On 24.11.2008, at 16:56, Steven Michalske wrote:
        >
        >> mkdir PNGS
        >> for SIZE in 16 32 64 128 256 512
        >> if [ -e FILENAME_$SIZE ]; then
        >> inkscape -C --export-png=PNGS/$FILENAME_$SIZE -w $SIZE -h $SIZE $
        >> (FILENAME)_$SIZE
        >> fi
        >>
        >> IconComposer -> icns
        >>
        >> most of this is manual with some simple bash scripts to sort folders
        >> to simplify drag and drop
        >>
        >> Thanks for pointing out the tiff2icns, how does the alpha channel
        >> work?
        >
        > tiff2icns does not handle 512x512 icons, and using it is a bit
        > complicated: You have to put all tiff icons into one file (with
        > `tiffutil -cat`). Because of that, I have written makeicns ( http://amnoid.de/icns/makeicns.html
        > ), which you can use to convert all your pngs to icns files like
        > this:
        >
        > makeicns -512 FILENAME_512 -256 FILENAME_256 -128 FILENAME_128
        > -32 FILENAME_32 -16 FILENAME_16 -out shinyicon.icns
        >
        > Both makeicns and tiff2icns use the alpha channel of the source
        > images.
        >
        > HTH,
        > Nico
        >
        > >


        --~--~---------~--~----~------------~-------~--~----~
        You received this message from the "vim_mac" maillist.
        For more information, visit http://www.vim.org/maillist.php
        -~----------~----~----~----~------~----~------~--~---
      Your message has been successfully submitted and would be delivered to recipients shortly.