I finally started a Cheatsheet for ProcessWire2.1+
Now it's also on processwire.com (auto fetching it from git)
http://www.processwi.../api/cheatsheet
The github project page:
http://somatonic.git...WireCheatsheet/
And there's the git repository:
https://github.com/s...sWireCheatsheet
I'll continue to add or remove things as times goes by. At some point this will get converted to a PW App.
02.06.2012:
- added with $input->urlSegments
- added support for GET param in url to &filter and set &advanced
- added support for hash in param to filter section
06.02.2012:
- updated urlSegment($n) description to avoid confusion
- remove some of the alternative syntax
17.12.2011:
- added new section "Files" to the sheet
- minor structuring of some advanced entries
08.12.2011:
- added fix to menu when scrolling
- moved some entries to advanced mode
- added toggle button on sections
- minor changes
04.12.2011:
- some restructuring, adds and removes
- minor tweaks overall, typos, ordering
- added "advanced" mode
27.11.2011:
- Added index collumn on left side
- You can now toggle sections using the index
- Also toggle show/hide all description of a category when clicking on blue titles.
- It resets all if you click in the table somewhere (in white space)
ADVANCED mode:
Mainly it started with only "System Configurations" being advanced, but I added many of the more advanced functions overall. I don't know if it really is the thing to go, but I thought why not try to have very simple and basic version so it would fit on a matchbox . So they're my guess on to what would be the more advanced stuff, and I had kinda hard time to decide what to do and how. After long back and forth I decided to just give it a go and see what people think.
Filter
I noticed that in mozilla, the live search filtering wasn't working after the changes i've done to it. I figured mozilla has no innerText, which is very practical to get content of a node but not subnodes. I had to use textContent, which returns all text including subnodes, so the search filter doesn't work as good as in other Browsers. May I find a way to work around it.
*Found that restructuring the markup was the only way to solve this problem. It should also now work much better in FF for the live search.
---
Bug reports, feedback and suggestions are always welcome. Hope you like it!