Lastly, and this time I mean it... I agree conceptually with the open source paradigm. But software has a way of migrating pretty easily into the torrent-o-sphere regardless of the intent of the original owner. I dunno, I have to think about that one...
I am a radical pragmatist and open source is not really working for Moodle. It just bumps along the bottom even though the installed base is now really large. So how to fix that? (Like it or not, it would probably involve somebody making money but the open source model prevents that.) I agree totally on the need for good client relationship management. If the TW apps I'm envisioning were for one off problems I'd buy into the service-centric consulting model fully. But with training, it could be a matter of swapping content in and out of a TW architecture. Yeah, Xavier's idea of licensing the template may be a good solution. The VBA open source analogy was not clear. I guess I meant something like using built-in functions or open source functions I download from the web are analogous to TW plugins. I.e., somebody else's work. I don't feel constrained to compile because of that. Steve On Jan 10, 11:40 am, FND <[email protected]> wrote: > > you guys are demonizing me for what appears to be a pretty legitimate > > question and line of inquiry. > > I think there's a misunderstanding here; yours is indeed a legitimate > question, and we're really not trying to demonize or attack you in any way. > > Since your original idea of hiding the source code turns out to be > largely infeasible (as explained in our original posts), we're offering > alternative perspectives that might enable you to go through with your > plan to create a TiddlyWiki-based application. > > So we're not being fanatical, trying to force you to open-source your > work - it merely seems that it's impossible to entirely hide the code in > the environment TiddlyWiki works in. > In fact, TiddlyWiki's using the BSD license precisely because it allows > a large degree of freedom and flexibility in terms of modifying and > redistributing the code* - that includes reuse for commercial purposes. > > Nevertheless, I apologize if that came across as offensive. > > > VBA is essentially "open source" in that it's bundled into Excel. > > I'm afraid that's not what open source means. > > -- F. > > *http://www.tiddlywiki.org/wiki/TiddlyWiki_License --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
