03-15-2024, 01:47 PM
Hi, for a potentially complex task like this - it is starting to look like writing an IDE.
I would first write down a list of all the features needed and then break these down into sub-tasks.
Do all this in some detail before writing any code!
Then look at any that you are not sure how to do, break these down further and prototype the hardest bits.
If these cannot be done, then modify the design accordingly.
For example, will it require a text lexer? to identify keywords, comments, literals, commands etc.
Since VS is too heavy, there may be other language choices, Java, php etc with much lighter environments with better support, but you cannot decide this until you have a very clear understanding of the requirements. If yoy stick with SB or sVB, then this may limit what is feasible and the design should reflect this as you prototype.
I would first write down a list of all the features needed and then break these down into sub-tasks.
Do all this in some detail before writing any code!
Then look at any that you are not sure how to do, break these down further and prototype the hardest bits.
If these cannot be done, then modify the design accordingly.
For example, will it require a text lexer? to identify keywords, comments, literals, commands etc.
Since VS is too heavy, there may be other language choices, Java, php etc with much lighter environments with better support, but you cannot decide this until you have a very clear understanding of the requirements. If yoy stick with SB or sVB, then this may limit what is feasible and the design should reflect this as you prototype.