User:Colm/Trimester2-assesment: Difference between revisions

From XPUB & Lens-Based wiki
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
=== connecting previous assessment ===
=== connecting previous assessment ===


[http://pzwart1.wdka.hro.nl/~colm/trimester-1_assessment/ link to trim 1]
 
 
* [http://pzwart1.wdka.hro.nl/~colm/trimester-1_assessment/ link to trim 1 assessment presentation]
* [https://pzwiki.wdka.nl/mediadesign/User:Colm/Trimester2-assesment this page on PZ wiki]
* [http://pzwart1.wdka.hro.nl/~colm/trimester-2_assessment/2016_04_05-trim2-assessment.html this page on PZwart1 server]


Slowly moving towards a broader consideration of interface and black boxing. Was the clarity I was calling for just a result of logical development following a method of boxing tools & utilities up? Are these boxes in a chain sequence or is it more organic? Where do I, the user, stand in this sequence?
Slowly moving towards a broader consideration of interface and black boxing. Was the clarity I was calling for just a result of logical development following a method of boxing tools & utilities up? Are these boxes in a chain sequence or is it more organic? Where do I, the user, stand in this sequence?


[[File:researchingplan3-2.JPG|class=research-plan1]] [[File:researchingplan3-1.JPG|class=research-plan2]]
The 'necessity' for such a system is clear, I'm glad one does not have to run each intricate item and dependency when executing a task. This model is not flawed or even really broken in any way. I'm looking at a logical consequence of this modeling: it's ''opaqueness''. (Looping back to this seems terribly logical. It is suddenly quite a simple point to be looking at my research from, but anyway.)
The 'necessity' for such a system is clear, I'm glad one does not have to run each intricate item and dependency when executing a task. This model is not flawed or even really broken in any way. I'm looking at a logical consequence of this modeling: it's ''opaqueness''. (Looping back to this seems terribly logical. It is suddenly quite a simple point to be looking at my research from, but anyway.)


Line 25: Line 30:
=== maps! schemes! ===
=== maps! schemes! ===


[[File:https://pzwiki.wdka.nl/mw-mediadesign/images/1/12/Montage-5.png|class=plan]]
[[File:Montage-5.png|class=plan]]
http://noahveltman.com/internet-shape/
http://noahveltman.com/internet-shape/
[[File:http://internet-atlas.net/img-web/relief33.svg|class=plan]] [[File:http://internet-atlas.net/img-web/cadre11.png|class=plan]] [[File:http://internet-atlas.net/img-web/divise13.jpg|class=plan]] [[File:http://internet-atlas.net/img-web/en-idiot1.svg|class=plan]] [[File:http://internet-atlas.net/img-web/en-collage2.svg|class=plan]]
[[File:http://internet-atlas.net/img-web/relief33.svg|class=plan]] [[File:http://internet-atlas.net/img-web/cadre11.png|class=plan]] [[File:http://internet-atlas.net/img-web/divise13.jpg|class=plan]] [[File:http://internet-atlas.net/img-web/en-idiot1.svg|class=plan]] [[File:http://internet-atlas.net/img-web/en-collage2.svg|class=plan]]
Line 45: Line 50:
I understand why these technologies are boxed up, and why these boxes must exist. I am fine with them, but understanding their sequence, and where I stand in their chain could be valuable.
I understand why these technologies are boxed up, and why these boxes must exist. I am fine with them, but understanding their sequence, and where I stand in their chain could be valuable.


So I started to look at the spaces between the boxes. Leverage points. Friction points, where it might be possible to insert objects (prototypes) in order to reveal the structure.
'''''So I started to look at the spaces between the boxes. Leverage points. Friction points, where it might be possible to insert objects (prototypes) in order to reveal the structure.'''''


=== Prototypes: ===
=== Prototypes: ===


* tips by tools: a bit old now, but still something I want to finish off. I attempted some javascript prototypes but not very promising with my skills at the moment. So I designed what I imagined the item to be, and I also have a CSS only proof of concept. Modes of address in interface.
[http://pzwart1.wdka.hro.nl/~colm/prototypes/tips-by-tools/ tips by tools:] a bit old an idea now, but still something I want to finish off. I attempted some javascript prototypes but not very promising with my skills at the moment. So I designed what I imagined the item to be, and I also have a CSS only proof of concept. Modes of address in interface.
* plug-ins / add-ons 'stylish' redesigns
[http://pzwart1.wdka.hro.nl/~colm/prototypes/cross-publish/ cross publishing]
* greasemonkey
* writing text in Markdown
 
* run a publishing script
 
* places text on a wiki page, pzwart1/~colm/, and a repo backup
-----


plug-ins / add-ons [https://userstyles.org/styles/107022/clean-wiki-splitted 'stylish'] redesigns
[http://wiki.greasespot.net/Main_Page greasemonkey]
[http://pzwart1.wdka.hro.nl/~colm/prototypes/scrollometer/ Scroll-o-meter]
* scroll meter
* scroll meter
* the starting point
* the starting point
Line 61: Line 68:
* non critical
* non critical
* question of the metrics, working out the metrics
* question of the metrics, working out the metrics
* [https://pzwiki.wdka.nl/mediadesign/User:Colm/RW%26RS-scrolling-essay An essay. RW & RM]
* a bit of the physical world on screens
* a bit of the physical world on screens
* relative units — relative inches
* relative units — relative inches

Latest revision as of 14:34, 5 April 2016

trim 2 assessment

Tuesday 5th April 2016 -- 14:00

connecting previous assessment

Slowly moving towards a broader consideration of interface and black boxing. Was the clarity I was calling for just a result of logical development following a method of boxing tools & utilities up? Are these boxes in a chain sequence or is it more organic? Where do I, the user, stand in this sequence?

Researchingplan3-2.JPG Researchingplan3-1.JPG The 'necessity' for such a system is clear, I'm glad one does not have to run each intricate item and dependency when executing a task. This model is not flawed or even really broken in any way. I'm looking at a logical consequence of this modeling: it's opaqueness. (Looping back to this seems terribly logical. It is suddenly quite a simple point to be looking at my research from, but anyway.)

I'm putting aside the moralistic and fearful opinions I have voiced between the start of the year and now, in order to concentrate on projects that might generate discussion / opinions for the audience it self.

In attempting to answer the question around the structure or sequence of the black boxes scheme, I collected a few examples of attempts of visualisations:


maps! schemes!

Montage-5.png http://noahveltman.com/internet-shape/ File:Http://internet-atlas.net/img-web/relief33.svg File:Http://internet-atlas.net/img-web/cadre11.png File:Http://internet-atlas.net/img-web/divise13.jpg File:Http://internet-atlas.net/img-web/en-idiot1.svg File:Http://internet-atlas.net/img-web/en-collage2.svg http://internet-atlas.net/ [[File:|class=plan]] Michael's 'where does the code run' drawing on the wiki? [[File:|class=plan]] 'if you please draw me a cloud' ?

then I tried a few more basic ones, to actually see if I could draw out what I thought I knew

File:IMG 20160403 193533-crop.jpg File:IMG 20160403 193508-crop.jpg

Temporary conclusion:

I understand why these technologies are boxed up, and why these boxes must exist. I am fine with them, but understanding their sequence, and where I stand in their chain could be valuable.

So I started to look at the spaces between the boxes. Leverage points. Friction points, where it might be possible to insert objects (prototypes) in order to reveal the structure.

Prototypes:

tips by tools: a bit old an idea now, but still something I want to finish off. I attempted some javascript prototypes but not very promising with my skills at the moment. So I designed what I imagined the item to be, and I also have a CSS only proof of concept. Modes of address in interface. cross publishing

  • writing text in Markdown
  • run a publishing script
  • places text on a wiki page, pzwart1/~colm/, and a repo backup

plug-ins / add-ons 'stylish' redesigns greasemonkey Scroll-o-meter

  • scroll meter
  • the starting point
  • an excuse to learn js
  • non critical
  • question of the metrics, working out the metrics
  • An essay. RW & RM
  • a bit of the physical world on screens
  • relative units — relative inches
  • protoype homepage
  • plug-in method ?

prototype ideas

  • visible traceroute, claim how complicated your page is!
  • cookie display?

live notes, tutorials, etc

I write up these quick notes and thoughts, and try to date them. They stay collected in a folder called drafts to lower expectations:


Retrieved from "https://pzwiki.wdka.nl/mw-mediadesign/index.php?title=User:Colm/Trimester2-assesment&oldid=93869"