Obviously, while TiddlyWiki can be used for many things, it's not suitable for everything. As for calculating and table editing, see Vincent's TWcalc and TWtable (1).
http://twtable.tiddlyspace.com/ w On 19 nov., 17:53, Nicholas Franks <[email protected]> wrote: > Thanks for the information Eric & Whatever. > > After looking over the links, I am not too sure that I could use TiddlyWiki > for the database. My first application was just a simple calculator that > calculated preset prices that the user could tweak. User liked the > "Click-click-click = price" method of calculating. However, a lot of > people wanted a more in-depth application, being able to set their own > items and prices, as well as save the information somehow...pretty much a > POS (point of sale) application. In order to cover the requests from the > users in requirements for exactly "what" they were charging and "how", I > had to develop a manufacturing database with MS Access, since I know > jack-diddly about MS SQL-anything (we didn't get to go over that in school). > > Of course the explanation makes it very generalized and vague as to why I > will most likely be unable to use TiddlyWiki for the needs of the users. > My recent application, Cake Price Calculator 2.0, was designed with the > ability to "Create an Order with Cakes" - "Create a Cake with Layers" - > "Create a Layer with a Pan & Cake/Filling/Icing Recipes"...each of these > have "Extras" that can be added with prices to calculate in such a way to > allow the user to fully control "what" the were charging and "how". Pan > Servings would calculate "price per servings" for the Recipes, other > "Extras" would calculate a flat rates depending on what they were. The > user can have Rental Items...etc, etc, etc... > > So, if you understand that basic description of what the application > currently does, I am building an Order with Items, that must be built with > Components first, all before calculating and assigning a Customer to the > order and setting Delivery information. The downsides of the current > application is Mac users cannot use it, and 64-bit users have architecture > issues with the MS Access database. On top of that there are features that > I have not been able to implement as I require feedback from the users > before I can proceed...since the majority of the users have 64-bit systems, > I have not had too many positive results :( > > I have currently been reading through all the TiddlyWiki documentation with > the mindset of a way to use it for the documentation only for my > application. However, now I'm looking into the interaction of TiddlyWiki, > along with the much appreciated links, as to have I can achieve the same > essential application. That would not only allow Mac users to possibly use > the application, but would also keep me from needing to mess with MS SQL > for the data. > > Sorry for the novel here...I'm pretty much new to developing anything > outside of C# & VB.NET, so this has been somewhat of a new experience > trying to adjust to. While I don't understand how it will all work yet, I > am working on that atleast ;) -- 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.
