User forums > Help
C++ comments inside generated C code?
ToApolytoXaos:
OK, fair enough.
Any thoughts for future improvements with SDK in general?
Any plans to separate UI elements from core logic of project?
oBFusCATed:
--- Quote from: ToApolytoXaos on October 16, 2013, 03:21:39 pm ---Any thoughts for future improvements with SDK in general?
Any plans to separate UI elements from core logic of project?
--- End quote ---
Patches welcome and be more exact what you need improved.
Generally the SDK quality goes up, not down with almost every commit:)
Edited: replaced are with and...
Alpha:
--- Quote from: oBFusCATed on October 16, 2013, 12:13:55 pm ---The check should ask the editor to see if it has C++ or C lexing, I think there is a global function that can tell what is the language somewhere in the global headers.
--- End quote ---
For reference purposes, the related global is:
--- Code: ---FileType FileTypeOf(const wxString& filename)
--- End code ---
ToApolytoXaos:
--- Quote from: oBFusCATed on October 16, 2013, 05:28:34 pm ---Patches welcome and be more exact what you need improved.
--- End quote ---
What I would love to see is a mechanism that would permit a user to open a file within C::B and offered the option to parse the current file's directory (while placing it in a temporary project), so it can enable auto-completion (if it's C or C++ code that is) and any available feature exists in IDE. This approach is what Sublime Text actually offers by default and I find it brilliantly convenient.
By the way, the parsing mechanism still produces duplicates, triplicates, and quadruplicates without offering further information about available candidates; only with mouse hover on the class or function et al. you get the info you need which is wrong IMO.
Another idea would be to separate C::B in multiple logical layers, in such way that would allow any interested developer to port project's *core* in ncurses (UNIX-like systems) or PDCurses (Windows), so users could use it from a terminal application.
I often work from terminal using vim, another powerfully brilliant editor, and honestly there are moments where I wish C::B was available, so I could use for example, debugger (valgrind actually) with the help of hot-keys.
Another idea would be the separation of auto-version from SVN into a more generic auto-version mechanism, like that of hashing key signature. I know that nightly builds use svn to generate the necessary version schema, but this bounds the user to use svn, while he or she could easily download the source code from a GitHub mirror and simply compile it without the hassles of VCS.
Last, but not least is the issue with wxSmith GUI Designer's size. When I'm using it via laptop, I have limited available space and I have to scroll up or down within C::B in order to view my generated user interface. I think, IMHO, a popup mechanism that unpins the entire wxSmith UI Design, (NOT the entire GUI mechanism, only the tab window) as a popup window (wxDialog's logic? IDK), would be much more convenient. (GIMP's docking mechanism maybe?)
Even though I suggest such ideas, it does not mean it's feasible or plausible to do such thing. Nevertheless, it's just food for thoughts I would say that could generate new ideas from such feedback.
--- Quote from: oBFusCATed on October 16, 2013, 05:28:34 pm ---Generally the SDK quality goes up, not down with almost every commit:)
--- End quote ---
Yes, I have already noticed that, and that is an amazing progression :)
BlueHazzard:
--- Quote from: ToApolytoXaos on October 17, 2013, 08:27:11 am ---By the way, the parsing mechanism still produces duplicates, triplicates, and quadruplicates without offering further information about available candidates; only with mouse hover on the class or function et al. you get the info you need which is wrong IMO.
--- End quote ---
Have you tried Settings->Editor->Documentation->Parse Documentation and Show token's details even....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version