> > Reinier has indicated interest to include dependencies into 1.8. I > don't think it is likely to be included before that. I have begun
Correct. It would be nice to add it to 1.8. 1.7.x is bugfix only > "eating my own dog food" and I'm still finding small quirks now and Best way to test :-) > then. It would be great to have more people trying out the code before > actually merging it into the master branch. > > To answer your original question: I haven't found any major problems. > The bugs are mostly related to GUI updates which are fixed after a > page refresh, so I'll say it would be possible to have a bugfixed > version in a couple of weeks which could be a candidate for inclusion > in the 1.8 branch. > I'll try to help with the remove-code, but I'm currently struggling to find the time. If anyone else is able to help, please do. > Reinier: FYI I think the Z-order problem is "worked-around" by > rerendering the affected todos. > Ok. But it needs to be fixed though, because the arrows are floating above the menu bar as well. Reinier > Regards, > /Henrik > > > On Sun, Jul 26, 2009 at 11:18 PM, Benjamin > Fleischer<[email protected]> wrote: > > Henrik- > > When do you think you'll integrate the action dependencies into the > bsag > > repository? I'd be willing to help test it and send you bugs, but > right now > > I'm using the 1.7_ branch rather than the latest tar.gz. It sounds > like you > > have it minimally working. > > -Benjamin > > On Wed, Jul 1, 2009 at 6:49 AM, Henrik Bohre <[email protected]> > wrote: > >> > >> As Nicholas Lee suggested, the quickest way (until we get that > >> chained-actions input form) could be to enter a number of actions > and > >> then add the dependencies with DnD. > >> > >> BR > >> /Henrik > >> > >> On Wed, Jul 1, 2009 at 1:23 PM, Luis Villa<[email protected]> wrote: > >> > On Wed, Jul 1, 2009 at 7:07 AM, Henrik > Bohre<[email protected]> > >> > wrote: > >> >> I can see that there might be times that this could be handy but > there > >> >> might be a danger in entering a great number of actions in a web > >> >> interface before saving them (see > >> >> > >> >> https://www.assembla.com/spaces/tracks-tickets/tickets/907- > Automatic-refresh-may-destroy-ongoing-edit), > >> >> or complexity in creating some kind of background save. > >> > > >> > if your auto-refresh is set so quickly that you can't enter a list > of > >> > bugs during that period... you have bigger issues. :) (That said, > I've > >> > always though that was a bogus preference that should be dealt > with by > >> > js polling for new bugs.) > >> > > >> >> My spontaneous reaction is that it may be better to streamline > the > >> >> existing input form instead. > >> > > >> > The existing input form should definitely be streamlined, though > >> > admittedly I spent some time trying to think about that problem > >> > yesterday and came up with no good suggestions. > >> > > >> > But unless it auto-fills the previous action it is always going to > be > >> > a pain to enter a long stream of dependent actions, which is why I > >> > suggested a separate page for that. > >> > > >> > Luis > >> > > >> _______________________________________________ > >> Tracks-discuss mailing list > >> [email protected] > >> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss > > > > > > _______________________________________________ > > Tracks-discuss mailing list > > [email protected] > > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss > > > > > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
