Developer Nexus

[Fuchida]

Agree.

Let's remember these ideas are meant to be for the client and shard of the Open Source.
Not any other installation.
Which makes the Offline KI fall away.

We are trying to find a way, that Cyan and us as a Community as an easy way, to incorporate, test and make available.
Cyan mentioned that they want the Guilds to be involved in the whole creating and testing of new content.
To be able to do that, the Guild of Maintainers need to have a way to access these beta stages of ages, before any ordinary explorer will access it.

That is why, we discuss another nexus system.

We need a new interface anyways. Therefore all these things could be handled by access codes, or access attributes, that the admin of the shard can give to members of the shards maintainers guild.
Making it possible to handle all of the nexii describe in both topics in one nexi only. (Except Cyan Nexus, which I still think should not really be touched, gives more work than to just program a new interface)

[Aloys]

We all agree about the need to access Ages under development, but developing a whole Nexus GUI just for this is a *lot* of work... It is much faster and much easier to develop a simple command line system like the offline Ki. If some people want to spend time developping a Dev Nexus, I don't mind; I don't plan to be involved in this, but it is a waste of time.

[nathan2055]

We need a new interface anyways. Therefore all these things could be handled by access codes, or access attributes, that the admin of the shard can give to members of the shards maintainers guild.
Making it possible to handle all of the nexii describe in both topics in one nexi only. (Except Cyan Nexus, which I still think should not really be touched, gives more work than to just program a new interface)

Well, maybe we should just have a developer tab in the WNexus. And eventually Cyan's Nexus is going to have to be edited, we are already discussing that in the thread for the WNexus.

We all agree about the need to access Ages under development, but developing a whole Nexus GUI just for this is a *lot* of work... It is much faster and much easier to develop a simple command line system like the offline Ki. If some people want to spend time developping a Dev Nexus, I don't mind; I don't plan to be involved in this, but it is a waste of time.

You're right. Although the main use for this was going to be in shards, the Offline KI works fine for this purpose.

[GPNMilano]

As far as a Nexus for Devs it's really not necessary. Assuming that testing will be done on online shards, those authorized to do the testing (the age writer and whoever is running the shards that it will be on) can simply use an internal client that can be used for this purpose. The internal clients have a lot of the stuff that the offline KI does built into them (sdl changes, link commands, spawn commands etc) that are necessary for bug testing a new age. All of which can be done with local data so the age never has to go to anyone but those developing it, and the shard owners. After which, once it's ready for release, the shard owner can simply put the age onto their shard and include it into whatever choice of integration of fan ages that's finally decided upon.

The way I see it, every age writer will have their own personal preference for the shard they wish to do their testing on. This will probably be a choice that ultimately will come down to the writer. Each will feel a kinship with a friend or community member that they trust, that has a shard. They will develop on that shard, and then distribute to the other shards if they choose to once their age is completed.

[nathan2055]

As far as a Nexus for Devs it's really not necessary. Assuming that testing will be done on online shards, those authorized to do the testing (the age writer and whoever is running the shards that it will be on) can simply use an internal client that can be used for this purpose. The internal clients have a lot of the stuff that the offline KI does built into them (sdl changes, link commands, spawn commands etc) that are necessary for bug testing a new age. All of which can be done with local data so the age never has to go to anyone but those developing it, and the shard owners. After which, once it's ready for release, the shard owner can simply put the age onto their shard and include it into whatever choice of integration of fan ages that's finally decided upon.

The way I see it, every age writer will have their own personal preference for the shard they wish to do their testing on. This will probably be a choice that ultimately will come down to the writer. Each will feel a kinship with a friend or community member that they trust, that has a shard. They will develop on that shard, and then distribute to the other shards if they choose to once their age is completed.

You're right, if bug testing commands are made available to testers, then I guess there isn't need for a Nexus. Although there is still posibility for use in open testing, that can be implemented it the new WNexus most likely.

Please direct further conversation to the main thread.

[Sirius]

Yes, there is no real need of a whole Nexus only for developers. The Writer's Nexus should be enough.

About the categories, Guild-specific Ages... Well, someone will have to decide. Anyway, with all the different opinions, there will always be some people who won't agree the way Ages are sorted.

Yes this would be more IC but the KI has also gotten way too fancy. I see no problem for an Admin to have the type of KI that we now poccess, but the regular explorer should only have the original Cyan KI...

I fully agree. Yeah, it is useful to have /jump to take nice screenshots or /link to go somewhere quickly, but still... all these function are only useful for Age developers.
But we should keep this idea for another topic .

[Aloys]

Random suggestion: as this project is starting to take off; should we ask for a new project subforum to discuss all this more easily?

[nathan2055]

Random suggestion: as this project is starting to take off; should we ask for a new project subforum to discuss all this more easily?

Actually, that's not a half bad idea! Let's request something.

[Whilyam]

Ugh. We don't need all these nexuses... nexi... whatever.

[nathan2055]

Ugh. We don't need all these nexuses... nexi... whatever.

I agree that the Developer Nexus isn't necessary. But a project forum to discuss this would help, instead of ideas being lost in a thread that has more posts than the "Introduce Yourself" thread.