WL6 supported either plain-text or HTML-based strategy descriptions, which made it much easier to outline, format, and itemize features of a complex strategy as shown in the WL6 screenshot below. It would be nice of WL7 had this same feature.
Rename
Note that for a pure bells and whistles request like this, there's a tradeoff:
1. increased memory consumption
2. slow down on opening of every strategy due to rendering the rich content.
P.S. Wealth-Lab 7 heavily utilizes Markdown where WL6 used HTML. Not sure if that would improve the memory footprint, though.
1. increased memory consumption
2. slow down on opening of every strategy due to rendering the rich content.
P.S. Wealth-Lab 7 heavily utilizes Markdown where WL6 used HTML. Not sure if that would improve the memory footprint, though.
QUOTE:So you're saying I can put the strategy description in Markdown to get some of the HTML formatting I had in WL6?
Wealth-Lab 7 heavily utilizes Markdown
I'm just saying that supporting either markup language would require adding a control - and some bloat as a consequence.
And I agree with you. Part of that is because HTML5 is much more bloated than HTML4. But HTML4 would be good enough for WL7. Even Rich Text Format would be better than plain text, although that wouldn't do outlining as HTML does with list definitions.
Are you suggesting an external app (mini web browser?) to render the strategy descriptions? I thought Dynamic Linked Libraries (DLLs) worked like third-party apps and only stayed loaded as long as they were needed. So DLLs minimized the memory footprint of the main application. Is this wrong?
I suppose the HTML descriptions could be saved in separate strategyName.HTML files with a link to those files in the WL7 strategies listing. Hmm. In that case, those *.HTML files would be maintained by a web IDE (JavaBeans, Eclipse, Visual Studio) instead of WL7. Is that where we are going with this? It's an interesting idea.
Are you suggesting an external app (mini web browser?) to render the strategy descriptions? I thought Dynamic Linked Libraries (DLLs) worked like third-party apps and only stayed loaded as long as they were needed. So DLLs minimized the memory footprint of the main application. Is this wrong?
I suppose the HTML descriptions could be saved in separate strategyName.HTML files with a link to those files in the WL7 strategies listing. Hmm. In that case, those *.HTML files would be maintained by a web IDE (JavaBeans, Eclipse, Visual Studio) instead of WL7. Is that where we are going with this? It's an interesting idea.
Your Response
Post
Edit Post
Login is required