Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

futurepixels.co.uk

Members
  • Joined

  • Last visited

  1. So, I have nearly finished my site. I have not transitioned to HTML5 as of yet as I am waiting for a bit longer to use it. However, I have added CSS3 to my site at the moment. My question is this: Should I be using CSS browser hacks i.e: - moz-transition , -webkit-transition , -o-transition to allow the design to look the same across browsers OR should I just use transition and wait for the browsers to catch up with the standards (Even though its not finalised yet?) I always put them in the order of - moz-transition , -webkit-transition , -o-transition, transition as I know that this is how CSS is read, but I have to validate without and then add the hacks after. It is time consuming and a royal pain. This is generally the reason for not using HTML at the moment, but want to. But at the moment I feel that the web is at a weird standstill at the moment and a with lot of mixed reviews on how to use CSS2, avoid CSS3 and HTML5. Value of the community if very much appreciated and would like to know your thoughts.
  2. Unfortunately, as much as I hate it, 80%+ users are windows based, & then a large percentage of them use IE7+. The way I design, use a base design for all browsers so the layout works, then add your HTML5/ CSS3 styling then jQuery if you use them on the site. A great style framework: Blueprint and once you get to grips, to customise the size: Custom Blueprint. I hope that helps. As bad as it sound, treat your users as if they have a windows machine with ie7 or ie8 as the lowest version which has poor performance. remember, you can have a show/hide element to say something like the following if lower versions of IE8 are found: "Sorry, but the site is optimised for IE8+. It will still work but with less enhancements."
  3.    Ben Evans reacted to a post in a topic: CSS3 causing browser speed issues
  4. Hi, One thing I would suggest is try to lay off the CSS3 for a major part of the site. If I am right, you are using a lot of reflections & shadows. I really like what you have done, but you have overloaded the screen with shadows, reflections and font effects from my point of view. You have to remember that browsers render the page an the viewers machine, so if someone with a slow machine & slow connection start to load your site, they are gonna leave before it is loaded, & if the page jumps it will have the same effect. I hate being negative, but the problem about looking pretty is that if someone is looking at your site to purchase or do business with you there is a chance they could be put off by the site. I've seen this so many times. CSS3 has still not been rolled out 100% & always remember that every browser implements web standards differently. The only one that does it to the specification is Opera, the others including ie8+, Safari & Firefox do it to how they think. As good as they are they still don't follow the specification. So, keep the CSS3 in there but try to minimise the text effects, gradient effects, shadows & reflections. Be subtle with them to make an impact, detail is the key. Hope you find this positive & not an attack.
  5. I am creating a pub site with food/ drink menu's. I am trying to make it as efficient as possible. I have it set up roughly like this: SELECT * FROM MenuList FOR EACH MenuList RESULT { <li> SELECT * FROM MenuCategory Category_1 SELECT * FROM MenuItem WHERE MenuList = MenuListID AND MenuCategory = MenuCategoryID FOR MenuItem { SHOW MENU ITEM DETAILS } Category_2 SELECT * FROM MenuItem WHERE MenuList = MenuListID AND MenuCatagory = MenuCatagoryID FOR MenuItem { SHOW MENU ITEM DETAILS } Category_3 SELECT * FROM MenuItem WHERE MenuList = MenuListID AND MenuCatagory = MenuCatagoryID FOR MenuItem { SHOW MENU ITEM DETAILS } </li> } This will show like this: Main Menu (MenuList) Starter (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) Main (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) Dessert (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) Special Menu (MenuList) Starter (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) Main (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) Dessert (MenuCategory) Item1 :: Description1 :: Price1 (MenuItem) Item2 :: Description2 :: Price2 (MenuItem) Item3 :: Description3 :: Price3 (MenuItem) My only issue is having a select statement for each item within the category. As I have them within <li> elements for the whole menu list's, I'm using jQuery to hide all <li> apart from the first. As it is self manageable, the client can add as many menus as possible. So, the risk is, if they create 10 menus, but with 6 categories & 50 items within each Category, the SELECT Statement within each Category could add up to 1000+ sql statements for the one page. My basic question after all that: Is there a way to split the sql statement by categories and show items via each split. If this makes sense, please could you help. Like I said, it works well but I don't want performance to be an issue for the client.
  6. For OS X - Billings App (MarketCircle). A great app. Has everything. Even an iPhone version.
  7. I use Money (Jumsoft) along with Billings App (MarketCircle). A winning format. Both have an iPhone version too which is a bonus. Edit: OS X versions are the ones I use.
  8. These were my general thoughts. I usually design by HTML/PHP - to - CSS - to - JS. I find the order works well. I just need to stick to that & stop listening to other people. Cheers guys. Liking this website.
  9. I've used it in the past for mobile versions of the sites I've created. Plus I've been playing with CSS3 and played with the browser sniffing to use HTML5/ CSS3 for browsers which use it or jquery for old browsers. Hope that helps?
  10. When I create static websites, I use jQuery for a bit of flare. But when I write Web Apps, like my admin panel I'm creating for dynamic sites I build, jQuery is used for more than a bit of flare. I like to use a back up plan in case the user has JavaScript disabled. However, what is the general opinion with JavaScript. Do you build a site that if the user has this disabled then they can not use the site or just that they have limited functionality. Or are you the person like me where you worry about everything working with or without JavaScript? Creating this admin panel relies on JavaScript a fair bit & I have but a <NOSCRIPT> tag in place that when they open the page it tells them JavaScript must be activated. -- Is this arrogant programming? Or should I cater for people who have JavaScript disabled?
  11. Hi, I'm in a debate with myself & someone else in regards to user friendly design. My site works well so far with the CSS disabled & the Javascript disabled. But, I was looking at doing a one page site as I've read articles describing this as better for SEO. I was originally going for the idea of a basic jQuery show/hide and each page (home/portfolio/blog/contact) would be held within there own DIV. The next idea would be to have a control page & use Ajax to call each page, but this does not sit well if the Javascript is disabled. Could someone help. Do I use standard pages or one page with the jQuery show/hide?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.