apeisa

What about offering stable releases as a zip downloads (I think tagging offers this on github), and giving latest dev simply from github master.

InputfieldSelector is the query builder. PW now has Selector fieldtype and inputfield in a core. That means you can add it to any page, and then you have it's selector value available in your templates. There it is reasonable simple to use that selector to build table and pagination for that data (maybe using jquery datatables and like). I don't think Lister has been develop at all front end in mind, so while it might be possible to it offer a "public view", I am not sure if it's good thing (it is obviously already quite a complex module). I think it could easily end up for something that views is for Drupal, and I remember I never learned that tool (it probably is huge productivity boost for those who can handle it)... InputfieldSelector of course misses the "columns" part, ie. choosing which fields to show. You cannot have it all.. or can you?

Finland for the win! Litmanen is the king!

What does js console say?

https://processwire.com/talk/topic/529-where-did-you-find-about-processwire/

Marvin, great idea! I think one of the big challenges in offering that kind of service is, that usually things that go into cron, really needs to work. So using your service in own application creates high dependency on your service. While minimize.pw just leaves images uncompressed when not available, having missed cron jobs is a big problem. Other than that - API looks great and yes, very often hoped for a functionality like that. Not sure if I would be willing to tie any business critical jobs to 3rd party service though, instead of building own cron jobs..

It opens lots of interesting possibilities (thinking especially Hanna codes and the likes). Oh, and seems to be very smooth implementation!

No, naming modules ProcessXxx doesn't move them to core tab. You probably saw it in core tab if you had it in wire folder first - module information gets cached. Also filename and classname should match. In your case ProcessReadCsv.module and class ProcessReadCsv

Jordan, in a bit hurry, but just wanted to quickly comment: very well said about in what position PW is regarding "heavy content" vs "easy editing". I think the best route will indeed be on building simpler tools to provide different tools on top of core, just like owzim said. I am happy to hear what kind of ideas you have regarding Fredi and making simple sites even easier for editor? Before I build Fredi, I played a lot with "real" live editing. That is easy for text and textareas, but falls short when trying to support all the different field types that PW has - and that is definitely one of the key selling points for PW.

100 fields is no problem. It seems though like a project that would gain great benefit from ProFields.

The one and original (reason for the shop module to exists): http://www.martanpuoti.fi

Hard to blame sysadmins only though. It's complex issue, involving developers and companies also. OT: I think one of the reasons I don't have much interest in mobile apps - lock in to hardware and os. Happy to see most new apps seem to be hybrids, where only small part is native (nav + webview).

I think you have file field instead of image field.

Usually few screenshots helps a lot too.

Ah, I had to browse code to grasp what it does. Now I get it (wohoo!). After understanding the code, readme makes totally sense First I understood only the field parsing part... Btw: I think the docs are pretty clear, it was just me taking own conclusions too early.

Teppo, why is this Inputfield instead of textformatter? Or am I missing something?

I have simply decided not to care about IE6-7 since two years ago. Living much happier life now

I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

Nik - PageTable supports @ convention.

So epic It just nickname we have been calling Ryan here at Avoine office. I mentioned that to Ryan and since then it has been his member title. For Finnish people Reiska is quite a traditional nickname and most famous Reiska is indeed Remontti-Reiska, who has been celebrity (also popular among ladies) here for a long time. I agree with Teppo, he represents only the finest values - not anything God like here though, but maybe our dear neighbors at Estonia sees him as a god I'm just giggling here for the idea many people googling and wondering about that strange connection

Create separate shared include file or class.

I love the idea for your module!

Are you running latest stable?

PageTable is new kind of fieldtype, coming in 2.5, but already available at dev branch. I think it has best parts of page and repeater fields combined. It allows creating and editing linked pages in modal, without leaving the page you are actually editing.

Can, not directly answering your situation, but have you seen the ProFields and the Table fieldtype there? If not, take a look: https://processwire.com/talk/store/product/10-profields/ Also PageTable field that ships with core (available on dev branch) might be great alternative (it does use pages, but it's much more "lightweight" in terms of UI compared to repeaters).