What should we call the CLI tool? - Printable Version +- CodeIgniter Forums (https://forum.codeigniter.com) +-- Forum: CodeIgniter 4 (https://forum.codeigniter.com/forumdisplay.php?fid=28) +--- Forum: CodeIgniter 4 Development (https://forum.codeigniter.com/forumdisplay.php?fid=27) +--- Thread: What should we call the CLI tool? (/showthread.php?tid=68724) |
RE: What should we call the CLI tool? - kilishan - 08-17-2017 (08-17-2017, 07:41 AM)Paradinight Wrote: https://spark.apache.org/trademarks.html Well, dang. I've emailed them to verify if it would violate their trademark since the actual product name is CodeIgniter, but I wouldn't be surprised if they do have issues with it. Their "derived phrases" requirement is pretty strict, though. That means we couldn't make a "Sparkly Unicorn" framework. Bummer. (08-17-2017, 07:41 AM)Paradinight Wrote: @sv3tli0 They're not quite the same argument The main point being that it makes it a little nicer to type when you use it frequently. It's not a deal breaker either way but I can see it being a nice touch, since I do get slightly annoyed by having to type the extension every time. RE: What should we call the CLI tool? - Paradinight - 08-17-2017 (08-17-2017, 07:54 AM)kilishan Wrote:(08-17-2017, 07:41 AM)Paradinight Wrote: https://spark.apache.org/trademarks.html you can use tab on the command line to autocomplete RE: What should we call the CLI tool? - orionstar - 08-17-2017 (08-17-2017, 08:10 AM)Paradinight Wrote: you can use tab on the command line to autocomplete Not on commandline of Windows RE: What should we call the CLI tool? - jarmen_kell - 08-17-2017 (08-17-2017, 07:54 AM)kilishan Wrote:(08-17-2017, 07:41 AM)Paradinight Wrote: https://spark.apache.org/trademarks.html damn. that's a shame. and ridiculous. "spark" is a common noun. just like laravel's "artisan" or symfony's "Console". even 'vulcan' is trademarked to Paul Allen. how could they've trademarked this? similar to the case involving the developer of infamous "candy crush". might as well use this just for a wouldn't-be-a-future-trouble name: https://www.uspto.gov/trademarks-application-process/search-trademark-database https://trademark-search.marcaria.com/en what a great effort's just to find a name. LOL... LOL... LOL RE: What should we call the CLI tool? - jarmen_kell - 08-17-2017 anyways.... how bout "lit".... since the name "Codeigniter" derived from something that have fire in it. so let's "lit" it... Lol RE: What should we call the CLI tool? - Paradinight - 08-17-2017 (08-17-2017, 08:23 AM)orionstar Wrote:(08-17-2017, 08:10 AM)Paradinight Wrote: you can use tab on the command line to autocomplete you can tab too. RE: What should we call the CLI tool? - orionstar - 08-17-2017 (08-17-2017, 08:35 AM)Paradinight Wrote:(08-17-2017, 08:23 AM)orionstar Wrote:(08-17-2017, 08:10 AM)Paradinight Wrote: you can use tab on the command line to autocomplete Yes you can tab, but it only looks in the current dir for files/dirs... RE: What should we call the CLI tool? - turecky - 08-18-2017 My suggestion on CLI name: wekker RE: What should we call the CLI tool? - sv3tli0 - 08-19-2017 I don't think that 1 file name will have problems because of some registered trademarks.. It's not a product or a project, it's just a single file.. With sparks don't forget that Laravel added such project > spark.laravel.com . RE: What should we call the CLI tool? - dave friend - 08-19-2017 CodeIgniter Command Line - CICL |