Call Me Back (MODx Revolution)

Quote from: ReSpawN at Dec 27, 2010, 10:22 AM

Each request has a db scheme that holds the name (which is a required field), a data field, properties, updated, created and state. In the data field you can enter all that you need to read back in the backend. By control of lexicons you can translate and extend your own form field.

Isn’t it possible to extend it with custom tables instead of all in the one data-field...
I’ve the background to extend the plugin with some more data like time-tracking field, pricing, etc. to get a real support-system.

Could you elaborate on that? Are you talking about another 3PC, Plugin or Snippet that can be controlled via such as system?

Quote from: ReSpawN at Jan 11, 2011, 10:20 AM

Could you elaborate on that? Are you talking about another 3PC, Plugin or Snippet that can be controlled via such as system?

hm, no. I initially thought about extending your addon in future to a more flexible puwerful system. I only thought you might should think about this while developing.

Smooth, I’ve already got two other projects lined up. I’m not going to tell you what they are because then I need to start asap! The only thing I can say, is that one of them is a support tool that can be used by the local bakery or a hosting company. I’ll let you fill in the blanks.

Quote from: ReSpawN at Jan 11, 2011, 12:15 PM

Smooth, I’ve already got two other projects lined up. I’m not going to tell you what they are because then I need to start asap! The only thing I can say, is that one of them is a support tool that can be used by the local bakery or a hosting company. I’ll let you fill in the blanks.

Okay, this is great to hear!

Finally had some time to finish up some of the more pressing matters, which allowed me to start working on CMB again!

The custom fields have been programmed in and they allow for great customizability! It’s almost a shame that this 3pc is gonna be so small.

The following screenshot shows a custom grid with the custom fields provided by the database row itself. Now, since it is a grid, it takes on every field and merges it into a stack. The biggest disadvantage is, that if your one record has 3 custom fields and the other has 10, the grid will show 10. Now, I am going to build in some more configuration for you to disable showing (hiding as it were) the fields you don’t want showing up in your grid.



And as you can see, the database model for MODx looks a bit different.


I hope you guys like it!

That looks great!
Perhaps I didn’t get the point but why is Db scheme different to normal modx scheme?

btw: If you need someone for e.g. German translation, I’m in. Is the project on github?

No, I’m an idiot when it comes down to GitHub. I’ve tried it several times and I still couldn’t figure it out. Local or remote.

The DB scheme is ONLY for CallMeBack, so in that sence, of course it is different. Perhaps you mean something else?

Quote from: ReSpawN at Jan 17, 2011, 11:35 AM

No, I’m an idiot when it comes down to GitHub. I’ve tried it several times and I still couldn’t figure it out. Local or remote.

The DB scheme is ONLY for CallMeBack, so in that sence, of course it is different. Perhaps you mean something else?

So, basic setup for git / github is really easy. If you want to, contact me via PN.

And as you can see, the database model for MODx looks a bit different.

You wrote that. And I understood it like your CMB DB scheme is different to MODx one’s. And because of that I wanted to know why... erhm, don’t care about. Not as important. Think I misunderstood.

It was meant as a simple representation of how many fields there are in the grid and how many there really are in the db scheme. Which proves the existance of configurable fields.