kongondo

Hi Knarf, Welcome to the forums. Unless you modify it, I don't think that's possible. Selectors get and find things in the db. Without a db, there's nothing to find/get . Are you storing your data in a file then? http://processwire.com/about/requirements/

Anybody used both Sublime Text and WeBuilder? I think I'd purchase WeBuilder over ST...(ignorant remark ).

Matthew, as usual, you provide a deep and eloquent response. Very helpful, thanks!

A description would be nice...what's included? Edit: Hmmm...Google says this is also on PB (plus other file sharing sites)...the description on PB (and elsewhere) talks about premium scripts....see where I am going with this? Can you please confirm? Thanks. If you are unsure, I'd suggest deleting the links until you are sure ...just a suggestion

Thanks for the tip Valery. You've given me ideas about something I'm working on Btw, I believe PW stores some of its data this way? E.g. data column in the modules table? I could be wrong.. I'd like to hear more thoughts about serialize actually...anyone?

Nice find pwired..

I like these two ideas Maybe I am under-thinking this but I but don't think these two ideas would be "very difficult" to implement? The main magic as I see it, happens in the default.php and topnav.inc (permissions check). See my proof of concept from a while back here..http://processwire.com/talk/topic/3754-proof-of-concept-processwire-admin-theme-switcher/ I would want the possibility to install multiple themes and choose which one to display. That's what I show in that post...If Admin themes were stored under "settings", changing themes would be a breeze.....Not sure how the upcoming theme switcher will look like though

Nice find Diogo! Thanks.

@Diogo, Thanks for the clarification. @As has been pointed out earlier, there will be varied opinions about this (reminds me of when MODX revo was deciding on a default theme ). I think I like the idea about an admin construction kit (although, now that I think about it, I fail to see how much different that would be from the present system since Ryan has pretty much followed a consistent method [e.g. jquery ui css classes] to build the default theme) that can be adapted to suit different needs. So, if we had these building blocks well-documented (i.e. what css classes affect what, where they come from, what the different PHP blocks do, etc) that will be your admin construction kit right there. But wait a minute, we already have this documented here by Ryan. Maybe improve on that? I don't know. Until I'm convinced otherwise (or catch enough sleep, whichever comes sooner ), I would continue supporting the minimal, no fuss default theme we have to be the default but make sure stuff like icons, etc. can be plugged in easily by those who wish to. Most of the changes we are discussing here are, after all, stylistic (CSS). Maybe the default theme needs a few tweaks.. A while back I was toying with the idea of creating a skeleton admin theme, a sort of admin starter kit. A simple black and white stripped down theme with heavily commented CSS , maybe with a few CSS options to move some stuff around, e.g. tree on left, tree on right etc but with the jQuery working as normal. As with many other ideas in my head...this remains just that...an idea

@Diogo, Maybe you'd like to clarify what you mean by "none of them worked well". I am not disputing your position, just pre-empting the inevitable question from others.."what did not work well?" {although Ryan maybe alluded to some of these above}. It will also keep this discussion going.

Oops! echo strtoupper($title); Corrected..

Works fine here... echo $page->title; // meine seite echo ucwords($page->title); // Meine Seite echo ucwords(strtoupper($page->title)); // MEINE SEITE echo strtoupper($page->title); // MEINE SEITE (btw) Edit: Corrected nonsensical code

FYI, Regarding sliding panels, sometime back I was working on an admin them with a top down slider/panel but never got to finish it...Here's the ugly screens....nowhere near Philipp's beautiful work

Uh, you forgot to type what the actual error says..

MODX also has always visible. I would prefer an option to always have it open or collapsible (not-open) - hidden like an accordion...I like the real estate offered by PW but sometimes miss the possibility to quickly get to a page on the tree

Btw, I think this thread is in the wrong forum? It should be in http://processwire.com/talk/forum/12-themes-and-profiles/ , no? At "worst" it should be in http://processwire.com/talk/forum/25-dev-talk/ but definitely not here (pub), me thinks I think there was a thread discussing this? Anyway, if one doesn't exist, feel free to start one by all means

Wow Philipp! Looking nice! Keenly watching this , thanks!

You learn something new everyday...thanks Antti and Peter

Peter, I think what Diogo meant to say is that this: $skip_trash = "has_parent!=$config->trashPageID"; could probably be (more efficiently?) replaced by this: $skip_trash = "has_parent!=7"; Unless Ryan has one crazy morning, the ID of trash will always be 7 <aside>Peter, any reason why you don't take advantage of the forum's inbuilt code highlighter? </aside>

I'm not sure, but I don't think you can only delete repeaters using remove() then saving? I could be wrong...

Bill, never mind...adrian beat me to it

Would this be of help? http://processwire.com/talk/topic/3619-updating-repeaters-via-api-without-removeall/

Yes, there's that as well... @Ryan...plans to upgrade jQuery to 1.9+?

Hi dhruba, Please try not to double post, thanks.

Ryan, Actually, you still have a couple of "live()" in various places in dev version: /wire/modules/Inputfield/InputfieldFile/InputfieldFile.js - 3 occurrences (lines: 10, 25, 78,) /wire/modules/Inputfield/InputfieldImage/InputfieldImage.js - 2 occurrences (lines: 3, 7) /wire/modules/Inputfield/InputfieldPageAutocomplete/InputfieldPageAutocomplete.js - 3 occurrences (lines: 122, 126, 194) /wire/modules/Inputfield/InputfieldPageListSelect/InputfieldPageListSelectMultiple.js - 3 occurrences (lines: 27, 30, 78)