Like mentioned earlier, selling the "Missing manual for tiddlywiki" on iOS will help to 1. Show what can be done with Tiddlywiki. 2. show how to make interactive multimedia apps with Tiddlypip 3. It will help the developers earn money. I will gladly buy it using an iTunes card. 4. It will help us educate others and spread the word about this project.
So 100% support for Tiddlywiki project / Tiddlypip. --- Rainbow പൂട്ടാത്ത കാറ് On Wednesday, August 26, 2015 at 1:08:25 PM UTC+4, RichardWilliamSmith wrote: > > Your app would be deployed under iOS in the same way as any other app. > I've never submitted one myself but apple say "There are no hosting fees > and Apple handles all payment processing. You receive 70% of sales > revenue." (https://developer.apple.com/programs/). The process would be > similar to apps built with Phonegap/Cordova. > > You can include your own javascript in tiddlywiki - you just need to do it > by writing macros and plugins - there is already a basic d3.js plugin, for > example, referenced by Jed in this thread - > https://groups.google.com/forum/#!searchin/tiddlywiki/d3.js/tiddlywiki/T7ZDfxOMLmw/kcobbp0KHe8J > > The reason TW can't run arbitrary javascript is twofold - a security issue > and a complexity issue. Tiddlywiki seems quite straightforward on the > surface, but it's actually very complicated (i don't claim to understand it > in detail) and any additional code has to play nicely with it's mechanisms, > which are unique. > > As for support, yes - you'll have to rely on the community and your own > initiative in understanding how TW works - that's because nobody gets paid > to support it or makes any money out of it, although I for one am firmly of > the opinion that Jeremy deserves to get paid for it if there is ever a way > for us to help make that happen. Tiddlypip was initially an idea to achieve > just that by providing a low-cost (but not free) way for people to get apps > built with TW into the app store. If you have a great idea for an app that > you think will make money then you should go for it. > > Regards, > Richard > > On Wednesday, August 26, 2015 at 4:26:08 PM UTC+10, D John wrote: >> >> The question was not a rhetoric. >> >> It was intended to make Tiddlywiki better than Filemaker and vice versa. >> Ecosystems improve only when there is competition. Otherwise they just >> keep advertising and believing they are 'awesomer' than other 'awesomes' in >> other.. Well. Ecosystems.. >> >> Filemaker Webviewer can do anything HTML5/CSS and Javascript (Plain old >> Javascript) can do. That is good for most new developers lured into Apple's >> Ecosystem with promises of shiny interfaces and user experiences. Any >> content created on Filemaker can be used on Filemaker Go for iOS. >> >> All database related processes - indexing, login, validating serial >> numbers, demo expiry, protecting content by encrypting the database are >> either automagic or easily scriptable in Filemaker. ( May be all this is >> much easier in TiddlyWiki. ) For users requiring to add another level of >> protection or separate UI from data or serve media to solutions, content >> can be hosted on FMP servers and served to FMP Go on iOS. But everything >> comes at a price for a product made for a "niche" market or so they say. >> Still it is a pain working on Filemaker because its a closed system. >> Features make it or break at the whim of the company and with versions. >> >> Which pushes the content creator to choose opensource web stacks like >> MEAN or LAMP. Thanks to Cloud, Single page applications are much more >> easier and wallet friendly than Filemaker. >> >> But tiddly on iOS is a greater idea. It is a lot of fun for programmers >> to RTFM and learn a new scripting language subset. >> >> I am not sure about this.. but >> >> From a content creator's perspective, it is a handicap Tiddlywiki cannot >> run Plain old javascript content. May be the Missing manual will >> demonstrate the Tiddly-way of integrating interactive HTML content (d3.js, >> createjs.js...) into Tiddlywiki wikis ? >> >> Would TiddlyWiki on iOS be able to embed multimedia content within apps >> without the need for an external server? >> >> Another trouble with Opensource is the "use as is case". If something >> breaks, the community helps, if they don't, we have to learn it ourselves >> by studying source code? >> >> Also this idea of taking tiddlywiki to iOS to monetize its contents will >> work without additional hidden charges for servers hosting the content? >> Like what XOJO already (http://www.xojo.com) offers? >> >> --- >> Rainbow >> I am a Pathologist, Working on the Dead brains of Rocket Engineers, who >> tried to learn Filemaker and Flash 15 years ago. >> Thanks to Malcom Gladwell, it only took 10 years to figure out that I >> better learn HTML/CSS/Javascript/UNIX/Photoshop/Illustrator/ to do better >> things at work. >> >> >> >> >> >> >> On Tuesday, August 25, 2015 at 6:48:44 PM UTC+4, RichardWilliamSmith >> wrote: >>> >>> I think the idea is for the Tiddlywiki manual to be given away for free. >>> Jeremy seems to think that it will be fairly straightforward to put content >>> in the app store using TW. It should be just as secure from 'pirates' as >>> any other web-stack app ported to the native app format - which is to say >>> that it should be pretty pirate-proof, unless someone really wants a copy, >>> in which case they'll find a way to make one. >>> >>> I'm not sure if your last question is intended to be rhetorical, but it >>> seems that Filemaker and TiddlyWiki do some of the same kinds of things but >>> TiddlyWiki is much more versatile. We can use it to make anything from >>> personal notebooks to mind-mapping tools to websites as well as database >>> UIs. The price of all the control we have over TW is it's relative >>> complexity and the possibility of breaking things horribly by typing the >>> wrong thing, which probably isn't the case with Filemaker, given that it >>> seems to cost hundreds of dollars. >>> >>> Is it currently possible to build your own apps with Filemaker and >>> deploy them to the app store? I found this >>> http://www.fmtouch.com/enterprisepr.pdf which seems to offer deployment >>> as a 3rd party service (which is weird if Apple own Filemaker) on a >>> subscription basis. If you want to encrypt user data, you need to apply for >>> a US 'export licence'. lol. >>> >>> Regards, >>> Richard >>> >>> >>> On Tuesday, August 25, 2015 at 7:35:02 PM UTC+10, 'aint John wrote: >>>> >>>> Hoping to see the "Tiddly Wiki Missing Manual on iOS" to prove the >>>> point that content can be protected from pirates and delivered on iOS as >>>> apps. It will work as a tool for demonstrating and learning Tiddlywiki on >>>> iOS. >>>> >>>> But then, What better can Tiddlywiki ecosystem do than an indexed >>>> database like Filemaker on iOS cannot currently do ? >>>> >>>> >>>> --- >>>> സായിപ്പിനിഷ്ടം മടത്തിലെ തൈര് >>>> >>>> On Friday, January 30, 2015 at 3:59:01 PM UTC+4, Jeremy Ruston wrote: >>>>> >>>>> Do you have an idea for TiddlyWiki content that you think people might >>>>> pay for? >>>>> >>>>> Perhaps a technical manual? Or a guide for your city? Training >>>>> materials for your company's field engineer force? Or maybe a >>>>> manualisation >>>>> of mental health intervention techniques? >>>>> >>>>> Would you be interested in working together to create your multimedia >>>>> TiddlyWiki content and wrap it up as an app that can be distributed and >>>>> sold on the iPhone/iPad app store? >>>>> >>>>> Here's the background for this invitation: I've recently finished my >>>>> work with CTRLio. I'm very grateful to them for the support they've shown >>>>> to my work on TiddlyWiki over the last 18 months. But now I need to find >>>>> new sources of income to replace my salary. There's a few weeks in which >>>>> I >>>>> can consider some radical options, and this is one of them. >>>>> >>>>> I want to explore the idea of building a commercial TiddlyWiki >>>>> ecosystem on top of the Apple platform of iOS, the Mac and iCloud. I'm >>>>> not >>>>> making any moral or philosophical judgement about Apple's place in the >>>>> world. I'm considering this plan just because the App Store is one of the >>>>> places that someone like me may be able to make money. >>>>> >>>>> This first step is simple: we create a framework for building iOS apps >>>>> that provide a terrific, read-only user experience for interacting with >>>>> TiddlyWiki documents. I'd want to support free or paid apps, with the >>>>> possibility of using in-app purchases for premium content. It would be a >>>>> way to deliver a highly custom, interactive user experience around >>>>> multimedia content. We would be able to deliver free updates to the app >>>>> and >>>>> content via the app store update process. >>>>> >>>>> Such a simple application would be the quickest way to get into the >>>>> app store - I believe in just a few weeks. The aim would be for the app >>>>> to >>>>> be invisible without much of a discernible user interface, just providing >>>>> the mechanisms for the content to take centre stage. It certainly >>>>> shouldn't >>>>> resemble the familiar default TiddlyWiki editing interface. >>>>> >>>>> I'm open to suggestions about how to structure this from a business >>>>> perspective. I'd need some upfront payment to fund the development, but >>>>> hopfully we'd find a big enough handful of people that individual shares >>>>> of >>>>> the startup costs would be relatively small. >>>>> >>>>> If enough people can provide the necessary commercial backing we can >>>>> use TiddlyPip to publish Eric's "Inside TiddlyWiki: The Missing Manual". >>>>> >>>>> Beyond simple read-only publishing, there would be a number of >>>>> incremental improvements we could make once we see regular revenue: >>>>> >>>>> # Support read/write functionality like annotations, with iCloud >>>>> syncing between iOS devices. >>>>> >>>>> # Support publishing custom, TiddlyWiki-based applications, such as >>>>> tw5.scholars. It wouldn't appear to be a TiddlyWiki file: it would behave >>>>> like a custom app for scholarly notetaking (including multi-device sync) >>>>> >>>>> # Support quizzes and questionnaires, with content unlocked by >>>>> successfully completing exercises >>>>> >>>>> # Support reporting of progress to the TinCan API >>>>> >>>>> # Support one-on-one student/educator interactions through the app. >>>>> Students might buy an academic textbook along with tokens to ask the >>>>> author >>>>> 5 questions via messaging within the app. >>>>> >>>>> # Create a full end-user application that enables the user to create >>>>> and work with TiddlyWiki documents on iOS devices. This is really the >>>>> ultimate goal from a development perspective. But it's a lot of work to >>>>> create such an app with enough polish to stand out in the app store, and >>>>> I'm not convinced there are enough people prepared to pay for apps like >>>>> TiddlyWiki. But if we can bootstrap things via the content publishing >>>>> route >>>>> then we ought to be able to gain the time to make the app sufficiently >>>>> polished and useful >>>>> >>>>> It's fun thinking about the possibilities. But we need to take this >>>>> journey as a series of small steps, and I need to quickly find out if >>>>> there's any hope of completing the first step. >>>>> >>>>> I need to know if there's anyone out there who might be prepared to >>>>> put some money on the table based on their belief that they have content >>>>> that could viably support this business model. So please let me know if >>>>> you >>>>> fit that description. Ideally, we'd find a handful of people which would >>>>> make it easier to fund the initial development, until the app store >>>>> revenues kick in. >>>>> >>>>> Please let me know if you have any questions or suggestions, >>>>> >>>>> Best wishes >>>>> >>>>> Jeremy >>>>> >>>>> -- >>>>> Jeremy Ruston >>>>> mailto:[email protected] >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ccce7578-6d2d-4bcd-a0ec-3f8f4565b3c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
