Google is Listening!
-
@jhauswirth said:
@jclements said:
Perhaps utilizing multicore processing would be possible for Layout rendering?
You guys want to know a funny thing? LayOut 2.0 on Windows
renders in another thread while you continue to work on the
document. What's so funny you ask? Well in LayOut 2.1 we
had to pull out the background rendering and guess
how many people noticed? ZERO!Well I certainly didn't...since I don't use Layout.
-
@hieru said:
@thomthom said:
.....a Plugin Manager would let you browse and download plugins directly from SU. And of course update when updates are available. The Plugin Manager should be available as an one-click-installer.
Basically something like Dreamweaver's Extension Manager?
Now there's a good idea!
-
I would think google should keep the SU in 32bit for the less intense users and release the 64bit for more intense users. Let us (the users)test it out and you will get your response of what we think that if the 64bit version actually benefit more to the intense users. Now a day, I believe computers set their 64bit application as their standard. I have seen laptops as low as $400 with 64bit window base application. I believe 64bit is the future if not the current then why SU stays as 32bit.
-
Peep
I want a way to selectively disable inferencing -- a checkbox list for which inferences should be on or off.
Not having that option is a major bummer for me.
-
I think that introducing coloured guide lines will ease a lot of work during construction.
Just a thought
Toxik
-
Hi,
In my opinion it will be essential to bring in SU (free and pro - especially free) linetype, lineweight, hatching, even it's a 3D modelling tool. (in fact, we all need a 2D plan before 3D modelling)
-
@julyyen said:
Hi,
In my opinion it will be essential to bring in SU (free and pro - especially free) linetype, lineweight, hatching, even it's a 3D modelling tool. (in fact, we all need a 2D plan before 3D modelling)
2D tools by TIG here: http://forums.sketchucation.com/viewtopic.php?t=22091
-
-
There are a lot of questions/suggestions available in this topic:
http://forums.sketchucation.com/viewtopic.php?f=180&t=13666All of them for the use of developers.
But if those people get the right tools, they can make better plugins and extend Sketchup possibilities.
It's like Pixero wrote:'extend the API'!
I know it is impossible to adress everyones wishes. But if you make the API better, then more people can try to answer those wishes...
-
@pout said:
There are a lot of questions/suggestions available in this topic:
http://forums.sketchucation.com/viewtopic.php?f=180&t=13666All of them for the use of developers.
But if those people get the right tools, they can make better plugins and extend Sketchup possibilities.
It's like Pixero wrote:'extend the API'!
I know it is impossible to adress everyones wishes. But if you make the API better, then more people can try to answer those wishes...
i'm sort of under the impression (judging by a couple of random posts by SUteam members) that they don't want to go full on in supporting plugins..
i'm pretty sure if they set up a depot app store type of thing then they'd have a gigantic slew of new problems to deal with.. fredoscale was a decent example of what may happen so imagine if that was happening to millions instead of thousands.
it'd be sort of sweet if google had an approval process of some sorts prior to rubies going live but again, that's a big undertaking in itself + we'd miss (some of) the benefit of talking directly with the developers and offering ideas/additions etc. (that could still occur but the process would be weeks/months instead of hours/days.) -
@unknownuser said:
i'm pretty sure if they set up a depot app store type of thing then they'd have a gigantic slew of new problems to deal with.. fredoscale was a decent example of what may happen so imagine if that was happening to millions instead of thousands.
If I may ask, what was the fredoscale example?
-
Due to an unknown design limitation on the API regarding the
UI::Commandobjects, context menus began to grey out when one used the plugin. -
-
Thanks.
-
Thanks for your input Gaieus. My observation with Sketchup in Ubuntu Koala with Wine 1.2 is very good speed using Nvidia drivers, so it must be using openGL natively. But you have a point because trying to make a raster export is disastrous. But working within Linux without doing that is snappy,apart from a garbled start screen. What I was thinking of was a Sketchup Linux written for Debian or Red Hat which has a large user base. Recently, Bricscad released a full Linux version of their CAD application and it is pretty impressive. Snappier than in Wine.
-
@unknownuser said:
i'm sort of under the impression (judging by a couple of random posts by SUteam members) that they don't want to go full on in supporting plugins..
i'm pretty sure if they set up a depot app store type of thing then they'd have a gigantic slew of new problems to deal with.. fredoscale was a decent example of what may happen so imagine if that was happening to millions instead of thousands.
it'd be sort of sweet if google had an approval process of some sorts prior to rubies going live but again, that's a big undertaking in itself + we'd miss (some of) the benefit of talking directly with the developers and offering ideas/additions etc. (that could still occur but the process would be weeks/months instead of hours/days.)Jeff,
I would not go that far to put the ruby plugin dev under their wings. I think the way it works now is ok.
There are a lot of good plugin ideas being put in a trash can caused by the lack of some basic classes.
The handling of problems with (and responsibility for) the plugin must be handled by the plugin author, not by Google SU. -
Smooth out the pencil tool lines and add points to edit the curves please.
-
For those who don't know the answers and discussion about ideas/votes are happening here:
Best,
Jason. -
@pout said:
Jeff,
I would not go that far to put the ruby plugin dev under their wings. I think the way it works now is ok.
There are a lot of good plugin ideas being put in a trash can caused by the lack of some basic classes.
The handling of problems with (and responsibility for) the plugin must be handled by the plugin author, not by Google SU.Pout—
Sure, developers should write good code, but I think Google SU is pretty irresponsible with the way they handle Plugins.
It's okay if they want the program to be a platform for developers, it builds community for giveaway software. However, they know full well that the vast majority of developers are unpaid volunteers, by definition amateurs. And who says amateurs should know how to code as well as a pro, let alone be able to afford the time to debug a plugin to the professional level?
Issue 2— Google hosts the forum, including a discussion for Plugins. However, there is no central directory, no place where all plugins are listed, rated, reviewed, explained and linked to. Right now you have to ask around, search around, track down all the posts and do a lot of homework. If this is what it takes to make a functional program (and the consensus is that plugins MAKE Sketchup, why not make it easier to figure out what you need to do the job you are working on?
Issue 3— You download a Ruby, open the folder and dump all its contents in the Plugins folder. No wonder there are naming conflicts! Give us a Plugins Manager. Rewrite the program so that you put Rubys in the Plugins Folder inside their own folder. With a moderate selection of Rubys I have 50 some items in there and no clue as to what goes with what. How are we supposed to debug if there is a problem? Dump everything and download it over again? Get real!
This stuff isn't rocket science, it's basic software management. It's just fine for a giveaway program, but lots of us have the pro version and for $500 this isn't a big upgrade, it's pretty simple and obvious.
Jim
-
The flip-side to that is it could be that some our best and brightest Ruby coders are here because of (rather than despite) the lack of overseers... that would make it too much like a job thus squashing the creative spirit.
I'm not a big fan of micro-management of anything -- I personally prefer to have people let me do my thing my way... if that doesn't happen then I find a new playground. I'm sure there are Ruby authors who feel the same way.
I mean the crux of it is they are dissatisfied with how Sketchup works and are trying to re-create it in their image. If you have to deal with oversight then you begin to take away the ability of the author to "dream out loud".
I understand your desire to make things easier, and that is certainly on the mind of the Sketchup developers, but developing for the lowest common denominator is why Sketchup needs plugins in the first place.
Best,
Jason.
Advertisement