From: webERP D. <web...@li...> - 2013-07-06 12:15:39
|
> I've started to have a > go at this transition to HTML 5 Great idea Phil. > I think there may well be some issues with input type="date" There are a lot of good sites discussing browser compatibility and incompatibility and I'm sure people have their favourites. I found this site is a good one for quickly checking if html5 or css3 is supported in any particular browser - so I'm still careful with what I use of HTML5 and CSS3 on sites. http://caniuse.com/ Cheers, On 06/07/2013, at 12:45 PM, webERP Developers <web...@li...> wrote: > > OK - it seems obvious this is the way to go .... I've started to have a > go at this transition to HTML 5 > > http://www.weberp.org/wiki/TransitionToHtml5 > > I think there may well be some issues with input type="date" with > respect to multi-language/date formats so I don't propose to go that > route just yet... datepicking in Firefox 4.01 doesn't work for me > either. I doubt there will be many using older browsers than me! We have > the nice little date picker already which isn't too bad. > > Anyone who fancies a go at a couple of scripts then that would make > light work of it - just cross them off the list when you've committed them. > > Phil > > Phil Daintree > Logic Works Ltd - +64 (0)275 567890 > http://www.logicworks.co.nz > skype:daintree > > > On 06/07/13 09:07, webERP Developers wrote: >> By the time you have all the plugins required - this does increase the >> burden considerably and I am rethinking this whole idea in view of good >> comments from Exson and Kalmer. I am not sure it is worth it with jQuery >> - I know we have been around this a few times now - I will research html5... >> >> Phil >> >> Phil Daintree >> Logic Works Ltd - +64 (0)275 567890 >> http://www.logicworks.co.nz >> skype:daintree >> >> >> On 05/07/13 20:30, webERP Developers wrote: >>> the problem is that one cannot put jquery plugins into single scripts if you >>> have not loaded them in the header. >>> >>> But also, one does not want to load all js for all scripts, if the plugins >>> are not needed there. >>> >>> . >>> Therefore, it is good if an ndividual script can ask weberp to add something >>> to the header, for example, as web2project does. One could copy their >>> functionality. >>> . >>> Then I can use jquery for manufacturing and BOM, whereas someone else who >>> does concentrate on something else can use an individual js approach. >>> >>> And each script would only load that js that is actually needed. >>> >>> Klaus >>> >>> >>> >>> -- >>> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Intention-to-roll-up-new-version-and-future-plans-tp4656547p4656558.html >>> Sent from the web-ERP-developers mailing list archive at Nabble.com. >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Web-erp-developers mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Web-erp-developers mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |