Witango-Talk: [Suggestions] Witango environment evolutions? [1/????]

[[Gauthier]]

Hi, it's a suggestion list I'm currently compiling as soon as an idea come to me since a week   here is some of the elements that I need to maintain a updatable list of feature/bugs at anytime anywhere: Separation between: EDITOR | SERVER | MELTED each of these section will contain a bunch of titled section that will contain     -an introduction paragraph     Separation between: Bugs-Correction | Features     there is also a level: (Doable|DreamUp) for each suggestion currently depending on my understanding of how the things actually work or not     a to be continued state   for the moment all these stuffs are hand-writed, and if anyone have still a system to share that will help me to manage all of this will be helpfull (an HTML|XML predefined structure will be a first step), so if anyone has currently a such system or idea to order all these raw listed features   Waiting for another way of work I will surely start from txt's stored in a dir structure waiting to have the XML/XSL knwoledge or the help from this communauty (if there is some people that think it will be valueable to maintain a such document for the product)     One thing is clear: I can't continue further if I don't have any storing/updating tools/format ;)   so let's begin   Begin ############################################################ � 1 EDITOR -CustomTags   -PropertyWindow   The property windows should be improved, the more I use it the more I think it's the best Development-Aid tools, and it's far away from availability into 'text-only' language   Bugs Correction � MultipleScreen bug <#PropertyWindow OnMove="if(this.left<0 OR this.top<0){STOPDRAGING}"> Remove the 'multiple screen' bug         Easyness:don't know really but it seems easy         Platform: Win32.         user-range:sensibly increasing ;)         A hint to correct the bug is to allow the property window top and left property to move into negative values   New Features � Resisable/Dockable PropertyWindow     Let us resize and dock this window, Since a recent time i didn't use it often, but now I'm working on bigger project -WorkSpace   New Features � Automated Temporary SNIPPET's (constantely generated from the opened action/files) � Object Workspace Drag n Drop     drag a method property should put <@VAR Method$ParamName> exactly as a snippet work � Get the comments of the methods and method params in the PropertyWindow -ActionView New Features � enlarge the comment column height of the selected action <PICTURE> [ToBeContinued] -Query The Query editor (double click on a 'DirectDBMS' action) can be improved: [ToBeContinued]   New Features -ResultTextEdit New Features     SCOTT CADILLAC or any other XML analyst SHOULD READ AND APPROVE IF the use of the definition file will help the new features integration to the editor, if so the most important is to design the editor accessors to these properties if some are missing (I didn't have any idea)   the things that have to be achived that dertermine the future features doability/availability -the ability to intropect the metatags attributes from witango.dtd will allow to implement editing features easily than without -The ability to introspect the tags attributes from standards XHTML,HTML definition (there is dtd definition for these standards if I'm rigth)     Many features are implementable if you have permanently the needed tags definition in memory when a result window is open....       perhaps translating current DTD into XML schema format     I'm currently just understanding that XSL should do the best work to populate each tags/metatags attribute(name/type) properties from an available XML Schema definition into the way the editor manage all his internal objects.   -The possibility to have collapsable region for all the metatag markup/code (that could be stored in the file) should be wonderfull, by default an auto collapser will collapse some of the main metatags pair -The possiblilty to have """"""""""""""""""""" """"""""""" (HTML/XHTML/XML/WML/ restof the world...) markup , by default an auto collapser will collapse some of the main tags pair     -Actions editing Bugs Correction �Parameters screwing <#CallMethodAction OnDragMethod="this.ParametersScrewing(randomparams)">         Easyness:don't know really but it seems easy         Platform: Win32.         user-range:Gigantic     Don't screwup the parameters when you just have modified the method definition and you redrag the method from the workspace on the ActionDialogWindow     It should at least         -let all the old Param/Value couple in a temporary section of the ActionDialogWindow         -Reassign all the value correctly with the params that are still named as before   New Features � ASSIGN Action     It will be cool if the assign action have a better representation: <PICTURE> -Preview Window reformulated from Daniel Richardy: A great idea will be to have an "integrated explorer" that will constantly show the result action that you are editing or the current application file process     DREAM UP ;) -Auto Documentation Surely an amazing feature for a such tool! A complete report (XHTML seems to be the best option) should be generated from a whole project or a selected item (Application file, ClassFile, Action...) a such report should contain:   � Array of variables used:     line: action name     row: variable name (order by Scope, Name) -Better TCF Methods integration �customisable CallMethod Action Icons     this will let us identifiate the called method quicly (because I always rename my actions and all the methods look like others methods) �customisable CallMethod Action Dialog box (doubleclick on action)     let us define the frontend of our MethodCall Action (perhaps as an HTML layout or a such thing) so our MethodCall actions can reach a high level of integration in big application (as a normal action) -Network file editing   all these suggestion require a pseudo WitangoDevServer part, so that is not for the moment ;)   �Allow multiple developers working on same file     The action should display as readonly mode when it's still open in another developer editor   � 2 SERVER   -Application Scope BUG take account of the domain avoiding screw of all applications that have a PATH=/ or that live in the same directory on multiples domains [ToBeContinued]       -Email Action � 32k Custom Header limit     Break this limit, so we can generate our mail entirely   -Integrate a "runtime-only" WebServer Reformulated from Daniel Richardy � have a runtime exe that will act as a WebServer and allow us to use taf without any installation on any computer, that will allow us to bundle Witango application on our CD-rom ... � The solution for the database will to have a "runtime only" odbc connexion from a stored file (Access/Rbase/XML...)   (I Just discover that some junks have implemented a small database support (table, query, view...) only with 'flatty' XML files that store the datas and that seems to work well for small ammounts of datas...)     � 3 MELTED -Action management � Break the 31 chars ActionName limit     TEXT EDIT: MetaTags surely rely on a specification available in the dtd that define each action/metatags structure and parameters type, so there is amazing possibilities allowing the editor to have a property inspector when a metatag is highlighted. and such wonderfull things in the developer life...     ########################################### END for the moment   Hopefully I wasn't at the vapourware session,if it was the case all the Witango developers will suddenly have the envy to kill me or keep me silent ;)))) So I'm in a healthy place away from any 'direct' reprisals ;)   Gauthier   PS:   -A big scuse for any redundance, I've edited this file in various condition (really tired, after reflexion pause, just wake, etc...) -please give feedback on parts that currently seems interesting. -If there is feedback, the most advanced XML analyst will really help me defining the way to store/edit all theses suggestion for the product and helping to implement it -I'm scarry that the v5 will have a grow effect on my ideas... -The masters of 'next version features implementation' are currently Sawmill (www.flowerfire.com) and TopStyle (www.bradsoft.com) they have dedicated 'features suggestion' forums/newsgroup, even if possible for small products, they have not a such tool as Witango to maintain/manage/analyze/develop/promote but I think that an implied user/developers communauty will help WithEnterprise and Witango (so all the current users) to have a brighter than bright future, by showing that a strenght communauty will manage almost anything if the product developers take the goods orientation for the product (that a thing that I'm sure) -Scuse me if there is bad formulation, misunderstanding, familiarity that will hurt anyone: really not my intention... -Sorry for the UGLY scheme, I wait any suggestion on how to manage all of this ;) -Sorry for the unfinished parts or just titled parts, I've to send the post now before going further... -I've sometimes used two terms that mean sensibly the same thing to enable (I hope) a better understanding -THANKS If you have read and try to understand until this last byte!!!!   EOF