That discussion sounds exactly like what I was thinking about. That outline sounded almost like you have acomplished this, is that true?
Outline?
I am for a loss!
Also, how did you get it to refer to other publication types from within the list?
Check out my shared sections on my website...
http://www.crayhillsolutions.com/Downloads-index-req-viewdownload-cid-1.html
I used SMARTY logic, and it works really good...
I got to create a XML template for it still, but for now it works GREAT! I can refer anything I want, including other websites:) The really cool feature is that I can link to Windows Docs, and because all the text fields still exist (though they are not shown) I can use them to insert search data. For example, I can cut and paste the contents of a Word document in it, without worring about the format, then include the URL... users will get the Word Document when they view it, but it will still be search able...
I am getting really good at making this tool do things that no one thought off. I have got this thing going well into areas J0rn never thought off.
I am really looking to get more into the development of this application.... I just finished a Selector replacement, that keeps compatibility, but also has functionality to help manage state.
I would like to make pagesetter use pnRender instead of its own copy of SMARTY... I would also like to tie into Xanthia SMARTY tags.. I think if we can have blocks within the Pagesetter templates, that this might be another aproach to handling the nested publication issues.
One of the problems with the current pagesetter, that is causing me some headache is the lack of instance within pagesetter. It would be nice if I could seperate a single publication into multiple instances.
Again, this comes down to a lack of plug-ins to the XML form template system (Guppy).
Maybe I dont know it yet though.
[Edited on 11/11/2004 by GreenJelly]
[Edited on 11/11/2004 by GreenJelly]