> > > I am interested in something similar to the GTK client PDA mode in > Sao, which makes it better usable on small devices. Comparing Sao > including your patch [1] and the GTK clients PDA mode with a one column > table [2], both results looking quite similar to me. > The only difference is an implementation detail in using div vs. > table. Please correct me if I am wrong, but as long as the form view in > the GTK client uses a table structure as raster, it would be easier > to implement the Sao "PDA mode" similar as a one column table. > > IIUC the only implementation argument for div is that bootstrap needs > it instead of table tags. But in the actual incomplete development > state of Sao I can not see a benefit in having bootstrap and all its > complexity integrated. I am even not sure if bootstrap is the right > tool for ... for gaining what exactly? But I am not an expert. >
Bootstrap and all its complexity? The way I see it bootstrap actually brings simplycity and flexibility... > > So for me it would be more than enough for now, to make just the next > step, and implement the one column view for small devices in a similar > way the GTK client does. > With bootstrap as shown in the poc, there is no *need* to implement a Sao "PDA mode", look at the screenshots, it's already there. Someone mentionned an "intermediary" mode between regular and gtk... OK replace (in the poc src/view.js): 'class': (widget ? widget.class_ || '' : '') + ' col-md-'+colspan*ratio with: 'class': (widget ? widget.class_ || '' : '') + ' col-md-'+colspan*ratio + ' col-sm-'+colspant*ratio*2 and you have it > > Thank you for investigation and sharing your bootstrap POC! > You are welcome > >
