Natara User Forums: Bonsai Beta Tried On Htc Hd2: Bugs And Performance Issues - Natara User Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Bonsai Beta Tried On Htc Hd2: Bugs And Performance Issues

#1 User is offline   yurkennis 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 125
  • Joined: 04-May 06
  • Location:Moscow
  • Devices::Treo680
  • OS:WinXP

Posted 29 May 2010 - 07:07 AM

I had a chance to try Bonsai on a HTC HD2, today's top-performing(?) WinMo device. I compared my experience with Palm Treo 680 which I still use very intensively.

First of all, when used with a large (2M) outline, WinMo Bonsai is much faster compared to Palm version--at least in some of the mainstream scenarios. It is very responsive in: applying filters (for both selecting 3% or 70% of items); browsing an outline tree back and forth with a filter applied; adding items when simple filters applied; indenting-outdenting items having no childrens.

However, there are many issues that don't allow even a top performing WinMo device to compete with old good Palm Treo 680 at the moment.
I marked with (!) the items that are stoppers for me in moving from Treo to HD2.

Functional bugs
1.(!) When outdenting a branch, its parent item gets duplicated: the parent item alone stays at the original position, while the whole branch also appears at the outdented position.
2. Sometimes, new record / new sibling creates an item but that item immediately disappears if it's not allowed by a current filter. Ideally the new item should be displayed without deactivating a filter for existing items--until a filter is re-applied (when the new item should disappear).
3.(!) With some filters, new records/new siblings are created but not displayed even though fit the filter applied.
4. For Item details multi-screen window, switching screens with a menu doesn't work--i.e. screen is not changed.
5. In some cases, copy/paste doesn't work for items/notes text (i.e. not for whole items and branches).

Performance issues
1.(!) When unlocking a device (with Bonsai active last time), it frequently takes about 8 sec before I can work with an outline.
2.(!) Outdent of a branch with 10 items in it takes 20 sec when 3% filter applied, intend of the same branch with the same filter takes up to 10 sec; move up/down of the same branch -- 13 sec.
3.(!) Collapse a branch with 20 items in it takes 8 sec when 3% filter applied.
4. Indent/outdent and move up/down of a branch with 10 children in it takes up to 4 sec when 80% filter applied.
5.(!) When activating/deactivating on-screen keyboard, it takes 1-2 sec of waiting when 3% filter is applied.
6. Splitting an item takes 4 sec with a 3% filter applied.

Usability issues
1.(!) An active item frequently disappears from the viewport when opening an on-screen keyboard (and effective screen height reduces). It then takes an extra effort to bring it back to the current window.
2.(!) For note editing, a full-screen mode would be much more usable than a single-line(!) text field under an outline.
3. For Item details multi-screen window, custom font size is as needed as for outline tree / notes window. Alternatively, font size is better nearly as large as menu. This is especially critical for editing notes, until the previous issue exists (i.e. single-line notes editing).
4. Support for HTC's suggest / auto-correction would definitely rock.
5. For some multi-line items, when I select an item (i.e. make it active and edit-mode), the item changes its height (as the text is re-flowed slightly differently)
6.(!) For Note column, an icon/empty space would be much more usable than True/False currently displayed.
7. Smooth scrolling of outline tree similar to HTC's Start Menu would be fantastic, but that's really about polishing.
8. View setting menu is very condensed, it takes half a minute to hit the right arrow / to select (and activate editing) of a right column width field. And of course, drag-n-drop of column widths would make it much easier to work with.
9. Zoom in/zoom out with a multifinger gesture would rock :-)

Some notes:
* everything was experienced with a 2M outline (desktop-side file size)
* the outline was always in HD2's internal memory, not on a flash card
* "3% filter" above means that out of total 1000 items in outline, roughly 30 are active with this filter (i.e. only 3% of items active)

On-screen vs physical keyboard?
I haven't finally decided whether I will choose HD2 or a WinMo device with a physical keyboard when WinMo Bonsai is ready for prime time.
From a day worth of using HD2, it feels like it's more productive to type and command with a physical kb. Interested in hearing others: anyone managed to be as productive with onscreen kb as you were with a physical one?

Thanks!

This post has been edited by yurkennis: 29 May 2010 - 07:36 AM

0

#2 User is offline   yurkennis 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 125
  • Joined: 04-May 06
  • Location:Moscow
  • Devices::Treo680
  • OS:WinXP

Posted 02 June 2010 - 06:57 AM

Could someone from Natara please comment which of the above issues will be very likely resolved before WinMo Bonsai is released from Beta as a stable product?
0

#3 User is offline   Richard Murphy 

  • Natara Staff
  • PipPipPipPipPipPipPip
  • Group: Developers
  • Posts: 1291
  • Joined: 26-January 05
  • Gender:Male
  • Location:Naperville
  • Devices::T-Mobile Dash, Dell Axim X51v, iPaq rx3715
  • OS:Win7 x64, WM6, WM 2003SE

Posted 02 June 2010 - 01:22 PM

I cannot make any promises, but I would like to try to resolve the functional bugs, assuming I can reproduce the issues. I understand the performance issue and have something in mind to help resolve sluggishness when Bonsai must do a full refresh. Until I implement the change, I will not know for sure if it will resolve all of the reported issues (but I would think it should).
As for the usability issues:
2. The note area is resizable. Try to tap and hold near the bottom center of the splitter bar. It was very hard to do with a stylus, so it might be near impossible now using your finger. I know using the splitter on touch devices is not a good idea...
6. Should be changed before final release.
I need to see about the other items.
Richard Murphy
Natara Software, Inc
http://www.natara.com
0

#4 User is offline   yurkennis 

  • Member
  • PipPipPip
  • Group: Members
  • Posts: 125
  • Joined: 04-May 06
  • Location:Moscow
  • Devices::Treo680
  • OS:WinXP

Posted 02 June 2010 - 03:10 PM

Thanks a lot, Richard--I'm never looking for promises, but on your informal opinion on what of the above seem to really matters. No obligations, I absolutely understand you as work in a similar SW dev co.

Looking forward to more of your comments. And I am ready to help with reproducing any of the issues reported.
0

#5 User is offline   skenop 

  • Junior Member
  • Group: Members
  • Posts: 16
  • Joined: 29-October 09
  • Devices::Tungsten E;TX
  • OS:XP

Posted 18 June 2010 - 07:44 AM

I have not become adept at the on-screen keyboard for any handheld apps, Bonsai or otherwise. I really figured that after using my Tilt2 for a while, I would look back on my affection for the Palm OS handwriting recognition with amused condescension. But I was wrong. I still think it (Graffiti *1*) is far and away the more efficient input mechanism. A distant second is a hardware keyboard, which is what I primarily use now of course. The on-screen keyboard only becomes desirable for one-handed operation, and it is still very tedious.

Your performance item #1 is definitely a factor in neglecting my outlines. I definitely miss the old days of one button press on the palm instantly opening my outline. Too bad I depend on my phone for other things and cannot just leave Bonsai active all the time ;)

All I can say at this point it, I appreciate having Bonsai available on some platform that is relatively current, and now that I have invested significant cash into Windows Mobile, I am not in any particular hurry for it to be ported anywhere else (except implementation of sync to the cloud, but that has its own risks). If I were to choose a new one today though, I would say Android. Need to add my vote to the poll...

This post has been edited by skenop: 18 June 2010 - 07:45 AM

0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users