User talk:Garman - Revision history

Garman: /* Photo sizes */ cmt

2009-02-22T02:16:29Z

Photo sizes: cmt

← Older revision		Revision as of 02:16, 22 February 2009
Line 102:		Line 102:
	:::::Refactoring is what I'm doing to the TIGHAR website--without altering it. See [[signal strength]]. There is a huge wealth of information scattered on the TIGHAR website that can be re-organized and synthesized. So the wiki allows accumulation of new information while also refactoring information already acquired.		:::::Refactoring is what I'm doing to the TIGHAR website--without altering it. See [[signal strength]]. There is a huge wealth of information scattered on the TIGHAR website that can be re-organized and synthesized. So the wiki allows accumulation of new information while also refactoring information already acquired.
	:::::[[User:Moleski\|Moleski]] 02:09, 22 February 2009 (UTC)		:::::[[User:Moleski\|Moleski]] 02:09, 22 February 2009 (UTC)
			:::::::Yes. The presentation of information has much sway on how that information is understood and learned. The classic site will always have its lasting strengths, meanwhile the wiki will also have its many and sundry strengths, which is why having both is cool and yep, the pith of a wiki is the taking in of new information whilst building on the bones of the old (and heh heh... sometimes refactorin' them bones, too :) [[User:Garman\|Garman]] 02:16, 22 February 2009 (UTC)

Moleski at 02:09, 22 February 2009

2009-02-22T02:09:03Z

← Older revision		Revision as of 02:09, 22 February 2009
Line 97:		Line 97:

	::::Yes, the classic site is its own world (articles here can link to it and one day, I glark, it will very likely link over here). I see nothing untowards about bringing over lots of information from the classic TIGHAR site, as TIGHAR editors along with Pat and Ric may see fit over time. The classic site does what it does in a helpful way, the wiki will do what ''it'' does in a helpful way and the two can easily thrive together. As you hint, as this Ameliapedia grows, folks will come to understand it more: Both will likely be enhanced by this, yet each will/should stand on their own. [[User:Garman\|Garman]] 02:04, 22 February 2009 (UTC)		::::Yes, the classic site is its own world (articles here can link to it and one day, I glark, it will very likely link over here). I see nothing untowards about bringing over lots of information from the classic TIGHAR site, as TIGHAR editors along with Pat and Ric may see fit over time. The classic site does what it does in a helpful way, the wiki will do what ''it'' does in a helpful way and the two can easily thrive together. As you hint, as this Ameliapedia grows, folks will come to understand it more: Both will likely be enhanced by this, yet each will/should stand on their own. [[User:Garman\|Garman]] 02:04, 22 February 2009 (UTC)

			:::::Help! I've been refactored! :-O
			:::::And hit my first edit conflict. WHEE! It's great not to be the only one here. Thanks!
			:::::Refactoring is what I'm doing to the TIGHAR website--without altering it. See [[signal strength]]. There is a huge wealth of information scattered on the TIGHAR website that can be re-organized and synthesized. So the wiki allows accumulation of new information while also refactoring information already acquired.
			:::::[[User:Moleski\|Moleski]] 02:09, 22 February 2009 (UTC)

Garman: /* Photo sizes */ cmt

2009-02-22T02:06:29Z

Photo sizes: cmt

← Older revision		Revision as of 02:06, 22 February 2009
Line 96:		Line 96:
	::::Galleries are wonderful! They very much fit the clickable image notion of a wiki. I forgot to say, any logged in user can change the default size of thumbnail they see (without changing anyone else's default size) in their user preferences. Some readers will already be familiar with this option, from having used other wikis.		::::Galleries are wonderful! They very much fit the clickable image notion of a wiki. I forgot to say, any logged in user can change the default size of thumbnail they see (without changing anyone else's default size) in their user preferences. Some readers will already be familiar with this option, from having used other wikis.

	::::Yes, the classic site is its own world (articles here can link to it and one day, I glark, it will very likely link over here). I see nothing untowards about bringing ~~any and all~~ information from the classic TIGHAR site, as TIGHAR editors along with Pat and Ric see fit. The classic site does what it does in a helpful way, the wiki will do what ''it'' does in a helpful way and the two can easily thrive together. As you hint, as this ~~side~~ grows, folks will come to understand it more: Both will likely be enhanced by this, yet each will/should stand on their own. [[User:Garman\|Garman]] 02:04, 22 February 2009 (UTC)		::::Yes, the classic site is its own world (articles here can link to it and one day, I glark, it will very likely link over here). I see nothing untowards about bringing over lots of information from the classic TIGHAR site, as TIGHAR editors along with Pat and Ric may see fit over time. The classic site does what it does in a helpful way, the wiki will do what ''it'' does in a helpful way and the two can easily thrive together. As you hint, as this Ameliapedia grows, folks will come to understand it more: Both will likely be enhanced by this, yet each will/should stand on their own. [[User:Garman\|Garman]] 02:04, 22 February 2009 (UTC)

Garman: /* Photo sizes */ cmt

2009-02-22T02:04:33Z

Photo sizes: cmt

← Older revision		Revision as of 02:04, 22 February 2009
Line 93:		Line 93:

	:::[[User:Moleski\|Moleski]] 01:01, 22 February 2009 (UTC)		:::[[User:Moleski\|Moleski]] 01:01, 22 February 2009 (UTC)

			::::Galleries are wonderful! They very much fit the clickable image notion of a wiki. I forgot to say, any logged in user can change the default size of thumbnail they see (without changing anyone else's default size) in their user preferences. Some readers will already be familiar with this option, from having used other wikis.

			::::Yes, the classic site is its own world (articles here can link to it and one day, I glark, it will very likely link over here). I see nothing untowards about bringing any and all information from the classic TIGHAR site, as TIGHAR editors along with Pat and Ric see fit. The classic site does what it does in a helpful way, the wiki will do what ''it'' does in a helpful way and the two can easily thrive together. As you hint, as this side grows, folks will come to understand it more: Both will likely be enhanced by this, yet each will/should stand on their own. [[User:Garman\|Garman]] 02:04, 22 February 2009 (UTC)

Garman: /* Photo sizes */ refactoring Marty's comments into one group

2009-02-22T01:46:53Z

Photo sizes: refactoring Marty's comments into one group

← Older revision		Revision as of 01:46, 22 February 2009
Line 71:		Line 71:

	::Both of these will wrap the text seamlessly.		::Both of these will wrap the text seamlessly.



			::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

			::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" TIGHAR web experience (which I also like very much), it's there for them.

			::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)

	:::I'll go to thumbnails right and left. I hope you don't mind photo galleries here and there:		:::I'll go to thumbnails right and left. I hope you don't mind photo galleries here and there:
	:::*[[maps of Nikumaroro]]		:::*[[maps of Nikumaroro]]
	:::*[[sextant box found on Nikumaroro]]		:::*[[sextant box found on Nikumaroro]]

	::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

	:::Thanks for the insight!		:::Thanks for the insight!

	::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" TIGHAR web experience (which I also like very much), it's there for them.

	:::1. It's where most of the fundamental information already is. I don't want to reinvent the wheel. I do want to add value. See the summary table in [[Earhart]] that I did yesterday. It's from Ric's article. See also the draft I just started on [[failure to communicate]].		:::1. It's where most of the fundamental information already is. I don't want to reinvent the wheel. I do want to add value. See the summary table in [[Earhart]] that I did yesterday. It's from Ric's article. See also the draft I just started on [[failure to communicate]].
Line 87:		Line 91:

	:::3. I'd rather go at a reworking of the information that leaves the classic site untouched for those who prefer the classic site. No need to rile the natives. I think the project is worth the time I have and will invest in it because, as Siddhartha said to Mara, "Some will understand." :o)		:::3. I'd rather go at a reworking of the information that leaves the classic site untouched for those who prefer the classic site. No need to rile the natives. I think the project is worth the time I have and will invest in it because, as Siddhartha said to Mara, "Some will understand." :o)

	~~::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)~~

	:::[[User:Moleski\|Moleski]] 01:01, 22 February 2009 (UTC)		:::[[User:Moleski\|Moleski]] 01:01, 22 February 2009 (UTC)

Moleski at 01:01, 22 February 2009

2009-02-22T01:01:11Z

← Older revision		Revision as of 01:01, 22 February 2009
Line 71:		Line 71:

	::Both of these will wrap the text seamlessly.		::Both of these will wrap the text seamlessly.

			:::I'll go to thumbnails right and left. I hope you don't mind photo galleries here and there:
			:::*[[maps of Nikumaroro]]
			:::*[[sextant box found on Nikumaroro]]

	::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.		::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

			:::Thanks for the insight!

	::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" TIGHAR web experience (which I also like very much), it's there for them.		::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" TIGHAR web experience (which I also like very much), it's there for them.

			:::1. It's where most of the fundamental information already is. I don't want to reinvent the wheel. I do want to add value. See the summary table in [[Earhart]] that I did yesterday. It's from Ric's article. See also the draft I just started on [[failure to communicate]].

			:::2. It's easier to get folks cooperating on the wiki. The website (apart from the Forum) is essentially a one-woman show. The wiki will allow lots more TIGHAR researchers to share what they've found. See, for example, [[Bones II]] and the articles that Tom King put up (they're not on the classic site). The intra-wiki links make the information in the wiki more accessible, too.

			:::3. I'd rather go at a reworking of the information that leaves the classic site untouched for those who prefer the classic site. No need to rile the natives. I think the project is worth the time I have and will invest in it because, as Siddhartha said to Mara, "Some will understand." :o)

	::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)		::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)

			:::[[User:Moleski\|Moleski]] 01:01, 22 February 2009 (UTC)

Garman: /* Photo sizes */ +

2009-02-21T22:23:12Z

Photo sizes: +

← Older revision		Revision as of 22:23, 21 February 2009
Line 74:		Line 74:
	::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.		::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

	::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" experience (which I also like very much), it's there for them.		::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" TIGHAR web experience (which I also like very much), it's there for them.

	::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)		::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)

Garman: /* Photo sizes */ ++

2009-02-21T22:22:28Z

Photo sizes: ++

← Older revision		Revision as of 22:22, 21 February 2009
Line 73:		Line 73:

	::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.		::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

			::Oh, one more thing, to stir up thinking... why try to re-weave the classic TIGHAR site, which is so cool as it is, into a "another version" of its own self on Ameliapedia, which could skirt the very benefits of having a wiki? If users want the "classic" experience (which I also like very much), it's there for them.

	::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)		::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)

Garman: /* Photo sizes */ t

2009-02-21T22:17:45Z

Photo sizes: t

← Older revision		Revision as of 22:17, 21 February 2009
Line 60:		Line 60:
	::This said, there are reasons why one might not want to lay the "look and feel" of a static website onto a wiki. First, a wiki is "dynamically" edited, the layout is going to get shifted and nudged about quite a lot, hence simplicity can be very helpful. Second, wikis tend to be taken as more "inter-operable" than standard websites: These days, users have many and sundry display sizes. Large, centered images will often not fit onto a screen or may otherwise upset the reader's flow.		::This said, there are reasons why one might not want to lay the "look and feel" of a static website onto a wiki. First, a wiki is "dynamically" edited, the layout is going to get shifted and nudged about quite a lot, hence simplicity can be very helpful. Second, wikis tend to be taken as more "inter-operable" than standard websites: These days, users have many and sundry display sizes. Large, centered images will often not fit onto a screen or may otherwise upset the reader's flow.

	::Moreover, centered images do not "wrap" the text. With careful layout, this can be ok and worthwhile, but more often, a lack of text wrapping can easily lead a less reader-friendly page.		::Moreover, centered images do not "wrap" the text. With careful layout, this can be ok and worthwhile, but more often, a lack of text wrapping can easily lead to a less reader-friendly page.

	::The standard is to "thumbnail" the image at the right of the page with this code:		::The standard is to "thumbnail" the image at the right of the page with this code:

Garman: /* Photo sizes */ + wrapping

2009-02-21T22:15:00Z

Photo sizes: + wrapping

← Older revision		Revision as of 22:15, 21 February 2009
Line 59:		Line 59:

	::This said, there are reasons why one might not want to lay the "look and feel" of a static website onto a wiki. First, a wiki is "dynamically" edited, the layout is going to get shifted and nudged about quite a lot, hence simplicity can be very helpful. Second, wikis tend to be taken as more "inter-operable" than standard websites: These days, users have many and sundry display sizes. Large, centered images will often not fit onto a screen or may otherwise upset the reader's flow.		::This said, there are reasons why one might not want to lay the "look and feel" of a static website onto a wiki. First, a wiki is "dynamically" edited, the layout is going to get shifted and nudged about quite a lot, hence simplicity can be very helpful. Second, wikis tend to be taken as more "inter-operable" than standard websites: These days, users have many and sundry display sizes. Large, centered images will often not fit onto a screen or may otherwise upset the reader's flow.

			::Moreover, centered images do not "wrap" the text. With careful layout, this can be ok and worthwhile, but more often, a lack of text wrapping can easily lead a less reader-friendly page.

	::The standard is to "thumbnail" the image at the right of the page with this code:		::The standard is to "thumbnail" the image at the right of the page with this code:
Line 67:		Line 69:

	*<code><nowiki>[[Image:snap.png\|left\|thumb\|this is my caption]]</nowiki></code>		*<code><nowiki>[[Image:snap.png\|left\|thumb\|this is my caption]]</nowiki></code>

			::Both of these will wrap the text seamlessly.

	::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.		::At first, the notion of having smaller images all the same size on a page can seem unsettling to someone thinking in terms of an editorially locked website along with the strong impact and drama a big photo can have. However, users of wiki interfaces know (or very quickly learn) they have only to click on the image to see it in its full size. This isn't "more fit or more helpful" than a standard website using a more magazine like layout, which can be wonderful (I do this on my own websites), but has to do with how wikis have developed and how they are most often used. Lastly, keeping to a standard layout format on each page makes things much easier for both editors and readers and tends to draw them more deeply into the content. So, anything goes as to how a wiki might be layed out, but there are reasons why sticking to some ways of doing things can make using a wiki more rewarding.

	::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)		::What do you think? [[User:Garman\|Garman]] 22:11, 21 February 2009 (UTC)