-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File extension #206
Comments
Hi - thanks and welcome to Silice! PAWS is great, so many excellent features and games! Extension: that is a good point. Unfortunately I wasn't aware about the file extension collision until late in the project, and I agree this is not ideal. I've since been thinking of changing it. This has little technical impact but a rather wide one in terms of repository. I'll bump this up in priority. |
Cheers for looking at PAWSv2, I hope you like it.
Silice is a great environment for learning about FPGA programming, and
sylefeb is great as a project leader on Silice.
…On Mon, 17 Jan 2022, 07:56 sylefeb, ***@***.***> wrote:
Hi - thanks and welcome to Silice! PAWS is great, so many excellent
features and games!
Extension: that is a good point. Unfortunately I wasn't aware about the
file extension collision until late in the project, and I agree this is not
ideal. I've since been thinking of changing it. This has little technical
impact but a rather wide one in terms of repository. I'll bump this up in
priority.
—
Reply to this email directly, view it on GitHub
<#206 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN4SYT6JOTLWHNXJSBOVO7TUWPDRTANCNFSM5MD5JOTA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi Rob, thanks :-) Cheers! |
A few ideas on extensions:
|
I'm happy with any of those, but I do like .silice as definitive, exactly
as per tin (don't worry if you don't get this reference, English joke).
…On Mon, 17 Jan 2022, 16:00 sylefeb, ***@***.***> wrote:
A few ideas on extensions:
- ".silice", after all most systems should support more than 3
letters? (e.g. ".html")
- ".si" short, does not seem too crowded, at least not in the FPGA
space. Also, that's Silicon in the element table.
- ".ic" is not bad either, and has the advantage to be a single letter
change.
—
Reply to this email directly, view it on GitHub
<#206 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN4SYT2DT6L37OLJ3TZ3XKLUWQ4JDANCNFSM5MD5JOTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@zipotron, I think that GitHub's
The extension is also listed in https://github.com/github/linguist/blob/80f3531e8a1014a23f4606458e5a528053ed3cac/lib/linguist/languages.yml#L2707, which is the Icestudio case I believe.
IIRC, there are historical reasons to use three characters for extensions. That might be irrelevant nowadays, but worth giving a thought. In the VHDL community, there is fragmentation between In this case, the content of Silice's Other than that, I like that |
Hi Unai - thanks for the suggestions! Yes I am not 100% comfortable with using a 'long' extension, (Side note: the reason I think the change is needed is because IceStudio is also for fpga hardware design, so that's one extension for two closely related things -- which is source of confusion.) |
Thanks Unai! Well, And .sil? Or .slc (just consonants)? |
Just for fill the three characters, because the idea of .si is cool |
I thought of |
I think that two characters ( https://en.wikipedia.org/wiki/8.3_filename
|
I definitely like .si |
Closing ; draft branch has now transitioned to |
Hello, first thing congratulate for this awesome work, I just discover this project last weekend and got in love with it.
I am writing this issue because, I discover by accident Silice. I found an interesting work (The PAWSv2 risc-v softcore) and I wanted to check it, when I saw the .ice extension I recognize it as a IceStusio files, and then try to open with my IceStudio, other amazing opensource project.
The big surprise was to discover that those .ice files was corresponding to another completely different project, this one, and the surprise became even bigger when discover that Github is not making the difference between the IceStudio code and the Silice code (for Github everything is "Slice") .
BTW Github is tagging .ice as a "Slice" not "Silice".
The text was updated successfully, but these errors were encountered: