I just posted a video about the WL8 development effort! Let's use this thread to answer questions about WL8 and talk about ideas for a new version.
https://www.youtube.com/watch?v=9JxJjqevTeU
https://www.youtube.com/watch?v=9JxJjqevTeU
Rename
Great video Glitch!
You mentioned that the new api will no longer use Windows system libraries. Will I still be able to get to Windows libraries if I want to do something beyond the WL8 libraries? Some things that come to mind:
* Fonts like WingDigs for annotating charts. I use this occasionally. I might want to use system fonts with WL8 custom font library.
* File support. I create spreadsheets occasionally out of a strategy to help with my analysis of securities. I've done this in WL6, but I haven't ported them to WL7 yet.
I'm sure there's more but this was the first things that came to mind.
You mentioned that the new api will no longer use Windows system libraries. Will I still be able to get to Windows libraries if I want to do something beyond the WL8 libraries? Some things that come to mind:
* Fonts like WingDigs for annotating charts. I use this occasionally. I might want to use system fonts with WL8 custom font library.
* File support. I create spreadsheets occasionally out of a strategy to help with my analysis of securities. I've done this in WL6, but I haven't ported them to WL7 yet.
I'm sure there's more but this was the first things that came to mind.
* The chart and the GUI will still target Windows, so yes you'll still be able to do those same things.
* The System.IO namespace is part of .Net6 cross platform so that's not going away.
But in general, you'll still be able to use Windows-specific things in WL8. Only if we eventually create a Mac edition would that capability go away.
* The System.IO namespace is part of .Net6 cross platform so that's not going away.
But in general, you'll still be able to use Windows-specific things in WL8. Only if we eventually create a Mac edition would that capability go away.
Glitch,
Will this be considered for WL8?
https://www.wealth-lab.com/Discussion/Additional-Machine-Learning-Algorithms-and-GPU-support-6014
Vince
Will this be considered for WL8?
https://www.wealth-lab.com/Discussion/Additional-Machine-Learning-Algorithms-and-GPU-support-6014
Vince
Adding VOLUME BUZZ for intraday strategies into the BUILDING BLOCKS could be helpful. Many strategies revolve around volume and having that data point could serve as a great filter for most intraday strategies.
Carova: No GPU utilization isn't one of the goals of the WL8 effort. That doesn't mean it won't have a place somewhere in the future, for example in a next-generation Neuro-Lab for example.
Volume Buzz, it sounds like that can be easily created as a new indicator, if you're talking about this?
https://www.tradingview.com/scripts/volumebuzz/
https://www.tradingview.com/scripts/volumebuzz/
Is it correct to assume all current WL7 add-ons and indicators will be available in WL8 by the time it is ready to be rolled out? If one has a lifetime subscription to TD Ameritrade for example in WL7 is that transferrable or will we have to rebuy another one for WL8?
Yes that’s correct.
Glitch,
Understand. How about building in some Machine Learning (such as "Trees")? Is that on the table? For example, LightGBM (https://en.wikipedia.org/wiki/LightGBM), an Open-Source "tree" ML product from Microsoft, appears to incorporate all of the most recent "tree" variations, and has built-in GPU support. 😁
Vince
Understand. How about building in some Machine Learning (such as "Trees")? Is that on the table? For example, LightGBM (https://en.wikipedia.org/wiki/LightGBM), an Open-Source "tree" ML product from Microsoft, appears to incorporate all of the most recent "tree" variations, and has built-in GPU support. 😁
Vince
Hi Glitch,
From the video, it seems that you already have a first prototype of WL running on .Net 6.
According to Microsoft, this should yield noticeable performance improvements:
https://devblogs.microsoft.com/dotnet/announcing-net-6/
Does your preliminary findings corroborate this? One of the few criticisms that I have about WL7 is that it is somewhat laggy, interface wise (when compared with WL6); and I was hoping this to improve with .Net 6.
From the video, it seems that you already have a first prototype of WL running on .Net 6.
According to Microsoft, this should yield noticeable performance improvements:
https://devblogs.microsoft.com/dotnet/announcing-net-6/
Does your preliminary findings corroborate this? One of the few criticisms that I have about WL7 is that it is somewhat laggy, interface wise (when compared with WL6); and I was hoping this to improve with .Net 6.
Will Visual Studio 2019 support .NET 6.0, or do we need to switch to VS 2022 first?
My main workstation is still running Windows 7 to support some old applications. And Windows 7 is very stable. Will we need to be running Windows 10 or 11 to use Wealth-Lab 8?
Also, does WL6 run okay under Windows 10 and 11? I would still want to use WL6 with WL8.
My main workstation is still running Windows 7 to support some old applications. And Windows 7 is very stable. Will we need to be running Windows 10 or 11 to use Wealth-Lab 8?
Also, does WL6 run okay under Windows 10 and 11? I would still want to use WL6 with WL8.
I haven't had success making Visual Studio 2019 work with the NET6-based WL8 project.
@superticker:
I have Windows 11 since when it came out and prior to that I had Windows 10 for a long time; and can confirm that WL6 works very well with both OSes.
Regarding the other older applications, very likely they will run properly too; worse case-scenario, you would need to run them in Compatibility Mode.
I have Windows 11 since when it came out and prior to that I had Windows 10 for a long time; and can confirm that WL6 works very well with both OSes.
Regarding the other older applications, very likely they will run properly too; worse case-scenario, you would need to run them in Compatibility Mode.
Would Visual Studio 2022 work under Windows 7?
Would WL8 work under Windows 7?
It's good to hear WL6 works under Windows 10 and 11, although I think it has to run in compatibility mode.
Would WL8 work under Windows 7?
It's good to hear WL6 works under Windows 10 and 11, although I think it has to run in compatibility mode.
WL6 runs perfectly fine in both Windows 10/11, without the need to enable Compatibility Mode.
Regarding custom extensions built in WPF, I noticed you have theming so are you using some 3rd party controls? If so, would they be usable in 3rd party extensions or would that break the license for those controls?
No third party controls, just standard wpf theming.
Some GUI wish items ( I would like to hear everyone's thoughts):
a) Move the interface to a docked window approach instead of the current MDI windowing. Reason: Utilizes screen space better and less tinkering with windows. Allows you to float a given window which is similar to the "New Main Workspace" functionality.
b) I would also like to see the concept of tabbed workspaces instead of just the "New Main Workspace". Reason: Easier to navigate between workspaces.
a) Move the interface to a docked window approach instead of the current MDI windowing. Reason: Utilizes screen space better and less tinkering with windows. Allows you to float a given window which is similar to the "New Main Workspace" functionality.
b) I would also like to see the concept of tabbed workspaces instead of just the "New Main Workspace". Reason: Easier to navigate between workspaces.
Hmm personally i’m partial to the MDI paradigm, call me old fashioned i guess 🤷🏼♂️
On top of that, i already rolled my own mdi library and ditched the klunky third party one we were using. At least this gives us more flexibility, for example maybe we can eventually implement some kind of smart docking.
Just a thought. I spend so much time in Visual Studio it's just what I'm use to.
How about adding workspace tabs then to the main workspace? I would also consider add the option of having workspaces sleep when they aren't activated to reduce the overhead.
How about adding workspace tabs then to the main workspace? I would also consider add the option of having workspaces sleep when they aren't activated to reduce the overhead.
That's a pretty radical change IMO. I mean, we now have MDI windows that you can configure and save as a Workspace. How would Workspace "tabs" complement or work with this design? I'm sorry but I don't want to complicate things much further at this stage, I feel the MDI windows are flexible.
I guess the tabs would replace what we have as the Menu items now? I can see it easily getting cluttered. It also wouldn't work well considering Workspaces also save the size and the location of MULTIPLE main windows.
I guess the tabs would replace what we have as the Menu items now? I can see it easily getting cluttered. It also wouldn't work well considering Workspaces also save the size and the location of MULTIPLE main windows.
Just finished porting the code base for the core product to WL8. Early impressions, it does seem like there’s a general performance improvement with .NET6.
Seamless importing of WL7 strategies is working as well, so this should be a smooth migration! Starting to work on porting over the extensions.
Seamless importing of WL7 strategies is working as well, so this should be a smooth migration! Starting to work on porting over the extensions.
Re: https://www.youtube.com/watch?v=9JxJjqevTeU&t=8s
Thanks. That was informative. Does the move to WL8 mean it will inherit "Windows-like" functionality in terms of everyday use, such as floating windows and the file save UI?
Thanks. That was informative. Does the move to WL8 mean it will inherit "Windows-like" functionality in terms of everyday use, such as floating windows and the file save UI?
Yes the basic UI is not changing.
Just saw the video. Looking forward to the WL8!
As a long-time WL6 (and some 7) user, the most critical and important request I have is: please give us more space.
Maximize strategy/chart/editor real estate. WL6 did an amazing job at that. It had options to hide almost all panels. Including the top navigation toolbar and icons, side drawing toolbar, bottom status bar. There is no need, for example, to permanently display license status or the local time. Those panels are clogging the screen. I much prefer to use that space for coding and see details on the chart. It improves overall usability.
As a long-time WL6 (and some 7) user, the most critical and important request I have is: please give us more space.
Maximize strategy/chart/editor real estate. WL6 did an amazing job at that. It had options to hide almost all panels. Including the top navigation toolbar and icons, side drawing toolbar, bottom status bar. There is no need, for example, to permanently display license status or the local time. Those panels are clogging the screen. I much prefer to use that space for coding and see details on the chart. It improves overall usability.
I'll add an option to hide the status bar and the toolbar. You can already hide the drawing toolbar and the left navigation panels.
QUOTE:
please give us more space.
There is the possibility to edit your strategy with an external editor of your choice.
QUOTE:
possibility to edit your strategy with an external editor ...
If I could edit the WPF chart of the strategy, I would add things like ProfitPerBar (or even other Performance Metrics; e.g., Sharpe Ratio) to the streaming strategy chart like WL6 does. But I'm not sure most Performance Metrics are available to the strategy.
There's a memory footprint issue with trying to compute the strategy chart and the Performance Visualizers together. WL is likely to have a smaller memory footprint (and better processor cache hit ratio) by computing them separately as it is doing now, which will be faster for WL.
When is the release date for WL8?
There's no fixed release date because we don't know when it will be perfected. But it's looking like it will be two to three weeks out.
Hello Glitch,
Will it be possible to change metric names in Wealth Lab 8?
Will it be possible to change metric names in Wealth Lab 8?
What do you mean, exactly? Provide a specific example.
Built-in metrics and those that come with libraries such as the PowerPack are not editable.
The reason I asked was because if there's something that made more sense for everyone, sure. On the other hand, if you want to customize labels, that could be a feature request. I could imagine a list of aliases to use for column labels, for example, to make them regional by language.
@Cone. Yes, I want customize labels that suits better to me.
@Eugene. As Eugene said.
See.
@Eugene. As Eugene said.
See.
QUOTE:
https://www.wealth-lab.com/Discussion/Change-name-of-the-Metrics-Columns-7258
I just looked up the Quote and quickly got Glitch's opinion on it - he's still firm against this one, so no need to get a feature request turned down again. Sorry.
@mrsic
As metric names are hardcoded inside the libraries, they cannot be customized.
As metric names are hardcoded inside the libraries, they cannot be customized.
You could always create your own ScoreCard that derived from BasicScorecard and overrides the method to generate the report, using your own labels. Or use finantic ScoreCard and create metrics using whatever names you want.
The entire code base has been migrated to WL8! Now it’s just a matter of polishing things up, release should be in a couple weeks!
That's great!
Just a question: will all the current WL7 extensions also be available for WL8, from the start?
Just a question: will all the current WL7 extensions also be available for WL8, from the start?
Yes all of ours are already migrated. Third party extensions might experience a delay as the authors might need some time to convert them.
Will WL7 users be able to update to WL8 for free or will there be a charge?
For free.
WL8 is going to have XML based Strategy which is great!
Are Workspace and DataSets files going to be XML based as well?
Are Workspace and DataSets files going to be XML based as well?
Any plan for considering these for WL8?
https://www.wealth-lab.com/Discussion/GetSessionOpen-access-daily-Open-today-s-partial-bar-from-strategy-code-6362
https://www.wealth-lab.com/Discussion/Default-bar-scales-for-bulk-data-update-7010
https://www.wealth-lab.com/Discussion/Strategy-Parameters-are-hidden-behind-Strategy-Settings-7237
https://www.wealth-lab.com/Discussion/GetSessionOpen-access-daily-Open-today-s-partial-bar-from-strategy-code-6362
https://www.wealth-lab.com/Discussion/Default-bar-scales-for-bulk-data-update-7010
https://www.wealth-lab.com/Discussion/Strategy-Parameters-are-hidden-behind-Strategy-Settings-7237
The first two requests are regular wishlist items so if one of these rises to the top it will be considered. This has been the policy.
Only DataSets and Strategies have changed to XML format, not WorkSpaces.
@Glitch
>Only DataSets and Strategies have changed to XML format, not WorkSpaces.
Could you consider XML format for WorkSpaces as well?
On WL6, I do edit DataSets and Strategies XML files but not very often.
However, I edit WorkSpaces very often in order to duplicate workspaces for various symbol and time range combinations for backtests and optimizations.
For example, I have workspace named like Top50ETF_2007, Top50ETF_2008, ..., Top50ETF_2021.
As the workspace name stands, there are 50 chart windows for one year time range.
When I need to create one for 2022, I copy the XML file and repalce the time range in the file.
>Only DataSets and Strategies have changed to XML format, not WorkSpaces.
Could you consider XML format for WorkSpaces as well?
On WL6, I do edit DataSets and Strategies XML files but not very often.
However, I edit WorkSpaces very often in order to duplicate workspaces for various symbol and time range combinations for backtests and optimizations.
For example, I have workspace named like Top50ETF_2007, Top50ETF_2008, ..., Top50ETF_2021.
As the workspace name stands, there are 50 chart windows for one year time range.
When I need to create one for 2022, I copy the XML file and repalce the time range in the file.
I’m sorry but that part of the development is completed. In fact we’re planning to release WL8 on Sunday.
Will all WealthLab extensions be ready for WL8 roll out?
All in-house extensions, yes.
@Glitch
Are WorkSpaces human understandable format?
It doesn't have to be XML only if I can modify...
Are WorkSpaces human understandable format?
It doesn't have to be XML only if I can modify...
They’re in the same format as WL7.
@Glitch
May I request it for feature request to be considered for WL8+ or WL9?
I think beta testing would be nice before completing the development.
May I request it for feature request to be considered for WL8+ or WL9?
I think beta testing would be nice before completing the development.
Of course, please submit this tagged with #FeatureRequest!
Your Response
Post
Edit Post
Login is required