Refactoring #1725
usc extension is used for Macro file and for designerModule file
| Status: | Rejected | Start date: | 05/17/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Miroslav Fidler | % Done: | 0% | |
| Category: | IDE | Spent time: | - | |
| Target version: | - |
Description
The usc extension is used for two different things:
- macro file, and designer module.
Is it possible to reserve a separate extension for the module usc file?
for example : msc or d(esigner)sc or l(ayout)sc
History
#1 Updated by Zbigniew Rebacz almost 7 years ago
No, for me the extension is perfectly fine. First of all .usc extension is designed to handle Esc file scripting language. It is designed only for that purpose. The macro and designer extensions are only the usage of that language. Moreover we can easily detect that given .usc file is designed to be macro rather than designer. We do this in MacroManager.
I highly recommended to reject this issue, but I will wait for Mireks opinion on this topic.
#2 Updated by Abdelghani Omari almost 7 years ago
the "fn" keyword is common between "macro file" and "layout usc file"
when a "layout usc fie" starts with one or more "fn", MacroManager laod this "fn", and it stop at the first unknown keyword.
the file then can be expoted/edited in MacroManager.
i think a new extenstion is the safe solution, especially if the "layout usc file" used only by theide.
If the idea is accepted, I can create the patch.
#3 Updated by Zbigniew Rebacz almost 7 years ago
- Status changed from New to Rejected
I think it will not happen, because of backward compatibility - please read my first commend. Mirek if you want to add something to the discussion - feel free to do this. The issue is rejected for now - we wait one month without any opinion ;)