search

blockdiag / blockdiag_interactive_shell

15 stars 7 forks source link

bin/buildout #9

Open tk0miya opened 6 years ago

tk0miya commented 6 years ago

When I do bin/buildout, these libraries are not installed for some reason. I am not sure why

app_lib: Library not installed: missing egg info for '/Library/Python/2.7/site-packages/funcparserlib-0.3.6-py2.7.egg'. app_lib: Library not installed: missing egg info for '/Users/ehu/blockdiag_interactive_shell/develop-eggs/setuptools-18.0.1-py2.7.egg'. app_lib: Library not installed: missing egg info for '/Library/Python/2.7/site-packages/webcolors-1.5-py2.7.egg'. app_lib: Library not installed: missing egg info for '/Library/Python/2.7/site-packages/Pillow-2.8.2-py2.7-macosx-10.10-intel.egg'.

tk0miya commented 6 years ago

From Takeshi KOMIYA on 2011-07-29 17:28:11+00:00

Fixed in r861. It will fixed at next version (0.8.5).

tk0miya commented 6 years ago

From Armin Ronacher on 2012-08-21 11:54:01+00:00

(Screwed up the formatting horribly, don't use bitbucket much these days. Can I edit the issue somehow?)

Also I am happy to file individual bugs for it but I am not sure if this tracker is the correct place.

tk0miya commented 6 years ago

From Takeshi KOMIYA on 2012-08-22 06:38:49+00:00

Thank you for your advice :-)

  1. Does not provide me with a way to define the font size

default_fontsize attribute will help you.

seqdiag { default_fontsize = 18; A -> B [label = "GET /"] }

Or, fontsize attribute can change fontsize of specified element.

seqdiag { A -> B; A -> B [fontsize = 20]; }

  1. font maps are incredible hard to debug because they don't provide you with any debug output if it fails (all exceptions are silenced)
  2. font maps with invalid references cause a recursion error but no indication of where it happens because the traceback is hidden. You can see that a recursion is happening because it prints the "unknown font family" message a few thousand times.

Sorry, its design is my mistake. I'll add 'seqdiag_debug' option to sphinx and pass-through all exceptions.

  1. SVG fonts are hardcoded to serif or sansserif (the latter not being a correct font definition for SVG so it falls back to serif)

You have to use fontmaps to change font-family. On start-up seqdiag, any font-families (without serif) have not been defined, then you could not use them.

Please write fontmap file like this::

[fontmap] monospace = /usr/share/fonts/.../foo.ttf monospace-bold = /usr/share/fonts/.../bar.ttf

The font-family should be formed as generic_family_name .

Sorry for no docs about fontmaps ...

  1. The metrics being wrong even if the font is set up properly when used with freetype2 and pillow on OS X (left pixel is hidden behind the shadow)

I fixed it recently: https://bitbucket.org/tk0miya/seqdiag/changeset/bf7792210cbdf608b5674dc3cf1e76c059102108

  1. shadows in SVG don't scale properly when the diagram is scaled down and there is no way to disable the shadow rendering either.

I wonder how do you scale down the diagram?

BTW, disabling shadows feature is implemented on next release.

  1. seqdiag (at least through sphinx) does not provide you with a way to lower the padding or add padding in places which makes it hard to use with a bigger diagram.

Yes. current version does not have feature controlling padding. Do you have any situation that would shrink or expand padding?

tk0miya commented 6 years ago

From Takeshi KOMIYA on 2015-07-04 10:54:57+00:00

blockdiag interactive shell will help you. It is a web application for Google AppEngine. It provides an API to generate images from user input.