Migx within another Migx

1.1661 s - Total time

Above is the time of the uncached page where i am using the above code 4-6 feels like something is seriously wrong. I would start debuging and removing stuff from page to really find out whats wrong.

I doubt the optimization head room lies in the MIGX itself.. because afterall whatever you do, your still using TV's..and those are the real loss. The optimization may lie in using MIGXdb instead of MIGX , which for a difference uses custom tables instead of actual tv's to store data in database. However the best option is imo still doing a custom component.. and completly avoid using TV windows. I don't want to hate on MIGX its brilliant idea, but i hate TV's and anybody who you ask, even opengeek will tell you TV's are not meant to be what we're using them for, and are imo the biggest downside of the MODX performance issues.

Quote from: yuka123 at Dec 19, 2012, 07:40 AM

1.1661 s - Total time

Above is the time of the uncached page where i am using the above code 4-6 feels like something is seriously wrong. I would start debuging and removing stuff from page to really find out whats wrong.

I doubt the optimization head room lies in the MIGX itself.. because afterall whatever you do, your still using TV's..and those are the real loss. The optimization may lie in using MIGXdb instead of MIGX , which for a difference uses custom tables instead of actual tv's to store data in database. However the best option is imo still doing a custom component.. and completly avoid using TV windows. I don't want to hate on MIGX its brilliant idea, but i hate TV's and anybody who you ask, even opengeek will tell you TV's are not meant to be what we're using them for, and are imo the biggest downside of the MODX performance issues.

That's how it should be (1.16s) =)!

I did a little debugging, but basically it's the structure of how content is (or has to be) inserted...so it's difficult to avoid all those conditionals, which are probably the cause for the performance issues...but I got around it using xFPC extra, page load time is around 500ms when cached once...solves the problem until I got time to fix this in a better way =)

For MIGXdb: Have to wrap my head around it, did not use it yet^^...and yes, if you can write these custom components yourself, I would do it too (but my lack of knowledge in extJS is holding me back from it, unfortunately =/).

What I would like to ask regarding your statement "against" TVs: How should they actually be used or said in other words, what kind of usage is wrong and what would be the right use case for TVs?

I'am using alot of conditionals aswell, and the time is normal. I would very much doubt that is the problem. I was facing the most similair problems when I was at start of debugging and looking for reasons for my load time. My load time was around 6sec before I started. On the end, I found out it was some 3rd party api I used, and xml_parse script I am using when displaying FB posts , after rewriting those using Ajax,the site is back and rolling in the 1sec full-uncached times. Sometimes its the things you would never think of.

Also EXTjs everybody is saying the same stuff about it on beginning , "oh that extjs", but I tell you once you start to actually trying to do something in it, you figure out its pretty simple, and not so bad as it seems.

About the TV's , if you ask me they were meant to be small helpers.. for things like dropdown combos to select things particular to resource, or some checkboxes, color pickers etc, they were not meant to store large amount of data. I think we're "over using" them. I mean that's why i keep ranting about "Create component" feature inside manager, where one would just click and select things to create his own component. I mean the most heavy part about doing the component is making sure all files are in place.. all the controlers resolvers etc etc. Once you do those..EXTjs is playing part.

Thats just my few cents, someone might not agree with me.

[ed. note: yuka123 last edited this post 13 years, 9 months ago.]

I mean that's why i keep ranting about "Create component" feature inside manager, where one would just click and select things to create his own component.

That's the idea behind the MIGXdb - CMP, but I think this is another topic.

Hello!

I have a couple of problems:

1. I get it to render my chunk in the resource but, it only shows 1 row
2. When I edit from the resource the anotations table is empty

I have attached a couple of images to help show what I mean.
I am using MODX 2.2.6, MIGX 2.4.0 beta3
I am not sure what other information would be helpful.
Any ideas of what I am doing wrong?

I am not sure what other information would be helpful.

your MIGX - configurations for outer/inner MIGX
the content of your renderChunk - chunk

Hello Bruno! Thanks for your quick reply!

Here is my renderChunk:


Here are my configurations:
Outer MIGX
Name: ResolutionResponsive
Formtabs Tab-> Edit Anotations
----Caption: Anotations
----Fields: ->Edit Anotations
--------Field Tab
------------Fieldname: Anotations
------------Caption: Anotations
------------Input TV: ResolutionResponsiveAnotations
------------Input TV type: migx
------------Configs: ResolutionResponsiveAnotations
--------Mediasources Tab
--------source From: I have been changing this with seemingly no effect
Columns Tab-> Edit Anotations
----Column Tab
--------Header: Anotations
--------Field: Anotations
----Renderer Tab
--------Renderer: this.renderChunk
--------Renderoptions
------------Name: migxColumnAnotations
Inner MIGX
Name: ResolutionResponsiveAnotations
Formtabs-> Edit Anotations
----Caption: Anotations
----Fields: All 4 fields only have entries for Fieldname and Caption
Columns Tab: All 4 columns only have entries for Header and Field [ed. note: greyskymedia.los last edited this post 13 years, 9 months ago.]

Can you also paste here, what you get, with just


in your chunk?

Good morning! This is what [[+Anotations]] holds:

[{"MIGX_id":"1","AnotationTop":"200","AnotationLeft":"200","AnotationIntro":"Anotation Intro Text Here","AnotationText":"Anotation text goes here."}]

I think I figured out why I only get one row to show up. This is what is in the db:

[{"MIGX_id":"1","Resolution":"1920","Image":"assets/img/bg1.jpg","Anotations":"[{\"MIGX_id\":\"1\",\"AnotationTop\":\"200\",\"AnotationLeft\":\"200\",\"AnotationIntro\":\"Anotation Intro Text Here\",\"AnotationText\":\"Anotation text goes here.\"}]"}]

I guess the new rows I add are not being recorded.