Jump to content

invision is making it hard to do any skinning


Guest GeoffreyK

Recommended Posts

im finding it hard to settle down and do some skinning work, as every time there is a new upgrade, it seems that i have to do all the work again.

In fact, i find the whole databased skin, cached css, macro board wrapper concept very annoying.

If i had it my way, everything would be stored statically in files.

This would make it alot easier to mod and to save backups, and incremental steps along the way.

Compared to 1.3, are other people finding it much harder to do their own modding and coding and skinning?

am i alone here??

Nothing against invision to personally.. i love their products... just wanted to see if others felt the same way!

geoff

Link to comment
Share on other sites

At the 1.1 version , the changes i had in my forums was too many , Skinning and mods .
Then i realized that i had to do all the changes when i was installing the newer versions .
I stopped installing mods and changing the look of my forums .
The only mod i want installed now is a shoutbox and a link to my homepage .
The reason is the questions you have . I'd like to have some extras in my forums but i am tired of the changes .

Link to comment
Share on other sites

im finding it hard to settle down and do some skinning work, as every time there is a new upgrade, it seems that i have to do all the work again.



In fact, i find the whole databased skin, cached css, macro board wrapper concept very annoying.



If i had it my way, everything would be stored statically in files.



This would make it alot easier to mod and to save backups, and incremental steps along the way.



Compared to 1.3, are other people finding it much harder to do their own modding and coding and skinning?



am i alone here??



Nothing against invision to personally.. i love their products... just wanted to see if others felt the same way!



geoff



That is the reason why I am thinking twice on buying the set. Dont have time to edit templates over and over and over again.
Link to comment
Share on other sites

I think there needs to be a seperate skinning engine. With IPD on the horizon, this may become a necessity. After all, how will skinning be done cross-site? Will it be based on a set in the IPD or in th IPB? Clearly if they want IPD as a main site, the skin sets and image files would need to be there.

Link to comment
Share on other sites

Honestly, I think of it as unless you have practically redone every single template bit in your skin, then it's not all that hard to check the 27 templates that changed with 2.1.2 and put them into your skin(s).

And if said template was never edited in your skin to begin with, then the upgrade script would make the changes, if it sees the bit as changed, it won't touch it, therby letting you do it manually.

Link to comment
Share on other sites

im curious... does anyone really find the online (ACP) editing of skins that useful?

I would much prefer to do it in dreamweaver, so i have edit undo ability as well as html wysiwyg ability.



I have not had any use for all the fancy caching of settings, skins, css etc.

I would much prefer everything to be in files.
What is the benifit of having everything cached in the db?


does anyone understand the need to change all the skin files class names??

thanks

geoff

Link to comment
Share on other sites

yeap. its really helpful since you dont have to edit the files themselves. if your good at programming html, it should be doable. and also. if you edit with some external program, it may mess up the formatting and everything and might not display it properly.

having it cached in the db also helps when upgrading the forums. when you upload all the new forum files, you dont have to make changes again into the skins to get it to what it was like before the upgrade

Link to comment
Share on other sites

im finding it hard to settle down and do some skinning work, as every time there is a new upgrade, it seems that i have to do all the work again.



In fact, i find the whole databased skin, cached css, macro board wrapper concept very annoying.



If i had it my way, everything would be stored statically in files.



This would make it alot easier to mod and to save backups, and incremental steps along the way.



Compared to 1.3, are other people finding it much harder to do their own modding and coding and skinning?



am i alone here??



Nothing against invision to personally.. i love their products... just wanted to see if others felt the same way!



geoff



I have to say that I was surprised at how little this upgrade effects skinning changes.
I had to edit one langfile after doing the upgrade in full. I was pleasantly surprised.
I'm not certain, but this version also seems to run more efficiently
Link to comment
Share on other sites

At first, I really liked having things centrally in the ACP. However, as time has gone on, I've started to feel a little more like GeoffreyK.

It's nice to have the tabs of Dreamweaver for code formatting for example, as well as various other features which only a full code editor can provide. Sure you can do things in DW and then paste into the codebox but then what are you saving?

Personally, I'd rather go back to files now.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...