Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have some doubts regarding the software licensing model.
Recently, while building a small web application, I used some icons/images from iconfinder.com. I filtered icons based on "Allowed for commercial use(No link required)". Though icons are listed based on the filtering, still I could see that "more details" of those images displays license(s) like - GPL, LGPL, Public Domain, etc.
My doubt is:
Can I use those icons/images for commercial user? Because I filtered icons based on "Allowed for commercial use(No link required)"
My web application is closed source. Do I need to keep the source-code open?
As of now my web application do not have credit link in the footer. Do I need to add a credit link in the footer, in case if I have to link back to the website? Is it possible for me to show the credit in the source-page, instead of adding credit links in footer? Will that conflict with the GPL, LGPL, Public Domain, etc licens.
Why a licensing model is displayed, if the filter is "Allowed for commercial use"?
Any help will be appreciated.
Thanks
I have made the filters as rough filters, which does not represent a single license. Allowed for commercial use simply means it can be used commercially. There might be some requirements such as putting a link to the author's website on the page. Because many developers don't want to put links to a designers page e.g. in an app, I have made a filter that removes those as well. The icons you find with "Allowed for commercial use(No link required)" can be used without linking to the author's website.
I would recommend you read the license for all icons you use from IconFinder.com.
I hope that helps.
Best regards,
Martin LeBlanc
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
My blog currently runs Jekyll and the Minimal Mistakes theme, and uses the theme's built in functionality to add the Disqus comments system.
This JavaScript-based commenting system, to me sort of defeats the purpose of having a static blog in Jekyll, considering:
Its JavaScript creates a decisively non-static page.
Comments are not stored with the website.
Comments are stored in some database instead of flat-text files.
My question is, therefore: What is a suitable system for comments that stays as close to the Jekyll philosophy as possible (an ideally runs on gh-pages)?
I found several possible candidates:
Isso is a comments system which is looks similar to Disqus, it works with a SQLite database
Jekyll::StaticComments seems pretty suitable, but it means you have to manually add the comments from emails.
Are there any other options? If so, what would work with gh-pages, and what would work on a self-hosted Jekyll blog?
Here's another solution which is dynamic and uses JavaScript, but doesn't store the comments at a 3rd party provider:
This guy made a static website with Jekyll, but uses GitHub's issue tracker to create his comments.
He uses GitHub Pages to host his blog, and for each new post, he creates a new issue in his blog's repository.
Then, he uses JavaScript to get the issue's comments from the GitHub API and show it on the page.
Here's a blog post which explains how to set this up:
GitHub hosted comments for GitHub hosted blogs
Whether a javascript loaded, externally hosted comment system "defeats the purpose" of a static site is a matter of opinion.
For me, the point is to be able to host the site as entirely static resources, to take advantage of caching, CDN, distributed hosting, etc. I have seen huge advantages to that, and externally hosting my comments doesn't conflict at all.
That being said, it's an interesting question.
Isso (like Disqus) uses JS on the client side and requires server side software (Python based) that you have to manage, so it doesn't seem like this is any closer to your ideal.
Jekyll::StaticComments is in the right direction, but it's not supported on gh-pages if you have GitHub processing your Jekyll site (you can of course generate the static site yourself and then host it on GitHub Pages).
You also need a way for users to submit comments, and then to get those comments into a file that can be used by the generation process (not necessarily via email as you thought though).
So you need to take comments from somewhere, possibly email, possibly yet another third party hosted app (SimpleForm maybe).
And then you need to manually put them into the YAML site, regenerate, then publish, or, you can set up an automated build process for your site, which can pull the user submitted content when available and build and publish automatically.
Other than manually accepting comments through an off-site medium, you're going to deal with something dynamic somewhere.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
i have an Educational website and i create always pdf files from my learning and ad them for download
but there is many learchers that download my files and reupload them somewhere else
i used google dmca but is there any way to Prevent from re-uploading my files?
One way is to use your .htaccess to prevent hotlinking, but even if you do that, you'll again have the problem that when someone views the document via an in-browser extension (e.g. Adobe Reader, Foxit PDF Reader), they can save it and you've lost control over what they can do with it. Or, depending on how you've set up your site, they can simply directly download it, leaving you again back at square one.
Hence, the solution is to bypass direct access to the document. And, there are a number of ways to do that, which varies based on technique and web software (platform) used.
However, since you didn't mention a particular platform or technology: you can use web controllers (MVC type controllers) to broker the dynamic viewing and displaying of the documents in tandem with a client-side tool / plugin to do the displaying for you (much like Scribd).
However, Scribd uses a proprietary Flash PDF viewer called iPaper, and while it isn't available for use, you can find many other alternatives on the web. One that comes highly recommended (there's even a tag on SO for it) is FlexPaper, an open source plugin that implements a client-side web-based PDF viewer - which I think will suit your needs perfectly (from here):
This project provides a light weight document viewer component
enabling PDF files to be viewed without having any PDF reader software
installed. This project provides both Flex library and stand-alone web
version.
Here are some demos of it in action:
http://flexpaper.devaldi.com/demo/
Sorry, by mistake posted partial comment. Anyway...
Why do you afraid of reuploading of your files ? Put links to original site into the PDF and get profit of this. More copies, more downloads, more popularity for your resource. If you indeed would like to make PDFs available from your site only, you have to hide files from users and provide some functionality to read them from your web site only (you can use existing sites of this type). That makes duplicating of your resources to be harder task, but be ready that many users reject to read it this way.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I will built an applications using Sencha Ext JS.
I tried a little application in order to lean it. But I was wonder what are the difference between the GPL and the commercial license?
I noticed that the code is exactly the same, and the way on programming also.
So what are the advantages to buy the commercial license?
Thank you
The GPL license is for open source applications. If you are creating an open source application and are compatible with the GNU General Public License http://www.gnu.org/copyleft/gpl.html (providing source code etc.) you don't have to buy a commercial license.
If you are releasing an application for commercial purposes and do not plan on sharing the source code... you would have to buy a commercial license. The advantages? Staying legal, rewarding Sencha for their great framework and supporting future updates to the framework to name a few!
NOTE: I am not a Sencha representative and/or lawyer. Contact Sencha http://www.sencha.com/contact/ to find out exactly what is required for your particular situation.
I'M NOT A LAWYER !!!
You can make money if you decide to use the GPL version. However you have to make your application source available moreover any one who is using your app as a library for his application should do too.
If you plan to open source your app then look at this thread: Which license should I use for my open source project
If not then go with the commercial one. Sencha touch provide a good FAQ regarding licensing:
https://www.sencha.com/store/licensing-faq/
Good luck with your choose.
I think this will help: http://www.sencha.com/products/extjs/licensing/
Also i think you require a commercial license if you are going to distribute(sell) your product and wants only you to have the permission to change the source code on the product and customers to only use them, open source license you need if you develop your application for your own purpose and whosever use it do have the permission to make any change in it(source code).
Cheers
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
Let's say I create a CMS that uses ExtJS.
I want to avoid the license fee, so I open-source the CMS on github.
Now let's imagine that I make your friend Dave a website that uses my CMS. I spend three hundred hours designing a logo and layout. Can I charge a fee for this, and would I be obliged to open-source Dave's website too or is it enough to just open-source the CMS?
I find this LPGL license a little confusing. Say hi to Dave for me.
Only ExtJS code prior to 2.1 is under LGPL. It currently uses GPLv3. That means if you distribute it, "the entire work, as a whole" must be licensed under GPLv3. The entire work may include code directly connected to ExJS. But "separate and independent works, which are not by their nature extensions of the covered work" (which probably includes server code) don't have to be GPLv3. So the way I interpret it, only code (e.g. client JS you develop) that tightly extends Ext would have to be released. See also this FAQ.
Regardless, you can charge as much as you want for services and/or the CMS itself.
IANAL.
ExtJS GPL Licence means that if you are using ExtJS under GPL Licence, and not modifying ExtJS itself, then you are Free to use ExtJS in whatever manner on any Website. But if you take ExtJS and start modifying ExtJS itself ( to make some better 'Super-Duper-ExtJS' Library ), then you have to share that with everyone, because if you start selling 'Super-Duper-ExtJS' to your Clients, then whats going to happen is that 'ExtJS-Company' finds itself Competing with Itself. I dont think you need to share your 'Website's Source-code' in any case. If you need to share your 'Websites source-code' ifself with other People while using ExtJS-GPL, then only the ExtJS-GPL Licence would start looking absurd, and you need to start looking at jQueryUI or DOJO ! But I dont think that 'ExtJS-Company' means to share your Websites-source just for the reason that you used their ExtJS Library ! What say .......
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'm re-writing an app that is a data-entry tool. The existing app is in Access and consists of a form with multiple grids, with each grid containing many columns that requires the user to scroll horizontally in order to view columns.
The current grids on the form are layed-out heirarchically in parent-child relationships. Top grid represents projects, grid below that represents the SKUs in the selected project, the grid below that represents season data (pricing, shipping info, etc) for the selected SKU above.
I'm looking for advice regarding good UI design principles for this kind of app. How do I design a form that gives the user the flexibility to see all columns for the data on the form without needing to scroll so much?
What are some good online resources for UI principles for business apps?
Thanks!
What I've found to be a general rule of thumb that helps to develop aesthetically pleasing user interfaces is the notion of only presenting as much as is needed for any given task.
One of the approaches we can take in designing forms is to focus the user's attention to the task or function at hand by centering controls on a horizontal axis.
Culture, too, plays a major role in the acceptance of the programs we write. For instance, in Western culture, we read from left to right and from top to bottom. Therefore, programs targetted for a Western audience should ideally follow that same design principle.
Here's some basic principles that will help
use friendly words and terms over obnoxious and demanding tones:
"The file could not be found at the location 'c:\temp'" as opposed to "A required file could not be found please fix the error."
single color schemes that apply to the overall look and fonts
common control layout on all forms presents
follow the design guidelines generally employed for the platform you are targetting
References
Here is some reference material to help you on your own unique path
(Windows) User Experience Interaction Guidelines
(Apple) User experience guidelines
Windows design principles
(Windows) Some design pointers
To summarize, I've found that overwhelming the user with all the information he/she might ever need to perform a simple data entry is not really an ideal way; rather progressively presenting functionality and the tools to do what they want is, to me, a much better alternative.
As always, place youself in the user's position: "Do I like what I see? Does it make me happy to work with it? Is the program too restricted? How can I make task X much easier to perform?"
usability.gov is a great resource for UI design. Also, check out wufoo.com, which is a form hosting website. Their blog is chock-full of interesting research on usability and form design.
This site may help you out: http://www.jankoatwarpspeed.com/post/2009/02/18/How-to-deal-with-large-webforms.aspx. Big points there being tabs & collapsible regions.
Additionally, if you don't necesarily need to show all of those columns horizontally, you can present them when the user clicks the entry to view more details. I typically prefer to show the critical information, and then require the user to view more details if they need specifics.
As Mike mentioned, "the notion of only presenting as much as is needed for any given task"