#applenewton — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #applenewton, aggregated by home.social.
-
I use unreadable super-fast handwriting while taking notes. So I use ink text to take notes on my #AppleNewton MessagePad 2x00, and transcribe afterwards
To me, this was an immediate upgrade over paper, as it let me replace all my books with one tiny pad that makes my notes beautiful and searchable -
You can use software that improves or enhances the built-in #AppleNewton handwriting recognition:
newtonfaq.com/newton-faq-n...
Newton FAQ: Newton OS -
Announcing the August release of the Newton Glossary!
This edition contains 2,312 terms, definitions, acronyms, colloquialisms, cross-references, and trivia related to the #AppleNewton.
Latest additions:
https://newtonglossary.com/latest
Full release notes:
-
Announcing the August release of the Newton Glossary!
This edition contains 2,312 terms, definitions, acronyms, colloquialisms, cross-references, and trivia related to the #AppleNewton.
Latest additions:
https://newtonglossary.com/latest
Full release notes:
-
Announcing the August release of the Newton Glossary!
This edition contains 2,312 terms, definitions, acronyms, colloquialisms, cross-references, and trivia related to the #AppleNewton.
Latest additions:
https://newtonglossary.com/latest
Full release notes:
-
Announcing the August release of the Newton Glossary!
This edition contains 2,312 terms, definitions, acronyms, colloquialisms, cross-references, and trivia related to the #AppleNewton.
Latest additions:
https://newtonglossary.com/latest
Full release notes:
-
Announcing the August release of the Newton Glossary!
This edition contains 2,312 terms, definitions, acronyms, colloquialisms, cross-references, and trivia related to the #AppleNewton.
Latest additions:
https://newtonglossary.com/latest
Full release notes:
-
@mrgrumpymonkey @tilton I briefly owned a Palm. Ebay doesn't seem lubricously over priced.
Sold it for a Newton though...
#retro #retroComputing #appleNewton -
@mrgrumpymonkey @tilton I briefly owned a Palm. Ebay doesn't seem lubricously over priced.
Sold it for a Newton though...
#retro #retroComputing #appleNewton -
@mrgrumpymonkey @tilton I briefly owned a Palm. Ebay doesn't seem lubricously over priced.
Sold it for a Newton though...
#retro #retroComputing #appleNewton -
@mrgrumpymonkey @tilton I briefly owned a Palm. Ebay doesn't seem lubricously over priced.
Sold it for a Newton though...
#retro #retroComputing #appleNewton -
@mrgrumpymonkey @tilton I briefly owned a Palm. Ebay doesn't seem lubricously over priced.
Sold it for a Newton though...
#retro #retroComputing #appleNewton -
A few weeks later:
1. Still love this thing just as much as I did on day 1. If anything, I love it even more.
2. I wish the handwriting recognition was better. I am fairly certain that I could spend a week learning PyTorch and end up with a better recognition model tailored specifically to my own handwriting. That’s much more a statement about how far machine learning has come in the past ~30 29 years than it is a statement about Newton’s handwriting recognition (which was widely recognized as the best handwriting recognizer until somewhere around 2010).
3. A capacitive touchscreen + capacitive pen would be a much nicer UX than a resistive touchscreen.
4. I do not know if having better/more modern connectivity would be a boon for my usage of this device. My newton, to me, is a device for taking notes. Being able to easily open mastodon would likely distract me from taking notes.
5. That said, I would love it if getting notes off of this device were easier. I am so used to having things automatically sync between my newer devices.
6. I might learn just enough newtonscript to show off a point (e.g. I want to make an app to show how easy it is to extend built-in apps. In this case, by adding a pronouns field to the Names app), but I’m not going to learn enough of it to make actually useful apps. -
A few weeks later:
1. Still love this thing just as much as I did on day 1. If anything, I love it even more.
2. I wish the handwriting recognition was better. I am fairly certain that I could spend a week learning PyTorch and end up with a better recognition model tailored specifically to my own handwriting. That’s much more a statement about how far machine learning has come in the past ~30 29 years than it is a statement about Newton’s handwriting recognition (which was widely recognized as the best handwriting recognizer until somewhere around 2010).
3. A capacitive touchscreen + capacitive pen would be a much nicer UX than a resistive touchscreen.
4. I do not know if having better/more modern connectivity would be a boon for my usage of this device. My newton, to me, is a device for taking notes. Being able to easily open mastodon would likely distract me from taking notes.
5. That said, I would love it if getting notes off of this device were easier. I am so used to having things automatically sync between my newer devices.
6. I might learn just enough newtonscript to show off a point (e.g. I want to make an app to show how easy it is to extend built-in apps. In this case, by adding a pronouns field to the Names app), but I’m not going to learn enough of it to make actually useful apps. -
A few weeks later:
1. Still love this thing just as much as I did on day 1. If anything, I love it even more.
2. I wish the handwriting recognition was better. I am fairly certain that I could spend a week learning PyTorch and end up with a better recognition model tailored specifically to my own handwriting. That’s much more a statement about how far machine learning has come in the past ~30 29 years than it is a statement about Newton’s handwriting recognition (which was widely recognized as the best handwriting recognizer until somewhere around 2010).
3. A capacitive touchscreen + capacitive pen would be a much nicer UX than a resistive touchscreen.
4. I do not know if having better/more modern connectivity would be a boon for my usage of this device. My newton, to me, is a device for taking notes. Being able to easily open mastodon would likely distract me from taking notes.
5. That said, I would love it if getting notes off of this device were easier. I am so used to having things automatically sync between my newer devices.
6. I might learn just enough newtonscript to show off a point (e.g. I want to make an app to show how easy it is to extend built-in apps. In this case, by adding a pronouns field to the Names app), but I’m not going to learn enough of it to make actually useful apps. -
A few weeks later:
1. Still love this thing just as much as I did on day 1. If anything, I love it even more.
2. I wish the handwriting recognition was better. I am fairly certain that I could spend a week learning PyTorch and end up with a better recognition model tailored specifically to my own handwriting. That’s much more a statement about how far machine learning has come in the past ~30 29 years than it is a statement about Newton’s handwriting recognition (which was widely recognized as the best handwriting recognizer until somewhere around 2010).
3. A capacitive touchscreen + capacitive pen would be a much nicer UX than a resistive touchscreen.
4. I do not know if having better/more modern connectivity would be a boon for my usage of this device. My newton, to me, is a device for taking notes. Being able to easily open mastodon would likely distract me from taking notes.
5. That said, I would love it if getting notes off of this device were easier. I am so used to having things automatically sync between my newer devices.
6. I might learn just enough newtonscript to show off a point (e.g. I want to make an app to show how easy it is to extend built-in apps. In this case, by adding a pronouns field to the Names app), but I’m not going to learn enough of it to make actually useful apps. -
A few weeks later:
1. Still love this thing just as much as I did on day 1. If anything, I love it even more.
2. I wish the handwriting recognition was better. I am fairly certain that I could spend a week learning PyTorch and end up with a better recognition model tailored specifically to my own handwriting. That’s much more a statement about how far machine learning has come in the past ~30 29 years than it is a statement about Newton’s handwriting recognition (which was widely recognized as the best handwriting recognizer until somewhere around 2010).
3. A capacitive touchscreen + capacitive pen would be a much nicer UX than a resistive touchscreen.
4. I do not know if having better/more modern connectivity would be a boon for my usage of this device. My newton, to me, is a device for taking notes. Being able to easily open mastodon would likely distract me from taking notes.
5. That said, I would love it if getting notes off of this device were easier. I am so used to having things automatically sync between my newer devices.
6. I might learn just enough newtonscript to show off a point (e.g. I want to make an app to show how easy it is to extend built-in apps. In this case, by adding a pronouns field to the Names app), but I’m not going to learn enough of it to make actually useful apps. -
Wondering if there is a need to model the battery door for the eMate…
-
Wondering if there is a need to model the battery door for the eMate…
-
Wondering if there is a need to model the battery door for the eMate…
-
Wondering if there is a need to model the battery door for the eMate…
-
Wondering if there is a need to model the battery door for the eMate…
-
Twenty seven years ago today, @paulguyot compiled and published the very first edition of the Newton FAQ.
This #RetroComputing resource is still maintained and actively updated by me and the #AppleNewton community.
-
Twenty seven years ago today, @paulguyot compiled and published the very first edition of the Newton FAQ.
This #RetroComputing resource is still maintained and actively updated by me and the #AppleNewton community.
-
Twenty seven years ago today, @paulguyot compiled and published the very first edition of the Newton FAQ.
This #RetroComputing resource is still maintained and actively updated by me and the #AppleNewton community.
-
Twenty seven years ago today, @paulguyot compiled and published the very first edition of the Newton FAQ.
This #RetroComputing resource is still maintained and actively updated by me and the #AppleNewton community.
-
Twenty seven years ago today, @paulguyot compiled and published the very first edition of the Newton FAQ.
This #RetroComputing resource is still maintained and actively updated by me and the #AppleNewton community.
-
Whoa, if I'm reading this correctly, then Newton had Autolayout, at least as early as 1996 (Newton OS 2). Autolayout didn't ship on iOS until iOS 6 in 2012!
> The viewJustify slot is used to set the view alignment and is closely linked in its usage and effects with the viewBounds slot.
> The viewJustify slot specifies how text and graphics are aligned within the
view and how the bounds of the view are aligned relative to its parent or sibling views. (Sibling views are child views that have a common parent view.)
> In the viewJustify slot, you can specify one or more alignment attributes, which are represented by constants defined as bit flags. You can specify one alignment attribute from each of the following groups:(Source: Newton Programmer's Guide 2.0, Pages 3-13 through 3-18, Apple)
-
Whoa, if I'm reading this correctly, then Newton had Autolayout, at least as early as 1996 (Newton OS 2). Autolayout didn't ship on iOS until iOS 6 in 2012!
> The viewJustify slot is used to set the view alignment and is closely linked in its usage and effects with the viewBounds slot.
> The viewJustify slot specifies how text and graphics are aligned within the
view and how the bounds of the view are aligned relative to its parent or sibling views. (Sibling views are child views that have a common parent view.)
> In the viewJustify slot, you can specify one or more alignment attributes, which are represented by constants defined as bit flags. You can specify one alignment attribute from each of the following groups:(Source: Newton Programmer's Guide 2.0, Pages 3-13 through 3-18, Apple)
-
Whoa, if I'm reading this correctly, then Newton had Autolayout, at least as early as 1996 (Newton OS 2). Autolayout didn't ship on iOS until iOS 6 in 2012!
> The viewJustify slot is used to set the view alignment and is closely linked in its usage and effects with the viewBounds slot.
> The viewJustify slot specifies how text and graphics are aligned within the
view and how the bounds of the view are aligned relative to its parent or sibling views. (Sibling views are child views that have a common parent view.)
> In the viewJustify slot, you can specify one or more alignment attributes, which are represented by constants defined as bit flags. You can specify one alignment attribute from each of the following groups:(Source: Newton Programmer's Guide 2.0, Pages 3-13 through 3-18, Apple)
-
Whoa, if I'm reading this correctly, then Newton had Autolayout, at least as early as 1996 (Newton OS 2). Autolayout didn't ship on iOS until iOS 6 in 2012!
> The viewJustify slot is used to set the view alignment and is closely linked in its usage and effects with the viewBounds slot.
> The viewJustify slot specifies how text and graphics are aligned within the
view and how the bounds of the view are aligned relative to its parent or sibling views. (Sibling views are child views that have a common parent view.)
> In the viewJustify slot, you can specify one or more alignment attributes, which are represented by constants defined as bit flags. You can specify one alignment attribute from each of the following groups:(Source: Newton Programmer's Guide 2.0, Pages 3-13 through 3-18, Apple)
-
Whoa, if I'm reading this correctly, then Newton had Autolayout, at least as early as 1996 (Newton OS 2). Autolayout didn't ship on iOS until iOS 6 in 2012!
> The viewJustify slot is used to set the view alignment and is closely linked in its usage and effects with the viewBounds slot.
> The viewJustify slot specifies how text and graphics are aligned within the
view and how the bounds of the view are aligned relative to its parent or sibling views. (Sibling views are child views that have a common parent view.)
> In the viewJustify slot, you can specify one or more alignment attributes, which are represented by constants defined as bit flags. You can specify one alignment attribute from each of the following groups:(Source: Newton Programmer's Guide 2.0, Pages 3-13 through 3-18, Apple)
-
(You can tell how quickly I'm reading the Newton Developer's Guide from these posts):
Newton OS 2 had basically 3 ways of creating apps:
1. Do everything yourself
2. Create a "form" style app using NewtSDK
3. Create a "book" app, because epub didn't exist yet.(1) is basically how modern iOS & Mac dev has worked for... basically ages.
(2) is super interesting. With Newton OS 2, they were like "a lot of apps are basically just CRUD for soups, let's make it as easy as possible to do that". Which also goes against some of Apple's current recommendations (You could kinda read parts of 4.2 (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) as banning stuff like this). I WISH Apple had stuff like this. Way too many apps are CRUD for some backend service. A decent portion of the apps I've worked on in my career have been CRUD for some backend service. Hell, I've been arguing for years at work to get support to create something like this so that we can stop re-inventing the wheel for each sub-feature of our way-larger-than-it-should-be app. And Apple had shipped this, in the mid 90s!
(3) is one of the examples where things have gotten better since Newton. Nowadays, we've standardized on formats for creating ebooks and such, making it much simpler to publish these (though, you could certainly do MORE things with a newton-style digital book, I imagine most people just used this to ship text-based content with light images, nothing too interactive).
-
(You can tell how quickly I'm reading the Newton Developer's Guide from these posts):
Newton OS 2 had basically 3 ways of creating apps:
1. Do everything yourself
2. Create a "form" style app using NewtSDK
3. Create a "book" app, because epub didn't exist yet.(1) is basically how modern iOS & Mac dev has worked for... basically ages.
(2) is super interesting. With Newton OS 2, they were like "a lot of apps are basically just CRUD for soups, let's make it as easy as possible to do that". Which also goes against some of Apple's current recommendations (You could kinda read parts of 4.2 (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) as banning stuff like this). I WISH Apple had stuff like this. Way too many apps are CRUD for some backend service. A decent portion of the apps I've worked on in my career have been CRUD for some backend service. Hell, I've been arguing for years at work to get support to create something like this so that we can stop re-inventing the wheel for each sub-feature of our way-larger-than-it-should-be app. And Apple had shipped this, in the mid 90s!
(3) is one of the examples where things have gotten better since Newton. Nowadays, we've standardized on formats for creating ebooks and such, making it much simpler to publish these (though, you could certainly do MORE things with a newton-style digital book, I imagine most people just used this to ship text-based content with light images, nothing too interactive).
-
(You can tell how quickly I'm reading the Newton Developer's Guide from these posts):
Newton OS 2 had basically 3 ways of creating apps:
1. Do everything yourself
2. Create a "form" style app using NewtSDK
3. Create a "book" app, because epub didn't exist yet.(1) is basically how modern iOS & Mac dev has worked for... basically ages.
(2) is super interesting. With Newton OS 2, they were like "a lot of apps are basically just CRUD for soups, let's make it as easy as possible to do that". Which also goes against some of Apple's current recommendations (You could kinda read parts of 4.2 (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) as banning stuff like this). I WISH Apple had stuff like this. Way too many apps are CRUD for some backend service. A decent portion of the apps I've worked on in my career have been CRUD for some backend service. Hell, I've been arguing for years at work to get support to create something like this so that we can stop re-inventing the wheel for each sub-feature of our way-larger-than-it-should-be app. And Apple had shipped this, in the mid 90s!
(3) is one of the examples where things have gotten better since Newton. Nowadays, we've standardized on formats for creating ebooks and such, making it much simpler to publish these (though, you could certainly do MORE things with a newton-style digital book, I imagine most people just used this to ship text-based content with light images, nothing too interactive).
-
(You can tell how quickly I'm reading the Newton Developer's Guide from these posts):
Newton OS 2 had basically 3 ways of creating apps:
1. Do everything yourself
2. Create a "form" style app using NewtSDK
3. Create a "book" app, because epub didn't exist yet.(1) is basically how modern iOS & Mac dev has worked for... basically ages.
(2) is super interesting. With Newton OS 2, they were like "a lot of apps are basically just CRUD for soups, let's make it as easy as possible to do that". Which also goes against some of Apple's current recommendations (You could kinda read parts of 4.2 (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) as banning stuff like this). I WISH Apple had stuff like this. Way too many apps are CRUD for some backend service. A decent portion of the apps I've worked on in my career have been CRUD for some backend service. Hell, I've been arguing for years at work to get support to create something like this so that we can stop re-inventing the wheel for each sub-feature of our way-larger-than-it-should-be app. And Apple had shipped this, in the mid 90s!
(3) is one of the examples where things have gotten better since Newton. Nowadays, we've standardized on formats for creating ebooks and such, making it much simpler to publish these (though, you could certainly do MORE things with a newton-style digital book, I imagine most people just used this to ship text-based content with light images, nothing too interactive).
-
(You can tell how quickly I'm reading the Newton Developer's Guide from these posts):
Newton OS 2 had basically 3 ways of creating apps:
1. Do everything yourself
2. Create a "form" style app using NewtSDK
3. Create a "book" app, because epub didn't exist yet.(1) is basically how modern iOS & Mac dev has worked for... basically ages.
(2) is super interesting. With Newton OS 2, they were like "a lot of apps are basically just CRUD for soups, let's make it as easy as possible to do that". Which also goes against some of Apple's current recommendations (You could kinda read parts of 4.2 (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) as banning stuff like this). I WISH Apple had stuff like this. Way too many apps are CRUD for some backend service. A decent portion of the apps I've worked on in my career have been CRUD for some backend service. Hell, I've been arguing for years at work to get support to create something like this so that we can stop re-inventing the wheel for each sub-feature of our way-larger-than-it-should-be app. And Apple had shipped this, in the mid 90s!
(3) is one of the examples where things have gotten better since Newton. Nowadays, we've standardized on formats for creating ebooks and such, making it much simpler to publish these (though, you could certainly do MORE things with a newton-style digital book, I imagine most people just used this to ship text-based content with light images, nothing too interactive).
-
If Walter Smith (the guy who designed NewtonScript) ever sees this, he'd be very indignant. If anything javascript was modeled after newtonscript (in actuality, they're both heavily influenced by a bunch of languages developed much earlier: Self, SmallTalk, C/C++, etc.)
-
If Walter Smith (the guy who designed NewtonScript) ever sees this, he'd be very indignant. If anything javascript was modeled after newtonscript (in actuality, they're both heavily influenced by a bunch of languages developed much earlier: Self, SmallTalk, C/C++, etc.)
-
If Walter Smith (the guy who designed NewtonScript) ever sees this, he'd be very indignant. If anything javascript was modeled after newtonscript (in actuality, they're both heavily influenced by a bunch of languages developed much earlier: Self, SmallTalk, C/C++, etc.)
-
If Walter Smith (the guy who designed NewtonScript) ever sees this, he'd be very indignant. If anything javascript was modeled after newtonscript (in actuality, they're both heavily influenced by a bunch of languages developed much earlier: Self, SmallTalk, C/C++, etc.)
-
If Walter Smith (the guy who designed NewtonScript) ever sees this, he'd be very indignant. If anything javascript was modeled after newtonscript (in actuality, they're both heavily influenced by a bunch of languages developed much earlier: Self, SmallTalk, C/C++, etc.)
-
Reading more Newton Developer Documentation, and I learned that every app executes as a subroutine in the same process. Which means that you can fully crash every other app if you mess up particularly badly (probably wasn't that much of an issue in practice, because NewtonScript was, in many, many ways, javascript for Newton).
From the Newton Developer's Guide:
> All Newton applications, including the recognition system, built-in applications, and applications you develop, run in a single operating system task, called the Application task.
The 90s were wild!
-
Reading more Newton Developer Documentation, and I learned that every app executes as a subroutine in the same process. Which means that you can fully crash every other app if you mess up particularly badly (probably wasn't that much of an issue in practice, because NewtonScript was, in many, many ways, javascript for Newton).
From the Newton Developer's Guide:
> All Newton applications, including the recognition system, built-in applications, and applications you develop, run in a single operating system task, called the Application task.
The 90s were wild!
-
Reading more Newton Developer Documentation, and I learned that every app executes as a subroutine in the same process. Which means that you can fully crash every other app if you mess up particularly badly (probably wasn't that much of an issue in practice, because NewtonScript was, in many, many ways, javascript for Newton).
From the Newton Developer's Guide:
> All Newton applications, including the recognition system, built-in applications, and applications you develop, run in a single operating system task, called the Application task.
The 90s were wild!
-
Reading more Newton Developer Documentation, and I learned that every app executes as a subroutine in the same process. Which means that you can fully crash every other app if you mess up particularly badly (probably wasn't that much of an issue in practice, because NewtonScript was, in many, many ways, javascript for Newton).
From the Newton Developer's Guide:
> All Newton applications, including the recognition system, built-in applications, and applications you develop, run in a single operating system task, called the Application task.
The 90s were wild!
-
Reading more Newton Developer Documentation, and I learned that every app executes as a subroutine in the same process. Which means that you can fully crash every other app if you mess up particularly badly (probably wasn't that much of an issue in practice, because NewtonScript was, in many, many ways, javascript for Newton).
From the Newton Developer's Guide:
> All Newton applications, including the recognition system, built-in applications, and applications you develop, run in a single operating system task, called the Application task.
The 90s were wild!
-
Spoiler … it’s definitely not the #AppleNewton
https://mstdn.social/@osnews/117095472896155575 -
Spoiler … it’s definitely not the #AppleNewton
https://mstdn.social/@osnews/117095472896155575 -
Spoiler … it’s definitely not the #AppleNewton
https://mstdn.social/@osnews/117095472896155575 -
Spoiler … it’s definitely not the #AppleNewton
https://mstdn.social/@osnews/117095472896155575 -
Spoiler … it’s definitely not the #AppleNewton
https://mstdn.social/@osnews/117095472896155575 -
I discovered that you can select script written using the “sketch” mode, and then double-tap on it to get the Newton to try to transcribe that to text.
This basically eliminates any reason I had to use the “ink text” mode.
-
I discovered that you can select script written using the “sketch” mode, and then double-tap on it to get the Newton to try to transcribe that to text.
This basically eliminates any reason I had to use the “ink text” mode.
-
I discovered that you can select script written using the “sketch” mode, and then double-tap on it to get the Newton to try to transcribe that to text.
This basically eliminates any reason I had to use the “ink text” mode.
-
I discovered that you can select script written using the “sketch” mode, and then double-tap on it to get the Newton to try to transcribe that to text.
This basically eliminates any reason I had to use the “ink text” mode.
-
I discovered that you can select script written using the “sketch” mode, and then double-tap on it to get the Newton to try to transcribe that to text.
This basically eliminates any reason I had to use the “ink text” mode.
-
Twenty nine years ago today, Newton, Inc. unveiled “an exciting, new look”, including a refreshed logo and corporate identity after being spun out of Apple earlier in the year.
-
Twenty nine years ago today, Newton, Inc. unveiled “an exciting, new look”, including a refreshed logo and corporate identity after being spun out of Apple earlier in the year.
-
Twenty nine years ago today, Newton, Inc. unveiled “an exciting, new look”, including a refreshed logo and corporate identity after being spun out of Apple earlier in the year.