[Libreoffice-ux-advise] [Bug 101772] UI - View source -> XML source raw editing mode, " make Dreamweaver obsolete"
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue Aug 30 12:37:34 UTC 2016
https://bugs.documentfoundation.org/show_bug.cgi?id=101772
Zenaan Harkness <zen at freedbms.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=10
| |1788,
| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=10
| |1179,
| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=36
| |977,
| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=34
| |391
Depends on| |101774
--- Comment #9 from Zenaan Harkness <zen at freedbms.net> ---
Thank you. The guts of this feature enhancement is fundamentally "to replace
DreamWeaver" (people use this proprietary software to efficiently make websites
based on 'templates' (see below)).
At least that "replace Dreamweaver" part is in this bug's summary :)
Re 'templates' in this context: the requirement is for DreamWeaver or DocBook
like templates (they are both similar) - "entities" or "named bits of content"
are the foundation.
So for example, bug #101774 (named content) is a dependency.
BTW, the libre "DreamWeaver alternatives" available such as BlueFish, do not
compare - and I've gotten DreamWeaver users to test BlueFish and other
software, but they cannot give up the combination of features that DreamWeaver
provides which actually work rather well to create HTML documents/ websites.
The feature requests/ bugs that this bug currently depends on to achieve
"DreamWeaver replacement status" may well expand in the future:
For example, see bug #101788 (split button for display modes - just in today
(thanks Heiko)) and which will relate also to bug #31481 (split panes - which
are very much part of "the DreamWeaver way").
Also, this bug collects in a single, visible and updatable location, all its
dependencies which in this case is not just one, but quite a few indeed; to me,
this seems valuable in this instance.
Also the documentation of the dependencies "in one location" is valuable (DRY
principle - Don't Repeat Yourself) - namely, in this bug, rather than repeating
ourselves in each of the dependent bugs with the same various wordings e.g.
"this is needed along with bugs a, b, c, d and e... to bring LO up to
compatibility with DreamWeaver MX from 2002."
Also consider when additional LO enhancement requirements (for DreamWeaver
compatibility) are identified - do we update each of the other "dependencies"
so they are all linked? This parent bug/feature does that linking in a single
consistent location, which is good for tracking the overall status of this long
term feature enhancement request.
I think all those separate feature enhancement proposals are not only useful,
but important in their own right. And once they are done, DreamWeaver is
replaced. Being clear on this goal might be useful to help inspire those who
have a passion for replacing proprietary software with libre software, to help
developing LO :)
(Finally, I am new to LO bug reporting, so of course I leave it up to you
capable bug curators to make the decisions which are best for the long term of
LO - I am really appreciating all the constructive feedback :) )
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=101774
[Bug 101774] Named content in writer; master documents; templates; docbook
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Libreoffice-ux-advise
mailing list