[Plugin] Layers Panel 1.2.1
-
Sorry guys, but I won't have time to work on Layers Panel until a long time. All my spare time is now dedicated to my new plugin (which I plan to sell, hence the priority)
Sorry for the inconvenience. The code is on GitHub, so if you find a coder willing to try to find his way into this mess (it was my first plugin, so quite messy), he can freely modify it and send pull requests.
GitHub - thomas-hauchecorne/Layers-Panel
Contribute to thomas-hauchecorne/Layers-Panel development by creating an account on GitHub.
GitHub (github.com)
-
@jiminy-billy-bob said:
Sorry guys, but I won't have time to work on Layers Panel until a long time. All my spare time is now dedicated to my new plugin (which I plan to sell, hence the priority)
I'm sure you have considered this but why don't you make this plugin commercial? I'd be happy to pay 5-10€ for this if it works properly. It seems to be pretty popular already..
It's entirely up to you what you want to work on though and I hope the SU team will pick up on your work soon.
-
Well, I thought about it. But I don't think that's the kind of plugin that fills a void. I mean, it does improve the layers workflow, but it doesn't create one. So I'm not sure there is really a market to sell this.
Plus, I realized that working with SU's default features and adding depth to them is risky. There are impredictable things, it's clunky.
It's kind of a mess, and Layers Panel has become like a big collection of workarounds. I'm not sure I could ever take it to a point where it's 100% working (even with a complete rewriting), I think there will always be bugs.
It has become really frustrating to work on this.My new plugin (which has nothing to do with layers) creates new features entierly, it doesn't need to keep track of model changes or being in sync with SU all the time. And let me tell you, it's so much more fun!
-
@jiminy-billy-bob said:
Well, I thought about it. But I don't think that's the kind of plugin that fills a void. I mean, it does improve the layers workflow, but it doesn't create one. So I'm not sure there is really a market to sell this.
Well Jiminy, I don't agree with you on this. It fits a void... updating layers on scenes has never been easier, finding layers has never been easier, changing colors (though not in bulk) has never been easier. They're not things that we couldn't have done before, but they're things we hated to do and now hate a little less...
however if
@jiminy-billy-bob said:It has become really frustrating to work on this.
then the plugin it's more than good enough as it is. Maybe SU team could pick on your ideas, give you something back and implement them internally. I know they should!Besides, we just want happy and creative developers
@jiminy-billy-bob said:it's so much more fun!
so you can do your thing!Thanks for Layers Panel and bring the next one on!
-
@jql said:
They're not things that we couldn't have done before
That's my point. I think people are willing to pay for something that they simply couldn't do before. And I mean enough people paying enough money for the time I would actually be spending on this.
I think one of the main reasons LP is popular is because it's free.Let's do the math, and let's be really optimistic while doing it.
I know there are around 500 unique daily user. So maybe 3 times that amount using it regularly? That's perhaps 1500 people.
I said let's be really optimistic, so let's assume 1/4 of that amount would maybe be willing to pay like $5 for LP. That's ~400*5 = $2000. Convert it to euros, take back taxes, etc. I could be working a month on this (and lowering my current incomes). I think I would need much more than a month to rewrite it completly, test it toroughly to iron out every bug. Plus maintenance, support, marketing, etc.
And that's while being really optimistic.
Yeah, I'm not sure the furstration is worth it.Apart from that, how would people react if suddenly LP was paid only?
@jql said:
Maybe SU team could pick on your ideas, give you something back and implement them internally.
I would love them to implement something like this without giving me something
I mean, I didn't invent anything. -
Feature request: Render Layers option compatible with Twilight Render
Suggestion:
-instead (or beside it) having that button "Move selection to the Highlighted Layer", it could be useful that right click on a certain layer to add this option. Why? - because it happened for me several times to accidentally have a different layer selected than the one I wanted to. But right clicking on a layer makes that 100% that is the wanted layer (because the user is ALREADY with the cursor on it). -
Plugin installed successfully, but I get a pop-up telling me it needs to be debugged. However, when I click ‘continue’, the succeeding pop-up only lists in-model layers and says ‘no issues’. This happens with any model. [OS X 10.10.2]
-
Do that debug in your template and save it as template and the template issue is no more.
Do that debug in any model and save it and that model's issue is no more.
This is most probably related to models you've developed when you had some prior "Layer's Panel" version installed.
-
Hello,
This is my favorite plug-in for organizing my model.
But I am unable to get it to work in SU 2015 (Mac OS X Yosemite).I have tried loading and unloading it several times. The layers panel open for only a split second and then disappears...I've never had this problem before and don't know when it started. only the 'layer state' panel stays open...
Can you tell me what I need to do to get this plugin to work properly?
Is it compatible with my system?
Do I need to delete older files?Thank you!
-
@brooklynarch said:
Hello,
This is my favorite plug-in for organizing my model.
But I am unable to get it to work in SU 2015 (Mac OS X Yosemite).I have tried loading and unloading it several times. The layers panel open for only a split second and then disappears...I've never had this problem before and don't know when it started. only the 'layer state' panel stays open...
Can you tell me what I need to do to get this plugin to work properly?
Is it compatible with my system?
Do I need to delete older files?Thank you!
Hi,
Same problem - it worked before and I don't remember updating anything, might have installed a plugin or two though.
SU 2015, OS X Yosemite. -
Pity to hear that this plug-in is discontinued developing. Would like to pay for it. It really speed up the workflow a lot.
-
@greatoe said:
Pity to hear that this plug-in is discontinued developing. Would like to pay for it. It really speed up the workflow a lot.
Sorry about that... But please understand that only few people are willing to pay for this, and not a lot of money.
I am curently developping another plugin that I will sell, so I can't take much time for Layers Panel.
I think LP is already pretty good as is. Although I will try my best to fix bugs.BrooklynArch, did you try what we discussed by email?
-
@siim11s said:
@brooklynarch said:
Hello,
This is my favorite plug-in for organizing my model.
But I am unable to get it to work in SU 2015 (Mac OS X Yosemite).I have tried loading and unloading it several times. The layers panel open for only a split second and then disappears...I've never had this problem before and don't know when it started. only the 'layer state' panel stays open...
Can you tell me what I need to do to get this plugin to work properly?
Is it compatible with my system?
Do I need to delete older files?Thank you!
Hi,
Same problem - it worked before and I don't remember updating anything, might have installed a plugin or two though.
SU 2015, OS X Yosemite.Uninstalled "CutList" plugin (inactivate did not help). LP now works again.
-
Great plugin ! Just started to use it. Please, please add Twilight Render support to it.
And second, automatic start with A LOT of layers crashes sketchup. Worth investigate.
Keep up the good work!EDIT:
-too bad it doesn't have a sorting function by column (name, state).Please continue developing it. It is a really good plugin (and I would pay for it, if that is the condition for you to continue development). Or at least, if you are not willing to, maybe someone else would take it to continue, if you will agree on that. Is so bad that an advanced layers manager goes to die.
EDIT2:
-In SU 2015, "Highlight Selection's Layer" doesn't seem to work. -
Have been waiting to try this plugin out for some time and just taking it for a first run in conjunction with Layout - really impressed
-
@derei said:
Or at least, if you are not willing to, maybe someone else would take it to continue, if you will agree on that. Is so bad that an advanced layers manager goes to die.
The source is on GitHub, anyone can fork the project and push updates. I'd be glad to release them.
GitHub - thomas-hauchecorne/Layers-Panel
Contribute to thomas-hauchecorne/Layers-Panel development by creating an account on GitHub.
GitHub (github.com)
-
I have a suspicion that Layers Panel is messing up with Scene settings. It won't keep the hidden/visible layers as set and something (couldn't figure what) makes certain scenes (the activated one) to update with the setting on that particular moment.
Eg: - i set some hidden/visible layers to a scene, then I update it. If I change something after that (add layer, hide layers, show more layers, etc), I will end up with a messed-up scene that won't keep the settings that i did to it in the first time.
This just renders the plugin mostly unusable.
Did this happened to others?
-
Have just dealt with this exact issue although I wouldn't say that it renders the plugin unuseable.
I simply scan through the scenes (50+ in current model) selecting/deselcting appropriate layers and updating the scenes as I go - takes a few minutes to overcome
-
You've done a pretty impressive job IMO
-
The ruby-side of the whole layers system is just a mess. It's really difficult, if not impossible, to keep track of everything. What the user does, what he expects to happen, what Layers Panel should do, and how. Some stuff is not even possible, for other stuff I had to use really dirty workaround.
You just ran into one of these. Nothing in the ruby API is planned to keep track of when a scene is updated.I'm aware of this issue, but I never found a better way to do it.
I know Layers Panel has problems, but the reason why I stopped pushing it forward is because the ruby API is not meant for this.
Frankly, if I knew in what I was diving into, I probably would never have started this project.
And that's why working on Skatter is so rewarding : It's a whole new tool, it's not built on some existing Sketchup system, I don't have to keep track of user actions outside the tool, etc. So it's much more stable and easy to develop.EDIT : You can see the original strugle on this : http://sketchucation.com/forums/viewtopic.php?f=180%26amp;t=54473
Advertisement