[TriLUG] New document on Bluefish, HTML and Styles Based Authoring

[Tim Jowers]

What I've found is similar. On no large project I've ever done was the
designer's HTML ever used. In fact, large financial institutes don't even
bother designing HTML any more. They just do screen graphics. HTML design
tools are a mess because they fail to integrate with the technology used to
build websites. The only way to "make" them work seems to be to use thick
AJAX (SPA/RIA,whatever) and dummy up REST services.  Even then, 99 times
out of 100 the hackers quickly "architect" their javascript in such a way
the "design" tools can no longer be used for a round trip.

I'd say Java is the worst but seems all server-side technologies are as bad.

So, I use BlueFish myself because I just need to edit HTML. It seems "HTML"
is not really a design language; so, design tools are sort of a misfit now.
They allow non-programmers to generate code. Not too useful because the
code is useless in a real environment. Maybe they are a good tool to work
with HTML template you buy from the Internet.

I'l go ahead and say it too, the "Graphics Designers" I've worked with
really have no clue about HTML, how a web browser works, or how the
software works. That's at a sampling of several of the largest corporations
in the USA.

My $.02,
Tim





On Wed, Aug 7, 2013 at 9:39 AM, Francois Dion <francois.dion at gmail.com>wrote:

> On Wed, Aug 7, 2013 at 8:32 AM, John Vaughters <jvaughters04 at yahoo.com
> >wrote:
>
> > You might not like Bluefish if.....
> >
> > Nice segment. I got some good laughs in there. Mouse vs. Keyboard and
> > Apple comments `,~)
> >
> > Been using Bluefish for years, but I am not a big HTML person. I liked it
> > for the same reason you did. I could not find any decent WYSIWYG and I
> > prefer text editing anyhow. GEDIT being one of my favorites for all file
> > types.
> >
>
> For publications (including content web sites), I think HTML is overkill
> and gets in the way. Particularly if you are doing multilingual, then it's
> even more excruciating. Although you want your final result to be html and
> css or pdf, a simpler no frill format such as
>
> The whole fait main [1] (in french, my article on DIY raspberry pi
> interface cables is at the bottom right) web site / magazine / pdf is all
> done straight from restructured text [2] on github. Similarly for Brython
> [3] the text and documentation is all in Markdown [4] format on bitbucket.
>
> The difference between the two is that in the first case the .rst files are
> converted to html during the pull from github process and serves static
> content, while in the other, what is on bitbucket is pulled without
> alteration and Brython does the conversion dynamically in your browser.
>
> And of course, markdown (or ReSt) is what you use for landslide [5] (we
> just talked about it in the open source presentation frameworks thread
> about a week ago)
>
> [1] http://faitmain.org/volume-1/index.html
> [2] http://docutils.sourceforge.net/docs/user/rst/quickstart.html
> [3] http://brython.info
> [4] http://daringfireball.net/projects/markdown/syntax
> [5] https://github.com/adamzap/landslide
>
>
> Francois
> --
> www.pyptug.org  -  raspberry-python.blogspot.com  -  @f_dion
> --
> This message was sent to: timjowers <timjowers at gmail.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
> address.
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web  :
> http://www.trilug.org/mailman/options/trilug/timjowers%40gmail.com
> Welcome to TriLUG: http://trilug.org/welcome
>