Skip to content
This repository was archived by the owner on Oct 1, 2024. It is now read-only.

Remove Processing Filetype (.PDE extension) #868

Merged
merged 6 commits into from
Jul 26, 2019
Merged

Remove Processing Filetype (.PDE extension) #868

merged 6 commits into from
Jul 26, 2019

Conversation

Dotrar
Copy link
Contributor

@Dotrar Dotrar commented Jul 16, 2019

referencing issue #838

This is really an annoying issue with these asking FOR pde support:
#217 #752 #793
but they are all individually wrong:
PDE is for processing, arduino uses INO. Arduino DID use pde prior to the first release ( as it was a cut-copy of Processing ) but now PDE on arduino is considered "read only" - read more here

Now with Ardiuno on 1.8.9 and Processing on 3.5.3; Both popular, both being used in their own way, allowing people to use pde files for arduino is sacrilegious to both camps.

In regards to other arduino-based examples and etc using PDE. (Looking at #752 specifically ) The correct place to submit an issue is on THAT codebase to rename .pde; not for tools like this one to support pde.

It also makes life difficult for people who use both Arduino and Processing in their educational work, such as myself. Any work I do in the Processing language is renamed to the Arduino extension automatically, and it doesn't need to be, because PDE is not arduino; INO is.

I hope this closes the issue enough to not bring this up again; It's like typesafety for files; you can't rename an short an int and call it a day because now code compiles.

@msftclas
Copy link

msftclas commented Jul 16, 2019

CLA assistant check
All CLA requirements met.

@Dotrar Dotrar changed the title Update package.json to remove .PDE extension Remove Processing Filetype (.PDE extension) Jul 16, 2019
@Sneezry
Copy link
Member

Sneezry commented Jul 22, 2019

I agree with you that the correct way should be to ask the original project to change .pde to .ino, but not make a tool to support .pde for Arduino.

However, as you said, we did have received some feedbacks to request .pde support. Usually, it is hard to meet all users' requirements, but we try our best to make it possible.

I do not think it is a good idea to tell users what is the correct way. It makes me remind the standard of utf-8, with BOM or without BOM.

A better way to handle this issue I think is to add a new configuration to enable/disable .pde support, and disable this feature by default. Then everyone should be happy.

@Sneezry
Copy link
Member

Sneezry commented Jul 26, 2019

Cool! Thanks!

@Sneezry Sneezry merged commit b5f7361 into microsoft:master Jul 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants