Zikula Community

• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 01, 2011 - 03:21 PM

  Planning to use BlankTheme in a new site, I went to review some information about BlankTheme and discovered to my horror that it has moved to Github and the Wiki is gone. Vanished. Kaput.
  
  Without the Wiki or other documentation, color me dead in the water.
  
  I understand moving the project. I do not understand why anyone would make all that documentation vanish. BlankTheme is not easy. The learning curve approximates 90 degrees. Without the Wiki it is certainly beyond me and probably will become a plaything for developers but not something useful for the other 99% of us.
  
  Sorry if I sound cranky about this. I'm trying pretty hard to only sound cranky and hide my true feelings.
  
  Please make the Wiki reappear!
  
  Peter
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Jul 01, 2011 - 04:06 PM

  My apologies about this,
  the 1.2 site had problems and I went straight to 1.3 clean install.
  
  I'll recover the info, but I need to find the time to.
  This movement was also because I've simplified BlankTheme quite a lot with the 1.3 features.
  I hope that you agree with me after you play with it in 1.3, that the learning curve is quite lower now with the control from INI files only. The 1.2 docs are deprecated in that way.
  
  The stuff can be done vía Web from the Theme's Admin Panel.
  And well, I've reduced the file number to the minimum expression.
  
  Enjoy it in auto-didactic mode by now,
  I will find the time to recover the stuff that was published before
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 01, 2011 - 04:14 PM

  Thank you. I have several 1.3 playsites on my localhost and I will try bt there. But I do not dare use it on a live site without the documentation, so I will have to hold off there.
  
  I love bt, despite the fact that it was a challenge. I was anticipating using it at the core for (almost) all my themes going forward and finding the documentation missing tonight generated a phreakfest.
  
  I'll look forward to the info re-appearing and especially to new and improved bt.
  
  Peter
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Jul 01, 2011 - 04:26 PM

  You can play around and meet the 1.3 features on the Theme Admin Panel.
  You will see you will be able to change the BlankTheme's configuration from there now.
  
  The basic .ini files are there for the basic possible configurations, you have a clear picture without noise on the BT capabilities I have to test Wikula for 1.3 and fix any details to mount the docs again.
  
  Greetz
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 01, 2011 - 04:36 PM

  I hope Wikula works on 1.3 - I won't be able to upgrade some important sites if it doesn't.
  
  FWIW, the site I was planning to move to BlankTheme is currently using Theme960, which has some of the capabilities of bt but is a bit easier on the brain. But Wikula doesn't work on Theme960 (when you go to edit a page, the editing text field keeps growing and you can never ever reach the submit button on the bottom), and the CSS used to make the main menu bulletless also means no bullets for unordered lists in News and Pages (this I'm pretty sure I can solve, but the Wikula problem has me licked) - which is why I was planning to move to bt this weekend.
  
  P
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Jul 01, 2011 - 04:43 PM

  I will try to play with a video maker and build a brief one to show the current capabilities.
  It will be friendlier than any doc, and a little faster I hope. Anyways, play with it and I hope you get the stuff working pretty fast
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 01, 2011 - 05:20 PM

  Will try.
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Jul 01, 2011 - 07:45 PM

  pheski

  
  But Wikula doesn't work on Theme960 (when you go to edit a page, the editing text field keeps growing and you can never ever reach the submit button on the bottom), and the CSS used to make the main menu bulletless also means no bullets for unordered lists in News and Pages (this I'm pretty sure I can solve, but the Wikula problem has me licked) - which is why I was planning to move to bt this weekend.

  
  The bullets are disabled by the reset.css of 960.gs, you can either take that out of the reset.css completely, or use the child selectors to add them back in to the areas you want them. However, I see the bullets where I expect them in other areas, so I'm not sure why you don't get them elsewhere.
  
  On the Wikula thing, I'm not sure why it's doing that, but it looks like it's something in the wikka.edit java script file as best I can tell.
  
  
  
  Edited by HalbrookTech on Jul 02, 2011 - 12:07 AM.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Jul 01, 2011 - 08:22 PM

  Okay, for some reason, Wikkaedit trys to resize the input window based on the browser window size, don't know why they chose to do that, but they do. For some reason, it's getting an ever growing size for the window and because it's seeing that, it's ever growing the input area. Removal of one bit of code stops it. in the wikkaedit.js file line 138, remove the +change and it stops the problem.
  
  I'm not sure why the javascript is detecting the window ever growing, I'll have to see if I'm using a div id or class some where that is confusing it, but at the same time, it seems like a bad design to make the edit window auto grow like that.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 02, 2011 - 02:47 AM

  Quote

  Removal of one bit of code stops it. in the wikkaedit.js file line 138, remove the +change and it stops the problem.
  

  
  That doesn't work for me.
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• DavidJ
  
  

  • Rank: Softmore
  • Registered: Jan 22, 2008
  • Last visit: Apr 04, 2010
  • Posts: 130

  Posted: Jul 03, 2011 - 12:37 AM

  The wayback machine has a snapshot with some of the documentation if it helps:
  http://web.archive.o…kula.org/blanktheme
  
  --
  David
  

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 03, 2011 - 01:55 AM

  DavidJ

  The wayback machine...

  
  
  Looks like enough information to keep me in business until 1.3 and the new version. Thanks.
  
  And why didn't I think of that?
  
  Peter
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 03, 2011 - 04:05 PM

  Quote

  The bullets are disabled by the reset.css of 960.gs, you can either take that out of the reset.css completely, or use the child selectors to add them back in to the areas you want them. However, I see the bullets where I expect them in other areas, so I'm not sure why you don't get them elsewhere.

  
  
  Here is a link to aNews page where the bullets do not show up. News is the only place I don't seem them. They show up fine in Pages.
  
  I have spent some time with Firebug and the reset, 960, fluid16, style and text CSS files and cannot seem to make it appear in News. I took the ul/ol none out of reset and then in fluid16 added none back for .alpha, which worked fine to avoid bullets in the main menu. I've tried various permutations of container_16 grid_12, omega, with no success. I'm sure I'm in the right place and on the right track because when I change ol to decimal-leading-zero, that shows up nicely in Pages. It just seems to be News that is immune.
  
  Related to $preformat.maintext in the news_user_articlecontent template?
  
  Not a deal breaker but a pain.
  
  Peter
  
  
  
  Edited by pheski on Jul 03, 2011 - 11:21 PM.
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Jul 03, 2011 - 04:56 PM

  Quote

  News is the only place I don't see them.

  
  
  Solved. It was including ul, ol, and li the margin and padding of zero in fluid16.css - which pushed the bullets off the visible part of the page in News but not in Pages.
  
  Sigh. It shouldn't have been so hard to find that. More coffee please.
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.