Jump to content

DominikDalek

Newbies
  • Posts

    3
  • Joined

  • Last visited

About DominikDalek

  • Birthday 01/01/1970

Profile Information

  • Location
    Poland

DominikDalek's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. You have one menu for the whole application as well, but some options will be enabled/disabled when you switch between documents (e.g. one layer doc should have "flatten layers" option disabled). In real life if you have two easels, one for sketching and one for oil painting and for some reason you prepare both pieces simultaneously, you definitely don't want the same tools for both. The fact that you have one tool dialog does not mean you should stick to one active tool, color, etc. per application. From my point of view - tool and color assigned to document is more intuitive (although most apps have them common for all documents). But still, it's your decision.
  2. Is this a final decision? This isn't the only approach possible, it's not even the best one (there is no thing as the best approach ). From my perspective both current tool and tool parameters should be workspace-specific. Imagine the following scenario: you're making an image processing using copy/paste technique. You want to take a piece of one photo and place it on the second one. You surely want selection tool active for source document and move tool for target. If you want to create a fancy rounded corner shape on target layer, you'll need selection tool for both, but rect. sel. for source and round sel. for taget. There are lots of scenarios like these two... Best regards, Dominik Dalek
  3. Hi, This used to be an email I sent to Paint.NET contact address, but it looks like for some odd reason I can't receive any mail from hotmail account. So here it goes in slightly modified version. First of all let me congratulate a great piece of software you are developing. I like it a lot and I'm coding texture generation plugin for it to automatize some processes for my Master's Thesis. I wanted to share some modifications to the core code as well. But the question is: do you accept any code in other form than plugin itself? Is there any place where you coordinate your work? (it's a bit of waste of time to code any feature which you probably brewed and commited into your source depot already.) So far I'm working on some CodeLab improvements and I modified plugins handling code so it is possible to manage them in subdirectories (it should come in handy with plugins amount increase in the future). Screenshot below. TIA. Best regards, Dominik Dalek
×
×
  • Create New...