Interesting debate. Without getting into the merits of open source debate I'd like to point out that TiddlyWiki is licensed under a BSD license, not a GPL license specifically to allow users to do whatever they like with it, including to include in other things and make a profit. Note however plugins licenses vary from author to author so these need to be checked before inclusion in a commercial product.
Back to SteveM's original question - "Is it possible to protect the content?" The answer is yes, but I'm not sure about how strong the protection is. For source code you can pack and compress the javascript. I imagine there are unpackers in existence, however the unpacked code will not be as readable as the original since variable names etc will be shorted. You get some protection, but probably less protection than a compiler will give you in other languages (there are compilers and also quite sophisticated reverse engineering tools for other languages). You can also make some of your algorithms data driven and protect these by encrypting the data. There are encryption plugins available for TiddlyWiki. However you then have the problem of key management - you'll have to give your users the encryption key, which they will then be able to pass on to someone else. However one would assume it would be cheaper for them to employ you than to pay someone else to reverse engineer your work and then do any extra work. Martin On 11 Jan, 00:53, SteveM <[email protected]> wrote: > A- > > You think like me which is both a blessing and a curse. (Dilettantism > is a gift or a disorder depending on how much money you have). > > e-me if you want to dialog (sbmack7_at_comcast.net). Would love to > trade ideas. > > Steve > > P.S. Thanks for the input. It's great. > > On Jan 10, 6:21 pm, "Alex Hough" <[email protected]> wrote: > > > SteveM. > > > Re: "you increase exposure to risk in not taking a risk so it might > > be worth taking the risk" - It could well be a Abbot and Costello > > line, but the Mr Adams who gives the law in question it name is Denis > > Adams, an ex-stats academic and cybernetics enthusiast. Apparently it > > is systemic (and statistically verifiable) fact that not taking risk > > is risk itself... something about the illusion of thinking you are not > > taking a risk being born out of lack of a model of the future ... or > > something like that (it makes me feel TagglyTagged just thinking about > > it) > > > I wonder what opportunities will open up when jQuery code are easy > > enough for non software TwFans to use? I've been looking at some them > > in anticipation. Their community is much bigger and documentation is > > better resourced. While I have been spend too much time being > > bewildered by javascript thanks to TW, jQuery makes a lot more sense. > > The code uses accesses css class selectors, so for example, a list of > > check boxes in a form can be converted to a slider by just giving them > > a class and telling the slider to got and do its business with them. > > > > So there's more of an opportunity cost (risk) if I developed > > something in TW but could not capture revenue from it. Because I'd > > have to set aside the quant stuff. > > > Cut and paste some resource from your development budget to > > incorporate some TW action. As an outward looking function, disclosing > > some of your core skills to the TW community (or 'week ties'[1]) will > > result in some new business contacts and some new ideas. The way the > > TW (and jQuery) communities are organized seem to me to be under the > > radar of the organization and innovation literature. The people seems > > so happy! > > > Alex > > > [1]http://en.wikipedia.org/wiki/Mark_Granovetter > > > > I see what you are saying about a TiddlyStyle". I've been thinking > > > about that too. Take for example Monkey Tiddly and Eric's plug-ins > > > for themes, navigation, sliders, etc. Well their mods to the Shadow > > > Tiddlers sometimes crash into each other. But there may be value in a > > > mashup rather than in selecting a single design paradigm. That's the > > > js tweak work that I think may be required to develop a slick end user > > > app. > > > > I'm sure other guys have thought of this already. But I think a new > > > avenue of creative work lies in leveraging the great plug in libraries > > > synergistically. > > > > Or something like that... > > > > Steve > > > > On Jan 10, 2:42 pm, "Alex Hough" <[email protected]> wrote: > > >> SteveM > > > >> It would be interesting to hear about your niche applications. > > > >> Developing one 'TiddlyStyle' might give some insight into some > > >> innovative business practice. > > > >> The Fractal Organization [1] mentions Adams law which states something > > >> to the effect that there you increase exposure to risk in not taking a > > >> risk so it might be worth taking the risk in disclosing your idea(s). > > > >> Alex > > > >> [1]http://tinyurl.com/9wruht > > > -- > > t: 0161 442 2202 > > m: 0781 372 50 17 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
