|
Welcome, Guest. Please Login or Register. Jul 24th, 2008, 11:32pm
Author |
Topic: New section for .DAX files (feature request) (Read 811 times) |
|
Balok
Junior Member
 
What, me worry?
Posts: 41
|
 |
New section for .DAX files (feature request)
on: May 25th, 2007, 4:19pm |
Quote | Modify
|
If you feel this belongs in New Features, please move it there. May I suggest a new section in the .DAX file where Javascript common to more than one page might appear? This would solve the problem of the same code used in multiple places, which I'm sure you're aware is a maintenance headache. Perhaps a new "Javascript" tab might appear in the DAX editor, as well. Thanks in advance.
|
|
IP Logged |
|
|
|
Firetongue
Administrator
    
Email
Posts: 1135
|
 |
Re: New section for .DAX files (feature request)
Reply #1 on: May 27th, 2007, 1:22pm |
Quote | Modify
|
Thanks for suggestion. Indeed, as more javascript is added to the default theme these days, separate javascript section makes a lot of sense. I will look into it. Andrei
|
|
IP Logged |
Upload your music catalog to Racks and Tags and get free unlimited collection storage - offer ending SOON!
|
|
|
Gagliem
Junior Member
 
Music is better when it's played live!!
Posts: 20
|
 |
Re: New section for .DAX files (feature request)
Reply #2 on: Sep 25th, 2007, 5:44am |
Quote | Modify
|
Hi Balok! I think it's a useful suggestion , as I heavily modified OCD with my own theme full of Javascript functions (Andrei knows it.. I posted him some topics about JS on OCD) and they're always used in more than a section, also it seems that OCD doesn't like external .js files (I tried different ways...) Cheers Emanuele
|
|
IP Logged |
|
|
|
Balok
Junior Member
 
What, me worry?
Posts: 41
|
 |
Re: New section for .DAX files (feature request)
Reply #3 on: Jul 19th, 2008, 9:01am |
Quote | Modify
|
Yes, I also tried various ways of shoehorning in external files without much luck. I also tried using an external editor to tuck them into the end of the styles section. OCD can't find them if they're there (and the template editor that comes with it won't even display them). And, of course, you can't refer to routines on one page from another, I'd guess because each page is loaded into a separate execution context. Hopefully, Andrei will get 'round to looking at this one of these days, but it might be harder to do than we think.
|
|
IP Logged |
|
|
|
|