ycodedotme / paintweb Goto Github PK

The color mixer panel should include a check box for enabling real-time 
color changes, such that users can try the new color with the drawing tool 
without having to accept the color change. This would make it easier to 
test new colors.

Note that this option should be disabled by default, due to performance 
concerns.

PaintWeb fails to load without config.imageLoad.

What steps will reproduce the problem?
1. open url http://www.robodesign.ro/paintweb/trunk/demos/demo1.html
on flex browser (html flex control, this is based on webkit)


What is the expected output?
--> all buttons control should be displayed

What do you see instead?
--> none of the buttons are displayed

What version of the product are you using? 
--> the latest

On what operating system and
which Web browser?
--> windows 7 home premium
--> browser: flex html control 

Please provide any additional information below.

Users should be able to scroll the main color mixer slider with the mouse 
wheel.

Inputs of type=number look like typical inputs of type=text now. PaintWeb 
should extend the GUI of these inputs automatically to include actions for 
increasing and decreasing the numeric value.

Make sure that the new GUI elements which enhance the numeric inputs are 
usable with the keyboard as well.

Currently, drawing tool objects are instanced when PaintWeb.toolActivate() 
is invoked. The PaintWeb.toolRegister() method does not create instances 
of tool objects. Some drawing tools need this to provide additional 
functionality within PaintWeb even when they are not active. Such examples 
are the Hand tool, the Selection tool and more.

By fixing this issue, some code from the user interface can be moved into 
the implementation of each drawing tool. This amounts to better future 
code maintainability.

The current TinyMCE plugin has not been tested (nor prepared) for use with 
multiple TinyMCE instances inside the same page, nor with multiple 
PaintWeb instances. There should not be too many issues, but this should 
be tested and fixed as needed.

Currently, PaintWeb does not allow users to cancel the color change with 
the press of the Escape key when an input is focused.

Make sure that users can press Escape when any input field is focused, and 
that the action of the Escape key is the same as "cancel color change".

The interface script includes hard-coded user interface functionality 
specific to drawing tools. This needs to be cleaned-up once issue #3 is 
fixed.

Currently PaintWeb allows users to crop an image only using the canvas 
resize handle (south-east of the image).

The PaintWeb API allows developers to resize and crop images, however the 
user interface does not yet expose this functionality.

Implement a GUI feature which allows users to crop and resize images.

One idea is to allow users to click the image dimensions element which are 
now displayed in the status bar. That would bring up on screen a floating 
panel where users can crop/resize the image as desired.

Currently the pencil drawing tool uses paths (typical lines) within the 
Canvas to draw as desired by the user.

The pencil tool should be improved such that it also allows users to pick 
brush shapes, pressure, size and transparency. The current mode of drawing 
should be kept as well, for performance reasons.

PaintWeb should allow users to increase/decrease the numeric value of any 
input of type=number with the mouse wheel.

Currently the PaintWeb configuration file is pretty big and it loads only 
once during application initialization.

The PaintWeb API should provide the means to load configurations on 
demand, such that the PaintWeb configuration could be split into multiple 
files. For example, config-basic, config-full, config-common, etc.

Based on minimal testing, some drawing tools in PaintWeb have problems 
when the user tries other mouse buttons. By default, the drawing tools 
only respect the use of the left click, however there might be problems 
when the middle and right buttons are used.

Investigate any such issues and fix them as necessary.

Currently some PaintWeb drawing tools share common configuration options 
like the lineWidth. This is not desired. Each drawing tool should have its 
own settings.

Implement a color bucket tool.

Currently PaintWeb loads an XHTML file which is appended into the 
destination document, and it also adds a reference to a CSS file, for the 
styling of the GUI. This works well when the target application makes 
proper use of CSS. However, it is common that mistakes crop out, and the 
PaintWeb GUI is affected by other style sheets in the application which 
can apply to elements of the PaintWeb interface.

One possible solution is to keep the entire user interface inside an 
iframe. In this iframe the element IDs would no longer need mangling and 
the style sheet could be merged in. The problem is with "floating panels" 
- they'd become stuck inside the iframe.

Another possible solution would be to use scoped styling from HTML 5. I 
need to check which Web browsers implement it (if they do).

While the new PaintWeb GUI made improvements over the previous version, it 
still lacks sufficient polish.

Olli Savolainen has made really good suggestions for user interface 
improvements. Other ideas for a better GUI include: tab reordering and 
regrouping.

The user should be able to use a flexible GUI which has containers that 
are dockable onto any side of the browser window or they can be used as 
floating panels. Each container should be draggable and groupable into 
tabs.

Allow users to double-click on the tab bar to minimize/hide the content 
and only show the tabs list.

The PaintWeb API provides sufficient functionality to allow developers to 
change the image background color, however the GUI lacks any such option.

Implement a GUI color input which allows users to change the image 
background color.

Some PaintWeb extensions use a lot of language strings. It would be ideal 
if the main language file could be split into multiple files, such that 
extensions can load their own strings only when needed.

The PaintWeb API should allow developers to load language files on demand.

Currently, PaintWeb saves images using their initial file format (that is, 
JPEG or PNG). Not all Web browsers implement support for saving the Canvas 
using the JPEG file format. Thus, if anything fails, the image is saved as 
a PNG.

The PaintWeb GUI should provide a place where the user can selected the 
*preferred* file format.

Currently developers have to edit the Makefile to configure the PaintWeb 
building process.

Implement support for using a separate configuration file where users can 
change how PaintWeb is built.

The idea would be to allow something like:

make config

which creates the config.mak file with default values. The developer can 
edit the file and then he can run the normal "make" process.

Hi,

When I use your demo, the eraser functionality does not work.

I draw some lines, add some text, and want to erase a bit.
I click on the eraser tool and drag it over the area, it adds some random grey 
noise
to the image but does not remove any drawing.

I tested this with Safari 5.0.5 on Mac OSX 10.6.8 and Google Chrome on Windows 
7.

Herman verschooten

Allow users to perform a horizontal/vertical image flip from the GUI and 
from the API.

Allow users to freely rotate the image, and also provide predefined 
rotation angles in the GUI. Make sure the API is exposed such that other 
parts of the application can reuse the functionality.

Currently any color saved in the color mixer is lost when the PaintWeb 
session completes.

Provide an API such that developers integrating PaintWeb into their 
environment can permanently save the custom colors.

Fixing this issue will involve the use of PaintWeb application events and 
will probably require a back-end for data storage (cookies, client-side 
files, or server-side files, depending on the environment).

Currently the Selection tool uses an off-screen Canvas element for 
buffering the selected pixels. From the said buffer, the pixels are copied 
and scaled using the drawImage method onto the destination Canvas.

The above approach might be slower and more cumbersome than simply using 
the transform() method available in the 2D context.

The color mixer panel should be resizable.

Users should be given the possibility to freely rotate the selected pixels 
using the Selection tool.

What steps will reproduce the problem?
1.
2.
3.


Please provide any additional information below.

At the moment PaintWeb extensions come in the form of a single JavaScript 
file which goes into the extensions folder.

Developers should be able to include language files with the strings used 
by the extension, and a configuration file if needed, in a single folder. 
However, this is not the only possible packaging scenario - any solution 
for easy deployment of packaged PaintWeb extensions is welcome.

What steps will reproduce the problem?
1. download release zip and unzip it.
2. delete src, samples and etc, just keep release files
3. add to my own javaee web content.

What is the expected output?
paintweb loaded without any error, but i always get error that 'not 
well-formed' and 'syntax error' when loading config json, language json and 
color window json though paintweb works so well.

What do you see instead?
no error from browser debug.

What version of the product are you using? On what operating system and
which Web browser?
lastest, Win7, FF 31.0

Please provide any additional information below.
Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead 
jquery.min.js:1
http://localhost/cmgr/easyui/jquery.min.js is being assigned a //# 
sourceMappingURL, but already has one
not well-formed config-example.json:1
not well-formed en.json:1
syntax error windows.json:1
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. 
jquery.min.js:5

The current PaintWeb interface needs to look more modern. One approach to 
the modernization of the GUI is to have it animated with CSS 3 Animations.

At the moment, only Webkit implements CSS 3 Animations, nonetheless more 
Web browsers will implement them as well (soonish).

Ideally, the PaintWeb configuration file should provide an option for 
disabling animations (for performance reasons).

To ease the PaintWeb integration into other Web applications, it would be 
a good feature to allow developers to specify a form input element they 
want to replace.

Common WYSIWYG editors can replace an input (typically a textarea 
element). When the user submits the form, the input value is updated to 
hold the HTML of the article the user edited.

PaintWeb should be able to replace an input (typically an input of 
type=text). When the user submits the form, the input value is updated to 
hold the browser-generated data URL of the image the user drawn.

The implementation should allow developers to specify a form input by ID, 
by class names, or directly with a DOM object reference.

Investigate the possible use of WAI-ARI attributes to further improve the 
application accessibility.

Currently, PaintWeb does not allow users to accept the color change with 
the press of the Enter key when an input is focused.

Make sure that users can press Enter when any input field is focused, and 
that the action of the Enter key is the same as "accept color".

The color mixer extension needs further code cleanup, organization and 
overall code quality improvements.

Currently PaintWeb only allows users to resize the canvas using the south-
east resize handle.

Make sure that PaintWeb allows users to also resize the canvas using the 
bottom and right margins.

Currently, the main color mixer slider cannot be focused and users cannot 
change the slider value with the arrow keys.

Implement support for focusing the main color mixer slider with the 
keyboard, and allow users to change its value with the arrow keys.

Currently any configuration changes made within PaintWeb are lost when the 
Web application session is ended.

Implement an abstraction layer for persistent user configuration storage. 
Possible back-ends: cookies and HTML 5 localStorage.