Well, a lot has happened since the last progress update.
As you know from my other post I didn't work on the new designer for a while.
For the last few days I had been looking at my code trying to figure out where I left off, where I was headed, and why I was doing things the way I was doing them. This old brain don't work like it use to.
So, today I actually wrote some code that has to do with the scintilla editor windows.
Will elaborate more when I get enough of the new coding done.
LarryMc
With some ideas from Sapero (even though I decided not to use his specific suggestions - too much of a rewrite from what I can understand) I have finally established the code structure where I will have multiple code windows available for viewing under the code tab and using a tab control at the bottom of the window to select which to actually view.
This will allow the user to open non-project files to copy/look at code they want to use in the project.
This will also allow the find-in-files tab to display non-project file(s) and open them in the Designer code tab.
Since I am not using MDI windows the user will not be able to look at 2 files at the same time (like can be done in the IWBasic IDE).
Also, if the user closes the designer while multiple files (project and non-project) are open AND has the "Load Last files" option selected and the "load last project" set then all the files will be opened when the Designer is next opened.
LarryMc
Spent a bunch of time this weekend trying to come up with a new/semi-new set of toolbar/menu icons.
I'm not very artistic but am pretty happy with what I got so far.
Coverting the structure over to opening multiple files instead of only one is slow going. I'm trying to stay out of the mode of fixing one thing and breaking three others. -- Not totally successful in that respect.
The new version currently has 12,500 lines of code (some pulled in from the 1st version and some new).
LarryMc
In the code editor tab I have the subroutine window working that contains a list of all the subroutines in the project regardless of which source file they are in.
Clicking one of the subroutines will open the file (if is not all ready open); select the tab that contains the file; and scrolls to the selected subroutine.
The font parameters for the subroutine list is set with the same preferences used for the code window.
Attached are 3 screen shots;
one showing the look of the new dropdown menus
one showing the new layout of the form editor tab and
one showing the layout of the code editor tab
LarryMc
Ran into a little stumbling block.
The new version allows multiple source files to be open at one time. This forces me to change how modifications are saved.
This has blown my previous "save scheme" (which wasn't simple) out of the water.
The problem area is in the syncing of changes the program automatically makes in the code when the forms and/or messaging handlers and changes made by the user directly. Add to that the fact that the new version allows the user to open non-project source files and the need to save changes on an individual file basis instead of the collective way it is done in the current version of the designer.
If I made all changes permanent when they are made the solution becomes pretty simple.
But that is not the way things normally work.
Anyone have any thoughts?
LarryMc
Resolved my issues with managing the changes to multiple files of different types.
Took a lot of rework to my existing code.
For those that are interested, I've made a little crude movie of what it is looking like (in use) right now.
Click the link; open the zip; run the exe.
preview1.zip (http://www.ionicwind.com/images/preview1.zip)
LarryMc
As I had mentioned earlier, VD2 will not use the registry. I had been using my CXmlLM class to put everything in xml files.
What I discovered is that I don't need the sophitcated structure capabilities of XML to do what I need (along with the extra navigation code).
So, I have converted over to the INI file format. I created 4 very small routines to read/write numbers/strings. Makes it very easy to code. On average it reduces my xml code requirements by about 800%. Also retains the ability to view the configuration contents with a text editor (which some may ultimately find useful in the finished product).
This will also speed up my coding of the "meat" of the new version of the designer.
LarryMc
Been focusing on the ini files and preference GUI for the last couple of days.
One thing that I had added in my todo list was to add a separate menu item to just do a compile of the resource file.
The way EB/IWB acts now is that it recompiles the rc file first and then continues on compiling the rest of the source files even if there was an error in the rc compile. And it won't relink with that or any other fatal compile error.
With all the separate source files in the Designer it does take a while to go through them all.
A pain when trying to debug errors in a resource file.
In the finished product if there is an error in the resource compiler the error message will be display with a hot link to the bad line the way errors in source files work. Clicking on the hotlink will open the rc file in the code editor so it can be fixed directly.
LarryMc
Just about through with the editor preferences dialog.
It will have everything that the current Edit Options has in IWB/EB plus:
the option to have keywords as typed/all uppercase/all lowercase (like in the current designer)
a button to set the color of non project source files the user opens
a button to copy the setup from IWBasic entries (if it is installed)
a button to copy the setup from EBasic entries (if it is installed)
If they are not installed the corresponding button will be disabled.
Again, the designer itself doesn't use the registry to store its entries.
Screenshot attached.
LarryMc
Finished with editor preferences.
Default control parameters (w, h, fg, bg, font) restructured to use ini file instead of registry.
This new structure (internal) will facilitate the user being able to add and configure 22 custom controls at runtime.
22 is an arbitrary number that fits into my GUI nicely.
On my todo list is add the ability to save multiple copies of the control parameters so that they can be varied between different projects the user may be working on.
Attached is a screenshoot of the default basic control dialog.
LarryMc
Now there is a separate compile function just for resource files.
That way the user can compile a project's rc file immediately after editing the file without having to recompile the whole project.
If there are any errors the user can double click the error line msg in the compile output window and the code editor will open , open the rc file, and highlite the line containing the error.
The existing button that compiles everything and links to an executable will still be available.
Version 2.0 is now up to 15,600+ lines of code.
LarryMc
Designer 2.0 will not use the iwb or eb help folder to store help files.
Same as for not using bin folder to store addon tool files
Now, when you switch designer between IWB and EB the designer help file menu will pickup the help files from the selected compiler and add them to the designer's help file + the help files that have been added to the designer via the Help Menu Editor.
The Tool Menu Editor will now add the tool configuration files to the Designer's tool folder and will no longer clutter either the IWB or EB bin folder.
Adding menu items to the Tools or Help menus will no longer require a restart to pickup the new additions.
16,600+ lines of code
Added menu option to remove tools and remove help items. (Not yet coded)
Currently working on Find in File function.
Will be a dedicated tab window in the designer.
results window will hold results of multiple searches
user will be able to select lines to be removed from results while retaining others
user will be able to clear all results with one button click
double clicking a result will take user to code window and specific line in file
LarryMc
Just finished the FindInFile feature.
As it turns out I REALLY like the way it works.
Especially the fact that the output list can contain the results of mutiple searches.
16,900+ lines of code
LarryMc
With some code provided by Sapero as the basis I've started working on the debug functionality.
I'm breaking new ground for myself here so I don't know exactly what I'll wind up with right now.
LarryMc
after spending the last day and a half looking into thr dglhelp.dll api's I have determined the complexities are enough for me to put it on the shelf for now.
There are plenty of things left to do on ver 2.0 that I know how to code(and want to have completed for the release of ver 2.0).
My time will be better spent working on them.
And besides, the user will always be able to use the debugger in the IWB IDE.
So, the designer's version of the debugger will probably wind up as a free revision upgrade to 2.0.
So, right now my next coding task will be that of making the adjustment when a project is moved to a new folder.
LarryMc
Just finished the code to check if a project has been moved to a new folder and, if so, making the necessary adjustments.
I needed that functionality for the next step which is the Backup/Restore menu options.
An entire project folder with all files/sub folders can be backed up into a single compressed file.
The user will be able to restore the project to any empty folder of their choosing at a later date.
This feature is to allow (and encourage) the user to make regular backups during a projects development in case of a crash.
So, now I'm working on backup/restore.
17,100+ lines of IWB code.
LarryMc
Just finished the backup\restore functions.
When the user selects the backup option for the current project
dialog opens with default backup name which is project name +date
i.e. t21-2010-12-29
the default backup folder is shown - the user can use it or change it - it is stored in the ini file.
when ok is selected some verification is done - a sequence number is added to the backup name so multiple backups can be made on the same project on the same day.
the backup is made with a vdz extension.
When restore is selected a dialog appears
the user has to select a project vdz file to restore (the open file dialog defaults to the last folder a backup was stored in)
the user has to select a destination folder for the project
the folder request dialog defaults to the PARENT of the last restore destination folder (this is because a project requires an empty folder to start.
The user selects/creates an empty folder and then clicks OK
The project is restored including all nested sub-folders and files.
==========================================
Now starting on EXPORT function
This function will create a new copy of the current project and strip all the protected area markers ( '@@ along with any associated comments) from all the files.
The exported copy can be used to share code with others without the designer overhead. The resulting files can be recompiled in the IWB IDE but not in the designer. The original project files will remain unchanged.
17,400+ lines of IWB code.
LarryMc
Just finished the coding of the EXPORT function
Attached are before and after main source files.
LarryMc
Added an embedded color picker.
Must be noted it is based upon an original idea of Graham Sutton's.
Use sliders to adjust color bars above sliders.
The center shows combination of fg/bg colors.
click button to copy color (fg or bg) to clipboard in either format shown on buttons.
dbl-click colored bars above sliders to open system color dialog and select colors from there.
17,800+ lines of IWB code.
LarryMc
Completed the Help Menu item and Tools Menu item editors.
Adding a menu item to those two menus works pretty much as it did before.
However there is an option for each editor to remove a current menu item.
(Before you had to open windows explorer and do it manually)
18,000+ lines of IWB code.
Quote from: Larry McCaughn on January 05, 2011, 01:05:09 PM
Completed the Help Menu item and Tools Menu item editors.
Adding a menu item to those two menus works pretty much as it did before.
However there is an option for each editor to remove a current menu item.
(Before you had to open windows explorer and do it manually)
18,000+ lines of IWB code.
The whole thing is looking good Larry!
...you sir, are one very prolific code slinger.
-Doc-
Completed the incorporation of the menu editor as a dialog.
Works like previous version with the added ability to import menus into project from other projects.
This feature will allow user to build one or more skeleton menus to be used in multiple projects.
19,100+ lines of IWB code.
LarryMc
Completed the incorporation of the resource editor as a dialog.
Works like previous version .
20,200+ lines of IWB code.
LarryMc
For those that care:
Just wanted to note that I haven't worked at all on the designer for the last few days.
I've been spending my time working on help files for IWBasic 2.0. Seems the previous owner did not furnish the ACTUAL files to recreate the help files. Reverse engineering and reconstructing is a little bit time consuming.
As soon as I'm through helping LarryS with this I will be back on my Designer.
LarryMc
Still working on docs for IWB 2.0.
LarryMc
I finally finished the Help files for IWB 2.0 that I've been working on since mid Jan.
I've got to do some personal things I've put off (like income taxes) but I should be back working on the Designer before the end of the week.
Just as it did after my daughter's passing it will take me a while to get back up to speed.
I will also need to make some changes to reflect changes made in IWB 2.0.
LarryMc
Actually got to do some coding today. Felt good.
Working on the Toolbar editor.
21,800+ lines of code
LarryMc
All the editors are now dialogs instead of tabs on the main window.
Been working on the menu editor.
The preview of the actual menu at the top of the screen is now more dynamic.
As changes are made to the treeview(and in the edit fields to the right) the preview is automatically updated.
At any time the user may expand the menus in the preview to see what they will look like in the final application.
A screenshot of that expansion is shown below.
23,000+ lines of code
Probably 95% complete on the new versions of the menu, toolbar, and tab editors.
That leaves the custom control editor ( I'm putting off a new Messagebox editor and About Box editor until the very last or possibly as a later revision.)
Decided to change the area I'm working in for a while.
Got the dialog completed for changing project options after a project is created.
Looks almost identical to IDE menu Project/Options (although there will be some options that I will not allow to be changed due to the structure of the designer.)
Now working on the code for getting those option changes to the compiler/linker.
23,400+ lines of code
LarryMc
I wonder how many likes of code this would have taken in C++ or other languages ;)
Quote from: Blue Steel on March 22, 2011, 02:34:52 AM
I wonder how many likes of code this would have taken in C++ or other languages ;)
From what I have seen (I don't like the cryptic nature of C-type languages) if would have taken 3-4 times as much code.
If it was left to me to write it in a non-BASIC type language it would never have been started.
LarryMc
completed the code for modifying project options after a project is created.
Will now go back to the code editor preferences and modify to support preprocessor color choice.
Also did some temp code cleanup resulting in an overall change of about -50 lines.
LarryMc
Now starting on option that allows user to add an existing iwb file containing common support routines that a user may use from project to project.
Will keep the user from having to create a non-form code file, opening the file with the common code, copying the code and pasting into the new non-form file(which is the currently available method.)
LarryMc
*iwb and *.eba non project files can now be added to an existing designer project.
Now will look into adding *.o,*.obj,*.lib, and *.asm files to existing project.
LarryMc
Well, I guess I'm over my 'bad hair' day. ::)
It seems I can't NOT work on the designer; I enjoy it too much. :o :o
Also, I think there are aspects of it that, in my opinion, are just too neat to not finish it. ;D
Besides, I always have the option to NOT sell it to anyone I choose (although I would hate to do that.)
So, for those who care, it is back in development. ;D
BTW, thanks for all the kind words, both public and private. :) :)
LarryMc
and don't forget those of us who understand and kept quiet, not pushing you in any direction ;)
I for one knew it would be hard for you to give up on your baby ;) I knew you'd be back working on it sometime .. lol
;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
Thanks guys.
LarryMc
Well, after all the hacking we've lost a couple of updates.
I've completed all the coding for adding an existing iwb file to an existing project.
This is intended to allow a user to have a source file that contains subroutines they like to use from project to project and easily add that file to a new project.
I've also completed the code that allows a user to add .o, .obj, .asm, and .lib files to an existing project for the same reason.
In all cases, a copy is made of the file to be added(regardless of where it is located) and placed in the current project's folder. That's to facilitate backup and restore functions.
Currently working on the message handler dialog.
The goal is to allow the user to add new custom messages (or existing MS messages that have not been incorporated into IWBasic) to each of the object types (windows,dialogs,and each of the control types). The user will also enter the root message handler name for the added message. The assigned value will be automatically assigned for custom messages and for added MS messages the user will enter the value.
This code will allow a user to add all desired messages when adding a custom control of their design.
When I have finished this module I will use similiar coding for adding custom styles.
23,830+ lines of code currently
LarryMc
Just completed the code for adding user defined messages/notifications to windows/controls.
Automatically adds SETID definitions and OnMsg/OnControl definitions and subroutines.
Will now start working same scheme for user defined styles.
23,900+ lines of code
LarryMc
Finished code for adding/deleting custom styles.
Required a lot of double checking to prevent duplicate definition errors with different values.
24,760+ lines of code
I think I'll change pace a little bit and now work on the MessageBox Editor tool I've had in mind to add for a while now.
LarryMc
I've got the GUI portion of my messagebox tool worked out.
Now to write the code generation part.
It will take care of 'IF' structure if the user picks a 2 button option and a SELECT/CASE stucture if a 3 button option is selected.
### will be used to identify a placehokder for the user to insert any desired variable (I'll take care of the "+ and +" around it.
The user may enter multiple lines of text and that number of lines will appear in the generated code.
When the save button is pressed the generated code will be copied to the clipboard.
The user can then move to the desired location in a source file and ctrl-v or right-click paste the code into their program.
LarryMc
Finished the MessageBox Builder tool.
I added a preview so that the user can see how the spacing will look.
mb1.jpg shows where I created a button for testing on a form.
It also shows the MB Builder open and my desired entries.
mb2.jpg shows the result of pressing the "preview"button in the builder.
This is exactly as it will appear in the final application.
If I like the result then I click save to save the generated code to the clipboard.
mb3.jpg shows the button click routine I added when I added the test button to the form.
To add the code I place the mouse caret at the beginning of the line I want the code to precede.
In this case the line with Return FALSE in it.
I either ctrl-v or right-click/paste to insert the code.
mb4.jpg shows the result of the pasting; ready for the user to enter their custom coding.
NOTE: If you use the buider more than once in a sub or at the local global level you will have to delete the int declaration for some of the msgret variable; or after you paste it you can change it to whatever varaiable name you want.
25,000+ lines of code.
Now I've got to figure out what to work on next.
LarryMc
Just finished the dialog/window for adding up to 22 custom controls configurations to the designer.
Also finished the page that allows the user to configure the default size, color, and fonts for any added custom controls.
Note: I must admit that my messagebox builder worked great while adding the error checking to the above two pages. ;D ;D
Now comes the tougher part; integrating the new controls into the overall drag and drop scheme along with the existing controls' code generation scheme.
When I get through with that then I will start cleanup (making sure I've gotten rid of all registery references and have then in ini files; working on the installer; and the required rework of the help file. Almost forgot, I still have some custom images to build for the designers menus.
"All I like is finishing..." ;)
Lines of code - 26,600+
Completed the code to support integration of a custom control into the designer.
There are slots available for 22 user defined custom controls.
While checking my ToDo list I noticed I haven't adopted the code for find first, next,last and previous. Nor have I adopted the code for "find in help"
So I'll be working on those two "search" related modules now.
Lines of code - 27,300+
LarryMc
Completed the code for find, find first, find next, find last and find previous while viewing a source file.
LarryMc
Completed the code for "find in help" which will search for a keyword in all the help files in the iwbdev/help folder.
Lines of code - 27,600+
LarryMc
Decided to work on menu icons for a while.
Got 13 more added.
LarryMc
Finished with what I'm doing with the menu icons for the designer itself; 47 icons in all
Got the skelton of the new helpfile about 60% set up.
ALL the screen shots that were in the old help file are outdated now so I have a lot of screen capturing to do. That's why it was necessary to get the menu icons done.
Most of the existing verbage in the old help file is reuseable but there is a lot that needs to be added.
As I go through redoing each section in the help file I will be testing everything I put in writing.
So, I'll be doing cleanup/bug fixing along the way.
LarryMc
Completed the code to allow the user to attach a browser to a window in the properties window.
Added the browser messages to the default set for windows.
Completed the code to allow the user to select an icon for a window/dialog.
Fixed a major flaw in how I was creating global variables.
Only 2 more items on my bugs liist that have to be done before a pssible release.
(I may find more when I start on the help file)
Lines of code - 27,790+
Larry:
Quick question. I have your initial version of Visual Designer from the old EBasic days. I'd like to upgrade to the current IWBasic version.
Is the IWBasic version a complete new purchase or is there an upgrade path from the older version?
Also, on the Ionic Wind website, is the version of Visual Designer being offered there the latest version? And do we download bug-fixed updates from that location and install or would we get current updates from somewhere else?
Thanks,
Logman
The "current" version of the Visual Designer as advertised on the main site pages is for IWBasic 1.8 / EBasic 1.737 and is not compatible with IWBasic 2.x.
Most people that currently have the Visual Designer did not pay me for it. It was given to them free because I felt bad that they had given the previous owner "up-front" money and never got what they thought they paid for.
Obviously, those people are not getting any sort of " deal" when I release the Designer for IWB 2.x.
For those that purchased the current designer this disclaimer was/is right above the purchase button:
QuoteNOTICE: This version will be updated only for bug fixes; there will be no new features added. Purchase of this version does not come with any entitlement/discount toward the release of Visual Designer for IWBasic II (scheduled for 1st Qtr 2011)..
So, to answer your question directly, their will be NO "DEALS" when I release the new version (with all the new features) specifically for IWB 2.x .
Also, back when I was in the middle of writing the current Designer, I got to a point that I knew I needed to backup and make structural changes in order to implement all the features I had in mind. I polled the interested parties at the time and no one wanted me to backup. All wanted me to keep going and get the designer released.
As a result, the new designer, when released, will not be backward compatible with projects created with the current version. There isn't a large enough user base to warrant all the extra effort.
LarryMc
Larry:
That's what I wanted to know. There will be a version compatable with IWBasic 2.0 and it will be coming soon.
That is the version I'll need.
Thanks,
Logman
A mini announcement of sorts.
The new name for the visual designer for IWBasic 2.x will be.....
drumroll.................
IWB+
below is the simple logo I'm going to use
(In the next day or so I will move this topic to a new, IWB+ board here)
LarryMc
I like it!
Larry
Will almost be worth the price just for the new logo! ;D ;D ;D ;D
You have chosen wisely. :) :) :)
Bill
Got a little bit of work done on the help file.
While doing that I discovered some program flaws.
In the course of fixing those I discovered several flaws with the inner action between the compiler and the debugger.
Sapero, in his usual fashion, knocked out the fixes pretty quickly.
However, being 1/2 way around the world from each other there is a lag in the process.
Plus my naps have to be tossed in there.
I'm actually working on adding two small features due to our recent debug efforts.
My compiler/linker output page has always had the feature of clicking on an error line and the designer going to the code with the error.
But it was missing a way to copy the text to the clipboard like can be done in the IDE; nor was there a means to print it out.
So, I've added a toolbar to the output window with a button for copying and one for printing.
I'm now starting on the code for my scheme to accomplish that.
When I get through with this I'll be back on the help file.
LarryMc
Well, that was quick. Finished that in less that 50 minutes. Was easier that I thought it was going to be.
Okay, tomorrow I get a fresh start back on the help file.
LarryMc
Just had another 'feature' idea.
It comes from what I setup and use for the designer itself.
Under the Project menu I'm going to add a 'To-Do' List option .
Selecting the menu option will open a text file for the user to use to keep track of things that need to be done.
Each project will have it's own todo file created automatically when the project is created.
Based upon how easy the last feature was to add I should be able to finish this off today without any problem.
LarryMc
It's amazing how many little things you can find wrong with a complex program when you start writing a detailed help file for it.
Nothing serious but just little things that don't work quite like I intended. :D
How long before I'm finished....Let's see......This is ..... 2011. ;D
LarryMc
It appears I've taken a step backwards. I was working on the part of the help file that describes adding child windows and dialogs. I hadn't visited this specific area of IWB+ in some time.
It generates the correct code but the working display of the forms is all haywire. I have no idea right now of what I did to screw it up so bad; therefore I have no idea how long it is going to take me to figure it out.
I think I've created a monster that has it in for me! ;)
LarryMc
Well, what appeared as a real mess at first glance turned out to not be quite so bad.
I focused on one and only one issue at a time and wound up fixing 6 distinct issues and now everything appears to be back to normal.
So, back to the help file.
LarryMc
Well, it's been a while since I've posted anything in this section.
Since I have finished the first pass of the help file I thought I would work on the installer for a while.
It's almost scary that I can see the light at the end of the tunnel.
I just hope it's not a train! :D
LarryMc
I am sorry, due to the current political climate, the light at the end of the tunnel has been temporarily turned off. Please continue on carefully and remember, those who are in the government are here to help....... ;D ;) ;D
Bill
or Obama gave the light to the unions as part of the stimulus. :o
are more likely is was taken away by the healthcare bill that Pelosi pushed through that noone read. :'(
LarryMc
On a more serious note I have finished the installer and successfully installed it on my computer.
I will now give it to two other individuals to playwith/test while I install it on my wife's laptop (when she isn't looking).
I also need to go through doing everything with it (on her laptop) just to make sure everything works on a pc other than mine.
I will also start working on the announcement for the forums and the update for the main web pages.
And I've got the 1st part of my pricing plan resolved but still haven't decided on the 2nd part.
"The future price will be $1,799.95 (or up) "<-------1st part :o
but "If you hurry, you can buy it in my lifetime for only $xx.xx " <------2nd part
;D ;D
That kind of marketing works for other people, why not me.
;D ;D
LarryMc
Larry..
QuoteAnd I've got the 1st part of my pricing plan resolved but still haven't decided on the 2nd part.
"The future price will be $1,799.95 (or up) "<-------1st part Shocked
but "If you hurry, you can buy it in my lifetime for only $xx.xx " <------2nd part
Sounds about right, to me..
Well, I putting the finishing touches on everything. I expect to release IWB+ before the end of next week.
LarryMc
BTW, I've decided on a price, $39.95 USD.
No special sales, no discounts, no trading for livestock.
$39.95 period.
Based upon what people paid in the past for pre-release software I feel that is an extremely fair price, especially considering all the time saving features it has.
Of course, there will always be those who disagree.
LarryMc
yep - i realised my mistake after i posted :)
it would have been much clearer if maybe the name decided on had been IWBD+ instead ;)
Me and Larry thought it was pretty clear, IWBasic and IWB+.
I had the little contest way back when I was early in the building of it.
Had a few entries but lost all of them when the site was hacked.
I posted again but got no takers(that were appropriate.
Anyway, it won't be hard to get use to. ;)
LarryMc
While using IWB+ to buid the dialogs for the IWMenuBar app I discovered a bug in how the style flags were being automatically added/deleted. Easy to fix once I found exactly where the code was wrong.
LarryMc
Larry M.:
The price is right, but in light of the Norton 5.0 update, does your IWB+ use the same software anti-piracy protection as IWBasic 2.0? If so, it will not run on the systems I use because of Norton running on Windows 7 platforms (nothing I can do about Norton--I'm stuck with it at all my client locations).
If this is not an issue, then I'm in.
Logman :)
Quote from: Logman on July 06, 2011, 06:35:49 AM
The price is right, but in light of the Norton 5.0 update, does your IWB+ use the same software anti-piracy protection as IWBasic 2.0?
No, it is not the same protection scheme.
To be honest, I had purchased the same protection package as LarryS (before I knew he was going to use it). It looked good on paper. But, based upon the various issues that arose with it I abandoned that notion pretty quick. You should have have no anti-piracy protection issues with IWB+ when I release it.
LarryMc
LarryMc:
That's great news. On that basis I'm looking forward to the release.
Thanks,
Logman :)
While making revisions for new features a User expressed a desire to install IWB+ on a memory stick so that it could be run on any available computer. The current code and the installer don't properly support that. Also, the current code and installer don't support IWBasic 2.5's non-use of the registry.
This is going to cause a delay in the new release of IWB+. I'm almost through with updating the help file for the current revisions.
When I finish that I will make the necessary revisions to the IWB+ code and its installer to support installing on a memory stick and for use with IWB2.5.
All this will just be a free upgrade.
The same sort of revisions will be made to the Chart Designer, Button Designer, and the rest of my creations in the future.
I'm currently making modifications to both the IWB+ and its installer.
As a memory jogger:
IWB+ was written for use with IWBasic 2.0
IWBasic 2.0 uses the registry and IWB+ looks in the registry to locate IWBasic's compiler when the User selects a compile function.
IWBasic2.5 doesn't use the registry therefore the User will have to tell IWB+ where the compiler is located.
My other creations (Chart Designer, Button Designer, etc) are setup the same way.
I was going to try to do everything I needed to do in one installer.
Having an installer that asks questions during the install process and reconfigures itself based upon the User's responses is rather complicated. I spent a couple of months on the one for the IWBasic2.5 beta version. And since I don't build installers all the time I have to relearn the installer commands and coding almost from scratch.
I decided that to do that for all my creations was going to be a mess I really didn't won't to deal with.
So, eventually, all my install packages will come with two installers;
one for installing in the Program Files folder(with the restrictions that are placed on it that forces the scattering of bits and pieces of the apps around the computer):
and one I call the "memory stick" version (which basically allows everything to be in one place; either on an actual memory stick or a single folder on the hard disk other than ProgramFiles.
To support the installation on an actual memory stick I'm going to read the serial number of the C drive hard disk and store that in the ini file so I can do a comparison to see if a memory stick is in a different computer than the last time IWB+ was run. I will also see if any of the stored paths have changed and/or exist and adjust as necessary.
I will also store the compiler location . If the stored path for the compiler is no longer there I'll open a dialog to let the User tell me if they want to forget the compiler, use the pre iwbasic2.5 version (which I can find in the registry) or the IWB2.5 version (which the User will have to tell me where it is installed since it doesn't use the registry.)
When everything gets done you'll be able to put IWBasic2.5 and all my creations on a single memory stick and carry it anywhere.
Finished the significant modification to enable IWB+ to have dual installers and support both IWBasic 2.0 and 2.5.
Now starting the update of the IWB+ help file to reflect changes.
New version will be released when I get through with help file.