SimpleIDE GUI Changes
jazzed
Posts: 11,803
Hi All.
I need your opinion before I go changing lots of things in the online user guide. Please help me decide which Project Options layout to keep.
Which is better for you: 1) the old look or 2) the new look ?
I could go either way.
This change is mostly to allow a smaller window for netbooks, etc..., facilitate adding project option features, and for adding SPIN compiler support later.
It also tries to address a long standing request to move board types into the Project settings. I'm honestly not as happy with that as I thought I would be, but it makes some things easier.
Thanks,
--Steve
I need your opinion before I go changing lots of things in the online user guide. Please help me decide which Project Options layout to keep.
Which is better for you: 1) the old look or 2) the new look ?
I could go either way.
This change is mostly to allow a smaller window for netbooks, etc..., facilitate adding project option features, and for adding SPIN compiler support later.
It also tries to address a long standing request to move board types into the Project settings. I'm honestly not as happy with that as I thought I would be, but it makes some things easier.
Thanks,
--Steve
Comments
Weighing in on behalf of the three universities we just trained on the Propeller right now. Two of the universities are Taiwan National University and Tsing Hua National University (#1 and #2 in Taiwan, respectively). The professors in these departments are ready to go with the Propeller now, but they actually aren't aware of a single hurdle that'll be a show-stopper: the ability to put Simplified Chinese Characters into the code. Our Japanese customers have the same problem. It would have been embarrassing if they asked us about this in our presentation, but thankfully we only got nabbed with PASM programming questions [I'm only a Spin programmer]. Any of you could have helped us out here . . .
Could somebody help us out and install the Chinese characters on their computer, and see if you could put them into Simple IDE as comments or within text strings [maybe for an LCD]?
And long-term, we are also supporters of making Simple IDE have Spin/PASM support along with C/C++. Parallax can help here as necessary, with financial support, testing, and whatever else you need (we have a bit of a humanpower shortage right now).
I realize these comments are not specifically applicable to the question asked above.
Thanks,
Ken Gracey
In general, I like the newer layout. However, not to beat a dead horse, but...many of these options need to be settable on a per file basis. I'm afraid that relying solely on Make to support multiple memory models isn't going to work long term, so you might as well consider this need while you are tearing it apart. I'm not suggesting that it needs to be implemented now, but rather keep this in mind when you are reworking things so you don't paint yourself into a corner.
I would like to see items in that "pane" update dynamically when you click on the files in the navigator. Also, since you will be supporting file types other than C/C++ in the future, consider how that will play into the preferences pane. A thought that I had, maybe not a great one, is to integrate Make into SimpleIDE, either via invocation or a library. Then you can use SIDE to generate makefiles or edit existing makefiles -- saves a lot of the heavy lifting and pushes the efforts to a common interface.
As for chinese/japanese, this is a straightforward i18n issue, if the editor widget supports Unicode and the file save/load is 8bit clean, Unicode should work.
I confirmed that the editor is i18n/Unicode compatible, but the save/load isn't. I pasted おはようございます into the editor as a comment and it worked, but when I closed/opened the file I just got a bunch of question marks.
In the Taiwanese market there are many 32-bit processors we've never even heard of, designed by Taiwanese companies and shuttled into the universities for use. Not much in the way of multicore as far as I can see without asking around. They understand and appreciate what the Propeller can offer, and they're very interested in image processing. Taiwan is a big player in the touch-screen display market, in both manufacturing and design.
Will be interesting to see what possibilities Simple IDE affords for Spin/PASM in the future. Steve better not get a real job because I think we'll be needing him. . .
Ken Gracey
Parallax Inc.
UTF-8 is the conventional coding and encodes using a variable length protocol: http://en.wikipedia.org/wiki/UTF-8
I had a look at the source, and the OpenFileName method is going to need an overhaul to be 8-bit clean.
Ray
The smaller window footprint will be good - I can see this being a great Netbook tool.
Don't worry about the Forth IDE....we'll probably start working on that!
Can you please point to an IDE program example that provides per file properties to help me understand what you're after?
C.W.
I saved & run. Sorry, it showed "???" for the characters. I closed & open the file & it showed one "?" for each character. The above is Simplified Chinese & I think its the same for Traditional Chinese. I think SimpleIDE cannot handle double-byte (unicode) ?
Same for Japanese:
FWIW, I really like the new layout, too. I know you've heard this but let me state it again: you've done a fantastic job with SimpleIDE in a very short time. Thank you. Solving the non-English character thing will really help move the Propeller beyond the choir that is always preached to.
Be still, my heart. I would love to have SimpleIDE as the only interface for Propeller programming.
I've been using it on and off for a couple of weeks now. There are no real issues and no real changes that need to be made. But rather than say nothing, I'd like to put in a vote to say that it is great, it is working well and doing the job just fine. If I find any issues I'll post but there are none at the moment.
Old look vs new look? I think new look. On the old one, the default is that the screen is a bit smaller and on those screenshots you will notice the platform dropdown menu near the top right does not show up. It is there if you enlarge the screen but it is not there on the default startup and a new user might miss it if they didn't enlarge the screen. On the new look it is there by default which would be better.
Keep up the good work!
Thanks for the input and wonderfully supportive comments.
Attached are some teasers. The Chinese translates to "Hello, Kai-Lan".
I watch "Ni Hao, Kai-Lan" with my grandson: http://en.wikipedia.org/wiki/Ni_Hao,_Kai-Lan I am his "Ye Ye"
The UTF-8 terminal is not ready yet. I'm not exactly sure what to do with it. More to study from Ken Thompson!
The terminal is the hardest part of this whole program - I'm looking into allowing other terminals like putty.
I'm working with one of our forum friends on Chinese translations for the IDE messages.
Hoping volunteers for other languages will step forward. Everyone will get credits for translations.
Thanks,
--Steve
https://sites.google.com/site/propellergcc/documentation/simpleide/user-s-guide#TOC-Project-Manager
Please review for unclear explanations. If you feel something is missing in the user guide, please speak up.
Thanks
--Steve
So, between Steve's fixes and mine, SIDE should be UTF-8 compliant. I don't know if terminal inputs work yet, but I suspect that is less difficult.
I imagine the support for Chinese translation is coming from MacTuxLin, our friend in Singapore. We appreciate this kind of support.
And it appears that Perry has got some Chinese support in the terminal program. Thank you!
Our Taiwanese, Hong Kong and Chinese customers will appreciate this a bunch. They're lurkers on this forum, often not posting but reading everything we do to get the right background. I encourage all of them to join in the forums and I think we'll see a few newcomers in the next month.
Ken Gracey
In writing up a quick SPIN/PASM Object tutorial, I realized/remembered the problem with adding .spin files from the Propeller Tool directly to SimpleIDE projects. SimpleIDE doesn't like the UTF-16 encoding used by the Propeller Tool, so you need to cut/paste between the two. It's not a big issue now once you know about it but it drives your crazy until you realize/remember the problem but if SIDE is going to do SPIN/PASM, then UTF-16 file support will be needed.
If it's a major item to change or adopt, at least for now, there needs to be a warning of some sort instead of just presenting an empty file where you thought there was going to be code.
I've been bouncing around from various editors/IDEs all week and SIDE has stood up well to all of them as far as functionality and ease of use. As I did this, I became more and more appreciative of the scope of Steve's achievement.
And I think there's more support from people not even posting on the forums. I'm in China right now and our office staff is using SimpleIDE, even porting some of our code to C. They're using LMM and find the tool perfectly suitable for their needs.
Ken Gracey
, oops, sorry.
I was able to open standard Spin files just fine, which tells me they are UTF-8 (which is the standard).
Let me try adding the Spin files again. I'm currently using 6.10
I'm referring to this issue (posts #15 and #16). I thought I re-experienced it this morning.
OK, here's what I see following these steps
1) New Project
2) Right click on .c file and select "Add File Copy"
3) navigate to library for Propeller Tool and select .spin file - file is added to PM window
4) click on the file you just added and SIDE switches to the tab for that file and it is EMPTY (line #1 with nothing else)
5) Right click on .c file and select "Add File Link"
6) select another .spin file from the library - the link is added to the PM window
7) click on the file you just added and SIDE switches to the tab for that file and it HAS contents!
8) open a .spin file with the folder icon or from the menu, select the file and its contents are displayed in a new tab
9) Right click on .c file and select "Add File Copy" and select the file you just opened
10) click on the file you just added and SIDE switches to the tab for that file and it is EMPTY (line #1 with nothing else)
Steps 4 and 10 shouldn't show me empty files.
"Add file Link" and copy/paste are work arounds but something strange happens with "Add File Copy" and standard .spin files. If you don't know the work arounds, it's very frustrating trying to get an existing .spin file into a project.
I've been able to open UTF-16 parallax-font based files for a while on various machines - I use DejaVu Sans Mono for example. Even Courier 10 works on my debian64 linux box with SimpleIDE 0.6.6.
You don't need actual parallax font to have a readable file, but it would be useful to have in a package.
I can reproduce steps with add file copy. I'll look into that. Thanks for the detailed "repeat by" sequence.
EDIT: appears to be a Windowsism. I'll have to look at the files.
Sure enough, the files are encoded as such:
The first 2 bytes are sentinel value to detect UTF-16 encoding. Since Qt is fairly smart, I suspect it is detecting this and handling it, since I'm able to properly open UTF-16 files in the editor.
While walking to the office I was thinking about the naming of these menu options.
It would seem more intuitive to call them:
Import with Copy
Import existing
Then add a "Create New" option (I don't recall seeing one).
You are adding a file to the current project. You either add the file to the project in 3 possible ways:
1) The file is somewhere else and you want it in the project AND the source in the project directory -> "Add File Copy"
2) The file is somewhere else and you want to leave it there but include it in project -> "Add File Link" (by the way, I like how the PM windows shows a linked file and also tha tyou can click on it and get it in an editor tab)
3) It's a new file you just created (using the NEW Icon or menu item) and you want it included in the project - "Add File Copy" fits here too, the copy just happens to be skipped since the file is already there.
"Add New" could be added but it makes things complicated since you need to solicit for a file name when the user clicks "Create New" so you can put it into the Project file list or you put in a space holder of "untitled" and then go back to change it when the user does a "save as". You could end up with multiple "untitled" if you don't solicit a name early.
Clicking "new", typing in text, "save as" then doing "Add File Copy" seems rather logical to me.
My 2 cents.