From Mod Dev Land

[-Calypso-]

'IN_DEV', 1 is all well and doing good things, the one thing that I know it does not do right now is allow exportation of custom template bits. Would like to have a way to export any template bit. Working on mod, the thing that takes the longest to build in the .xml other than tables/fields/inserts etc. is template bit. May have a mod with any number of template bits but making the .xml currently has to be done 1 by 1.

Thanks for looking.

[Alex]

Erghh.. you can already do this? We do it for Tracker and Shoutbox, we don't manually write those XML files for templates!

The whole idea is that if you have IN_DEV on, you edit the skin PHP files through cacheid_1, and don't actually use the Admin CP at all for templates. Then after your done, you go to Skin Tools, and click 'rebuild master skin files from:', and make sure the PHP box is checked with cacheid_1 in it.

Thats how your meant to do it :)

[-Calypso-]

Wouldn't it be much easier to just be able to export the built templates? I build mine through the acp.

[Alex]

Depends on preference really, I know when IPS develop products, they always edit the PHP files directly, instead of using the skin manager, which is probably why its done the way it is.

But just to let you know, editing cacheid_1 is the same as editing in the skin manager, it doesn't convert the code like the other files do, its still the pure HTML (<if> etc. are allowed in there)

[Michael]

I'm confused. I have IN_DEV turned on on my localhost board, and I can then use the ACP to create and manage master skin templates in there, and then export them, all without having to edit any cacheid_1 files whatsoever.

[-Calypso-]

It should be easier for mod devs, maybe I been doing it the long way but i set up my main php, load the skin_ and lang_ files and start building. When i'm done I got 1 by 1 copy+paste template bits / data variables to the .xml

[Michael]

When you turn on IN_DEV, do you not have the option to manage your master skin templates from the Skin Manager page, by clicking the Options button beside the "IPB Master Skin Set" row? And do you not have the "Developers: Export Module Skin Files" section at the bottom of that page?

[Amy T]

You could do it the way I do it.
I create the xml file. I hardly do any skin work in the admin cp as I find it is much easier to just create the xml files.
And to test to see if they work I just install them with the UMI.

[-Calypso-]

When you turn on IN_DEV, do you not have the option to manage your master skin templates from the Skin Manager page, by clicking the Options button beside the "IPB Master Skin Set" row? And do you not have the "Developers: Export Module Skin Files" section at the bottom of that page?

Not a clue (not gonna bother looking either), sorry for creating this topic. Won't happen again.

[Michael]

So you've got it working now then?

[-Calypso-]

no, don't worry about it

[Alex]

Michael, if you have IN_DEV on, you don't actually need to use the Admin CP, you CAN use the admin cp to manage master templates, but you still have to add templates through the database. Cacheid_1 literally is just writing functions, than telling the skin manager to update it, does it all for you.

[Michael]

To me it's easier to just use the Admin CP than to mess with the files.

[Amy T]

I thought my way was easy.

[Lindsey_]

I just edit the skins in the Admin control panel. Tho i dont make mods :P

[alj]

i think -Calypso- mean that ips staff can make it much easier by
his point
and add dev zone area that make coding and creating mod easier
and safe a lot of headache they make it easy to install by adding
plugin system and many core improv to the V3 of ib but hard for the coder
to create there mod

[bfarber]

i think -Calypso- mean that ips staff can make it much easier by

his point

and add dev zone area that make coding and creating mod easier

and safe a lot of headache they make it easy to install by adding

plugin system and many core improv to the V3 of ib but hard for the coder

to create there mod

I don't think Calypso was talking about any of this personally. ;)

Calypso - with IN_DEV enabled you can export *entire* skin files, but not individual template bits. You can export template bits individually, but they're written out as SQL queries rather than XML files.

[-Calypso-]

I think i found it, I can export skin_example from skin_id #. That seems to work although it has eluded me for almost 2 years now (if it's been there that long). I was looking more along the lines or separate custom bit. After a bit of research I found that if I changed the 'set_id=1' to 'set_id=#' then I can export individual temp bits from and skin, even fresh made template bits. Was considering adding a tool to remotely change this in my Tools & Settings and use 'set_id='.$this->ipsclass->vars for it.

Thanks :)