Enrique Vega wrote:
> This concerns me a great deal and should concern midgard developers. It
> seems to me that, due to the amount of knowledge and experience that you
> guys have, that it would take a reasonably short amount of time to develop a
> set of generic code which could be put in a shared style or snippet for web
> site developers who do not have php/midgard programming knowledge. Let's
> face it, most web site developers on the internet today have little or no
> experience programming! So I beg of you to consider setting a priority to
> develop and include some generic navigation code as part of the standard
> distribution of midgard.
We will allways welcome contributions of snippets or examples for the
manual.
Getting either of these to do something useful without knowing anything
about
PHP is likely to be stretching Midgards' abilities, though. Personally,
I think Midgard is an enabling technology. It may not be a end-user tool
for everyone. Ami does have something in mind for 2.0 which is more in
tune with
your needs; I wish he was around right now to explain but he's on
holiday right
now.
> If I may presume to give advice on the type of code needed for navigation, I
> would like to suggest creating separate code for the following standard
> navigation:
>
> 1. web site code which displays an index of:
> a. all pages
> 1. sub pages
> b. all topics
> 1. sub topics
> c. all articles
> 1. individual articles
> a. include the ability to add field information
> 1. ie; author name, address, from person record
> d. forward, back, & top links for pages, topics, & articles
These are all doable in essence. The issue is presentation. I can
certainly
create php functions which return all pages, or all topics, etc. but
there
is no clean way of blending that with your own custom layout.
> 2. comment code so user can understand & select fields to use
> a. allows for learning curve & publish web sites in a timely manner
That I fully agree with, David has started work on that.
> in the nadmin manual. This was great, but not enough. I wanted for my
> fullindex.htm to not only show all the articles in the topic, but also
> display the sub topics and the articles within the sub topics. So I started
> looking and modifying the news snippet code.
>
> I've included a part of the news snippet which I copied to a <[news]> style
> that I modified to get all articles, including articles from sub topics in
> my fullindex.htm. By changing mgd_list_topic_articles to
> mgd_list_topic_articles_all I was able to generate a listing of all
> articles, including sub articles.
If you want all the articles, mgd_list_topic_articles_all will do the
job. If you want
all the articles outlined by topic, it will take recursive calls to
mgd_list_topic
to get that done.
> This is great, but what I really wanted to do was to get only a listing of
> all sub topics.
See above.
> I spent the better part of a day looking through manuals and
> code, which by the way had little or no comments for users to understand. So
> now I am at a dead end. I have no idea how to get my news page to
> dynamically display sub topics or even topics without going through a long
> learning curve. It seems that I am going to have to learn php AND midgard
> before I can develop a simple dynamic web site using midgard and nadmin :-(
The manual does need work; in fact, right now it ought to be one of the
most thankful
things to work on, there being so much room for improvement :/ We'll get
there
eventually, but in the meantime volunteers of any technical skill level
are welcomed
to help out. As I have mentioned a long while ago, not being extremely
well-versed
in C and/or PHP is an actual plus when writing user documentation (with
aid from the
developers of course).
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
