[Bf-docboard] Original (higher quality) manual images available

[Tobias Heinke]

Hello Campbell,

Sure it is extra work, but it can be used parallel with images.
With screenshot you limiting yourself by keeping in mind that the image 
can't be to large in the end.

Talking about images:
Please: Scale down the browser window to around 500px width - until the 
menu collapse:
https://www.blender.org/manual/editors/nla.html#strips
:D

Fragile: When a problem occures the "bug" is in the single CSS-file and 
can be fixed afterwards.
But even screenshot of the viewport with flat color shading could be 
easily exported thanks to Freestyle SVG-export.
Ya, WebGl would be awesome - looking forward to year 2020.

The integration of html-fragments is tricky:

 1. Deliver xml + script to user. Script generates html fragment and
    adds it into the frame.
 2. Html fragment paced directly into manual page. (Sphinx?)
 3. Stand-alone html-page load with an i-frame.

 1. CPU intensiv (mobile), security
 2. Only if the merging is done with Sphinx-scripting
 3. I-Frame need a fixed scaling [html5] (script: side scale - i-frame
    scale)

I-frame are used on many MDN pages "live result"(scroll up pls):
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Forms/Advanced_styling_for_HTML_forms#Dealing_with_the_select_nightmare

Open fonts and kerning... But kerning in browser seams to be a use or 
not use thing.
The problem the fancy scaling that Blender does: effective pixel size 
(screen size/pixel density).
Affecting everthing independently: font size, border radius (alias round 
edge), margin
That's why Blender looks different on every screen. (- also every 
screenshot looks different)

I've implemented conditions and working on defining enviroment varibles 
(e.g. context.active_object.mode = "OBJECT").
I had to digged deep into Blender code:
[layout.prog] is heavly overloaded spreads up and nearrows down again 
"everything's a button = a rectangle = html box-model",
UI-Code in the modules/editors/spaces, 1. Level Data Management "RNA". 
Quirks compability code.

Thumbnails? - Html fragments can be scale to every size like SVG.

Next time I've planned to show a demo for side by side comparison.

Tobias

Am 27.02.2016 um 06:32 schrieb Campbell Barton:
> Hi Tobias,
> While this seems like a fun challenge, I'm quite skeptical that this
> would be usable for us.
>
> Currently document writers can take a screenshot and commit it, I can
> only assume this would take some extra step when adding images.
>
> On the other hand if this was made into a build-step, its going to
> slow-down building documentation.
>
> It also seems rather fragile - subtle differences in font kerning are
> likely to make text display differently (where it may not fit).
> And this would have to somehow support thumbnails too.
>
> Solid colors already compress quite well with PNG, and shaded areas of
> the screen will have to be images anyway (unless you incorporate WebGL
> into this system).
>
> The potential to have interactive parts of the image could be useful
> in some cases,
> however that can be done using images too.
>
> On Sat, Feb 20, 2016 at 3:55 AM, Tobias Heinke
> <heinke.tobias at t-online.de> wrote:
>> Hi everybody,
>>
>> On big image files - huge repository
>>
>> 70% of the images are screenshot of the UI.
>> I've started a attempt to solve this problem once and for all
>> by copying the Blender UI to HTML + CSS + SVG.
>> This is done by parsing an XML file with JS to HTML.
>> The generated html fragments can then be used as a replacement for the
>> images.
>> The icons are the original Blender svg-icons.
>>
>> The biggest problem is the 3D shading Blender does,
>> but I found work arounds.
>>
>> https://github.com/tobiasHeinke/BlenderWebUI
>>
>> The Fun start with the preserved interactivity:
>> CSS hover or with JS script:
>> Show tooltips, dynamically highlight regions, functional widgets...
>> User can select Blender theme: change CSS file,
>> OS specific key map
>>
>> This interface could also be used by the blend4web project.
>> Or does it even already exists somewhere out there on the interweb?
>>
>> Greetings
>> Tobias
>>
>>
>> Am 09.02.2016 um 19:45 schrieb gandalf3:
>>
>> I created a task for this, if it's of any use
>>
>> On 02/09/2016 08:49 AM, Campbell Barton wrote:
>>
>> Hi, when moving to away from the wiki we chose to use quite compressed
>> images to avoid a huge repository.
>>
>> Since then, there are some images which look noticeably low quality,
>> so I've gone back and made an archive of all the images from the wiki.
>>
>> Realize its not so convenient to manually go over each image, so we
>> can just do this for prominent images with noticeable problems.
>>
>> Here's the archive:
>> http://download.blender.org/ftp/ideasman42/wiki_manual_images.tar (122mb).
>>
>>
>>
>>
>> _______________________________________________
>> Bf-docboard mailing list
>> Bf-docboard at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-docboard
>>
>>
>>
>> _______________________________________________
>> Bf-docboard mailing list
>> Bf-docboard at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-docboard
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20160227/89e53085/attachment.htm