Hi. My name's Ryan (rjhughes on the trac).
I've submitted a couple of patches in the last week or so: (#1484816, using keypress instead of keydown to allow repeat) (#1484806, an option to allow strftime formatting)
But I've got a feature I'd like to work on: Currently, it shows you 40 (or whatever your pagesize is) messages, and if you scroll to the bottom of that list and wnat to see the next messages, you have to click the "next page" button.
I would like it to put placeholders into the table for all your messages, so that you can just keep on scrolling, and it will load your messages on demand. I would like this to be available as an option.
I would like to know which branch I should be working on -- the trunk, or devel-vnext? Here's the tradeoff:
It would be easier if I didn't have to do a whole bunch of merging to get it to vnext once that goes live. HOWEVER, if vnext is considered so experimental that it's going to be 5 years before it comes out, then it would be much easier for me to just merge it into vnext at some time.
So: Which branch should I do this work on?
Thanks. --Ryan _______________________________________________ List info: http://lists.roundcube.net/dev/
On Sun, Mar 2, 2008 at 11:38 PM, ryan@iheartryan.com wrote:
Hi. My name's Ryan (rjhughes on the trac).
I've submitted a couple of patches in the last week or so: (#1484816, using keypress instead of keydown to allow repeat) (#1484806, an option to allow strftime formatting)
But I've got a feature I'd like to work on: Currently, it shows you 40 (or whatever your pagesize is) messages, and if you scroll to the bottom of that list and wnat to see the next messages, you have to click the "next page" button.
I would like it to put placeholders into the table for all your messages, so that you can just keep on scrolling, and it will load your messages on demand. I would like this to be available as an option.
I would like to know which branch I should be working on -- the trunk, or devel-vnext? Here's the tradeoff:
It would be easier if I didn't have to do a whole bunch of merging to get it to vnext once that goes live. HOWEVER, if vnext is considered so experimental that it's going to be 5 years before it comes out, then it would be much easier for me to just merge it into vnext at some time.
So: Which branch should I do this work on?
Hey Ryan,
first off - thanks for your patches. We really appreciate it!
I am skipping right to your last question - after 0.1-stable is out, we'll work on merging devel-vnext (which is a bit broken right now) into trunk and then continue from there. That's a lot of work, but it only needs to be done once.
I know, not the best (or most satisfying) reply ever. But this is what we are working on.
Cheers, Till _______________________________________________ List info: http://lists.roundcube.net/dev/