Friday, May 14, 2010
CodeAssistor version 0-0-2
CodeAssistor version 0.0.2 has been released. This version includes CODE-FOLDING (wohoo!) and GOTOLINE functionality.
Sunday, May 9, 2010
CodeAssistor listed on the Scintilla "Related Projects" site
Neil has put the CodeAssistor onto his list of projects related to Scintilla
Happy Day!
http://www.scintilla.org/ScintillaRelated.html
Happy Day!
http://www.scintilla.org/ScintillaRelated.html
CodeAssistor once again compiles against vanilla Scintilla-Cocoa
Mike Lishke has merged all of my changes (mullinpatches/mousewheel/makefilework) into the trunk of Scintilla-Cocoa. Version 66 of CodeAssistor will compile against Version 34 of Scintilla-Cocoa (lp:scintilla-cocoa).
Mike Lishke has also merged in all of Neil Hodgson's main scintilla changes + added some helper functions in the ScintillaView for Font changing and Text searching.
Looks like a good day as far as Scintilla-Cocoa goes :)
Mike Lishke has also merged in all of Neil Hodgson's main scintilla changes + added some helper functions in the ScintillaView for Font changing and Text searching.
Looks like a good day as far as Scintilla-Cocoa goes :)
Saturday, May 8, 2010
Goto Line added to CodeAssistor
Hmmm... so thats why you do requirements analysis, because if you dont, you forget an important feature (like find... or like line-goto).
Im lucky this time. I was able to "tack on" Finding and line-goto w/o much hassle (its a homework task for my readers to see if my design could have been better if I had remembered these tasks).
Anyways. CodeAssistor now has the ability to Goto lines (CMD-G). interestingly I had to add an "owner" property to the upstream ScintillaView class. I had to add this so that Scintilla notifications would be percolated all the way up to the NSDocument (or NSObject if a Single document model is used) that controls the ScintillaView. I did this so that I could hide the Finder/Goto TextEdits when the ScintillaView regains focus.
Because of this change, revision 66 (and onwards) of CodeAssistor now _requires_ my mullinpatches (lp:~masmullin/scintilla-cocoa/mullinpatches) and will no longer compile against vanilla Scintilla-Cocoa. Previous to this, Vanilla Scintilla-Cocoa could have makefiles hacked up (my mullinpatches has some changes to the vanilla makefiles-which I supplied in the first place anyway) and work properly with CodeAssistor, Although I've fixed a few bugs in Scintilla-Cocoa that MikeLischke hasn't integrated yet, so you would want to use mullinpatches anyways.
The amount of divergence mullinpatches is from vanilla Scintilla-Cocoa is starting to worry me. Right now, I think it's still possible to do a pretty clean merge of mullinpatches onto vanilla since vanilla is static, but if other developers start fixing bugs on vanilla Im going to have an additional chore of updating my mullinpatches.
Not only that, but Im concerned that Scintilla-Cocoa isn't integrating changes from the main Scintilla code stored on sourceforge (eg there was some changes done by Neil Hodgson to the main Scintilla code just 3 days ago... these havn't made it into Scintilla-Cocoa).
Looks like Im going to have to get myself a good visual diff tool (gah, I dont really wanna fork over the cash for Araxis, but it's the supreme tool for this purpose).
Im lucky this time. I was able to "tack on" Finding and line-goto w/o much hassle (its a homework task for my readers to see if my design could have been better if I had remembered these tasks).
Anyways. CodeAssistor now has the ability to Goto lines (CMD-G). interestingly I had to add an "owner" property to the upstream ScintillaView class. I had to add this so that Scintilla notifications would be percolated all the way up to the NSDocument (or NSObject if a Single document model is used) that controls the ScintillaView. I did this so that I could hide the Finder/Goto TextEdits when the ScintillaView regains focus.
Because of this change, revision 66 (and onwards) of CodeAssistor now _requires_ my mullinpatches (lp:~masmullin/scintilla-cocoa/mullinpatches) and will no longer compile against vanilla Scintilla-Cocoa. Previous to this, Vanilla Scintilla-Cocoa could have makefiles hacked up (my mullinpatches has some changes to the vanilla makefiles-which I supplied in the first place anyway) and work properly with CodeAssistor, Although I've fixed a few bugs in Scintilla-Cocoa that MikeLischke hasn't integrated yet, so you would want to use mullinpatches anyways.
The amount of divergence mullinpatches is from vanilla Scintilla-Cocoa is starting to worry me. Right now, I think it's still possible to do a pretty clean merge of mullinpatches onto vanilla since vanilla is static, but if other developers start fixing bugs on vanilla Im going to have an additional chore of updating my mullinpatches.
Not only that, but Im concerned that Scintilla-Cocoa isn't integrating changes from the main Scintilla code stored on sourceforge (eg there was some changes done by Neil Hodgson to the main Scintilla code just 3 days ago... these havn't made it into Scintilla-Cocoa).
Looks like Im going to have to get myself a good visual diff tool (gah, I dont really wanna fork over the cash for Araxis, but it's the supreme tool for this purpose).
Friday, May 7, 2010
Where do I find CodeAssistor?
Today Dave left a comment on my last post suggesting that I post links of where to find CodeAssistor... SOOOOO..... without further wait.
You can check out the source using bzr via "bzr branch lp:codeassistor"
You can download v0.0.1 executable @ http://launchpad.net/codeassistor/v0-0-1/v-0-0-1/+download/CodeAssistor-v0-1-1.zip
The project homepage is found @ https://launchpad.net/codeassistor
Note to anyone who wants to contribute: Launchpad and bzr make "drive by contributions" VERY VERY easy to do and offer some highly professional workflows (code reviews, bug-tracking, revision control). I highly suggest that all developers create themselves a launchpad account.
HINT FOR STUDENTS: If *I* were to go back to school again, I would ask my teachers if I could use Launchpad for all my coding projects.
You can check out the source using bzr via "bzr branch lp:codeassistor"
You can download v0.0.1 executable @ http://launchpad.net/codeassistor/v0-0-1/v-0-0-1/+download/CodeAssistor-v0-1-1.zip
The project homepage is found @ https://launchpad.net/codeassistor
Note to anyone who wants to contribute: Launchpad and bzr make "drive by contributions" VERY VERY easy to do and offer some highly professional workflows (code reviews, bug-tracking, revision control). I highly suggest that all developers create themselves a launchpad account.
HINT FOR STUDENTS: If *I* were to go back to school again, I would ask my teachers if I could use Launchpad for all my coding projects.
Wednesday, May 5, 2010
The CodeAssistor released v0.0.1
I've released my first version of the CodeAssistor software. CodeAssistor is an extremely simple MacOSX code editor that works with c,cpp,cxx,h,m,mm,xc,java, and txt files.
Whats an .xc file you ask? Well because CodeAssistor will one day become cross platform I wrote a few helper functions to facilitate using either ObjectiveC code or C/C++ code (via #ifdefs). On Macs the .xc file will be compiled using -x objective-c++ and on other platforms can be compiled as c or c++ code.
With the help of these helperfuncs I've been able to keep the Scintilla Controller classes strictly c++ rather than Objective-C++, and therefore it will be easier to port to windows/linux.
Basically .xc stands for "Cross C"
I like using it a lot. It's my main editor now. I like creating it a lot. There are still LOTS of features to work on (anyone feel like helping? contact me at masmullin@gmail.com)
I released it under the BSD licence, so yeah... have at'er.
Whats an .xc file you ask? Well because CodeAssistor will one day become cross platform I wrote a few helper functions to facilitate using either ObjectiveC code or C/C++ code (via #ifdefs). On Macs the .xc file will be compiled using -x objective-c++ and on other platforms can be compiled as c or c++ code.
With the help of these helperfuncs I've been able to keep the Scintilla Controller classes strictly c++ rather than Objective-C++, and therefore it will be easier to port to windows/linux.
Basically .xc stands for "Cross C"
I like using it a lot. It's my main editor now. I like creating it a lot. There are still LOTS of features to work on (anyone feel like helping? contact me at masmullin@gmail.com)
I released it under the BSD licence, so yeah... have at'er.
Friday, April 30, 2010
Scintilla Cocoa Bzr and Launchpad
I've started investigating the software product Scintilla. I'm specifically looking into the mac versions of scintilla (cocoa and macosx inside the source tree).
After doing some work with both the cocoa and the macosx version, I truly appreciate how much extra "stuff" apple gives you with the cocoa platform.
In exchange for some control over how things work (ie certain tasks become automagical) Apple gives you really easy ways to implement saving/opening/multipleDocs/"dirty-alert" etc. It's really quite amazing.
I've managed to work on a few bugs for this software because launchpad-bzr is VERY VERY easy to to drive-by-contributions.
So far, I've contributed
- mouse wheel fixes (zooming more like firefox, horizontal scrolling no longer needs holding the shift key, no more zooming 'jumpyness' when using the magic mouse)
- makefiles to build the cocoa project and makefiles to build the sample application
Im currently creating my own Source code Text editor called CodeAssistor because there is a serious lack of light-weight text editing software on the mac.
CodeAssistor is actually pretty solid right now, and I use it for all my editing needs (C,C++,ObjC,make,txt... java is there too but sorta tacked on). The application is comparatively tiny, only 2.5MB (TextWrangler is 28.8MB, TextEdit is 16.3 MB, jEdit is 30.8MB) and blazingly fast. Unfortunately it lacks a Search feature (DOH!) which I totally forgot about when I was thinking about the UI and now have to figure out how to not make the program ugly.
What kind of text editor doesn't have a search feature? DOH DOH DOH. Thats why i have yet to release the software. A textEditor w/o search is just plain stupid.
After doing some work with both the cocoa and the macosx version, I truly appreciate how much extra "stuff" apple gives you with the cocoa platform.
In exchange for some control over how things work (ie certain tasks become automagical) Apple gives you really easy ways to implement saving/opening/multipleDocs/"dirty-alert" etc. It's really quite amazing.
I've managed to work on a few bugs for this software because launchpad-bzr is VERY VERY easy to to drive-by-contributions.
So far, I've contributed
- mouse wheel fixes (zooming more like firefox, horizontal scrolling no longer needs holding the shift key, no more zooming 'jumpyness' when using the magic mouse)
- makefiles to build the cocoa project and makefiles to build the sample application
Im currently creating my own Source code Text editor called CodeAssistor because there is a serious lack of light-weight text editing software on the mac.
CodeAssistor is actually pretty solid right now, and I use it for all my editing needs (C,C++,ObjC,make,txt... java is there too but sorta tacked on). The application is comparatively tiny, only 2.5MB (TextWrangler is 28.8MB, TextEdit is 16.3 MB, jEdit is 30.8MB) and blazingly fast. Unfortunately it lacks a Search feature (DOH!) which I totally forgot about when I was thinking about the UI and now have to figure out how to not make the program ugly.
What kind of text editor doesn't have a search feature? DOH DOH DOH. Thats why i have yet to release the software. A textEditor w/o search is just plain stupid.
Subscribe to:
Posts (Atom)