Subject:
|
Re: Perspectives on a Lego Community Website
|
Newsgroups:
|
lugnet.general, lugnet.org
|
Date:
|
Fri, 19 Sep 2003 19:40:17 GMT
|
Viewed:
|
1892 times
|
| |
|
|
In lugnet.general, Paul Hartzog wrote:
| |
Actually that’s backwards. Administrators could update information through a
central web-interface and then any information they wanted displayed on their
own pages would be done using web objects that retrieve information from
various community databases.
For example,
A central site registry where you put the URL for your site into a db could
be used to allow anyone to link to your site on their own page using a web
object which would automatically update if you change your URL in the central
database, i.e. no one would actually have to know your URL, just how to
link to you using a web object.
More powerfully,
as I mentioned in the interview, we could standardize our color-names if TLC
gave us that info (which they subsequently did). I think simple
implementations like this would be a good place to start: colors, part
numbers, set numbers (again TLC determines those), etc.
|
Ok, I understand now. And I like it a lot. IMO, that would be pretty darn cool.
(And also from what stuff I know, a lot easier to implement.)
So it all sounds good. Does anyone else have other ideas for places where this
kind of thing could be useful?
Jason Spears | BrickCentral | MichLUG
|
|
Message is in Reply To:
 | | Re: Perspectives on a Lego Community Website
|
| (...) Actually that's backwards. Administrators could update information through a central web-interface and then any information they wanted displayed on their own pages would be done using web objects that retrieve information from various (...) (21 years ago, 19-Sep-03, to lugnet.general, lugnet.org, FTX)
|
10 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
