Hi Jennifer,
> I have a TI Nspire that I bought for college.
Which model ? Clickpad, Touchpad, CX ?
> Well, my major is Computer Science.
Good :)
> That means math through at least Calculus III, and two semesters of
> Calculus based Physics. I am taking Intermediate Algebra and
> Introductory Physics this summer, and will be taking Advanced
> Algebra in the Fall, along with a course in algorithms and data
> structures in Java and one in assembly language.
For the latter course, despite its ARM processor, the Nspire isn't
necessarily the best choice, but it's what you have :)
> I can use my iPhone to view PDFs, as well as my iPad.
Indeed, and besides, smartphones and tablets can handle unmodified PDFs,
while mViewer for Nspire/Ndless needs a conversion to BMP, PNG, etc.
(and while the built-in OS documents require a conversion to a laughably
inefficient proprietary format).
> It is mainly the coding in C/ASM that interests me.
For that purpose, OS 3.2.0.1212/3.2.0.1219 is clearly not an option at
the time of this writing, and chances are that it won't be for months.
Therefore, I'll clearly advise you against using 3.2.0.121x ;)
Especially so if you're using a Clickpad / Touchpad Nspire: the OS is
getting larger and larger, so it leaves less and less RAM free, which,
in turn, reduces the maximum complexity of documents / programs that the
older models can handle. It's likely that TI will soon stop upgrading
the OS for the older models.
As long as users can downgrade to 3.1.0.392, people of the open
development community have little incentive to work full-time on
reverse-engineering the new OS series, instead of going through our
respective existing todo/wish lists:
* USB support for improving (e.g. keyboard for typing) and expanding
(using the Nspire's host capabilities, or exposing it as various devices
to hosts) the use cases of the platform;x
* expanding Lua capabilities through native code;
* etc.
TI will probably raise the anti-downgrade protection limit as soon as
several high-profile bugs / performance regressions have been fixed; but
for now, as far as programming in C/ASM is concerned, 3.1.0.392 is fine.
> I had seen the problems with documents.
Said documents being a prime example of what not to do in computer
science: applying a brain-damaged, very heavyweight document format to
an embedded platform, notwithstanding the pre-existence of more
standard, lighterweight document formats. And it's probably intentional.
But I'll stop here because you seem to have read the earlier threads on
that topic.
Bye,
Lionel.