-
Notifications
You must be signed in to change notification settings - Fork 25
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
Enhancement : try to build with Paladin if BeIDE is not found #71
Comments
I've just took a look at this one, because... why not? Got the IDE menu showing, "Bring to Front" causes Paladin to start (or activate if already running), and "Make" also causes Paladin to try and start building the active/open project, if any. Add/Remove file do not work. There's seems to be a mismatch between the
But then re-defines:
Meanwhile, Pe is using:
"Project->Group" menu item also non-functional. Paladin does not seems to support the Making this work properly, would probably require coordination with @mbrumbelow for the Paladin side of things. Also... (paging Dr. @humdingerb for this question) do we still care about supporting BeIDE on Pe? Should we just Paladin |
I don't know the answer to most of these questions. Haven't used Pe since Koder got usable (and that one much less since Genio) and haven't run BeOS for over 20 years... :) Doesn't Paladin come with its own Pe-forked editor? I expect people coding with Paladin already use its Pe-forked editor, no? The old Pe can still try hooking up with the ol' BeIDE if available, I guess? |
Paladin used to use "PalEdit". No more since 2014. It relies on Pe since then (AFAICT). I'll just go with approach I took on #90 then. If someone wants to compile Pe with BeIDE support (instead of Paladin), they can try compiling Pe under BeOS :-P. |
How time flies... just a decade ago. :) |
It would be better to use some add-on for this functionality instead of hard-coding every possible IDE. |
Source/Utils.cpp
line 161 :
We could try to find "application/x-vnd.dw-Paladin" as a fallback.
The text was updated successfully, but these errors were encountered: