To Both, Thanks for your replies. I understand what you are saying. You look at TW as a labor of love. And I really appreciate the great work that Jeremy and all of the plug-in developers have done.
My take on it is more pragmatic. Apps get developed when there's money in it. It seems like a tension exists in the open-source community because "profit" is made to be a bad thing. But it's your ball of wax so I sincerely respect your opinion. Here's what I'm getting at specifically. I have targeted a training app for a specific domain. I think I can TW their training modules. The value to the customer would be a visually and navigationally superior product (relative to PowerPoint). So my customer would sell that value prop to their customers. I would sell them TW design services for each course they produce. Easy enough. However if I give them a TW course with everything exposed, I essentially give them a template that they could run with or farm out to another consultant. So they could use me - only once. I'd stand a big risk of losing downstream development with that scenario. Given that risk, I would not do the first one at all. There's a general philosophical issue embedded here. I looked at Moodle early last year and was really impressed with the product. There are maybe 500 plugins. Probably more than half are dead altogether and another 20% have to be cleaned up. So that plugin library contains perhaps 400 orphans because there is no incentive ($) for developers to repair/upgrade what are fundamentally good ideas. So Moodle is free, but in many respects dysfunctional because of it. That's open source. Great ideas with no incentive for discipline so products remain in the sandbox. Comments? Steve On Jan 10, 9:20 am, "Daniel Baird" <[email protected]> wrote: > On Sun, Jan 11, 2009 at 12:01 AM, SteveM <[email protected]> wrote: > > > I've been playing around with TW and I have some ideas for niche > > applications. However I need to learn js to tie pieces together. > > Given my relative naivete with html/js, my question is how to protect > > the content? Can an app or app functions of a TW be compiled? Are > > there other ways to encrypt html/js source code? If there aren't, > > then I suppose I won't try. > > > Any advice or references would be appreciated. > > As I understand it, you can obfuscate your JavaScript but not really encrypt. > > I guess you could do the important parts of your algorithms on a > server somewhere and just supply the results, but that would break the > single-file, go-anywhere nature of TW, which seems to impede adoption. > > Who are you protecting your code from? Are you planning on selling your work? > > ;Daniel > > -- > Daniel Baird > I've tried going to the XHTML <bar /> a few times, but it's always closed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
