> > > > My reckoning (based mostly on writing the wicket and restfulobject > > viewers) > > > is that it takes about 20 days' work to spike a viewer, then 50~100 > days' > > > work to complete the thing. > > How much work is involved in writing a generic client side RO based > > viewer. I guess it also depends on the technology being used. > > > > Reckon it's about the same. Maurizio ... if you're reading this, perhaps > you could keep track? > > I will, we estimated 60 days for the DHTMLX viewer.
Maurizio 2013/2/1 Dan Haywood <[email protected]> > On 1 February 2013 11:19, Minto van der Sluis <[email protected]> wrote: > > > > Looks interesting, are you offering :-)? > > I would love to, but I wonder if I ever get it finished due to time > > constraints ;-) > > > > I hear you! > > > > > > My reckoning (based mostly on writing the wicket and restfulobject > > viewers) > > > is that it takes about 20 days' work to spike a viewer, then 50~100 > days' > > > work to complete the thing. > > How much work is involved in writing a generic client side RO based > > viewer. I guess it also depends on the technology being used. > > > > Reckon it's about the same. Maurizio ... if you're reading this, perhaps > you could keep track? > > > > > > BTW what is the current status of RO upgrade from 0.52 to version 1.0. > > There was some activity on the ML a while ago, but it seem to have dried > > up. > > > > I've just written an article on RO for a journal, where I promised that > there would be work done on it over the next few months. So I guess I'd > better follow through on that.... > > Actually, Jeroen and I have this morning just hatched a plan where I'm > planning to do a little refactoring of some of the RO functionality to make > it more generally reusable (to serialize objects as JSON for publishing). > So perhaps as part of that I'll fill in some of the missing gaps. > > Cheers > Dan >
