practical size limitations?
Dear use-livecode I am beginning work on a learner's dictionary for Norwegian, and am looking into using LiveCode. A few basic questions: 1. I assume it would be best to use a database as a backend to the ultimate dictionary, but I am quite sure that I don't have the skills to set up SQLite or any other database proficiently. (I can learn, I'm sure, however) 2. If I take the easy way out and list each headword and its forms on a separate card, will a large number of cards slow the searching and displaying of items beyond usefulness? 3. Does anyone know of such a language dictionary developed using LiveCode? Thanks for any input and ideas. Louis Janus ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: practical size limitations?
Hi. I don't think you need an external database. Unlike Hypercard, LC does not handle tens of thousands of cards quickly. But it can easily and instantly handle what you have in mind. Place your data in a field or custom property and load it into a variable on openstack. You might also use an array, but that is a matter of style. Then you can retrieve your words and definitions and display at will. The whole app resides on one card. Craig Newman -Original Message- From: Louis Janus janus...@umn.edu To: use-livecode@lists.runrev.com Sent: Fri, Apr 1, 2011 10:56 am Subject: practical size limitations? Dear use-livecode I am beginning work on a learner's dictionary for Norwegian, and am looking into using LiveCode. A few basic questions: 1. I assume it would be best to use a database as a backend to the ultimate dictionary, but I am quite sure that I don't have the skills to set up SQLite or any other database proficiently. (I can learn, I'm sure, however) 2. If I take the easy way out and list each headword and its forms on a separate card, will a large number of cards slow the searching and displaying of items beyond usefulness? 3. Does anyone know of such a language dictionary developed using LiveCode? Thanks for any input and ideas. Louis Janus ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: practical size limitations?
I don't have much experience using LC as a storage method but the manual recommends that if you have more than 2000 records to store you should consider using an external database. SQLite is not hard to learn and there are a lot of tutorials out on the web, plus free SQLite management tools. I'd say you'll spend a lot more time learning how to use LiveCode than how to set up a simple SQLite database, although the LC learning curve is very much worthwhile. Pete On Fri, Apr 1, 2011 at 7:56 AM, Louis Janus janus...@umn.edu wrote: Dear use-livecode I am beginning work on a learner's dictionary for Norwegian, and am looking into using LiveCode. A few basic questions: 1. I assume it would be best to use a database as a backend to the ultimate dictionary, but I am quite sure that I don't have the skills to set up SQLite or any other database proficiently. (I can learn, I'm sure, however) 2. If I take the easy way out and list each headword and its forms on a separate card, will a large number of cards slow the searching and displaying of items beyond usefulness? 3. Does anyone know of such a language dictionary developed using LiveCode? Thanks for any input and ideas. Louis Janus ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Pete Molly's Revenge http://www.mollysrevenge.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: practical size limitations?
I'm a quarter Norwegian! I'd buy that! I like the idea of using an array, given that all the data you could ever conceivably have will fit into memory snugly. For a dictionary, that may not be the case. SQLite would be the way to go if not. Lots of cards, no buenos. SQL is not that hard to learn, especially if all you are doing is finding and retrieving small sets of records from a single table. SQLite has a plugin for Firefox that can handle most things you would want to do with it. Seriously, I would love to buy that dictionary when you are done, ESPECIALLY if it were an iPhone app. Bob On Apr 1, 2011, at 7:56 AM, Louis Janus wrote: Dear use-livecode I am beginning work on a learner's dictionary for Norwegian, and am looking into using LiveCode. A few basic questions: 1. I assume it would be best to use a database as a backend to the ultimate dictionary, but I am quite sure that I don't have the skills to set up SQLite or any other database proficiently. (I can learn, I'm sure, however) 2. If I take the easy way out and list each headword and its forms on a separate card, will a large number of cards slow the searching and displaying of items beyond usefulness? 3. Does anyone know of such a language dictionary developed using LiveCode? Thanks for any input and ideas. Louis Janus ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: practical size limitations?
I know databases are the grownup way to do things. But I loaded 1,000,000 words into 1,000,000 lines of a field by generating random strings of six chars. Takes no time to do that (0.6 seconds). I retrieved a random word from that field. Takes no time at all (3 ticks). If you had a million words separated with a comma from their definitions, you would also spend no time accessing them. One card, one field and a button or two for functionality. Craig Newman -Original Message- From: Bob Sneidar b...@twft.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Fri, Apr 1, 2011 1:08 pm Subject: Re: practical size limitations? I'm a quarter Norwegian! I'd buy that! I like the idea of using an array, given that all the data you could ever conceivably have will fit into memory snugly. For a dictionary, that may not be the case. SQLite would be the way to go if not. Lots of cards, no buenos. SQL is not that hard to learn, especially if all you are doing is finding and retrieving small sets of records from a single table. SQLite has a plugin for Firefox that can handle most things you would want to do with it. Seriously, I would love to buy that dictionary when you are done, ESPECIALLY if it were an iPhone app. Bob On Apr 1, 2011, at 7:56 AM, Louis Janus wrote: Dear use-livecode I am beginning work on a learner's dictionary for Norwegian, and am looking into using LiveCode. A few basic questions: 1. I assume it would be best to use a database as a backend to the ultimate dictionary, but I am quite sure that I don't have the skills to set up SQLite or any other database proficiently. (I can learn, I'm sure, however) 2. If I take the easy way out and list each headword and its forms on a separate card, will a large number of cards slow the searching and displaying of items beyond usefulness? 3. Does anyone know of such a language dictionary developed using LiveCode? Thanks for any input and ideas. Louis Janus ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
