Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by GLWalker

  1. This is what I did to the existing category infoBox on my build to give it the styling it has. This is very close to what we need to obtain a horizontal menu, just have to make sure the whole damn tree is exploded on initial load.


    $OSCOM_CategoryTree = new category_tree();
      $OSCOM_CategoryTree->setCategoryPath($cPath, '<strong>', '</strong>');
      $OSCOM_CategoryTree->setSpacerString('  ', 1);
      $OSCOM_CategoryTree->setParentGroupString('<li class="list-group-item nested"><ul class="list-group selected">', '</ul></li>', false);
      $OSCOM_CategoryTree->setChildString('<li class="list-group-item">','</li>');
      $data = '<div id="bm-cat" class="panel panel-default">' .
    		  '  <div class="panel-heading">' . MODULE_BOXES_CATEGORIES_BOX_TITLE .			  '    <button type="button" class="infoBox-toggle" data-toggle="collapse" data-target="#bm-cat-body">' .
     '	  <span class="sr-only">Toggle Navigation</span>' .
     '	  <span class="caret"></span>' .
     '    </button>' .
     '  </div>' .
    	   '  <div id="bm-cat-body" class="infoBox-collapse collapse">' .
    		  '    <ul class="list-group">' . $OSCOM_CategoryTree->getTree() . '</ul>' .
     '  </div>' .

  2. Categories box will be staying as a side column infobox until someone codes up something else (eg a good horizontal menu)


    If anyone has time to study over the new category_tree class - maybe they could find the key to making a horizontal menu - Ive tried various things, and been able to generate a full list of everything, which is what needs to happen. But the list is not nesting properly. It outputs as so:


     <li>Category Name 0</li>
       <li>Category Child of 0</li>

    When it should be:

     <li>Category Name 0
      <li>Category Child of 0</li>


    I've tried doing this by using the existing functions, and even extending the category_tree, but I believe on of the protected functions is preventing me redoing the nesting. Anything but touching the actual class file :)


    Unfortunately I have no code examples of what Ive done to post, as when things get so far, I like to just start over fresh. However Tomato Cart uses the same category tree, though it has been slightly modified, and they have also extended the class to get their horizontal menu working, it can be seen at their demo site here: http://demo.tomatocart.com/


    Their class file can be seen here:


  3. Heres where I'm at, all controlled modularly. These are infoboxes which look different in the footer and normal if in the side columns. Thoughts ?


    I am in desperate need of some payment icons (vias, mastercard, paypal) which must be GPL or MIT license and distributable. Anyone got any or know where to get some?


    I like it. I changed some classes on mine, so it now looks different in the footer than the side column.

    The account box in yours is something I think is needed.


    I was also thinking a simple text box, which the store owner control's by way of the modules language file. This makes it modular, yet also easily customizable without a lot of markup.

  4. All, I am particularly interested in viewing examples (for inspiration) of what you view as a good/great footer area (of any ecommerce website).


    Speaking of which, any interest in a footer module area? I added a call in the infoBoxes to select footer, and then a short jQuery wrap function to help keep the widths identical to the infoBoxes in the left and right column.




    In my example I have information, best sellers and a new banner box. You'll notice that the banner spans the area that would normally fit 2 infoBoxes. When the banner box is loaded, jQuery picks up on it and changes the col-md-* class. However, if the banner were to be loaded in left/right column then it would just fit like any other infoBox -( of course the banner would need changed to one made to fit there_.

  5. http://wsfive.com/bs-master/index.php



    so far, more in the works.


    header search form, language dropdown, currency dropdown, and navbar greeting are all done using a function, just place a simple call in and show it.


    Planning to do the same with the shopping cart.


    By the time the header is filled up, there wont be many infoBoxes left to display!

  6. @@burt

    So this is doing away with the product_reviews_info page? That is really not needed anyhow.


    I like how it is looking, but would recommend just stacking the reviews as a list, and add an anchor text using the review ID. Then when viewing just a specific review from the main reviews page, (if applicable) the product_info page, the anchor id can be appended to the url so it lands on the proper review.


    I think pagination could become a problem unless a function were wrote that figures the exact page based on the number of reviews for that product divided by the page results setting?

  7. I was playing around with the bootstrap collapse classes, following along with navbar-collapse. I redid them and and applied to an infoBox and it works out very well with no change in any javascript functions.


    So if you go into a smaller viewport the infoBox will collapse, just like a nave menu, leaving the button to open it the infoBox Content beneath.


    This may be a good way of saving room while still letting the user pick which content they want to see. I think it is better than applying a hidden class because the content still has to load even if hidden and this at least will let one see what loaded, while saving space.

  8. best_sellers <-- Very useful

    categories <-- Extremely Useful

    currencies <-- Needs separate function for plug and play use elsewhere

    information <-- Extremely Useful

    languages <-- Needs separate function for plug and play use elsewhere

    manufacturer_info <-- Needs separate function for plug and play use elsewhere

    manufacturers <-- Very useful

    order_history <-- Very useful

    product_notifications <-- Needs separate function for plug and play use elsewhere

    product_social_bookmarks <-- Needs separate function for plug and play use elsewhere

    reviews <-- Very useful

    search <-- Needs separate function for plug and play use elsewhere

    shopping_cart <-- Needs separate function for plug and play use elsewhere

    specials <-- Very useful

    whats_new <-- Very useful


    customer_greeting - - - needs a different position, like the header


    With that said I feel everything is already there in a box should just remain to appease those who want to use them. But the items I marked as plug and play functions, most can be fir into the header, or even footer, as you do find on a lot of sites. By plug in play im not really thinking of coding osc_template functions all over the header and footer, just writing a function and placing it where you want it to show.


    If anyone looks on my testing site I placed earlier, you can see a bit more what I'm talking about, though its generally become a scratchpad of ideas now and may or may not be broken when you visit it.

  9. Was creating some functions for use in header/nav-bar. I need a third eye on this:


    // return currency dropdown menu
       function tep_navbar_currencies() {
      global $PHP_SELF, $currencies, $HTTP_GET_VARS, $request_type, $currency;
      if (substr(basename($PHP_SELF), 0, 8) != 'checkout') {
        if (isset($currencies) && is_object($currencies) && (count($currencies->currencies) > 1)) {
    	  $currencies_array = array();
    	  while (list($key, $value) = each($currencies->currencies)) {
      $currencies_string .= '<li><a href="' . tep_href_link(basename($PHP_SELF), tep_get_all_get_params(array('id' => $key, 'text' => $value['title'])) . 'currency=' . $key, $request_type) . '">' . $value['title'] .'</a></li>';
     $currencies_link = '<li class="dropdown"><a href="#" class="dropdown-toggle" data-toggle="dropdown">' . TEXT_NAVBAR_CURRENCIES_TITLE . ' <b class="caret"></b></a>' .
    			  '    <ul class="dropdown-menu">' .
    		 $currencies_string .
      '    </ul>' .
      '  </li>';
        return $currencies_link;

    It works as is, but I am wondering if the hidden variables as found in the function to submit the select form of currencies, is necessary.

  10. http://wsfive.com/bs-master/index.php?cPath=3_10


    I believe this one is ready, I did a lot of tweaking and have tested on iphone and works well, even with two grids side by side.


    If selecting grid in mobile, it looks much like the new products module, but choose list and you get a few more details.


    Added 2 keys to ht_ module, default grid in desktop view and default in mobile. Use can select from 1 to four for desktop, and 1 or 2 for mobile.


    I'll be committing after I triple check it twice.

  11. @@Dan Cole , thanks for checking it.


    I think you may be viewing a cached copy - Im getting things to stack now in mobile grid.


    I think in actuallity, certian items in the grid need to just hide in mobile view, Im just trying to leave them all on to begin with.


    The price in list view, by default it would set next to the buy button, but I tweaked the css just a bit to show proof of concept that each element can actually be moved around to diffrent areas. It gives a lot of flexibility for when a shop owner wants to have a certian look. Every item is inside its own wrapper, which in part gives it the ability to be placed anywhere inside the thumbnail.


    I do agree that the mobile should be limited to just a single listing per row, but I'm trying to think ahead for that store owner who is going to insist that there be at least 2 products side by side :)


    It doesnt need to be set that way for default, but at least the inner workings can be there.

  12. I see the issues with double boxes in small viewport - and they can be remedied by changing the width in responsive mode, I'll put some fixes in for them shortly.


    I do agree that it is probably best to have a single display in small viewports rather than double, but depending how much is turned on to actually display, double could work out.


    A seperate class is used for responsive viewports, so its really very simple to change it to show 1 item per row. What may look good is to hide the switch for grid/list and keep it at 1 product per row.

  13. @@altoid Thanks for looking, but I havent touched the new products yet - it will be next if @@burt is hapy with the product listing module.


    I did notice that the new products display looks pretty good with the default layout in osc_template.php of columns set @ -2 and main content set @ -8 But when I change it to column @ -3 and main content @ -6 it gets the hanging cliff effect.


    What I wrapped around the product_listing layout will remedy that cliff effect.


    The css and such I used is not dependent on bootstrap, so it can be an osC exclusive :thumbsup:

  14. I took a copy of the Master, and placed it inline with changes to the product listings.




    Please report how it works out in different views, right now is set to use 2 product per row in grid view, this can easily be changed to show up to 4, and responsive view can also be seperately set up to show up to 4.


    This is only set up on the pages that use the product_listing module, not for the new products module.