Hi,
I read a lot of stuff about the new topics, nexus and sections layout
from the latest CVS. I'm not entirely confused but want your advice :-)
An subset of my simple topics layout could look like this:
(A) Application Domains
(B) Agriculture
(B) Energy
(A) The Industry
(B) Government
(B) NASA
My level (A) is unsubmittable nexus with children
My level (B) is a topic with one parent
What I want to do is nothing fancy:
(1) Have some topics to appear on main page
(2) Have some topics to appear on the "nexus page"
For (1), there is no problem, I simply post the story for the topic
under main page and it's done. For (2) however, I want advice for the
best way to do it.
I haven't played with blocks yet, but I'd like stories that are not
on main page to appear in a block such as Slashdot's block for
sections' list with the number of non-main-page stories showed as "x
more". Can this be done for nexus topics?
The section addition code is broken in backslash and I don't feel any
urge for sections if there a way, for the user, to get a clue about
new stories not on main page for a specific nexus.
Thanks for any advice :-)
Alex :-)
SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

I found previous discussions started by George Clark and Mark Gaulin.
The conclusions are not known and there is obviously still confusion
on this very issue. Anyone want to help clear things out? Reading
from what I included below, it seems I would need different skins for
each nexus, right?

= = = = =
A tidbit:
Mark Gaulin:
I think my final assessment is probably close: to post a story to a
topic and not have it show up on MainPage, that topic must have a
parent (or grandparent) topic that is a nexus, and there must be a
skin associated with that nexus. If there isn't one then the story
will have no primaryskid and will not appear anywhere (unless the min
weights are set such that the story ends up being rendered into
MainPage anyway).

IMH, that's a bug.
Shane
= = = = =

Le 05-08-18 9:01 pm, Alexandre Leroux a :
I read a lot of stuff about the new topics, nexus and sections
layout from the latest CVS. I'm not entirely confused but want your
advice :-)

An subset of my simple topics layout could look like this:

(A) Application Domains
(B) Agriculture
(B) Energy
(A) The Industry
(B) Government
(B) NASA

My level (A) is unsubmittable nexus with children
My level (B) is a topic with one parent

What I want to do is nothing fancy:
(1) Have some topics to appear on main page
(2) Have some topics to appear on the "nexus page"

For (1), there is no problem, I simply post the story for the topic
under main page and it's done. For (2) however, I want advice for
the best way to do it.

I haven't played with blocks yet, but I'd like stories that are not
on main page to appear in a block such as Slashdot's block for
sections' list with the number of non-main-page stories showed as
"x more". Can this be done for nexus topics?

The section addition code is broken in backslash and I don't feel
any urge for sections if there a way, for the user, to get a clue
about new stories not on main page for a specific nexus.
--
Thanks for any advice :-)

Alex :-)
--

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams *
Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/
bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

That post that you found from Mark - that's *very* old. It mentions
the weights - it used to be that you could associate 'weights'.

Regarding posting a story and having it not show up on the main
page from the sound of it, this is now a non-issue too. I
routinely post stories on lottadot, in a section, and I do not want
those stories on the frontpage. I just use the ^X+V to move the
topics around or remove them from the available list when editting a
story.

Shane

Aug 18, 2005, at 10:43 PM, Alexandre Leroux wrote:

I found previous discussions started by George Clark and Mark
Gaulin. The conclusions are not known and there is obviously still
confusion on this very issue. Anyone want to help clear things out?
Reading from what I included below, it seems I would need different
skins for each nexus, right?

= = = = =
A tidbit:
Mark Gaulin:
>
>I think my final assessment is probably close: to post a story to a
>topic and not have it show up on MainPage, that topic must have a
>parent (or grandparent) topic that is a nexus, and there must be a
>skin associated with that nexus. If there isn't one then the story
>will have no primaryskid and will not appear anywhere (unless the min
>weights are set such that the story ends up being rendered into
>MainPage anyway).
>>
>>
>
IMH, that's a bug.
Shane
= = = = =
>
>
>
Le 05-08-18 9:01 pm, Alexandre Leroux a :
>
>I read a lot of stuff about the new topics, nexus and sections
>layout from the latest CVS. I'm not entirely confused but want
>your advice :-)
>>
>An subset of my simple topics layout could look like this:
>>
>(A) Application Domains
>(B) Agriculture
>(B) Energy
>(A) The Industry
>(B) Government
>(B) NASA
>>
>My level (A) is unsubmittable nexus with children
>My level (B) is a topic with one parent
>>
>What I want to do is nothing fancy:
>(1) Have some topics to appear on main page
>(2) Have some topics to appear on the "nexus page"
>>
>For (1), there is no problem, I simply post the story for the
>topic under main page and it's done. For (2) however, I want
>advice for the best way to do it.
>>
>I haven't played with blocks yet, but I'd like stories that are
>not on main page to appear in a block such as Slashdot's block for
>sections' list with the number of non-main-page stories showed as
>"x more". Can this be done for nexus topics?
>>
>The section addition code is broken in backslash and I don't feel
>any urge for sections if there a way, for the user, to get a clue
>about new stories not on main page for a specific nexus.
>>
>>
>Thanks for any advice :-)
>>
>Alex :-)
>>
>>
>
>SF.Net email is Sponsored by the Better Software Conference & EXP
>September 19-22, 2005 * San Francisco, CA * Development Lifecycle
>Practices
>Agile & Plan-Driven Development * Managing Projects & Teams *
>Testing & QA
>Security * Process Improvement & Measurement * http://www.sqe.com/
>bsce5sf
>
>Slashcode-general mailing list
>Slashcode-general (AT) lists (DOT) sourceforge.net
>
>>
>>
>
>
>

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams *
Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/
bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

Aug 18, 2005, at 9:01 PM, Alexandre Leroux wrote:

Hi,

I read a lot of stuff about the new topics, nexus and sections
layout from the latest CVS. I'm not entirely confused but want your
advice :-)

An subset of my simple topics layout could look like this:

(A) Application Domains
(B) Agriculture
(B) Energy
(A) The Industry
(B) Government
(B) NASA

My level (A) is unsubmittable nexus with children
My level (B) is a topic with one parent

What I want to do is nothing fancy:
(1) Have some topics to appear on main page
(2) Have some topics to appear on the "nexus page"

For (1), there is no problem, I simply post the story for the topic
under main page and it's done. For (2) however, I want advice for
the best way to do it.

I guess I'm unsure what you're asking. It should be very simple for
you to set stories in the (2) situation appear on the appropriate
nexus page.

I haven't played with blocks yet, but I'd like stories that are not
on main page to appear in a block such as Slashdot's block for
sections' list with the number of non-main-page stories showed as
"x more". Can this be done for nexus topics?

Sure, it can be done, where there's a will there's a way. Afterall,
Slashdot's doing it :)
You're referring to the left-hand-side, under the login, right?

I don't know that it'll do what you're wanting, out-of-the-box. I
know this has been asked before. (it should be in the faq). Search
the archives, maybe there's prior discussion about it, or on
slashcode.com or lottadot.

The section addition code is broken in backslash and I don't feel
any urge for sections if there a way, for the user, to get a clue
about new stories not on main page for a specific nexus.

well I would think, if we ever get a 'section editor' it'd really be
called a 'skins editor'. I dunno what terminology the STG guys would
prefer there. Guys?

For now, you have to create your skins/sections by hand with sql.

Shane

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

>What I want to do is nothing fancy:
>(1) Have some topics to appear on main page
>(2) Have some topics to appear on the "nexus page"
>>
>For (1), there is no problem, I simply post the story for the
>topic under main page and it's done. For (2) however, I want
>advice for the best way to do it.
>
I guess I'm unsure what you're asking. It should be very simple for
you to set stories in the (2) situation appear on the appropriate
nexus page.

Yeah - for stories to appear on the appropriate nexus page, am I
right if I say the only thing missing is to have different skins/
sections for my nexus topics?

Right now,
There seems to be only three possibilities:
- This story will be on the Main Page [x], and linked from Technology
[x].
- This story will be .
- Story will not appear.

My problem is of course with the "This story will be ". It happens
when a nexus topic is in the -^- Sectional -^- while I have only
the default mainpage skin/section existing.

Related: how do I associate a nexus topic to a specific skin/section?
I'm sure I saw this somewhere in backslash, but can't find it
anymore. Not in

I searched lottadot's faq for further answers, none found. I'll flll
it if this issues gets solved :-)

Thanks :-)

Alex

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net

Hi list,

Issue solved. For clarity's sake, here's answers to my own questions.
Thanks to Shane (and Mark) whom helped me understand.

I wanted two types of stories: those for main page, those not for
main page.
Stories must be associated to a skin to appear anywhere (e.g. http://
site/search.pl?tid=19).

What was missing on my site was another skin than mainpage associated
to my new nexus. This is done by adding/changing skins in the skins
table. Example, "update skins set nexus="15" where skid='2';" , where
the nexus value is the tid of the nexus-topic. This skin is a
section. You'll probably want to change the hostname, name and title
values of this skin directly in the table too.

Actually, I created a few section-skins, each one associate with a
nexus-topic. Required because I wanted the good name to appear (the
"title" value of the skin) when the story is set within a section-
skin and on mainpage in the mean time.

I added this info in lottadot's faq.

Alex :-)

What I want to do is nothing fancy:
(1) Have some topics to appear on main page
(2) Have some topics to appear on the "nexus page"

For (1), there is no problem, I simply post the story for the
topic under main page and it's done. For (2) however, I want
advice for the best way to do it.

>>
>I guess I'm unsure what you're asking. It should be very simple
>for you to set stories in the (2) situation appear on the
>appropriate nexus page.
>>
>
Yeah - for stories to appear on the appropriate nexus page, am I
right if I say the only thing missing is to have different skins/
sections for my nexus topics?

Right now,
There seems to be only three possibilities:
- This story will be on the Main Page [x], and linked from
Technology [x].
- This story will be .
- Story will not appear.

My problem is of course with the "This story will be ". It happens
when a nexus topic is in the -^- Sectional -^- while I have only
the default mainpage skin/section existing.

Related: how do I associate a nexus topic to a specific skin/
section? I'm sure I saw this somewhere in backslash, but can't find
it anymore. Not in

SF.Net email is Sponsored by the Better Software Conference & EXP
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Slashcode-general mailing list
Slashcode-general (AT) lists (DOT) sourceforge.net