10-08-2018, 12:08 PM
(10-08-2018, 09:04 AM)Alexandre Machado Wrote: I'm not captain (and I don't like boats) but if you send me your change file(s) I can compare it with my code base and see what I can do.
Alright General Machado))
The altered IWBSRegion unit is included in the 2nd version of the IW Bootstrap demo project I uploaded yesterday.
At first I thought I needed to comment out the 4 lines at the bottom of InternalRenderCss(), but then I realized that the BSRegion automatically adds the first child div. So this change probably isn't needed.
The heart of the change was adding bsttAnchor, bsttButton, bsttListItem, bsttSpan, bsttUnorderedList.
The reason is because when using IWBootstrap, you have regions containing regions containing regions so many times, that choosing the TagType is vastly superior that implementing OnHTMLTag. When you choose the TagType, the Tag is displayed at design-time in the upper-right corner.
It actually takes quite a bit of time to "visually" design a significant Bootstrap page using these components. Whereas if you look at a section of HTML with any code editor with syntax highlighting -- you can actually take in and comprehend a lot of code all at once. So anything to help declaratively is very useful.
And if you read the other posts, it is not just "nice", but 100% critical that there be anchors and buttons that can act as design-time containers. Otherwise the best you can do is dump a chunk of Bootstrapified HTML inside some "inner script" property -- which, if you do -- you lose the ability to attach events in the OI.
In short, as I see it -- it's not possible to use IWBootstrap "as is" to implement complex designs -- unless you make the changes that I made to BSRegion. And even then I had to do a little hacking to get my clicks to work.
Your feedback would be incredibly useful. I'm sure there's something I'm not seeing.