Jump to content

apeisa

Moderators
  • Posts

    4,629
  • Joined

  • Last visited

  • Days Won

    53

Posts posted by apeisa

  1. I have something simply to show if you guys are interested in this. Very simple stuff, three files:

    adminbar.inc
    adminbar.css
    adminbar.js

    [removed broken screenshots]

    There was already this modal variable on admin theme that stripped all the unnecessary stuff out, so I think something like this have been in thoughts before? Only bad thing is that after "Save Page" the modal state doesn't stay and it shows the navigation.

    I will keep improving this and it would be great to hear some comments & ideas.

  2. Edit: I mean, even if you look at this picture from Matrix plugin:

    config.jpg

    It really does resemble template creation :)

    It is true that you can achieve all the same results with pages & templates, but I think most important thing here is to make it easier for editors to create and manage the data. You can see the difference here:

    hero.png

    (That little plus sign on the bottom is important -> You add more "rows" easily when editing the page)

    But I also do not like that there is 2 very different ways to create same end result. So that is why I think that it would be better to allow creating & editing of other pages inside parent page.

  3. As far as I remember Matrix is more like "repeatable set of fields". So you could have template like "Football game" (soccer, not American ;))

    There you could have Matrix for different events:

    [table]

    [tr]

    [td]Minutes played[/td]

    [td]Event type[/td]

    [td]Player[/td]

    [td]Team[/td]

    [td]Details[/td]

    [/tr]

    [tr]

    [td]12 min[/td]

    [td]Goal[/td]

    [td]A. Peisa[/td]

    [td]Chelsea[/td]

    [td]Chelsea leads 1-0[/td]

    [/tr]

    [tr]

    [td]35 min[/td]

    [td]Goal[/td]

    [td]J. Litmanen[/td]

    [td]Ajax[/td]

    [td]1-1[/td]

    [/tr]

    [tr]

    [td]72 min[/td]

    [td]Red Card[/td]

    [td]A. Peisa[/td]

    [td]Chelsea[/td]

    [td]Peisa is out of the game[/td]

    [/tr]

    [tr]

    [td]88 min[/td]

    [td]Goal[/td]

    [td]J. Litmanen[/td]

    [td]Ajax[/td]

    [td]Ajax leads 1-2[/td]

    [/tr]

    [/table]

    And those fields (or cells) are not only text, but also images, files, links, relations, dates etc...

    This is ideal for situations where these are relevant data mainly for this template, they have to be easily updated etc. It would be really slow to create 1-20 different pages for every event for each game. I'm not sure if this is best example, but hope it makes this idea clearer.

    I actually think that it would be better (and maybe easier module and more in line with current way of building sites), if we could add/edit/remove other pages through editing other page. I mean if I have two templates: soccer_game & soccer_game_event. Soccer game template has page reference field for multiple game events. This reference field could have some pretty ajax magic that it would allow creating new soccer game events right on soccer game page. It would be so nice :)

  4. I am reading through source code and there is some syntax that is unfamiliar to me. First in templates there is line like these:

    echo "<li><a$class href='{$child->url}'>{$child->title}</a></li>";

    Why there is {} around properties? Does it have any function or does it only make code cleaner?

    And then at ProcessPageList.js there is lines like this:

    if(child.status & 1024) $li.addClass('PageListStatusHidden secondary'); 

    What does & at that line? I have a good guess, but I have never seen that syntax before so better ask than assume :)

    This probably isn't best forum for such a general programming questions, but it would really help me to understand what is happening under the hood (and of course learn some new programming at the same time).

  5. I created simple "Related pages" reference on default site. I noticed that if I choose something on Parent of selectable page(s) option, I cannot revert back to empty (which allows all pages with selected template to be chosen). If I choose "Home" then (rightly so) only first level pages are available.

    There is screenshot to make this easier understand. I think there should be "Reset to default" or something like that.[/img]

    post-79-132614277275_thumb.gif

  6. Thank for your replies. I am using Chrome (webkit), so this explains the differences.

    And yes, I think I should have ability to say thing like:

    "Bodytext field on my Basic Page template shouldn't allow images larger than 500 pixels"

    It's not nice to scale huge images smaller and huge images also tend to break layouts. Usually I never want to allow larger images than the width I have on my css.

  7. Hi

    Just installed ProcessWire on localhost and it seems to be very clean and polished! I remember that in demo video you showed easy resizing of images, but I cannot repeat that?

    I would be great if we could give maximum width for images (dunno which would be right place: image field or textarea field? Probably latter, since you could use same images in bodycontent and sidebar...), and ProcessWire would automatically process (hehe) images to right size. I tried to see if there is that kind of functionality already in place, but I didn't find anything.

    But so far I have been very impressed and I will probably try using this on some personal project as soon as possible.

×
×
  • Create New...