6652
I think, you have an older version. Download the MyTabs 2.0 Final, and it should fix your issues.
In the Options, you'll also set the "OnMouseOver" to no, which will allow you to change the tabs only when you click on them.
In the Options, you'll also set the "OnMouseOver" to no, which will allow you to change the tabs only when you click on them.
6653
I don't have Mastop, so I cannot tell you that, but if you have Firefox, install this extension:
http://chrispederick.com/work/web-developer/
and then use the "View Style Information" option to see exactly which CSS element drives the color.
It's an excellent tool.
Speaking of which, our Mambo friends recommend following tools:
Top 5 Font Tools for Web Designers
Top 10 Colour Tools for Web Designers
Top 5 Font Tools for Web Designers
Worth checking them out...
http://chrispederick.com/work/web-developer/
and then use the "View Style Information" option to see exactly which CSS element drives the color.
It's an excellent tool.
Speaking of which, our Mambo friends recommend following tools:
Top 5 Font Tools for Web Designers
Top 10 Colour Tools for Web Designers
Top 5 Font Tools for Web Designers
Worth checking them out...
6655
Small follow-up:
It's always good check on Google to make sure that we don't make any mistake.
As you can see from this article on Groklaw (a legal website), there was a case where a developer tried to revoke a GPL license. The response from the legal minds on Groklaw was:
Quote:
Here are couple more links related to this case:
gpl-violations.org
Infowares.com
As stated in another thread, it is our goal to have all XOOPS-related code in our repository, so XOOPS users can use it, or analyze it and learn from it.
However, we are committed to help McNaz to resolve any issues, especially any hardship for him or his company (e.g. people contacting him for support) resulting from having the files in our repository.
It's always good check on Google to make sure that we don't make any mistake.
As you can see from this article on Groklaw (a legal website), there was a case where a developer tried to revoke a GPL license. The response from the legal minds on Groklaw was:
Quote:
I know by now you've seen the notice by the guy claiming to "revoke" the GPL license on his code, because I'm getting email about it.
Here's the answer to your question: Quote:No. One can't retroactively revoke licenses previously granted, unless the license terms allow you to do so. The most you can do is stop granting new licenses.
Yes, I verified this with an attorney. Here's the GPL v2. See any terms allowing you to revoke? Me neither. You can find a lot of resources to help you understand the GPL on Groklaw's permanent GPL resources page. I'm doing my part, and I hope the guy does his by studying it.
If you change your mind and don't want to use the GPL any more, you can stop and use something else on new code going forward, and you can dual license your own code, but you can't redo the past and pull back GPL'd code. That's one of the beauties of the GPL, actually, that even if some individual gets a bug up his nose, or dies and his copyright is inherited by his wife who doesn't care about the GPL and wants to take it proprietary, or just to imagine for a moment, a Megacorp were to buy off a GPL programmer and get him to pretend to revoke the GPL with threats, and even if it were to initiate a SCO-like bogo-lawsuit (based perhaps on a theory under Copyright Law § 203, termination of rights -- lordy do we have to endure a living demo in some courtroom somewhere of every antiGPL theory found on every message board before they give up?), it doesn't matter ultimately, I don't think, as to what you can and can't do with the GPL. The GPL is what it is. Please don't use it if you don't like the terms.
Here are couple more links related to this case:
gpl-violations.org
Infowares.com
As stated in another thread, it is our goal to have all XOOPS-related code in our repository, so XOOPS users can use it, or analyze it and learn from it.
However, we are committed to help McNaz to resolve any issues, especially any hardship for him or his company (e.g. people contacting him for support) resulting from having the files in our repository.
6656
Quote:
Ron, let Marcan (i.e. SmartFactory) speak for himself and show that it was him who decided to move away from XOOPS.
Perhaps it was XOOPS moving away from SmartFactory like they did from GIJOE. It just depends on how you look at it.
Ron, let Marcan (i.e. SmartFactory) speak for himself and show that it was him who decided to move away from XOOPS.
6658
McNaz,
I'm afraid, we have a misunderstanding about the GPL License, under which you've released your programs. The GPL states clearly:
Quote:
Since the license explicitly forbids you to ask us to surrender the rights to distribution, it's clear that you cannot ask us for that, as it would violate the license.
Quote:
I can understand that you might not want to have your email in the source code in order to avoid any support calls, and if you desire to remove it (together with other identifiers, like URL or name of the company), then of course we can do that for you.
Another option is that you can reassign the Copyright to somebody else (e.g. XOOPS), and then permanently remove yourself from the source code going forward.
Let us know, how would you like to proceed, and as long as the GPL license allows us to do so, we'll be glad to do it...
I'm afraid, we have a misunderstanding about the GPL License, under which you've released your programs. The GPL states clearly:
Quote:
Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights.
Since the license explicitly forbids you to ask us to surrender the rights to distribution, it's clear that you cannot ask us for that, as it would violate the license.
Quote:
the inclusion of these modules on Xoops' download repository is generating unwelcome support issues for both my self and my company
I can understand that you might not want to have your email in the source code in order to avoid any support calls, and if you desire to remove it (together with other identifiers, like URL or name of the company), then of course we can do that for you.
Another option is that you can reassign the Copyright to somebody else (e.g. XOOPS), and then permanently remove yourself from the source code going forward.
Let us know, how would you like to proceed, and as long as the GPL license allows us to do so, we'll be glad to do it...
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|