horst

Hi all, I want to present a preview of my new Portfolio. Actually I'm unsure with some points and the images aren't the final ones and other pieces aren't finished too. But the look is ready and maybe it would be good to get some feedback from the critics here ;-) The site actually runs on PW 2.3 stable, the used modules are: ImagesManager ImageMinSize Thumbnails FieldtypeTextUnique Minify I have disabled direct access via .htaccess to portfolio-images that resides in the files folder. Thumbnails and images related to infos and news can be accessed directly, all others have to use a proxy page I have build as PW-template. With the ImagesManager I initially have created my six categories (albums) and manage all uploads. Via a hook into ImagesManager on upload I'm able to rename the original images and create 3 variations (600px, 900px, 1200px). Also I stripp all Exif and IPTC data from them but populate them with the minimal needed IPTC data. That way I never have custom related infos in the images, neither in filename nor in metadata. I use serverside mobiledetection and also JS to detect viewport dimensions. This should be used to serve images that fit best to devices and viewport dimensions. But it isn't ready now. The layout / design is done from HTML5 boilerplate. There are no frameworks or thatlike used / needed. But there is heavy use of Javascript (jQuery-Libs: Swipe, Stapel, Flexslider), but the site also runs completly in noscript mode. Also the single-image-view in NoScriptMode lets you loop through the gallery and displays the content scrolled down to the image if needed. (That's one of the advantages of old veterans that have build html-pages during browser war 1995/98 ) All critic, suggestions etc is welcome: http://pw4.nogajski.de/

Hi everfreecreative, you have done a very good and useful write up here. Thank you very much. I want to drop two notes / suggestions / additions, - maybe. I also don't want to upload single images to single pages - but if you once have the need for a more scalable Gallery, you may use Somas ImagesManager to manage the creation of your gallery categories ( = albums) and to do the mass-upload by e.g. selecting up to 50 images at once and drag-drop them onto the upload field. (I don't know if IM supports upload via Zip's) Very good to support noscript, - but personally I don't like the opening in additional browser windows. You also can include a "single image view" to present the single images. With this, a visitor stays in a single window when browsing your galleries and doesn't get cluttered with mass _blank-windows. - But that's only _my_ preference. Many Greets. EDIT: hmm, - yeah, - I have had to do a phonecall during writing the post, - so now Soma has already pointed you to it

http://www.google.com/search?q=caldav+php+client So, you also don't need a fully client, - you only want to read, not to write. https://github.com/DAViCal/davical/blob/master/inc/caldav-client.php

DB-Host often should be simply localhost Also if your provider allows connection from the outside, (not all do that), you should use / prefer the term localhost if possible, because you avoid dns lookup for every DB-query! Results in better performance!

Hi Billy Koch, there are also some threads existing which cover relevant things to userpages / communitysites and that like. There are also code examples or strategies on how to implement things best. So, you have to look around for this and some existing modules and have to put together found parts to become your desired site / module. And like Matthew already said, if there is a part you need help on, ask here ...

Oh, I've found a sponsored version: kongondos avatar was dressed up by: Beechfield, Amazon & brille-24.de If you want sponsoring on your own, here is the photoshop-file: kongondo_avatar_dress-up__psd.zip

Oh, Kongondo! TFFM :: ToFastForMe

Hi joshuag, Sorry, I wasn't very clear, but you first have to klick [edit] and afterwards [use full editor] or how ever it sounds, and then, (I swear!), you get it.

Soma, your maths is good! - only it has to result in images that all fit into the viewport. I think, one has to decide which is the max landscape ratio image dimensions and which is the max for portraits that one want take care of: 2:1 for landscape and 2:3 for portraits, for example, than one has to calculate the area(s) for the smaller (?) one of them (depending on viewport) so that they fit into it. After that, one has to calculate all images that are between 2:1 and 3:2 that they get close to that area. Extreme ratios get smaller, but this ones are rare. This is a linear solution! This may lead into small and poor looking images on large canvas, so one have to find something between the linear equivalent version and one that takes into account the single image presentation and shows landscapes in a landscape-viewport a bit larger, and portrait-images in a portrait-viewport a bit larger.

Ah, ok! Hhm, yeah, that's exactly the point what I meant with it is shown in the second screenshot: ---------------- Yeah, and what can be done when images are (pre)loaded and the user resizes the window? Good question. Til now I have only the solution to use some javascript to keep track of viewport-sizes and imagesizes, and if the viewport resizes somehow smaller it's ok, just display images smaller too. But if it changes orientation extremly or switch from a small window to fullscreen, puh, I have to reload! But how to reload only the images that needs to be displayed larger than the first downloaded version, I haven't solved it yet.

My problem is exactly that I don't want serve, for example, all images with a max width, because then an image with 2:1 is three times larger than one with 2:3, or has double surface area of a square image. So it appears to be much more important than the smaller displayed ones. What I need is a formula that calculates the equivalent surface area depending on the viewport for different images. For example you have three images w x H A 3000 x 1800 px B 2300 x 2300 px C 1500 x 2000 px the max useable viewport is 600 x 600, how would you calculate the new dimensions for the three images, so that they all fit into the viewport and have all a equivalent surface area?

Hi Alicia, welcome to the forums. maybe this can become usefull: http://processwire.com/talk/topic/3748-cms-critic-now-powered-by-processwire/page-2#entry36867 All that other stuff you are talking about, I don't understand enough of.

Hi everyone. I'm coming to an old thema of mine. When it comes to present different sized and different orientated images on screens, it is always a bit frustrating. Maybe most time (on desktop) there is a landscape oriented widescreen, on which you can show a panorama image (2:1) very large but that it fits into the viewport. If you want to show a square image (1:1) you only have the half (content/amount?) of surface area. (The image only has half superficial content). And if you want show a Portrait (maybe 2:3) this image is somewhat more smaller displayed than the square one. So, I'm searching for some math that calculate dimensions depending on a equivalent superficial content and depending on the available viewport. Puh! But maybe it also shouldn't be a (technical) linear one. when downsizing the panorama to an equivalent, it looks a bit poor, alone in the viewport. For example, with the width and height of an image one can create a superficial content number: 100 is a square, 200 is a 2:1 and so on: 1:1 = 100 5:4 = 125 4:3 = 133 3:2 = 150 2:1 = 200 Is there anybody on the forums who can build a elegant maths formula for that? Or there are other suggestions, thoughts to that?

@RyanPierce: you may have a look to Hanna Code

<not-serious>Good luck! </not-serious> Did you know Somas ImagesManager? It could be an option, I think.

Hi Adam, great! I have just downloaded and installed it on a local site. And it feels very well. Thank's for sharing it. I have noticed a little issue: Notice: Undefined variable: nav in W:\WEB_MIRRORS\_ProcessWire\pw3d_BETA3\htdocs\site\templates-admin\topnav.inc on line 7 and a missed, (but not needed file I think) Warning: include(_gravatar.inc) [function.include]: failed to open stream: No such file or directory in W:\WEB_MIRRORS\_ProcessWire\pw3d_BETA3\htdocs\site\templates-admin\default.php on line 113

in addition to pwired here http://processwire.com/talk/topic/3785-alternative-syntax-for-control-structures-a-tip-for-newbies/#entry37007 http://processwire.com/talk/topic/3691-tutorial-a-quick-guide-to-processwire-for-those-transitioning-from-modx/?view=findpost&p=35953 http://processwire.com/talk/topic/3754-proof-of-concept-processwire-admin-theme-switcher/?view=findpost&p=36621 http://processwire.com/talk/topic/3785-alternative-syntax-for-control-structures-a-tip-for-newbies/?view=findpost&p=36950

Ovi, not much time, but when Anttis code isn't a module and "class CommentFormWithRatings extends CommentForm" why do you doesn't extend Anttis class? class OvisCommentFormWithSorting extends CommentFormWithRatings and then you have there a public function processRatingInput() { that call parent::processRatingInput(); and then do your stuff ? So, completely untested, but its like I understand the OOP System from PHP 5x, what is relative new to me, so- maybe I'm wrong.

Hi SteveB, here is a thread that covers some of these, also it includes a usefull code-snippet from Luis, http://processwire.com/talk/topic/3359-quickly-setting-up-fields/

Hi Luis, weird thing! I have tested a bit with PW Version 2.3 stable, and it seems that PW and PHP also does a right job. But MySQL could be wrong. I have created a float field and it works as you have described, but also when trying to save 10000.11 it store and retrieve 10000.1 !! But to be short, I have tracked the action until to PW saves the value: "INSERT INTO `field_test_float` (pages_id, data) VALUES('1109', '10000.11') ON DUPLICATE KEY UPDATE data=VALUES(data)" After that, I have looked into that field with a MySQL-Editor and it stores 10000,1 and not 10000,11 (When you use 10000,16, it will result into 10000,2) So, after that I have manually edited the field in the MySQL-Editor, typed 10000,11, save, refresh, and voila there are only 10000,1 in it ! It's definitely a MySQL-thing. But I haven't found a solution, only some posts on stackoverflow and mysql datasheets that I do not understand http://stackoverflow.com/questions/4520620/float-precision-problem-in-mysql http://stackoverflow.com/questions/2160810/mysql-whats-the-difference-between-float-and-double http://dev.mysql.com/doc/refman/5.1/en/storage-requirements.html

I cannot say something to the design (background, font, etc) because I have not enough knowledge of these things, but the color combination has at least not enough contrast: http://leaverou.github.io/contrast-ratio/#%23C6DF9F-on-%23BD7254 (So, you don't need to get a green ratio with that tool, but orange would be better)

Oh, that's good! Very kind, Ryan. So with the locally used PW-Version every works fine in PHP 5.2 and 5.3. When I switch to the last PW-DEV-Branch it only works with PHP5.3 (AddHandler php53-cgi .php), but with PHP 5.2 I get this Parse-Error: unexpected T_PAAMAYIM_NEKUDOTAYIM in /htdocs/wire/core/Modules.php on line 241, (but I also have installed all modules again). With the last stable PW-Version I don't get this Parse-Error in PHP 5.2. and everything works fine. If you are interested and want look into this you may do, but for me it is pretty fine to go with the stable Branch. If you want to look into this, you can switch PHP in first line of htaccess, and there are three wire folders to switch between versions: wire.dev, wire.orig, and wire (the last stable). I don't need to use this installation because I have setup allready a second one that I can use. So if you want you can do with it what you want.

@Matthew: I never would tell regular users the admin-login url. I would use different doors!

Hi totoff, very nice design, (luftig!). But sorry, no bugs found! only a little typo in Dritttrimester, in $page->name it is with double t in PageHeadline with double t and in BrowserTitle, Submenu right and in all other text it is with triple t.

@Ryan: I have done a big mistake! I have exported the wrong DB-Version. I have local setup pw3b.host.local with DB pw3b pw3c.host.local with DB pw3c and it should be pw3d.host.local with DB pw3d They are different Branches of the same site. But I can't remember why and when, I have switched pw3d.host.local to work with DB pw3c instead of 3d. I'm so sorry that I have wasted your time!