Forum > Neo

Neo - A WoW Development Suite

<< < (21/81) > >>

majorcyto:
Hmm, i can't remember where i read about the 6 texture layer thing either though so for the sake of it unless someone else can confirm lets just discredit my statement and assume its 4 still lol.

Glad to hear about the other options, i actually have a Surface Pro 3 as well that comes with the N-Trig pen (very similar to Wacom) and i would love to be able to use it to "paint" textures. The SP3 supports most of the Pen API's as far as i know except for Wacom specific ones.

Edit - The team functions would be very much welcome!

Steff:
I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.

majorcyto:

--- Quote from: "Steff" ---I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.
--- End quote ---

Ok, that sounds good! The Surface Pro 3 pen actually has 2 triggers on the pen itself that can be used, and I know the Wacom pens usually have at least 2 as well, so there might be a way to implement for instance raise and lower into the triggers of the pens themselves, Of course this could be done at a later time and wouldn't need to be researched right away.

The main thing is to have a UI format that's easy to use with a mouse, or a drawing pen. (Or implement a second UI mode in the settings for pen mode.) One thing you might want to look into is the general WinTab API the drivers are available on the surface series, and I think Wacom as a generate interface for pens. You can do some special detection methods, such as for instance.. when the pen is being used on the screen ignore the palm/hand input. So you can use the pen across the screen without accidently activating other buttons.

Anyways some of these things are kinda more specialized and I would understand if they weren't looked at or implemented I am just throwing the ideas out there in general. General Pen Support would be just as nice.

------

Going back to team features for a minute, it would be cool if we could some how have synced multi-map editing. All though the logistics of making sure the map chunks don't corrupt between the wow edit clients would be problematic, just the locking of the map at least (and showing it locked) would for sure be a massive helpful feature. But I have seen a few editors allow up to 8 people to edit or change the same map. But then you would have to have something like a sync-server that the user would need to run for their team to make sure the data and editor positions stay up to date.

Anyways, just talking at this point. I haven't actually used the NEO WoW Edit tool on my surface pro 3 yet, only on my beefy desktop I will download VS 2015 today on my Surface and try it out and let you know its performance. It will probably be fine though.

Keep up the good work.  :D

Kaev:

--- Quote from: "majorcyto" ---
--- Quote from: "Steff" ---I have 2 days time this weekend and will get a gfx tablet tomorrow. So i can implement my basic UI ideas and try if all also fits to tablet input.

First I will implement the basic project managment parts. To open a new project, load one. Implement the application settings and the file and project view. Then integrate the map editor as first possible editor.

The editing of ground has only rais up implemented jet. So lower simple dont work. In the moment the main focus ist planing how all should work out and cromon gives 200% to implement all the wow data stuff and rendering properly.
--- End quote ---

Ok, that sounds good! The Surface Pro 3 pen actually has 2 triggers on the pen itself that can be used, and I know the Wacom pens usually have at least 2 as well, so there might be a way to implement for instance raise and lower into the triggers of the pens themselves, Of course this could be done at a later time and wouldn't need to be researched right away.

The main thing is to have a UI format that's easy to use with a mouse, or a drawing pen. (Or implement a second UI mode in the settings for pen mode.) One thing you might want to look into is the general WinTab API the drivers are available on the surface series, and I think Wacom as a generate interface for pens. You can do some special detection methods, such as for instance.. when the pen is being used on the screen ignore the palm/hand input. So you can use the pen across the screen without accidently activating other buttons.

Anyways some of these things are kinda more specialized and I would understand if they weren't looked at or implemented I am just throwing the ideas out there in general. General Pen Support would be just as nice.

------

Going back to team features for a minute, it would be cool if we could some how have synced multi-map editing. All though the logistics of making sure the map chunks don't corrupt between the wow edit clients would be problematic, just the locking of the map at least (and showing it locked) would for sure be a massive helpful feature. But I have seen a few editors allow up to 8 people to edit or change the same map. But then you would have to have something like a sync-server that the user would need to run for their team to make sure the data and editor positions stay up to date.

Anyways, just talking at this point. I haven't actually used the NEO WoW Edit tool on my surface pro 3 yet, only on my beefy desktop I will download VS 2015 today on my Surface and try it out and let you know its performance. It will probably be fine though.

Keep up the good work.  :D
--- End quote ---
Don't forget that you don't need VS 2015 anymore. 2013 will work too. :P

stoneharry:
Just compiled it to take a look at it, my thoughts:


* The text on the left tabs looks blurred (see here: http://i.imgur.com/4K6R5ip.png )
* The text on the welcome screen should be in column(s), not wide screen. It is very hard to read text that goes across the entire screen.
* If you close the tabs on the left by opening them then pressing the 'x', I could not see a way to bring them back without restarting the app.
* When I pressed on Scott Test the program became very slow, almost not responding, and tested all ADTs. This should not happen, some sort of verification to see if this will happen and warn the user and say do they want to proceed, or something.
* Loading screen was very nice, making it fit the full window would be better.
* The default key bindings are intuitive. I didn't need to look them up.
* Holding down some key to move faster would be nice.
* Square brush or circle brush would be handy (I don't know if this is how they do post-wotlk mountains).
* Tooltips on the different algorithm types would be handy.
* The title of the application needs to be updated from WoWDev to Neo.
* There is no way to return to map selection.
* The icon for each map should be it's minimap if feasible.
I realise this is still early stages but these were my initial thoughts.

Navigation

[0] Message Index

[#] Next page

[*] Previous page