> > > But how will they be aligned? > Both behavior could be possible depending on the implementation, once again it is an fairly good idea, nothing tested yet
> > |small| larger | larger |small| > |small| larger | larger |small| > | colspan3 |small |small| > | colspan3 |small| > > > That's the idea I have, now as I said, it needs implementing and > testing. > > Anf if it doesn't work, I guess we can use that part of the "resize" > > javascript already written > > I tested a lot of possibilities before writing the resize function but > all my attempt did not worked for all cases. The best test cases are the > party form, the invoice/sale/purchase forms. > As I said at the TUB2013, form me the resize method renders exactly the > same way as the GTK included the same glitch. > Right now, as you can see from the screenshots, I've done most tests using invoice form since it is probably the most complex one, I intend to keep doing taht. I'm pretty sure you've tested plenty of things, the difference here is that we can use a base of mixins done by professionnals and also I'm not better than you or anybody else but Nan-tic said they were willing to get involved and 3 people are smater than one (except when beer is involved but that's another story). So why not giving it a try but I don't want to waste my time either. > Also for history, we want to have the same rendering because we want to > use the same definition of the view (same XML). And we don't want to have > to test on both application to be sure it renders as we expect. And > finaly, we don't want to have to introduce hacks in the views to make > them works correctly and nicely on both application. > Who said anything about hacks? So if I understand well what you are saying. If xfill/xexpand work as intended and the interface renders on larger screens as it renders on the gtk client AND renders on smaller screens as it does in pda mode, the codereview replacing tables by div's would be included in sao? > >
