Jump to content

Adam Kiss

Moderators
  • Posts

    1,303
  • Joined

  • Days Won

    7

Everything posted by Adam Kiss

  1. Hm, another abandonware by me ^^ D'oh! It was 2.3, I've just finished this module and like few days later Ryan introduced in the core. Darn!
  2. +1, Dash is absolutely awesome stuff.
  3. Hey all, long time no hear! The Ace Editor it's kind of abandonware at the moment, since I've been working with different platforms lately (like mostly ruby and print , but I'm planning to look into the module, it's support of pw 2.4 etc, and I've got some more ideas. Will see. Thanks, Adam
  4. Anyway, I think using page.id in selectors isn't anywhere in documentation, and it's actually probably much better than custom PHP code (just because I don't have to have any PHP code in DB)
  5. Thanks Ryan, seems that it is again that part of year where I have to revise what goes where in my PW installs
  6. Hey all, I am developing some custom Process modules for a website, and in those i'm including_once some files. Now, I didn't want the editor to have all the unused parts of website (users, modules, etc.) in his user interface, so I created limited role, and added to both the editor and administrator same permission, which was then used with the Process module. public static function getModuleInfo() { return array( 'permission' => 'internal-tools' ); } But what's curious – and I can't think of why it happens – is that it seems, that when the module is loaded, different roles (users) have different path set up as CWD(). For admin, it's: /.../www.domain.com/site/templates/ For editor, it's: /.../www.domain.com/ Now, I can simply not use relative path to include file, but rather a realpath/dirname(__FILE__) combination, but I am not sure whether this is wanted behavior, or some kind of mis-setup I did. Any thoughts are welcome.
  7. There seems to be no simple way to use pages children with the Page field. Only solution seems to be the custom PHP code, but that limits the inputfield options. I would think that this kind of usage for "featured" children is more common, but alas, I was wrong. Is it possible to add this?
  8. Hey all, I have a quick (?) question here. I am using prepend/appendTemplateFile in my config for site's header/footer. When using URL segments, I throw 404 Exception for non-existing URL segments, which is all well. The problem is, that at the moment of 'throw new…', there already is one page header rendered, and the exception renders it again for 404 page. Is there any way around this? Thanks. Edit: require_once for the append/prepend files solves this, so I opened issue on github: https://github.com/ryancramerdesign/ProcessWire/issues/282
  9. Something about knowing only a hammer and nails comes to mind.
  10. So if I want to use stable Localized page names (mind you, not latest, but stable and ready for production), I should go for the dev, right? (2.3.0 has localized page names marked as 0.0.3 – not Ready f/ Production)
  11. Hey, Arimo a has webfont version on Google Fonts, released under Apache License v2.0, so it is redistributable. You can also download it
  12. Ryan, how can I leverage (what I assume) stable version of Language Support – Page Names from dev? Should I just drop /wire/modules/LanguageSupport from dev branch to production? Thanks
  13. Just a blind dab – don't you have something like text-transform: lowercase; in your css?
  14. While it served as a good wake up call for me — I'll look into semantics and specs a bit more, for sure — i can't really stand some of the articles arguments, such as the button example; and what bothers me most is how quick the author is when dismissing opposing opinions, because 'he personaly never seen such situtation', and, judging by his companys references/his dribbbles, there's much more of what he hasn't seen than what he has seen.
  15. More alive… Well. I don't know, whether it's because of the icons, or because the are no boxes/lines/backgrounds that would reinforce the masonry grid, but it feels that articles all over the place, without any sense of order. I think your homepage would benefit from more strict grid, or if you really want something unusual, come up with it manually. In any case, I'd force a bit of order on the items. On the other hand (to offset this at least a little), the spacing between items is just perfect on mobile. Other small things I noticed: on the Projects page, the images are little decoupled from their respective items. I understand this is a result of some internal "no item backgrounds" rule, but it's weird. Maybe adding a 'no-screenshot' thumbnail to all items would help a little. Also, on iPhone, the header as something like doubled right margin then left margin. But also, the fonts look even more fabulous on teh mobile. I commend you on that selection again, I really like the general typography.
  16. I passionately hate the logo, but I commend you on the font selection, especially of the blog articles, reads very well, even when it's in non-native language and I'm quite tired. Good work. Also notes regarding layout: I'm not sure masonry sits well with your homepage, not to mentioned the small github/twitter badges flying all over the place.
  17. Edited. Good luck with your restoration. Adam
  18. What a waste of perfectly fine domain for german processwire group – recruitment agency, bah! Nice work though, thumbs up. Except the logos. The resizing sucks.
  19. It isn't, not with 'vanilla' PW. But there are already some modules that can give you this – search http://modules.processwire.com/ and it's pretty simple to roll your own. In case you want to build micromodule for yourself, to learn a little, do following: - create textformatter module – you'll add it to the textarea (before md parsing!) - comeup with some combination of letters not naturaly used in text - capture the text - find correct picture for it - replace the original text with pictures URL done. When I did this last time (can't share code due to licensing issues, but it was fun to build it nevertheless), it took something like 20-30 lines to do it (excluding PW's module structure), so… pretty simple.
  20. I'm not really a fan. The background is very 90s, and the semitransparent red looks very vomit-ish. For something slightly less subjective, you seem to have very little saturation contrast, i.e. everything is very desaturated. Try to throw in some white and at least one more saturated color (preferably something important), it will probably work better.
  21. Interesting… I have exactly zero unused designs from last two years, I think.
  22. I'm using 2.2.9 ATM, but I'll update ASAP. Thanks Ryan
×
×
  • Create New...