Jump to content

Nico Knoll

PW-Moderators
 View Profile  See their activity

  • Posts

    1,835

  • Joined

  • Last visited

  • Days Won

    21

 Content Type 

Everything posted by Nico Knoll

  1. Nico Knoll
    Why would you want that? Btw.: Why not just using $page->id ?
  2. Nico Knoll
    I think it's better to put this post in the Wishlist?
  3. Nico Knoll
    Love this. I could give you some kind of category especially for this on processwire.tv?
  4. Nico Knoll
    Looks great
  5. Nico Knoll
    Like what?
  6. Nico Knoll
    He probably used the default one. I didn't make the site. They had another company doing it for them.
  7. Nico Knoll
    Not sure if anybody else could have said that better in this objective way. <3
  8. Nico Knoll
    Well I think the best way to learn ProcessWire is to just use it for a site. When I started using it I directly build a site with it and learned most of which I had to know about it in that time (back then when there was no multilanguage and PW 2.2 (or even 2.1?) was the hot shit) Site looks nice Only change I would suggest: make the sidebar at least 220px and not only 150px. It looks a little ... pressed
  9. Nico Knoll
    No they don't. I did a lot of websites within the last 3 years using ProcessWire and everybody loved how simple and intuitive the backend is for them (they only see the page tree). I was never a big fan of the old admin backend. But I fell in love with the new Reno theme so me and my clients loving the backend now. P.S.: My father's corporation website is made with WebsiteBaker and he never liked it. But he likes ProcessWire backend.
  10. Nico Knoll
    @peter: I think that's a point we already had. Because there is somehow a misinterpretation of the word "user" in this whole topic. The user is the end customer, the person who is going to use processwire to add/edit content. And yeah processwire is user-friendly in that sense But a user is not the person who programs the website (as long as it isn't for himself ). That's the programmer/coder/designer/whatever.
  11. Nico Knoll
    Sorry to interrupt but I finished another version of "GetStarted". I like it a lot more then he version before and got rid of the tooltips. Texts are copied from wikipedia and not final. What do you think? GetStarted2.zip Edit: fixed a minor install error.
  12. Nico Knoll

    I WANT YOUR VOICE!

    Nico Knoll replied to blad's topic in Jobs

    @blad: Why not making the hard-cut version of the video first so we could throw some ideas in if something is missing and doing the voice stuff afterwards? Thanks for making this anyway
  13. Nico Knoll
    I think I may get rid of the tooltips and just going to add those textboxes like on the "home" site to "fields", "templates" and "pages" with a short description what it is ad how to create it. It shows until you hit the x (each textbox would get it's own x) or uninstall the module. On the bottom of each of those textboxes I would add a "read more" link to the docs page of the specific topic. So you would have kind of a little instruction but it wouldn't be as annoying as the tooltips. What to you think?
  14. Nico Knoll
    @NorbertH: Feels like home here
  15. Nico Knoll
    Working on it
  16. Nico Knoll
    I think you don't have to comment each line. Just group them up and put the comment above the group. Only if it is something special you should an additional comment next to the line. Anyway nice work!
  17. Nico Knoll
    Maybe it's some kind of forum virus?
  18. Nico Knoll
    Thanks Only have to hide the tooltips again afterwards and do some more fine-tuning
  19. Nico Knoll
    Inspired by the pdf I made a little proof of concept welcome page + guide through how to create a field, template and page. Check it out: GetStarted.zip Edit: Updated it.
  20. Nico Knoll
    Well my idea for snippets.pw was including two different types of "posts": "snippets" and "receipts". Snippets: Snippets would be really short code blocks including maybe 1-2 descriptive lines and inline comments. But mostly the pure code. Receipts: Receipts would be a little more advanced. They would first explain which "ingredients" (fields, templates) are needed. Then show the code with more description. At the end you would see the results as screenshots or as html code. So this post type is more like a tutorial. --- After talking to LostKobrakai and marcus about this it appeared that they had slightly different ideas about this. But I think I would be fine whatever way we go as long as something helpful emerges. And as long as I can put my 2 cents in
  21. Nico Knoll
    Gonna mention it again: We're working on snippets.pw
  22. Nico Knoll
    Made my day
  23. Nico Knoll
    Found it. it was JSON related. Working code: if($this->input->get->render != 'JSON') $event->return = $event->return.'n';
  24. Nico Knoll
    Hey, I want to show some html code before PageListRender (on the "pages" list page in the backend). I created a module which hooks into "ProcessPageList::execute". Works fine. HTML code is added. But the page list won't load anymore afterwards.... So is there a better way to do this? Or another function I could hook into? -- Nico
  25. Nico Knoll
    @woop: Thanks for taking the time to do this - it's amazing and I think you're right in each of your points!!
×
×
  • Create New...