Thanks for the replies.
I'm aware that the Jquery UI is needed during administration/editing but my site does not need it when being viewed by the general public.
Part of my brief for my current site is to keep the number/size of the files loaded on page load to a minimum especially as the site is to be targeted to mobile devices. As I mentioned the Jquery UI takes up a large proportion of the resources loaded so having the option not to load it would be great. I know it only gets loaded the once but my client will still ask why such a large file is being loaded when we don't use it 99.99% of the time.
I also understand that the default.css file defines the look and feel of the DNN Core but it too gets in the way when skinning the look and feel of your own skin. I'm sure I'm not the only one to have come across this. Deleting the content of the default.css is not really the best approach as you then have to duplicate those definitions in your own style sheet. Plus a DNN upgrade would put the definitions back.
For instance why does the DNN 7 default.css file define the look of my p, h1, h2, li, ol, hr tags. So now I have to override those definitions in my own style sheet which increases my workload and increases the file sizes.
In my humble opinion the definitions in the default.css file should only be used to define the look/feel of the core and my own style sheet should define the look/feel of the actual site.
I love using DNN and these are 2 inconveniences that I am currently fighting with
Thanks for listening and keep up the good work
Tony