IDE project (fenics's Worklog)
an ide obviously 
feature requests?
Not a whole lot changed except for some bug fixes and the implementation of my tab control
http://www.pirate-sheep.com/whisker-0.3.7.rar
Not sure what to do next. Yeah, there are a lot of things a fenix IDE could have but I don't want to go overboard and add unneeded features that make it too bloated.
http://www.pirate-sheep.com/whisker-0.3.7.rar
Not sure what to do next. Yeah, there are a lot of things a fenix IDE could have but I don't want to go overboard and add unneeded features that make it too bloated.
(Posted on April, 13th 2008, 14:26)
Comments
Rincewind said:
"Run-time error '5': Invalid procedure call or argument"
As for features these are a must: the ability to set the font, font size, line height, user-defined hotkeys, the ability to close/open the side bars, a stay-on-top feature like in Context that makes the window sticky (works great against the windows sidebar popping up when I'm too close with my mouse).
As for features these are a must: the ability to set the font, font size, line height, user-defined hotkeys, the ability to close/open the side bars, a stay-on-top feature like in Context that makes the window sticky (works great against the windows sidebar popping up when I'm too close with my mouse).
(Posted on April, 13th 2008, 15:11)
Sandman said:
Like I mentioned in IRC the other day: adding of external tools, so you can run an exe or batch file with or without parameters. And these parameters should also be able to have a few keywords, like %dcb for the dcb filename (see ConTEXT for some good examples)
A way of implementing the external tools: have a menuitem 'tools' (like File) in which one can add items (like New or Open in the menu File) which can be activated. A nice way of making hotkeys is to be able to bind them to menu items and then the tools are automatically hotkeyable as well.
Also the ability to add include directories (-i parameter for fxc). Actually you should throw in all the parameters of the fxc and fxi in GUI form and for some, like -i, it should be possible to specify multiple. These settings are global and projectonly. So if there is no project or the project doesn't have the settings, the global ones are used.
A way of implementing the external tools: have a menuitem 'tools' (like File) in which one can add items (like New or Open in the menu File) which can be activated. A nice way of making hotkeys is to be able to bind them to menu items and then the tools are automatically hotkeyable as well.
Also the ability to add include directories (-i parameter for fxc). Actually you should throw in all the parameters of the fxc and fxi in GUI form and for some, like -i, it should be possible to specify multiple. These settings are global and projectonly. So if there is no project or the project doesn't have the settings, the global ones are used.
(Posted on April, 13th 2008, 17:30)
fenics said:
allright, you can now add tools to the menu, which is structured like
Add tool...
-----------
tool 1
tool 2
etc. keywords at the moment are %dcb, %active (the active file), %project (project path)
just need to find a way to save them. I also think a checkbox might be a good idea to let it display the console output of the executed tool , if any.
Add tool...
-----------
tool 1
tool 2
etc. keywords at the moment are %dcb, %active (the active file), %project (project path)
just need to find a way to save them. I also think a checkbox might be a good idea to let it display the console output of the executed tool , if any.
(Posted on April, 14th 2008, 14:28)
fenics said:
alright, output from tools is not shown in the debug window :X
(Posted on April, 14th 2008, 15:02)
fenics said:
When I"m done moving a lot of code around to improve readability and when I'm done making sure it reads settings (recent files and tools) from an xml file instead of a .ini file again.
(Posted on April, 17th 2008, 12:35)