SimpleMenu

Me too. I’ve seen demos and it works just fine, thank you. And much faster than the current parser, too!

Quote from: zi at Dec 04, 2005, 04:55 AM

I think, it would be something like this

[!mysnippet? &param=`[[myothersnippet? &param=`[*myTV*]`]]` &param2=`[*anotherTV*]`!]

Hope this helps

regards,

zi

Is this thing true? Could you guys give me more detail about when this thing will be implemented in the next release? On TP4?

My goodness, that will solve a lot of headache problem that I need to work on right now.

Another thing, are we going to see an improvement of implementing modules on MODx, such as preset installation/packaging? As well as preset configuration that can be used, instead of having to insert the plugin, snippet, chunk, and TV one by one, and then use modules to interconnect them and add modules variables one by one again to be used by the corresponding snippets, chunks, and plugins.

What I have in mind is that, the packaging will have an install.xml, which contains information for every bit information of plugins, chunks, snippets, and TVs. Then in the first part, it will have info for the modules itself, so that when the MODx system read this file, it will create a new module to the database, assign the variables and parameters for that module. After that it will install each snippets, chunks, plugins, and Tvs one by one by putting them in database, copying the needed files and registering it to the module that was created before that

After all done, I’m expecting the xml installation file will have a section as documentation to be shown after installation to guide user on what they need to do next. I also want to see another documentation section to be shown before installation, so that the user know what they are installing and what is the next thing that they need to expect.

Hope this has been implemented or it can be another suggestion of the packaging itself. I would suggest adding another folder in the assets directory to contin all the packaging file in one folder, or if the system able to extract zip file, it will be really great.


Best regards,
Wendy Novianto

Hi wendy,

The new Paser (and MODx core) will change your world completely. MODx will be 100 times more module than it is today!

MODx - The more MODular and extensible Content Management And Application System.

Quote from: ScottyDelicious at Dec 03, 2005, 10:14 AM

I have been using an eto snippet called "ListChildOrSibs", but I abandoned it because it does not respect the "Show in Menu" box being unchecked...

Hmm... I will probably have to go back and modify, or should I say, MODxify some of the snippets I wrote for Etomite. The Show in Menu option wasn’t available in Eto so there was no need for that feature. However, now that I am working more with MODx, updates like that would be pretty useful.

Oh I ACHE for a MODx snippet library...

Its coming, its coming its coming!

Quote from: jaredc at Dec 05, 2005, 07:50 AM

MODxify some of the snippets

I like that term

Quote from: Djamoer at Dec 04, 2005, 10:16 AM

Another thing, are we going to see an improvement of implementing modules on MODx, such as preset installation/packaging? As well as preset configuration that can be used, instead of having to insert the plugin, snippet, chunk, and TV one by one, and then use modules to interconnect them and add modules variables one by one again to be used by the corresponding snippets, chunks, and plugins.

What I have in mind is that, the packaging will have an install.xml, which contains information for every bit information of plugins, chunks, snippets, and TVs. Then in the first part, it will have info for the modules itself, so that when the MODx system read this file, it will create a new module to the database, assign the variables and parameters for that module. After that it will install each snippets, chunks, plugins, and Tvs one by one by putting them in database, copying the needed files and registering it to the module that was created before that

After all done, I’m expecting the xml installation file will have a section as documentation to be shown after installation to guide user on what they need to do next. I also want to see another documentation section to be shown before installation, so that the user know what they are installing and what is the next thing that they need to expect.

I know this is something that Mambo has recently implemented and the new Joomla beta will have- a universal installer via an XML file and zip/tar packaging. To be able to install dependencies through one zip would be great.

Another option they are adding is to install packaging via a URL. So instead of downloading the file to your PC, then uploading and installing it. Instead, you just point to the URL of the package and it goes through the install process you described above.

Chuck