What if we could use <blank>?
-
@azuby said:
...
Ruby has GUI support for:
TK
wxWidgets
Qt
GTK
Fox
WebDialogs for SketchupAre any of these built-in?
@unknownuser said:
Multi line consoles:
WebConsole - http://sketchuptips.blogspot.com/2007/08/plugin-webconsolerb.html
d/Code - http://www.errorinitus.de/ => SoftwareI am talking about the Ruby Console in SU. Ruby has many good editors but not embedded directly into SU.
@unknownuser said:
Your first steps could be using a bridge between Ruby and Python (or use the Sketchup SDK to write your own lib):
Ruby/Python - http://www.goto.info.waseda.ac.jp/~fukusima/ruby/python/doc/index.html
Ruby-Python-Bridge - http://www.vyperlogix.com/ruby-python-bridge/
pyRuby-Python-Bridge - http://pypi.python.org/pypi/pyRuby-Python-Bridge/1.7This is exactly how i want to start. The reason for this thread was to test the waters for SUuppers who would be interested in a Python API. From here i plan to get Python talking to Ruby, build support and see where it goes from there. Are you interseted in having more choices azuby?
-
Azuby,
If you (or anybody for that matter) know of a highlevel language besides Python that has more quality documentation, stable built-in GUI, clear syntax, is easy to learn, widely known and accepted, has a future, and open source -- Please let me know because i will dump Python and crusade for that language religiously.My religion is not Python, my religion is any language that will give me the most production with the least effort and expenditures. Which is the definition of a good language. this is the 21st century, it's time to send some archaic, redundant languages off to their destiny of extinction. Let today's high-levels rule until the next generation of languages renders them obsolete!
-
So quit posting here and just go make the tutorials, and do your python stuff. Aint no one here stopping you.
Chris
-
Christopher,
I see a lot of rage in your posts. Maybe you are angry because you are having trouble learning Ruby, and taking that frustration out on me. It's OK, i can understand that
. Ruby is not nice to a nuby.But there is light at the end of the tunnel Chris, one way or another i am going to improve SU for everybody. Maybe you should get involved and contribute some of your ideas instead of pitching temper-tantrums to those who are trying to improve this great software. Which will, in effect, make your learning process much easier, and your potential for success much greater.
BTW, I love your quote
-
I understand, why fight a losing battle?!
FYI: C and Python interact very well, you can optimize with C where needed.
Now you have the best of both worlds. The readability, maintainability, and clear syntax of Python, coupled the speed and low-level access of C.
WOW!, If you have as much experience as you say, then you would know that.
-
I think you mis-read my posts. No real temper tantrums here per se. I would like there to be more tutorials for ruby in SU for beginners. I'm working my way through it, but I know it could be better. I'm pretty sure that python wouldn't make it much easier though. I have plenty of good info on Ruby. Its just difficult for my brain to understand it in context with SU. I would have the same trouble with Python. Its ok though, I'll figure it out and all will fine. And I did give my ideas. Go get working on the tuts. Thats all that I want. I've seen you say repeatedly that they are in progress - great. So go finish them
Chris
Thanks for the complement on my quote. I put it on when I was a noob on the forums years ago. I liked it so I've kept it ever since.
-
I think if i where to ask a stranger for a favor, I would do it in a very humble way, and I would probably want to include a "please" or "thank you" somewhere in the conversation. What do you think Christopher?
As we speak I am creating a Group dedicated to a SU Ruby tutorial aimed at non-programmers. This tut will teach basic programming principals while writing scripts for the Ruby SU API. I am writing the tut all by myself at this time. You see i could just teach myself Ruby, and then look down on the others who don't know it, but i want to give back, and empower my fellow SU brothers and sisters.
I want people to learn and give back them selfs by adding to this tutorial as a community project. You see if everybody volunteered a piece of their time (instead of just gimme, gimme, gimme all the time) maybe the SU world would be a better place(9 years ago)? Eh Christopher?
-
Hi Jessetopher, sounds like you want me to contribute more to the SU community because I'm not holding my own and I don't know much about community involvement.
And don't worry about the tuts. I'm just giving you a hard time cause you're so verbose here on the forum. I'm sure they'll get done and they'll be great. So don't mind me, I'm probably just cranky from having to work all weekend long.
Chris
-
All this sounds interesting (apart from "bickering"
). Can you tell us when the first tuts are going to be ready. I am keen to get me going. Are you saying that you intend to make a bridge which would than enable people to use Python instead of Ruby? -
@jessejames said:
I will smash this wall to pieces, and lead you into the promised land!
I look forward to it.
@unknownuser said:
Has anybody seen such commitment for teaching/improving the SU Ruby API in SU's 9 years??
SU has only had an API since v4, and i believe there have been incremental improvements with each new version of SU, although i wouldnt be able to tell you what they were.
-
@jessejames said:
Has anybody seen such commitment for teaching/improving the SU Ruby API in SU's 9 years??
The SU Ruby API was introduced as being available for the first time in June 2004 with SU V4.
-
@unknownuser said:
The SU Ruby API was introduced as being available for the first time in June 2004 with SU V4.
Thanks Todd and Remus for correcting me. Here is my newly edited version.
Has anybody seen such commitment for teaching/improving the SU Ruby API in the almost 5 years since it's introduction?
? -
@remus said:
...i believe there have been incremental improvements with each new version of SU, although i wouldnt be able to tell you what they were.
points at quote
-
Hello sepo,
@sepo said:
All this sounds interesting (apart from "bickering"
). Can you tell us when the first tuts are going to be ready. I am keen to get me going.The tut is in very beginning stages at this point, since i am the only author working on it. I had to stop and pursue this effort because of the current limitations of..
1.) Ruby documentation in general
2.) No built-in GUI toolkit in Ruby
3.) The single line Ruby Console in SU is detrimental to a new Rubyists learning experience.A multi-line Console must replace the current single-line console. That way a Ruby Nuby can write code in a natural way, using indention. Interactive seesions are the key to learning a new language fast and painlessly. The "get results right away" aspect of interactive consoles makes learning more fun.
But the current Console sets up users for failure before they get a chance to even start. I also think a simple built-in text editor (or plug-in) would be a great idea to simplify work flow. Most software with an API, includes some sort of text editor built in and usually it has syntax highlighting.
So my current crusade is for SU to grow a Python API. Python has the first two already, and the last would be no problem. This would also give people choices -- i like to have choices.
So far my Ruby tut only covers strings, floats, integers, and functions -- all of which still need polishing. Plus i want to include leaning the API along with Ruby at the same time by building on a simple script throughout the tutorial. This sort of "see results right away" is what will keep people interested and motivate them to learn.
Right now a huge brick wall is between you and SU scripting. I will smash this wall to pieces, and lead you into the promised land!
@sepo said:
Are you saying that you intend to make a bridge which would than enable people to use Python instead of Ruby?
I am saying i want SU to grow a Python API so people can choose which language they want. But bridging may be the only step available at this point. Then i could develop a group of advocates who could convince the SU team to include a real Python API -- since most of the work would be already complete, and the need would be proven, the incorporation would be minimal.
Hence the reason for this thread, to find out what interest there may be in "SU land" for Python scripting. All that would be needed is good API docs, Python already has thousands of great tuts out there free of charge, and Python has a great easy-to-use built-in GUI toolkit.
Most of all, i believe Python is much easier to learn, making it perfect choice for any API -- and i intend to prove that by personally tutoring anybody interested in Python scripting. That's how committed i am!
Has anybody seen such commitment for teaching/improving the SU Ruby API in SU's 9 years??
EDIT:
Has anybody seen such commitment for teaching/improving the SU Ruby API in the almost 5 years since Ruby has been here??Look, SU is the best piece of software i have ever seen, truly revolutionary 21st century software. The UI is flawless, the design is flawless. The only short-coming is the scripting API.
Scripting must be accessible for all, not just a few professionals at the top. Every hard-core user of SU will need the power scripting provides. Python like SU, is revolutionary in the programming world. The marriage of these two great powers will guarantee the upward evolution of SU for years to come!
PS: i am not upset with Chris, i just wish he would get on board with improving Ruby or including Python thats all. The only way any of this will get better is if we make it better.
-
Can you say that you've done so much for the Ruby API before you actually have it done? Here's a deal, I'll heap praises upon you once you've done something.
Chris
-
Remus,
I am referring to the short-comings i see about Ruby scripting. I am sure many great advancements have been made before i came along, and I see many dedicated people writing scripts, and answering questions.Here are the reasons I believe, learning Ruby is more painful than it needs to be...
1.) Lack of free, clearly written tutorials for the Ruby language aimed at non-programmers.
2.) Lack of good examples in the Ruby SU API(#1 would cancel this out though)
3.) The need for an improved Multi-Line Interactive Console in SU.
4.) The need for a simple integrated text editor w/syntax highlighting
5.) The need for a simple to use real GUI toolkit built-in to the scripting language(script and go)These would greatly improve the SU scripting experience for all. This is the main reason for my recommendation of the Python Programming language. Python has the docs, and built-in GUI(TK) already. The text editor and multi-line console would need to be created either way.
Ruby and Python are the only two languages that stick out in the very high level programming world(IMO). Ruby and Python share some similarity's, but they also differ greatly in approach and style. The bonus here is that people could choose the language that best fits there mind-set. This would truly be beneficial to SU and all who use SU.
-
I fully agree with #1 and 2. I'm not familiar with what #3 is in Ruby or any language, so I don't know what I'm missing. I'm sure it would be welcome though. Isn't there a plugin for this already? #4 is something that seems like a no brainer to include from the start, but what do I know? So I agree, it would be nice - no, more than that. Is there a way to incorporate SciTE or something into SU? It seems like there should be better real time feed back (well not realtime, but better testing and execution) inside of SU. (How are #3 and #4 different? I don't quite get what the difference is) #5 I haven't seen how poorly the built in ruby options are.
Those are some great points and they would be a good starting point for helping get more of us into ruby.
Chris
-
- What is wrong with WebDialogs?
- What is wrong with the multi line consoles I mentioned? (Have you tried them?)
- Why not writing an own Python lib with the help of the Sketchup SDK instead of using a bridge and getting angry about Ruby?
I agree: Sketchup Ruby (1.8.0) is just a basic thing. "True" Ruby (>= 1.8.6) has lots of great libs.
(PLEAC Ruby - kind of documentation)
azuby
-
@azuby said:
- What is wrong with WebDialogs?
- What is wrong with the multi line consoles I mentioned? (Have you tried them?)
- Why not writing an own Python lib with the help of the Sketchup SDK instead of using a bridge and getting angry about Ruby?
I agree: Sketchup Ruby (1.8.0) is just a basic thing. "True" Ruby (>= 1.8.6) has lots of great libs.
(PLEAC Ruby - kind of documentation)
azuby
I'm sorry azuby for adding my 2 cents, I realize this quote was directed @JJ.
I don't hear anyone getting angry about Ruby. All that's being discussed is having another Scripting option that would co-exist along with Ruby, within SU. I'm not a programmer, I'm not interested in learning 2 more languages just so I can incorporate WebDialogs in SU. How long are WebDialogs going to be around, before something new comes along? The Web and its content are constantly changing. Look at all the different video formats on the Web. No one can agree on a standard. We just keep adding more, because each might infringe on the patent rights of the other. However if I was 20 again and had the programing skill you speak of, I might be tempted to agree with your point of view. -
Hello Azuby,
@azuby said:
- What is wrong with WebDialogs?
Nothing that i know of, I just prefer a real GUI toolkit. The great thing about Pythons built-in GUI Tkinter is it's simplicity. Pro's and noobs will find it equally useful.
@azuby said:
- What is wrong with the multi line consoles I mentioned? (Have you tried them?)
No i haven't. What i want is a built-in Multi-Line Interactive Console in SU. The first experiance a new scripter will have is "playing around" in the console. Using a one-line-at-a-time Console will surely defeat them before they have a chance.
@azuby said:
- Why not writing an own Python lib with the help of the Sketchup SDK instead of using a bridge and getting angry about Ruby?
Good Idea!, i will look into this.
Thanks
Advertisement