Difference between revisions of "Talk:Skin test"

From PortlandWiki
Jump to: navigation, search
Line 8: Line 8:
 
# I can scavenge functionality from existing php, and insert them into static html. (This will work as long as I can find simple versions of them. There are elements I've already bumped into such as modified and # of visits that are too cryptic for me to decipher)
 
# I can scavenge functionality from existing php, and insert them into static html. (This will work as long as I can find simple versions of them. There are elements I've already bumped into such as modified and # of visits that are too cryptic for me to decipher)
 
# I can hijack existing css, in order to bend Piki to my will. This will be my fallback, since I'm pretty sure I can do this. Perhaps this is all I should do, since it seems most of the skins are basically css-modified monobooks. (thing is, I don't want to just shuffle things around, I really believe that certain items should be grouped differently.
 
# I can hijack existing css, in order to bend Piki to my will. This will be my fallback, since I'm pretty sure I can do this. Perhaps this is all I should do, since it seems most of the skins are basically css-modified monobooks. (thing is, I don't want to just shuffle things around, I really believe that certain items should be grouped differently.
 +
# I can go back to the drawing board, and come up with a different design. It's possible that the reason I have no dev support, is because no one likes the design I have. Being stranded is a result of passive aggressive, unwilling to get behind. (I had a design that somehow added more respect and clarity. I have admit that my design is a bit heavy on color...nah scratch that. I just looked at my comp again. It rocks)

Revision as of 13:07, 5 September 2011

xx

--Matthew (talk) 22:55, 4 September 2011 (UTC) (Well, I give up. I still don't understand the php I'm looking at. All the skins I want to hack from, are actually clones of monobook. (as in there's no code, but links to the monobook code.) and guess what? Monobook is freakin' complicated. I mean, I've hacked at html before, and I can figure it out, but the php used here doesn't use full html. Tags are split up so there aren't even solid tags to jump from. I'm stuck again 9/4/2011 3:55pm...is piki worth it???)


--Matthew (talk) 19:49, 5 September 2011 (UTC) Today I have a couple of things I can try:

  1. I can scavenge functionality from existing php, and insert them into static html. (This will work as long as I can find simple versions of them. There are elements I've already bumped into such as modified and # of visits that are too cryptic for me to decipher)
  2. I can hijack existing css, in order to bend Piki to my will. This will be my fallback, since I'm pretty sure I can do this. Perhaps this is all I should do, since it seems most of the skins are basically css-modified monobooks. (thing is, I don't want to just shuffle things around, I really believe that certain items should be grouped differently.
  3. I can go back to the drawing board, and come up with a different design. It's possible that the reason I have no dev support, is because no one likes the design I have. Being stranded is a result of passive aggressive, unwilling to get behind. (I had a design that somehow added more respect and clarity. I have admit that my design is a bit heavy on color...nah scratch that. I just looked at my comp again. It rocks)