Experimenting with making mockups in Workbench. There's still some pitfalls for someone like me who doesn't do this regularly, but it's really nice to not have to fuck around with padding, pixel grid alignment, font sizes, etc. like in Inkscape.
@tbernard This is great for simple mockups. Blueprint is pretty easy to pick up for people who have some coding experience. Inkscape is still unbeatable for more complex interfaces / custom patterns, though
@tbernard just tried using it yesterday for a similar purpose of making screenshots for developer documentation. Blueprint really makes it easy.
Now that I think of it, Blueprint + some random generated data + Workbench inside Builder, and GNOME development would be really EZ with the Android-grade level of convenience.
@tbernard What do you think of Blueprint? Is there anything that would make it easier for design tasks like this?
@flyingpimonster Not really, Blueprint worked great for me! I think most of the issues I had were with other stuff (e.g. not knowing some widgets can only have one child, figuring out widget property names, how to link radiobuttons, and so on).
@flyingpimonster Actually, one thing that comes to mind: I was struggling with the indentation level, making sure I have matching brackets, and the like a few times.
Better error reporting for that and an auto-formatting feature would be helpful there.
@flyingpimonster @tbernard there are some things that fail silently I'd like to provide hints for, like when order of properties is important (GtkAdjustment) or when only a single child is allowed. Not sure yet if in Workbench or Blueprint - wdyt?