home.social

#200lx — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #200lx, aggregated by home.social.

fetched live
  1. @stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

    Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

    VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

    I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

  2. @stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

    Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

    VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

    I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

  3. @stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

    Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

    VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

    I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

  4. @stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

    Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

    VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

    I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

  5. @stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

    Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

    VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

    I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

  6. Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

    • Simulates a stack of index cards.
    • Each note has an index line.
    • Notes are auto alphabetized by index. No other sort order is possible.

    Cardfile has separate card and index views. NoteTaker shows both at once.

    This is the simplest class of application that I believe is justified in calling itself a #database.

    #HP200LX #retrocomputing

  7. Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

    • Simulates a stack of index cards.
    • Each note has an index line.
    • Notes are auto alphabetized by index. No other sort order is possible.

    Cardfile has separate card and index views. NoteTaker shows both at once.

    This is the simplest class of application that I believe is justified in calling itself a #database.

    #HP200LX #retrocomputing

  8. Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

    • Simulates a stack of index cards.
    • Each note has an index line.
    • Notes are auto alphabetized by index. No other sort order is possible.

    Cardfile has separate card and index views. NoteTaker shows both at once.

    This is the simplest class of application that I believe is justified in calling itself a #database.

    #HP200LX #retrocomputing

  9. Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

    • Simulates a stack of index cards.
    • Each note has an index line.
    • Notes are auto alphabetized by index. No other sort order is possible.

    Cardfile has separate card and index views. NoteTaker shows both at once.

    This is the simplest class of application that I believe is justified in calling itself a #database.

    #HP200LX #retrocomputing

  10. Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

    • Simulates a stack of index cards.
    • Each note has an index line.
    • Notes are auto alphabetized by index. No other sort order is possible.

    Cardfile has separate card and index views. NoteTaker shows both at once.

    This is the simplest class of application that I believe is justified in calling itself a #database.

    #HP200LX #retrocomputing

  11. @flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

    #hp200lx

  12. @flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

    #hp200lx

  13. @flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

    #hp200lx

  14. @flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

    #hp200lx

  15. @flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

    #hp200lx

  16. I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

    This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

    • Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
    • A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
    • A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

    The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

    #HP200LX #retrocomputing

  17. I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

    This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

    • Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
    • A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
    • A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

    The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

    #HP200LX #retrocomputing

  18. I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

    This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

    • Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
    • A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
    • A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

    The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

    #HP200LX #retrocomputing

  19. I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

    This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

    • Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
    • A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
    • A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

    The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

    #HP200LX #retrocomputing

  20. I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

    This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

    • Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
    • A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
    • A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

    The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

    #HP200LX #retrocomputing

  21. @interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

    archive.org/details/manualsbas

    #retrocomputing #hp200lx

  22. @interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

    archive.org/details/manualsbas

    #retrocomputing #hp200lx

  23. @interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

    archive.org/details/manualsbas

    #retrocomputing #hp200lx

  24. @interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

    archive.org/details/manualsbas

    #retrocomputing #hp200lx

  25. @interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

    archive.org/details/manualsbas

    #retrocomputing #hp200lx

  26. @AlgoCompSynth That would be muLisp, as I ran across quite by accident the other day. Sure enough, it's amazing on the #200LX! I've been working on Project Euler: it's quite addictive.

    github.com/MartinHepperle/muLI

    #hp200lx #lisp

  27. @AlgoCompSynth That would be muLisp, as I ran across quite by accident the other day. Sure enough, it's amazing on the #200LX! I've been working on Project Euler: it's quite addictive.

    github.com/MartinHepperle/muLI

    #hp200lx #lisp

  28. @AlgoCompSynth That would be muLisp, as I ran across quite by accident the other day. Sure enough, it's amazing on the #200LX! I've been working on Project Euler: it's quite addictive.

    github.com/MartinHepperle/muLI

    #hp200lx #lisp

  29. @AlgoCompSynth That would be muLisp, as I ran across quite by accident the other day. Sure enough, it's amazing on the #200LX! I've been working on Project Euler: it's quite addictive.

    github.com/MartinHepperle/muLI

    #hp200lx #lisp

  30. @AlgoCompSynth That would be muLisp, as I ran across quite by accident the other day. Sure enough, it's amazing on the #200LX! I've been working on Project Euler: it's quite addictive.

    github.com/MartinHepperle/muLI

    #hp200lx #lisp

  31. I can't believe it, but I found an old-arse CF card of 32MB size and made it work in my 200LX! Now, DOOM8088....and a ton of other games. #retro #retrocomputing #retrogaming #retrogames #200lx #msdos

  32. I can't believe it, but I found an old-arse CF card of 32MB size and made it work in my 200LX! Now, DOOM8088....and a ton of other games. #retro #retrocomputing #retrogaming #retrogames #200lx #msdos

  33. I can't believe it, but I found an old-arse CF card of 32MB size and made it work in my 200LX! Now, DOOM8088....and a ton of other games. #retro #retrocomputing #retrogaming #retrogames #200lx #msdos

  34. I can't believe it, but I found an old-arse CF card of 32MB size and made it work in my 200LX! Now, DOOM8088....and a ton of other games. #retro #retrocomputing #retrogaming #retrogames #200lx #msdos

  35. I can't believe it, but I found an old-arse CF card of 32MB size and made it work in my 200LX! Now, DOOM8088....and a ton of other games. #retro #retrocomputing #retrogaming #retrogames #200lx #msdos

  36. HP Connectivity Pack is now installed on my phone, allowing me to view and convert files from the #hp200lx's native PIM apps. Phone and HP #200LX are now a self-sufficient pair, with no PC required to transfer, view or edit files. (And yes, I also have Lotus 1-2-3 on my phone. Who doesn't?) No lock-in, no bullshit, just data files in well-understood formats readable anywhere. Can it still be called #retrocomputing if it's still so useful in the modern age?

  37. HP Connectivity Pack is now installed on my phone, allowing me to view and convert files from the #hp200lx's native PIM apps. Phone and HP #200LX are now a self-sufficient pair, with no PC required to transfer, view or edit files. (And yes, I also have Lotus 1-2-3 on my phone. Who doesn't?) No lock-in, no bullshit, just data files in well-understood formats readable anywhere. Can it still be called #retrocomputing if it's still so useful in the modern age?

  38. HP Connectivity Pack is now installed on my phone, allowing me to view and convert files from the #hp200lx's native PIM apps. Phone and HP #200LX are now a self-sufficient pair, with no PC required to transfer, view or edit files. (And yes, I also have Lotus 1-2-3 on my phone. Who doesn't?) No lock-in, no bullshit, just data files in well-understood formats readable anywhere. Can it still be called #retrocomputing if it's still so useful in the modern age?

  39. HP Connectivity Pack is now installed on my phone, allowing me to view and convert files from the #hp200lx's native PIM apps. Phone and HP #200LX are now a self-sufficient pair, with no PC required to transfer, view or edit files. (And yes, I also have Lotus 1-2-3 on my phone. Who doesn't?) No lock-in, no bullshit, just data files in well-understood formats readable anywhere. Can it still be called #retrocomputing if it's still so useful in the modern age?

  40. HP Connectivity Pack is now installed on my phone, allowing me to view and convert files from the #hp200lx's native PIM apps. Phone and HP #200LX are now a self-sufficient pair, with no PC required to transfer, view or edit files. (And yes, I also have Lotus 1-2-3 on my phone. Who doesn't?) No lock-in, no bullshit, just data files in well-understood formats readable anywhere. Can it still be called #retrocomputing if it's still so useful in the modern age?

  41. The next #Forth program I write on the HP #200LX will be #uuencode / #uudecode so I can transfer binary files to/from hosts that don't support #zmodem. #HP200LX

  42. The next #Forth program I write on the HP #200LX will be #uuencode / #uudecode so I can transfer binary files to/from hosts that don't support #zmodem. #HP200LX

  43. The next #Forth program I write on the HP #200LX will be #uuencode / #uudecode so I can transfer binary files to/from hosts that don't support #zmodem. #HP200LX

  44. The next #Forth program I write on the HP #200LX will be #uuencode / #uudecode so I can transfer binary files to/from hosts that don't support #zmodem. #HP200LX

  45. The next #Forth program I write on the HP #200LX will be #uuencode / #uudecode so I can transfer binary files to/from hosts that don't support #zmodem. #HP200LX

  46. omg I was not expecting winning #Freecell on the HP #200LX to do the bouncy cards thing
    #HP200LX #retrocomputing

  47. omg I was not expecting winning #Freecell on the HP #200LX to do the bouncy cards thing
    #HP200LX #retrocomputing

  48. omg I was not expecting winning #Freecell on the HP #200LX to do the bouncy cards thing
    #HP200LX #retrocomputing

  49. omg I was not expecting winning #Freecell on the HP #200LX to do the bouncy cards thing
    #HP200LX #retrocomputing

  50. omg I was not expecting winning #Freecell on the HP #200LX to do the bouncy cards thing
    #HP200LX #retrocomputing

  51. I bought a large storage card for the #HP200LX. Sadly, the HP itself is the only machine I have working right now with a PC card slot. The card came preloaded with neat #200LX-ready software, which I am backing up to my PC. Copying hundreds of megabytes of software over 9600 baud serial... takes... um... a while!?

  52. I bought a large storage card for the #HP200LX. Sadly, the HP itself is the only machine I have working right now with a PC card slot. The card came preloaded with neat #200LX-ready software, which I am backing up to my PC. Copying hundreds of megabytes of software over 9600 baud serial... takes... um... a while!?

  53. I bought a large storage card for the #HP200LX. Sadly, the HP itself is the only machine I have working right now with a PC card slot. The card came preloaded with neat #200LX-ready software, which I am backing up to my PC. Copying hundreds of megabytes of software over 9600 baud serial... takes... um... a while!?

  54. I bought a large storage card for the #HP200LX. Sadly, the HP itself is the only machine I have working right now with a PC card slot. The card came preloaded with neat #200LX-ready software, which I am backing up to my PC. Copying hundreds of megabytes of software over 9600 baud serial... takes... um... a while!?

  55. I bought a large storage card for the #HP200LX. Sadly, the HP itself is the only machine I have working right now with a PC card slot. The card came preloaded with neat #200LX-ready software, which I am backing up to my PC. Copying hundreds of megabytes of software over 9600 baud serial... takes... um... a while!?