Jump to content

felix

Members
  • Posts

    214
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by felix

  1. Hehe, indeed - it is working now. :)

    I have a small critique about the boxes on the home page, specifically the ones at the bottom left of the image. I think it's because of the font width that the text is slightly hard to read over the darker portion of the image. Obviously, it is readable, but there's a small amount of strain there.

    I also see that there's what appears to be a language switcher at the top right. Will there be any new languages in the future?

    Yup. It was a problem with the apache vhosts :/

    You're right. It's hard to read. I'll check if we can adjust the transparency or add some text shadow to make it more readable.

    Yup: sgh is operating internationally so there will be an english version in the future. 

    Btw: Thanks for all your feedbacks. They're really helpful!

    Edit:

     

    Hi Felix,

    very nice site, though - as a designer - I'm a bit unsure about the very strong "boxiness" of the design. Do you know what I like about your postings apart from showcasing great sites? They give proof that webdesign as a business isn't dead!   ^_^

    Good work!

    Hey totoff, The "boxiness" is part of their corporate design. I think it's a matter of taste rather than an issue. I personally like it a lot though it has some drawbacks when doing a responsive design (same/fixed height & width boxes are really hard to implement in the way they are used within the site as the content needs to always fit in because you aren't allowed to vertically expand the box).

    Webdesign as a business is getting harder and harder as you need clients who understand it's not enough (for them) to buy a (mostly awesome looking) wordpress template for 50 bucks. I don't think "Webdesign" is a dying profession but it's shifting from developing "websites" to developing app like information systems that are device and context agnostic. I really like the direction Mozilla is going with it's Firefox OS and it's freshly released developer browser and hope the "web vs. native war" will get more equal as web technologies like webrtc, webaudio, webgl, ecmascript 6[...] evolve and are well supported across all devices. In my opinion it would be a big loss if the openness of the web is interchanged with closed ecosystems like apples or microsofts. But this is propably worth it's own thread :)

    • Like 2
  2. Felix I really like this one. It's clean, yet vibrant, and then so easy to use. Great stuff! :)

    Thank you!

    Hi Felix

    I get fed up of liking your showcase posts - you keep doing really nice websites! :)

    Can you do a terrible one so I don't feel forced to like it?

    I'll ask the next customer if we can do an ugly site for them. I'm sure they gonna agree. Will keep you updated! ;)

    • Like 1
  3. Another processwire relaunch made by neuwaerts: The Website of the Shopping Mall "Galerie Luise" which is located in the center of Hannover, Germany.

    The mall was recently bought by one of our customers, accom (whose [interims]website is also powered by processwire and launched some weeks ago) and needed some refreshment in terms of design, marketing and strategy. As a result we've created a slightly adjusted logo, a new claim, new print materials and a shiny new websites which mainly features upcoming events held in the galerie luise.

    http://www.galerie-luise.de/

    • Like 14
  4. As I've mentioned in this thread there is quite a bunch of websites that we (neuwaerts) are launching these days. 

    Today i present to you: sgh-net.de. SGH is a german specialist for business process outsourcing (i.e. they scan all of your incoming paper mail and make it available digital or take care of your companys invoicing) . The website features plenty of (css)3d and large imagery stuff to play with. Sadly there is no english version yet. Have fun exploring and thanks for your feedback:

    sgh-net.de

    • Like 4
  5. There currently is an issue with the "Template Data Providers" Module which prevents variables that are set within the "dataprovider" files (controllers) are accessible in the template later.

    The module works like this: For every template you create a file that handles fetching and manipulating data (doing "business logic"). The files look like this:

    <?php
    
    class HomePage extends \nw\DataProviders\PageDataProvider {
    
    	public function populate() {
    
    		$this->foo = 'bar';
    
    	} 
    }
    

    foo from there should be available as $foo within the template. This worked until 2.3 but seems to be broken now.  

    The module Hooks to beforePageRender and executes the populate() method where the variables are set:

    https://github.com/marcostoll/processwire-template-data-providers/blob/master/TemplateDataProviders.module#L147

    I tracked down the issue to the core module "PageRender" ( https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/modules/PageRender.module#L305 ) where $page->output(true) is called and creates a fresh copy of the Page object. At this point all variables that were added get lost because they aren't persisted.

    Any Ideas how to avoid this?

  6. Hey owzim,

    this is exactly the reason why i don't want to completely replace the render method (plus i honestly don't know what would happen if the method is replaced not only by one but several modules).

    I'll start a thread asking if it's possible to make the variables persistent in the module development board.

    • Like 1
  7. Actually beforePageRender doesn't change any output or replaces vars. It just adds data to the page object. So imo there should be no need to replace the default render method.

    I tracked the problem down to the Core-File "PageRender.module" (line 305) where output = $page->output(true); gets called. $page->output(true) returns a new, uncached TemplateFile object which is filled with a fresh "Page" Object via $fuel = self::getAllFuel(). So if there would be a way to permanently store the variables set inside the hook (I've tried using setFuel('page',$page) but that didn't work) this would be fixed. Any Ideas?

  8. Hey owzim. I'm glad you like the module. We're still using it in all of our projects (but as I've already mentioned combined with TemplateTwigReplace) so it has to be maintained further even if it's only for our own projects.

    I'll look into this issue and try to do my best in the next days. Sadly marco (who is a great software engineer - a lot better than me) isn't working for neuwaerts anymore but if I can't resolve this issue by myself I'm sure he'll help us fix it.

    • Like 3
  9. Diogo: this check won't work in chrome as it reports beeing touch enabled always (no matter if the device itself supports touch or not).
    You might want to have a look at detectizr which is an add-on for modernizer that detects the  device, device model, screen size, operating system, and browser details and (like modernizr) adds the respective classes to the html-tag so you can use them for your touch/non-touch handling.

    • Like 3
×
×
  • Create New...