semhoze Posted February 18, 2012 Share Posted February 18, 2012 (edited) 1st, thanks for all your great work guys and especially to Rick for starting it all - I just did all editing work for my new online business (icons, logos, banners, etc) in PDN. I also did some photo editing work some time time ago in PS and PSE and don't miss them at all! I'm not a pro, so apologies in advance if some suggested features don't make any sense. In no particular order: 1) My vote for Export in addition to Save As. Export would simply do Save As but without replacing current file format PDN is editing. It's quite annoying: saving a file as pdn to preserver layers, then saving it as jpg, closing jpg, and reopening pdn file, over and over and over again. 2) General approach for temp overrides to speed up work. Some examples: a) Holding Alt while clicking to start Text would turn off AA for that particular text that you are about to type - regardless what the setting on the toolbar is. holding Ctrl while selecting region with Magic Wand would set tolerance to zero temporarily - regardless what the setting on the toolbar is. These temp overrides, imho, should be discussed and unified across many tools before implementation, so that for example Alt can be set to temp disable AA for whatever tools AA is applicable/implemented, while Ctrl can be for zero tolerance (selections, masks, eraser, clone/stamp, etc). 3) Ants like in PS - it really helps seeing what's selected. 4) Color picker that can go outside of PDN while picking colors - very handy. 5) Plugins folder (Effects) - PDN should look in subfolders recursively too, if any, so that one can create those and organize plugins anyway one likes. For example, if I want to try some plugins and don't find them of use, I can just delete that folder I created for them and keep everything clean. Right now, I have a whole of bunch of them in one and don't know what belongs to whom and what are dependencies. That would also help with organization if plugins are accompanied by config or other files and prevent conflicts and dlls being overwritten. 5a) Perhaps Plugins menu item tooltip should show full path of the dll implementing that effect - very handy for removing bad/unused plugins or, once 5) is in place, finding author: Effects\BoltBait\BadPlugin.dll ;-) 6) pdt extension for templates - this is like dot or xlt. Those would be just pdn files with renamed extension so that PDN would not overwrite them if we click Save, but prompt for a file name assuming pdn extension. Pretty much the very same way MS Word defines dot files: user-created starting points (just documents) with automatic protection from being overwritten if user forgets and clicks Save. Save As dialog would of course offer pdt type. ---- Hope this helps. I'll keep them coming. Thanks for listening. Edited February 18, 2012 by semhoze Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.