Jump to content

Mike Rockett

Members
  • Posts

    1,452
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by Mike Rockett

  1. Okay wait - ignore my previous post. It does actually work (where you use the skin name first, and then the root-relative path to its folder), but it won't load because the following URLs are forbidden (403):

    /site/modules/InputfieldCKEditor/skins/office2013/?t=E6FDskin.js

    /site/modules/InputfieldCKEditor/skins/office2013/?t=E6FDeditor.css

  2. Hi Mike - does this help: http://stackoverflow.com/questions/17863112/ckeditor-move-skins-folder-somewhere-else ?

    I think that link is saying that using just / instead of using all those ../ will get you to the root of your site so maybe something like /site/modules/InputfieldCKEditor/skins/office2013 would work.

    Hi Pete, unfortunately that doesn't work... It just uses two slashes somewhere in the middle of the path...

    wire/modules/Inputfield/InputfieldCKEditor/ckeditor-4.4.3/skins//site/modules/InputfieldCKEditor/skins/office2013

    See my post below. Also, I didn't realise before that you had to specify a skin name before the path. I tried without it, and it gave my the result as striked-out above.

  3. Greets :)

    I'm using the dev-build of PW for one of my sites (obviously will upgrade to 2.5 when released).

    I'm not a huge fan of the default CKEditor skin, and would like to use the office2013 theme instead.

    How would I go about doing that?

    Update

    I have tried adding a skins directory in site/modules/InputfieldCKEditor and loading the skin via config.js, but it looks for the skin in the wire/modules/Inputfield/InputfieldCKEditor/ckeditor-4.4.3/skins directory... Any way to change that?

    Update (again)

    This works, but isn't so elegant:

    ../../../../../../../site/modules/InputfieldCKEditor/skins/office2013

    Surely one could make it so that it looks in both the `wire` and `site` directories for skins?

    • Like 3
  4. i'm going to start a new project on processwire. shall i start with 2.4 or wait for 2.5? i read on the news section that 2.5 is very much around. maybe i should wait?

    In agreement with everyone else - start with the current dev. That's what I'm doing for two sites I'm busy building. When it's released, it's simply a matter of 'upgrading', as Ryan said.

    We're aiming for soft launch this Friday and official a week later. Tried for last Friday but still had some issues to resolve + waiting on some things. I believe it's safe to start using now, but you'll still want to upgrade when 2.5 is official.

    That's fantastic news indeed!

  5. Very nice site indeed, and clean too! Simple always works best. :)

    With regards to Affix, it doesn't seem to be working for me, in any browser. I'm running 1366x768, and there's definitely enough estate for it to become fixed when I scroll (also, no bookmarks bar, and I'm using the small taskbar on Win8), but that's just visually-speaking. When I go fullscreen, it works. Most people use 1366x768 (laptops), and so I'd suggest making some kind of an alteration to make it work. Perhaps if you make Affix ignore the "Modify Search" heading, and only do the block beneath it?

    I'm busy building a site for a charity, and found myself in the same place with the home page slider - I'm just using repeaters, as they really are efficient.

    Edit: If you decide to use repeaters, be sure to set your image field to only accept one image. Then, when you call it in your template, you still need to call the first() method, like this:

    <?php print $slide->your_image_field->first()->description; ?>
    

    I'd like to make one comment with regards to the design: it feels almost too Bootstrap generic. If it were my site, it would be inclined to, at the very least, change the font, heading colours, and the bullet-footer (perhaps you could scrap the indent, remove the bullets, and split each link with a thin, light line). There's also a 1px white line at the bottom - I would definitely remove that.

    That said, the site, as it is, is very friendly, and easy to use - so kudos for that. I would only make the changes as the Bootstrap look is too generic - at least for me anyway...

  6. I'm not going to make too many comments about responsive design at this point, and only because I haven't fully ventured into it myself (I'm only building my first fully responsive site on PW now...) That said, I do think it's a good idea. I'm based in South Africa, and it seems to be the trending thing with all modern designers. In addition, even my clients in Cameroon want their sites to be responsive.

    Otherwise, I do like the sites, @muzzer. One nit to pick: On the Uncharted Wilderness Tours site, it says "About Us page" in the footer. The word "page" should not be there. I am very sure that was a simple oversight. Yes?

  7. Does seem a tad slower though... Loaded up in just over 6 seconds this time around. Then again, yesterday's results were also a bit jumpy. First test was under 5 seconds, second test was as I mentioned before, and the third test was over 7 seconds... Nonetheless, load times are good enough, the way I see it. :)

    • Like 1
  8. @diogo - I see, great stuff :) Works great.

    In terms of speed, from here in SA, an initial complete reload took 5.92 seconds over 34 requests, including render-time. DOMContentLoaded (before assets) was 1.41 seconds. :)

    • Like 1
  9. Quite an interesting site, I must say. Love the fact that it's just different. :)

    With regards to the font, all my browsers are rendering just fine. The issue at hand is with regards to DirectWrite. If it's turned off, it doesn't look so good at all. But, as stated already, it should be on by default now, so the majority of Chrome users will see the correct rendering.

    With regards to the grey button, that's a silly IE thing that Redmond has never, ever bothered to change. Alternatively, it's the order of your CSS rules. By that, I mean that you are declaring a color for all buttons after you're declaring them for the menu in particular. Still, that seems to be an IE thing, because no other browser has an issue. I think adding !important to the rule for the menu button should fix it. I know, using that flag is bad. But sometimes, you just gotta use it anyway, because it does its job.

    I find it quite interesting that you chose to use a strike-out on the bottom menu links when viewing a page. Any particular reason why you chose to do that?

    • Like 1
  10. Very nice site :) I just have a few nits to pick from a user experience point of view:

    1. The top menus' anchor tags do not fill to the size of their menu blocks 
      <div class="mymenu bn block">...</div>
      

      This means that I have to click on the actual anchor link.
      Whereas, you did this with the menu on the left, making it easier to click on each item. (Only thing I noticed with the left menu is that the anchor tag for "Luxury Honeymoons" goes past the length of the black parent container. Oh, and these links also don't seem to show which one is currently being viewed, i.e a 'current' class.)
       

    2. Same concept with the Top 10 drop down. I should be able to click on any part of that, instead of just the drop down arrow.
       

    3. I think more work could be done with how the site responds to different screen sizes. As soon as I scale down my browser, or use the device renderer, everything starts overlapping everything else. Unless, of course, you did not intend for the site to be responsive, which is what I've gathered.

    Despite this, I really do like the simplicity and usability of the site. It isn't overly complicated, and anything you need to click on is shown to you straight away, which makes it a friendly site.

    Kudos! :)

    • Like 1
  11. Indeed - it is a great site. very nicely built.

    Must agree with Philipp here. In fact, there are several images that are too large. Sure, they're not all 2.3MB, but they're a tad too big.

    May I suggest that you have a look at this article for more information on how to work around this:

    http://www.smashingmagazine.com/2014/02/03/one-solution-to-responsive-images/

    The article makes reference to these as well:

    http://www.smashingmagazine.com/2013/07/08/choosing-a-responsive-image-solution/

    http://adaptive-images.com/ (this looks quite promising)

    And perhaps a loading indicator? Changing the title to "Loading..." was not easily noticeable for me; perhaps some people have slow connections/latency may question if a page is even loading.

    Otherwise, I like it! :D

    • Like 1
  12. In a nutshell, I moved away from other systems and started using Bolt, due to its custom content-type-driven system. There are some features that Bolt lacks, some of which are not planned to be implemented as yet. Specifically I was interested in a hierarchy set-up, with content-types.

    That's when I stumbled into ProcessWire (not for the first time, I might add - I had seen it before, but the styling turned me off for some reason). When I did, I saw a new website, and an amazing admin-theme, which won me over pretty darn quickly.

    My first site in PW is for a Cameroon-based company, called AEG & Partners. For my first attempt, I'm quite proud. It was really easy to put together, and very straight-forward when it come to building custom modules.

    Glad to say that, at this point, I won't be looking back. :)

    Edit: Oh, and Ryan, I did pop an email through with regards to the showcase link - it doesn't have a thumbnail... Was my image incorrectly sized?

    • Like 1
  13. I love this - it's such a unique design, something I really appreciate. :)

    Going to +1 the scroll-with-touch-pad problem, and I think it's worth mentioning that it's quite jumpy on my touch-screen as well. It's probably a missing-link with regards to my resolution, which is 1366 x 768. When I drag that main slider up/down, it jumps a little, every now and then. Tapping the arrow, however, obviously creates a smooth effect.

  14. Hi, and welcome cwsoft :)

    I'm also pretty new around here, having fully switched to ProcessWire a little over a month ago. I, too, came from various different systems (PyroCMS, SilverStripe, WordPress [yes, also forced ;)], Typo3, and Drupal). PW has really done a good job at melding everything together in such an elegant, and simple, fashion.

    So yeah, welcome to the club :)

    @renobird: I can't wait for 2.5 - going to give the dev branch a try today. :)

    • Like 1
×
×
  • Create New...