rincewind Posted December 10, 2004 Report Share Posted December 10, 2004 Hi, those who have followed the appropriate threads in the Programming forum and the one about the xnet-webinterface in CTD already know, that we well have to assign each xnet entry a symbolic name. In the xml file for the xnet this will replace the current name string.The name to show in he GUI will be looked up in a language file.The symbolic name will for example be used to assign each entry the right model and for being able to link the right xnet-entry to an inventory item. Sp what we should agree on her is some form of naming scheme for those names so it doesn't get too confusing. For now, the generel direction goes somewhere towards ITEM_PLASMA_CANNON, ALIEN_GREY, ALIEN_GREY_AUTOPSY, etc. But there has never been official talk about it. So here's room for discussion, now... Greetings, Rincewind Link to comment Share on other sites More sharing options...
Guest Azrael Posted December 10, 2004 Report Share Posted December 10, 2004 Hi, those who have followed the appropriate threads in the Programming forum and the one about the xnet-webinterface in CTD already know, that we well have to assign each xnet entry a symbolic name. In the xml file for the xnet this will replace the current name string.The name to show in he GUI will be looked up in a language file.The symbolic name will for example be used to assign each entry the right model and for being able to link the right xnet-entry to an inventory item. Sp what we should agree on her is some form of naming scheme for those names so it doesn't get too confusing. For now, the generel direction goes somewhere towards ITEM_PLASMA_CANNON, ALIEN_GREY, ALIEN_GREY_AUTOPSY, etc. But there has never been official talk about it. So here's room for discussion, now... Greetings, Rincewind<{POST_SNAPBACK}> IMO we should keep it simple, if it's not going to be shown to the player, then we should follow a pattern like that you suggested. We could group them in: ALIEN_[] (live and autopsies)WEAPON_[] (both Human and Alien, though they could be in two categories)TANK_[] (tanks)ITEM_[] (miscellaneous equipment, both Alien and Human, ditto WEAPON)SHIP_[] (Human aircraft)UFO_[] (Alien Craft)FACILITY_[] (Base Facilities)COMPONENT_[] (UFO components)RESEARCH_[] Link to comment Share on other sites More sharing options...
kander Posted December 11, 2004 Report Share Posted December 11, 2004 (edited) The idea: Category and name as taken from the XML file, for simplicities sake. All in uppercase, spaces replaced with underscores, apostroph's (in UFO's) stripped. WEAPON_HUMAN_PISTOLWEAPON_LIGHT_RIFLEWEAPON_HEAVY_RIFLEWEAPON_AUTO_CANNONWEAPON_ROCKET_LAUNCHERWEAPON_GRENADEWEAPON_PROXIMITY_GRENADEWEAPON_LASER_PISTOLWEAPON_LASER_RIFLEWEAPON_HEAVY_LASER_RIFLEWEAPON_PLASMA_PISTOLWEAPON_PLASMA_RIFLEWEAPON_HEAVY_PLASMA_RIFLEWEAPON_FUSIONBOMB_LAUNCHERWEAPON_ALIEN_GRENADEWEAPON_STUN_LAUNCHERAMMO_PLASMA_RIFLE_CLIPAMMO_HEAVY_PLASMA_RIFLE_CLIPAMMO_STUNBOMBAMMO_FUSION_BOMBAMMO_PISTOL_CLIPAMMO_LIGHT_RIFLE_CLIPAMMO_HEAVY_RIFLE_CLIPEQUIPMENT_HIGH_EXPLOSIVEEQUIPMENT_STUN_BATONEQUIPMENT_MOTION_SENSOREQUIPMENT_FIELD_MEDICAL_KITEQUIPMENT_PSIONIC_AMPLIFIEREQUIPMENT_FLASH_PODEQUIPMENT_STANDARD_ISSUE_UNIFORMEQUIPMENT_LIGHT_ARMOREQUIPMENT_HEAVY_ARMOREQUIPMENT_FLIGHT_ARMOREQUIPMENT_PSIONIC_PROBEEQUIPMENT_SMOKE_GRENADEFACILITY_BARRACKSFACILITY_ACCESS_LIFTFACILITY_SMALL_RADARFACILITY_LARGE_RADARFACILITY_MISSILE_DEFENSEFACILITY_LASER_DEFENSEFACILITY_PLASMA_DEFENSEFACILITY_FUSION_DEFENSEFACILITY_GENERAL_STORESFACILITY_ALIEN_CONTAINMENTFACILITY_PSIONIC_TRAINING_LABFACILITY_GRAV_SHIELDFACILITY_MIND_SHIELDFACILITY_HYPERWAVE_DECODERFACILITY_LABORATORYFACILITY_HANGARFACILITY_WORKSHOPARMAMENT_SIDEWINDERARMAMENT_TITANARMAMENT_CANNONARMAMENT_LASER_CANNONARMAMENT_PLASMA_CANNONARMAMENT_FUSION_MISSILE_LAUNCHERAUTOPSY_MORLOCKAUTOPSY_SATYRIANAUTOPSY_VIPERAUTOPSY_SILABRATEAUTOPSY_ARTOPODAUTOPSY_CLOAKAUTOPSY_GREYAUTOPSY_SPAWNAUTOPSY_RAPTORAUTOPSY_VENTRICULANTAUTOPSY_TERROR_DISKAIRCRAFT_XC-1AIRCRAFT_XC-11AIRCRAFT_XC-2AIRCRAFT_XC-22AIRCRAFT_XC-33RESEARCH_ALIEN_ORIGINSRESEARCH_MARTIAN_SOLUTIONRESEARCH_CYDONIA_BUSTRESEARCH_ALIEN_RESEARCHRESEARCH_ALIEN_ABDUCTIONSRESEARCH_ALIEN_RETALIATIONRESEARCH_ALIEN_SUPPLYCOMPONENT_XENIUM_122COMPONENT_ALIEN_ALLOYCOMPONENT_NAVAGATIONCOMPONENT_XENIUM_REACTORCOMPONENT_UFO_CONSTRUCTIONCOMPONENT_ALIEN_FOODCOMPONENT_ALIEN_ENTERTAINMENTCOMPONENT_ALIEN_SURGERYCOMPONENT_ALIEN_REPRODUCTIONCOMPONENT_ALIEN_EXAMINATION_ROOMUFO_SMALL_SCOUTUFO_MEDIUM_SCOUTUFO_LARGE_SCOUTUFO_BATTLESHIPUFO_INTIMIDATORUFO_HARVESTERUFO_SUPPLY_SHIPUFO_ABDUCTORXCAP_CANNON_TANKXCAP_ROCKET_TANKXCAP_LASER_TANKXCAP_PLASMA_HOVERTANKXCAP_LAUNCHER_HOVERTANKWEAPON_SYSTEM_LASERWEAPON_SYSTEM_PLASMAALIEN_MORLOCKALIEN_SATYRIANALIEN_VIPERALIEN_SILABRATEALIEN_ARTOPODALIEN_CLOAKALIEN_GREYALIEN_SPAWNALIEN_RAPTORALIEN_VENTRICULANTALIEN_TERROR_DISKINTERROGATION_SOLDIERINTERROGATION_MEDICINTERROGATION_COMMANDERINTERROGATION_LEADERINTERROGATION_NAVIGATOR Edited December 11, 2004 by kander Link to comment Share on other sites More sharing options...
guyver6 Posted December 11, 2004 Report Share Posted December 11, 2004 The idea: Category and name as taken from the XML file, for simplicities sake. All in uppercase, spaces replaced with underscores, apostroph's (in UFO's) stripped. WEAPON_HUMAN_PISTOLWEAPON_LIGHT_RIFLEWEAPON_HEAVY_RIFLEWEAPON_AUTO_CANNONWEAPON_ROCKET_LAUNCHER...cutThat looks impressive, Kander . Thou please consult that names with Xenocide names, becouse we're not using original UFO names anymore (copyright issues). Anyway, what about naming Xnet topics different way, as sometime ago Red Knight proposed. In example XNET_* or TOPIC_*, like XNET_WEAPON_AUTO_CANNON (I don't know our name for that weapon ). Why? Here comes why: For items this scheme for naming xnet entries is quite enough. But take an example of RESEARCH_LIVE_NAVIGATOR (example), this can reveal informations about any of the aliens ships, so UFO_something. Having XNET_UFO_* topics distinguish them as xnet entries from UFOs flying around earth. Or an alien research. Researching live alien gives you live alien xnet entry, researchin dead alien gives you an autopsy. How to name researches for those? ALIEN_* or AUTOPSY_*? Having XNET_LIVE_* or XNET_AUTOPSY_* gives you far more flexible design IMHO. Anyway the researches design isn't quite ready becouse when we was making schemas for static data definition, we've encountered few problems (like everyone of us - Red Knight, Rincewind and me - saw the problem of researches in different way), so as I can remember we have delayed the discussion. So, my propositios: ITEM_* - all items, this includes categories like:ITEM_WEAPON_*,ITEM_AMMO_*,or leave it as separateWEAPON_*AMMO_*becouse the "class" of the item is taken from xsd:type attribute in xml file, but we have to make XNet entries names separate from the rest of names, so:XNET_*, like:XNET_WEAPON_*, XNET_AMMO_*, etc. My 2 cents. Guyver Link to comment Share on other sites More sharing options...
rincewind Posted December 11, 2004 Author Report Share Posted December 11, 2004 (discussion of prefixing xnet- entries with XNET_ I'm not quite sure if prefixing them poses other problems, if you have for example a dead alien in your inventory, it would be nice to offer a button leading right to the appropriate xnet-entry (if researched).If the name is different, we would need another xml-file relating aliens (or items) to their appropriate xnet-entries.On the other hand, this would allow for more flexibility... Hmmm.... Rincewind Link to comment Share on other sites More sharing options...
rincewind Posted December 11, 2004 Author Report Share Posted December 11, 2004 (discussion of prefixing xnet- entries with XNET_ I'm not quite sure if prefixing them poses other problems, if you have for example a dead alien in your inventory, it would be nice to offer a button leading right to the appropriate xnet-entry (if researched).If the name is different, we would need another xml-file relating aliens (or items) to their appropriate xnet-entries.On the other hand, this would allow for more flexibility... Hmmm.... RincewindJust had a look at basic.xsd. there, most of the prefixes are already defined, once for all kinds of stuff ITEM_, FACILITY_, etc. But also XNET_*.So I guess, we'll have to use an XNET_-prefix for the xnet-entries and then later have to relate them somewhere to the actual items, etc. Rincewind Link to comment Share on other sites More sharing options...
guyver6 Posted December 12, 2004 Report Share Posted December 12, 2004 (discussion of prefixing xnet- entries with XNET_ I'm not quite sure if prefixing them poses other problems, if you have for example a dead alien in your inventory, it would be nice to offer a button leading right to the appropriate xnet-entry (if researched).If the name is different, we would need another xml-file relating aliens (or items) to their appropriate xnet-entries.On the other hand, this would allow for more flexibility... Hmmm.... RincewindI will be possible. That way or another we need to be able to tell that when we have dead alien in store then we can research it and we need to tell what xnet entries are being actived. So this can be easily used for that feature also. Just had a look at basic.xsd. there, most of the prefixes are already defined, once for all kinds of stuff ITEM_, FACILITY_, etc. But also XNET_*.So I guess, we'll have to use an XNET_-prefix for the xnet-entries and then later have to relate them somewhere to the actual items, etc. RincewindYou know, what is now in schemas doesn't have to stay there forever . If something looks like it could be changed, why wouldn't we do that? Greetings,Guyver Link to comment Share on other sites More sharing options...
red knight Posted December 12, 2004 Report Share Posted December 12, 2004 That is part of the refactoring, if you need to change anything better to do it in the beginning. So in short in the scheme now doesnt means in stone. GreetingsRed Knight Link to comment Share on other sites More sharing options...
Guest Azrael Posted December 12, 2004 Report Share Posted December 12, 2004 But some of the names in the XML file are not final yet, so that eventually will have to be changed, like RESEARCH_MARTIAN_SOLUTIONRESEARCH_CYDONIA_BUSTRESEARCH_ALIEN_RESEARCHRESEARCH_ALIEN_ABDUCTIONSRESEARCH_ALIEN_RETALIATIONRESEARCH_ALIEN_SUPPLYCOMPONENT_XENIUM_122COMPONENT_ALIEN_ALLOYCOMPONENT_NAVAGATIONCOMPONENT_XENIUM_REACTORCOMPONENT_UFO_CONSTRUCTIONCOMPONENT_ALIEN_FOOD Alien Alloys, UFO construction and Cydonia or Bust names haven't yet been decided. I'm not sure how this affects your work, but I'd just let you know Link to comment Share on other sites More sharing options...
guyver6 Posted December 14, 2004 Report Share Posted December 14, 2004 But some of the names in the XML file are not final yet, so that eventually will have to be changed, like RESEARCH_MARTIAN_SOLUTIONCOMPONENT_ALIEN_FOOD Alien Alloys, UFO construction and Cydonia or Bust names haven't yet been decided. I'm not sure how this affects your work, but I'd just let you know This doesn't affect our work right now, just becouse it's yet to be programmed, so don't worry, the names will be developed in time, and when something will be needed then I'm sure that we'll ask you (CTD) to deliver proper name . Guyver Link to comment Share on other sites More sharing options...
mikker Posted December 15, 2004 Report Share Posted December 15, 2004 (edited) What about the "get more types - get more info" idea of the live alien research? so an alien could go into categories: Field data: Reports from field Autopsy: Autopsy details Specimen: Any live Bagground: Live Leader/Commander (medic and engineer too) That would then become....... ALIEN_GREY_FIELDALIEN_GREY_AUTOPSYALIEN_GREY_SPECIMENALIEN_GREY_STORY (I'd imagine that they'd follow each other in 1 doc) Edited December 15, 2004 by mikker Link to comment Share on other sites More sharing options...
Recommended Posts