Early Progress: Migration to N810 & Garnet VM

[Ken Latham]

It appears that Shadow is working pretty well under the Garnett VM on
my new Nokia N810.

I just moved over some of the pdb files and up it came. The Garnet
release (supposedly 5.5.0) does NOT use Calendar, Memos, Tasks and
Contacts. It uses the older databases: Datebook, Notepad, ToDo, and
Address (respectively).

Strangely enough, the ToDo application is MIA and I'm not sure about
moving one off of my older units ... could be a problem there. But
then again, my Sony UX50 used Garnett 5 and still had the old
databases ... whether the ToDo app will work under the VM or not is
questionable.

Ergo, Shadow linking is a no-show (crashes) so far without the support
for ToDo. I have yet to move the databses over since my Treo backup
software doesn't backup the "mirror" databases, but that will soon be
rectified (since it has the option to).

Also, there seems to be no support in the VM for the N810 5-way, but I
have not really tried all the hardware models it can simulate ...
maybe one will work. In the meantime, I have the pen, Grafitti and a
collapsable DIA.

Ken

P.S. *Loving the N810*, big 800x480 screen (except the Garnett VM),
Inet through WiFi at home/hotspot, DUN through my (Verizon) Treo when
not ... Finally the *whole* internet in one neat little package (not
in little pieces like the iPhone).

P.P.S. Jeff, if you feel there is any licensing issue with me moving
Shadow, let me know. I will gladly pay again to get the thing working
without that awful slowdown on my Treo. Though, I do plan to move
Shadow off the Treo entirely if I can.

[jmarkevich]

I am increasingly frustrated with Garnet VM. I can't sync anymore, it
constanty fails with "Connection Lost" no matter what I do. Not
only is the platform closed, they have ZERO communication with users.
That's a lousy beta program.

Any possibility of porting the Linux desktop version to the n8x0?

Post by Ken Latham
It appears that Shadow is working pretty well under the Garnett VM on
my new Nokia N810.
I just moved over some of the pdb files and up it came. The Garnet
release (supposedly 5.5.0) does NOT use Calendar, Memos, Tasks and
Contacts. It uses the older databases: Datebook, Notepad, ToDo, and
Address (respectively).

Yep, amazing devices huh? PIMs available are pretty lame though.

Post by Ken Latham
P.S. *Loving the N810*, big 800x480 screen (except the Garnett VM),
Inet through WiFi at home/hotspot, DUN through my (Verizon) Treo when
not ... Finally the *whole* internet in one neat little package (not
in little pieces like the iPhone).

[Jeff Mitchell]

On Mon, 21 Jan 2008, Ken Latham wrote:

# Strangely enough, the ToDo application is MIA and I'm not sure about
# moving one off of my older units ... could be a problem there. But
# then again, my Sony UX50 used Garnett 5 and still had the old
# databases ... whether the ToDo app will work under the VM or not is
# questionable.

If you've got one of the POSE versions around, try exporting the
To Do pdb from that and import it into your N810. (ie: A ToDo database
where you've wiped everything, so its should a header pretty much..
minimizes incompatibilities.)

Shadow plays by the OS rules and recommendations where possible so
hopefully should work well :)

# P.S. *Loving the N810*, big 800x480 screen (except the Garnett VM),
# Inet through WiFi at home/hotspot, DUN through my (Verizon) Treo when
# not ... Finally the *whole* internet in one neat little package (not
# in little pieces like the iPhone).

I've got a UMPC I've been fiddling with; interesting, but in my
case a very awkward keyboard. The EEE looks very interesting for a lot of
people.. nice keyboard, nice display, etc, can install Windows/Linux/etc..
just no touchscreen on it. But $250-$350!

# P.P.S. Jeff, if you feel there is any licensing issue with me moving
# Shadow, let me know. I will gladly pay again to get the thing working
# without that awful slowdown on my Treo. Though, I do plan to move
# Shadow off the Treo entirely if I can.

I've never been that anal; should've been but never was ;)

FWIW, it would seem Shadow Desktop should be portable to the N810.
It'd take me a bit of work to figure out how to produce the ARM binary for
it, but the toolkit and dependant libs I use (not many) should all be N810
friendly. (yay for Unix/Linux!) Thats a big 'hmmm'. to me...

jeff

--
If everyone would put barbecue sauce on their food, there would be no war.

[Ken Latham]

Jeff,

Please don't let this distract you!!

Remember this is an Access *beta*. And if you were to spend any time
working on Shadow, I'd have to kill myself if you spent it working on
getting it running under the Access VM.

Suicide?! Too extreme!! you say? Not if you think about what the
other users of this group would do to me if you spent your time on
that instead of *real* Palm devices, just because I piqued your interest!

In fact, I'm a little nervous that you took time to comment on this
post! ;)

Ken

Post by Jeff Mitchell
# Strangely enough, the ToDo application is MIA and I'm not sure about
# moving one off of my older units ... could be a problem there. But
# then again, my Sony UX50 used Garnett 5 and still had the old
# databases ... whether the ToDo app will work under the VM or not is
# questionable.
If you've got one of the POSE versions around, try exporting the
To Do pdb from that and import it into your N810. (ie: A ToDo database
where you've wiped everything, so its should a header pretty much..
minimizes incompatibilities.)
Shadow plays by the OS rules and recommendations where possible so
hopefully should work well :)
# P.S. *Loving the N810*, big 800x480 screen (except the Garnett VM),
# Inet through WiFi at home/hotspot, DUN through my (Verizon) Treo when
# not ... Finally the *whole* internet in one neat little package (not
# in little pieces like the iPhone).
I've got a UMPC I've been fiddling with; interesting, but in my
case a very awkward keyboard. The EEE looks very interesting for a lot of
people.. nice keyboard, nice display, etc, can install

Windows/Linux/etc..

Post by Jeff Mitchell
just no touchscreen on it. But $250-$350!
# P.P.S. Jeff, if you feel there is any licensing issue with me moving
# Shadow, let me know. I will gladly pay again to get the thing working
# without that awful slowdown on my Treo. Though, I do plan to move
# Shadow off the Treo entirely if I can.
I've never been that anal; should've been but never was ;)
FWIW, it would seem Shadow Desktop should be portable to the N810.
It'd take me a bit of work to figure out how to produce the ARM binary for
it, but the toolkit and dependant libs I use (not many) should all be N810
friendly. (yay for Unix/Linux!) Thats a big 'hmmm'. to me...
jeff
--
If everyone would put barbecue sauce on their food, there would be no war.

[Jeff Mitchell]

On Tue, 22 Jan 2008, Ken Latham wrote:

# Please don't let this distract you!!
#
# Remember this is an Access *beta*. And if you were to spend any time
# working on Shadow, I'd have to kill myself if you spent it working on
# getting it running under the Access VM.
#
# Suicide?! Too extreme!! you say? Not if you think about what the
# other users of this group would do to me if you spent your time on
# that instead of *real* Palm devices, just because I piqued your interest!

Oh fear not, thats low on my priority list. If Palm,
PalmSource/ACCESS cannot keep Garnet sensible on their own devices, then I
cannot imagine the horror of it on an entirely different device. Below my
comment is about Shadow _Desktop_ however .. ie: In theory, if I assembled
the toolset, it would build more or less 'out of the box' and 'just work'
as it does now.

(The gotcha there is .. a desktop designed UI would probably be
atrocious on the small touchscreen .. its designed for keyboard and mouse
on a large display.)

So on the one hand.. its a fun idea, just to see how it sorts out.
Should just resize the desktop as is to the handhelds screen res and see
how nasty it is. or if the dialogs even fit :)

On the other though, the key thing I see and hope for.. is devices
with SDKs, OSes, hardware and so on that can be compatible with Real Code,
not Evil Horrible Paincode. Shadow Desktop is written very conveniently,
if not the most artfully.. whereas Shadow Handheld has had to grow through
very extreme conditions (original Palms made you... creative. As I've said
before.. writing code for a Commodore 64,then growing and running it on a
mainframe down the road .. thats some effort and growing pains :)

So I look forward to these emerging devices where I can leverage a
large and fully functional existing codebase for a change (the desktops,
rather than the handhelds).. having to reimplement chunks for every new
device is what makes all us handheld developers wish to kill ourselves,
too :P

jeff

The baby has slept through the night 3 times in about 10 days. Let
us hope ;)

--
If everyone would put barbecue sauce on their food, there would be no war.

[Griff]

And this is why development has to be focused on the desktop. You stand a
lot better chance of getting new users of the desktop to purchase given the
move away from Palm devices.

You'll get a bigger bang for the buck as you add features to ShadDT *IF* it
can also be easily compiled to emerging technologies such as the N810.

Of course you know you already have your first two alpha testers for when
you decide to give a compile a whirl. ;-)

-----Original Message-----
From: Jeff Mitchell
Oh fear not, thats low on my priority list. If Palm,
PalmSource/ACCESS cannot keep Garnet sensible on their own devices, then I
cannot imagine the horror of it on an entirely different device. Below my
comment is about Shadow _Desktop_ however .. ie: In theory, if I assembled
the toolset, it would build more or less 'out of the box' and 'just work'
as it does now.
(The gotcha there is .. a desktop designed UI would probably be
atrocious on the small touchscreen .. its designed for keyboard and mouse
on a large display.)
So on the one hand.. its a fun idea, just to see how it sorts
out.
Should just resize the desktop as is to the handhelds screen res and see
how nasty it is. or if the dialogs even fit :)
So I look forward to these emerging devices where I can leverage a
large and fully functional existing codebase for a change (the
desktops,
rather than the handhelds).. having to reimplement chunks for every new
device is what makes all us handheld developers wish to kill ourselves,
too :P