Hackfest2015 Topics - Revision history

Frigory: Category:Hackfest

2016-06-15T14:55:17Z

← Older revision		Revision as of 14:55, 15 June 2016
Line 207:		Line 207:

	Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.		Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.

			[[Category:Hackfest]]

Tavmjong: /* Harfbuzz: Better CSS support and User Fonts (WOFF) */

2015-05-05T11:08:58Z

Harfbuzz: Better CSS support and User Fonts (WOFF)

← Older revision		Revision as of 11:08, 5 May 2015
Line 173:		Line 173:

	<p style="width:60em">There will be a Harfbuzz documenting session taking place at the same time as the Inkscape Hackfest. Maybe we can get some expertise on how to improve our font handling. CSS now has much more sophisticated ways of selecting alternative glyphs that Harfbuzz may support. Also, it would be nice to be able to use user fonts, in particular WOFF fonts, into Inkscape. At the moment we rely on Pango for all our font related stuff and Pango's support for new CSS stuff and for user fonts is negligible if completely non-existent.</p>		<p style="width:60em">There will be a Harfbuzz documenting session taking place at the same time as the Inkscape Hackfest. Maybe we can get some expertise on how to improve our font handling. CSS now has much more sophisticated ways of selecting alternative glyphs that Harfbuzz may support. Also, it would be nice to be able to use user fonts, in particular WOFF fonts, into Inkscape. At the moment we rely on Pango for all our font related stuff and Pango's support for new CSS stuff and for user fonts is negligible if completely non-existent.</p>

			<p style="width:60em">'''We met with the Harfbuzz developers.''' In particular, we discussed ''user fonts'' and ''OpenType'' features with Behdad. Behdad has already push [http://mces.blogspot.fr/2015_05_01_archive.html changes into Pango that will allow us eventually to support WOFF fonts]. He is also working on adding the ability to access OpenType font features through Pango (various ligatures, swashes, etc.) and should have in done within the week.</p>

	=== Swatches ===		=== Swatches ===

Tavmjong: /* Make Systems */

2015-05-05T10:58:13Z

Make Systems

← Older revision		Revision as of 10:58, 5 May 2015
Line 183:		Line 183:
	=== Make Systems ===		=== Make Systems ===

	'''~~UNDER REVIEW~~''': Alex is doing an independent comparison to see if the simplicity of WAF outways the popularity of CMAKE.		'''DONE''': Alex is doing an independent comparison to see if the simplicity of WAF outways the popularity of CMAKE.

			<p style="width:60em">'''We will start with CMake''': We have a partial build system already done with CMake. This will be a great improvement over autotools. We'll evaluate CMake vs. WAF again at a later date.</p>

	==== CMake (Bryce) ====		==== CMake (Bryce) ====

Tavmjong: /* Misc */

2015-05-05T10:54:15Z

Misc

← Older revision		Revision as of 10:54, 5 May 2015
Line 122:		Line 122:
	* PDF Import, text as path (semi-broken)		* PDF Import, text as path (semi-broken)
	* Text flow		* Text flow
	* Swatches		* Swatches '''GSoC Merge in Progress'''
	* Geometric bucket tool (Paid development?)		* Geometric bucket tool (Paid development?)


	=== Testing ===		=== Testing ===

Tavmjong: /* Refactoring */

2015-05-05T10:52:53Z

Refactoring

Tavmjong: /* SVG 2 strategy (Tav) */

2015-05-05T10:49:35Z

SVG 2 strategy (Tav)

← Older revision		Revision as of 10:49, 5 May 2015
Line 27:		Line 27:
	=== SVG 2 strategy (Tav) ===		=== SVG 2 strategy (Tav) ===

	* Overview/rundown of relevant new SVG2 features. ~~What are they, what will need done to implement them?~~ '''DONE'''		* Overview/rundown of relevant new SVG2 features. '''DONE''' See [http://tavmjong.free.fr/SVG/svg2.html SVG 2 Features in Inkscape]
	* How do we handle fallbacks?		* How do we handle fallbacks? '''Use [http://en.wikipedia.org/wiki/Visitor_pattern Visitor's Pattern]''' Code is tightly bound to Inkscape, must be internal.
	* When do we add things to the GUI? ~~(When three browsers offers support?)~~		* When do we add things to the GUI? '''Earlier, the better; with SVG 1.1 export.'''

	=== Program flow (Tav) ===		=== Program flow (Tav) ===

Tavmjong: /* Agenda */

2015-05-05T10:42:59Z

Agenda

← Older revision		Revision as of 10:42, 5 May 2015
Line 12:		Line 12:
	## 2geom: sync '''IN PROGRESS'''		## 2geom: sync '''IN PROGRESS'''
	## Tackle GTK3 flickering bug. '''IN PROGRESS'''		## Tackle GTK3 flickering bug. '''IN PROGRESS'''
	## Selection - boost multiindex		## Selection - boost multiindex '''NOT STARTED'''
	# Bugs		# Bugs '''IN PROGRESS'''
	# Code Review '''DONE'''		# Code Review '''DONE'''
	# Code Documentation		# Code Documentation '''NOT STARTED'''
	# Roadmap Review '''DONE'''		# Roadmap Review '''DONE'''
	# Accessibility		# Accessibility '''DONE'''

	* What do we want to accomplish?
	* How should we record this meeting?
	* How can others participate?
	** IRC
	** Google Hangouts?

	== Work pages ==		== Work pages ==

NeoPhyte Rep: /* Accessibility */ Changed to Accessible Graphics and Language Support which are wiki style links to same site.

2015-04-29T22:18:40Z

Accessibility: Changed to Accessible Graphics and Language Support which are wiki style links to same site.

← Older revision		Revision as of 22:18, 29 April 2015
Line 110:		Line 110:
	* Adding language metadata (so that screen readers know what they're reading, but also for other benefits)		* Adding language metadata (so that screen readers know what they're reading, but also for other benefits)

	I've summed up some of the discussion in two wiki pages: [~~http://wiki.inkscape.org/wiki/index.php/Accessible_graphics~~ Accessible Graphics] and [~~http://wiki.inkscape.org/wiki/index.php/Language_support~~ Language Support]. See also		I've summed up some of the discussion in two wiki pages: [[Accessible Graphics]] and [[Language Support]]. See also

	* [https://bugs.launchpad.net/inkscape/+bug/170340 Bug #170340, "metadata: need User Interface for SVG accessibility features"]		* [https://bugs.launchpad.net/inkscape/+bug/170340 Bug #170340, "metadata: need User Interface for SVG accessibility features"]

Ameliabr: /* Accessibility */ summary of discussion and outcome

2015-04-29T14:28:57Z

Accessibility: summary of discussion and outcome

← Older revision		Revision as of 14:28, 29 April 2015
Line 106:		Line 106:
	<p style="width:60em">Amelia Bellamy-Royds, an SVG WG member, will be giving a talk at LGM on making SVGs accessible. She is available Monday afternoon and/or Tuesday to talk to us about how we can make it easier in Inkscape to make accessible SVGs. Things we can do include:</p>		<p style="width:60em">Amelia Bellamy-Royds, an SVG WG member, will be giving a talk at LGM on making SVGs accessible. She is available Monday afternoon and/or Tuesday to talk to us about how we can make it easier in Inkscape to make accessible SVGs. Things we can do include:</p>

	* Automatically generating alt text when converting from Text to Path.		* Automatically generating alt text when converting from Text to Path. '''Tav has pushed a fix -- the text will be saved as aria-label attribute.'''
	* Making it easy to add common ARIA[1] ~~attributes~~		* Making it easy to add [http://www.w3.org/TR/wai-aria/ common ARIA attributes] (Didn't really discuss this)
			* Adding language metadata (so that screen readers know what they're reading, but also for other benefits)

	[1] http://~~www~~.w3.org/TR/~~wai-aria~~/		I've summed up some of the discussion in two wiki pages: [http://wiki.inkscape.org/wiki/index.php/Accessible_graphics Accessible Graphics] and [http://wiki.inkscape.org/wiki/index.php/Language_support Language Support]. See also

			* [https://bugs.launchpad.net/inkscape/+bug/170340 Bug #170340, "metadata: need User Interface for SVG accessibility features"]
			* [https://bugs.launchpad.net/inkscape/+bug/1249423 Bug #1249423 "Properly support the <switch> element and the "systemLanguage" attribute"].

			Both of these bug reports existed, but they've been updated with new comments and references.

	=== Misc ===		=== Misc ===

Tavmjong: /* SVG 2 strategy (Tav) */

2015-04-27T13:40:48Z

SVG 2 strategy (Tav)

← Older revision		Revision as of 13:40, 27 April 2015
Line 33:		Line 33:
	=== SVG 2 strategy (Tav) ===		=== SVG 2 strategy (Tav) ===

	* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them?		* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them? '''DONE'''
	* How do we handle fallbacks?		* How do we handle fallbacks?
	* When do we add things to the GUI? (When three browsers offers support?)		* When do we add things to the GUI? (When three browsers offers support?)


	=== Program flow (Tav) ===		=== Program flow (Tav) ===

← Older revision		Revision as of 10:52, 5 May 2015
Line 74:		Line 74:
	Some possible changes to discuss:		Some possible changes to discuss:

	* Moving to C++11 (AV)		* Moving to C++11 (AV) '''Alex adding tests to code base.'''
	** code cleanup/maintainability		** code cleanup/maintainability
	** improved data structures/templating		** improved data structures/templating
	* Adding a hard Cairo 1.14 dependency (AV)		* Adding a hard Cairo 1.14 dependency (AV)
	** Fix bitmap downscaling issue		** Fix bitmap downscaling issue
	* Gtk+ 3 migration (AV)		* Gtk+ 3 migration (AV) '''GTK3 missing some functionality.'''
	** Get rid of lots of conditional code		** Get rid of lots of conditional code
	** Get rid of embedded GDK library fork		** Get rid of embedded GDK library fork
	** Some "cleaner" API available		** Some "cleaner" API available
	** How do we handle canvas flickering/rendering issues?		** How do we handle canvas flickering/rendering issues? '''Alex working on clean-up.'''
	* C++ification (AV)		* C++ification (AV)
	** Migrate widgets/dialogs to Gtkmm		** Migrate widgets/dialogs to Gtkmm
Line 94:		Line 94:
	* Unnecessary profileration of namespaces (Krzysztof)<p style="width:60em">Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.</p>		* Unnecessary profileration of namespaces (Krzysztof)<p style="width:60em">Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.</p>
	* Directory structure. (Krzysztof)<p style="width:60em">Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM).</p>		* Directory structure. (Krzysztof)<p style="width:60em">Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM).</p>
	* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof)		* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof) '''Join LPE'''

	=== Accessibility ===		=== Accessibility ===