> I don't do much web authoring, but recently, we asked me to update a
> new web site for an organization, because the person that did it had
> gone. Looking the HTML code, I have soon realized that there were
> common pieces in each HTML pages, the menu at top of each page that
> deploy when you hover over it. And some kind of main pages at the left
> side. At firlst, I thought about factoring out these common pieces and
> replace them with PHP includes. But I don't like much the idea of
> having to replace HTML by PHP, just to include HTML files. Iframes
> would seems not so unreasonable, but I somehow doubt about the fact
> that the top menu will accept to show outside of the iframe when I
> will hover over it. I finally learned that previous web author used
> Dreamweaver, and that they do have templates, to handle common HTML
> code for many pages.
>
> Now, for me, a template is basically just an HTML file that I include
> in an other.
> Problably between:
> <-- BEGIN Inluded file: somefile.html -->
> <-- END Included file: somefile.html -->
That's doable. But please note that somefile.html is NOT an HTML
file but the serialization of a HTML fragment only. It's not a
full document...
Let me think about it. I may add that feature to v1.1 or the next
one.
> Guess it would be cool to have a + sign, that let you show or hide the
> included file.
>
> Should the editor allows you to edit this region?
> In a very simple solution no.
Hmmmm... Again, that's doable in the Wysiwyg view. Not easy at all
but doable. In the source view though, that's much harder and I have
no idea if Ace (the source editor BlueGriffon uses) will let "mark"
a section of the document as read-only. I have to investigate.
</Daniel>
Doable but difficult. I have a blog post about it.
Please read http://is.gd/xJxsAR
</Daniel>
> How can we help?
Easy: buy my add-ons. And I'll hire more people to work
on BlueGriffon. I'm not kidding.
</Daniel>
This is not html. I can't go beyond the html spec, sorry.
</Daniel>
> that's not really the open-source-community-fashion...
> if you don't like volunteers - that's your decision...
"Open source" never implied "starve to death". I am keeping
the editor open source and free because I sell add-ons. This
is not an extra activity for me, I spend 200% of my time on
BlueGriffon. No other option (service, pro version) is feasible
on such a product.
</Daniel>
> I never said anything about starving...
> I asked how we, the user-community of bluegriffon could help and your
> decision is not to cooperate with volunteers to improve bluegriffon
> other than recieving translations.
> As i said: your decision...
I never said that. And I got multiple code contributions for 1.0.
> I just wanted to help with my spare time.
> But that is obviously of no value for you.
Start with fixing minor defects you find using the app?
> Donation to support a project is something completely different and
> there are tons of ways one can support opensource.
> I tried to support bluegriffon, but you refused to accept that help...
Ask KompoZer's maintainer how much he got from donations in 5 years.
Probably around 3000€
Nobody can live and maintain software for 5 years on that.
</Daniel>
No. You can certainly define your own elements in xhtml/html5 and
use your own namespace for that. But I prefer relying on non-intrusive
XML comments <!-- ... --> that on new elements; that way, the HTML
validator will not complain.
</Daniel>