The name can still be separated when stored/transmitted, the client and other places where you insert your name would simply look for the space character and use it to separate things when necessary.
Melinda Green escreveu: > You'll get a lot of support from Philip for merging first+last names > as it is one of his biggest pet peeves, but I'm pretty sure that this > is *way* out of scope for the Snowglobe project since the assumption > of first and last names is shot all through client and server code. It > would likely require a concerted effort by a Linden, and given all the > higher priorities, I doubt we'll see this happen anytime soon unless > Philip personally decides to take a crack at it. > > -Melinda > > Tigro Spottystripes wrote: >> I think this would be a good time to bring up >> http://jira.secondlife.com/browse/WEB-968 ' merge "First name" and "Last >> name" into "Full name" ' >> >> Melinda Green escreveu: >> >>> Mike Monkowski wrote: >>> >>>> Cypren Christenson wrote: >>>> >>>>> * The use of a combo box for the first field, with selection setting >>>>> the contents of multiple fields, may be confusing. Any other options >>>>> here that would be more intuitive while also keeping the aesthetic >>>>> sensibility of the existing login screen would be welcome. >>>>> >>>> How about auto completion? >>>> >>> Hey, that's a great idea! It would require a tricky special >>> implementation of auto-complete that would offer matching first+last >>> name pairs and then on acceptance would separate them to fill in the >>> other text boxes, but that UI would likely be more natural to a new >>> user than an editable drop-down field. This still requires a way for >>> users to erase entries from the list but I think my previous >>> suggestion of tying that action to unchecking the "remember >>> password" check box might work. >>> >>> >>>>> * Possible security concerns with the characters selected for the >>>>> delimiters. With LLPanel::childSetPrevalidate to filter characters >>>>> from input, the worst-case scenario seems to be that a malicious user >>>>> could edit settings files and induce boost::tokenizer to fail to >>>>> parse >>>>> the string correctly. In that event, we would simply clear the >>>>> relevant fields. Are there other concerns I'm missing? >>>>> >>>> I think the settings are FirstName and LastName. I don't see the >>>> password in the settings file. But instead of mashing everything >>>> together, you could create setting called FirstNameAlt1, >>>> FirstNameAlt2, LastNameAlt1, LastNameAlt2, ... You'd have to make >>>> sure that you move the names up the list when one gets deleted, >>>> otherwise you wouldn't know where to stop, since I don't think the >>>> settings lookup allows a wildcard. >>>> >>> This would be new data. I like Cypren's suggestion to mash it all >>> together into a single (new) string value rather than as separate >>> settings and/or places that would only need to be gathered all >>> together anyway. For compatibility, I suppose it could look for the >>> old First/Last Name settings when the new setting is not found but I >>> don't see that as important. >>> >>> Good luck! >>> -Melinda >>> _______________________________________________ >>> Policies and (un)subscribe information available here: >>> http://wiki.secondlife.com/wiki/SLDev >>> Please read the policies before posting to keep unmoderated posting >>> privileges >>> >>> >> >> > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
