Bryan Goldstein's Blog

My Xserver Repository on Github

2010-02-06T18:27:00.000-08:00

I moved my xserver github repository to http://github.com/brysgo/xserver now this is not to make people thing that my repo is the official one, instead it is so I can use the master branch to mirror the official one. This will allow me to make the blob branch the one I am modifying. Now this major change isn't just based on an outburst of OCD, although I can't say that it didn't have anything to do with it. A second benefit of this, that I will not be able to take advantage of, but others will, is that my master branch can be forked with github. Since I plan on keeping the master branch up to date with the official repository using a cron job, others can take advantage of this and fork my repo with github. I don't know if anyone will find this helpful, but I certainly would have.

Xserver Blob Branch

2010-01-23T22:29:00.000-08:00

The blob branch is still continuing and will hopefully get finished by the end of the school year. I have been using the issues list in github.com as my to-do list for the project. When I get through the rest of the things listed there my code should be ready for another review. After I run it past Peter, I will either have another list of issues to take care of, or I will be able to start testing.

Anyone who wants can still check up on my work, I keep the github repository up to date with mine. If you want to look over my shoulder, you can look at my changes by taking a diff using 'git diff' against the HEAD of the official xserver git repo.

If you have a suggestion, feel free to send it my way. If you have patches to submit I will be happy to take a look at them.

Winter Quarter MT Status Update

2009-12-13T08:11:00.000-08:00

Now that my coursework has eased up slightly, I will be allocating more time for multi-touch work. I plan on picking up the pace of my Xorg blob events project and also CSH's multi-touch table.

While they still aren't in a working state yet, my blob events repositories are available on git hub here. If you want to take a look at what I have so far, run a git diff against head of the mainstream xserver or inputproto repository.

Progress on CSH multi-touch was on hold towards the end of last quarter due to some of the complications caused by attempting to do blob detection with visible light. Namely, it would be very hard to cancel out the projector's image in the camera. This quarter instead of doing this, CSH will be turning to the time tested method of rear Diffuse Illumination (DI). For this, CSH will be buying 4 LED boards containing 48 LEDs each. I also plan on bringing up the purchase of a PS3 eye camera since the one we are currently using is being borrowed and still has the IR filter in it. It would be preferable to get a pre-modded PS3 eye that already has the filter we need.

The CSH multi-touch machine has been wiped and Arch Linux has replaced Ubuntu since rolling releases are easier to work with right now. The latest version of X is running on this machine and "mpx" is functional. I am working with Ryan Huffman to try and get his mpx tuio driver working.

The CSH multi-touch table should be starting to come together towards the end of the quarter, I hope to have it ready well before the RIT Innovation Fair so that CSHers have ample time to write software for it.

Edit:

> Actually ended up buying 8x48 led boards

> Voted money to buy a PS3 eye that we will have to change the filter on ourselves

> Still no luck in attempts to get the mpx tuio driver working, computer locks up

Delegation of CSH Projects

2009-10-04T19:48:00.000-07:00

When I see a project I need to see working, I generally do it. But after a rather blunt reminder from an interviewer, I realised not only that this makes me less efficient in groups, it also has the potential to make other people hate working with me.

So for the benefit of myself, and the people around me, I have decided to delegate all of my current project, except for the one that I have the most to learn from. I have effectively begun the process of handing over the reigns on all of my CSH projects to this years freshmen, in hopes that they will some day do the same.

Together, with a little guidance, they will be doing what I could not have hoped to accomplish all by myself. With that said, I will have more time to focus on the project that matters most to me at this point.

That project would be getting a TUIO based blob protocol working in X.org. The project I spent many a summers day working on, will hopefully come to an end in a reasonable amount of time. And in all my recent epiphanies of project delegation, It is clear to me why Peter doesn't just add multi-touch support himself. There are so many things you can do with a project when you are in as deep as he is, and even though they may all be trivial to you, if you try to do them all yourself, you will get nothing done. Instead you have to focus on the task at hand, and teach the people around you to help.

Good luck freshman taking on my projects, if you need any help, don't hesitate to ask.

Diffused Illumination Multitouch

2009-09-19T15:04:00.000-07:00

Last night I made an attempt to get the CSH FTIR multi-touch table working. The problem was that all attempts to make a compliant surface had failed. In addition, the IR light sources are not nearly strong enough. The solution I decided to go with involved unplugging the IR lights, and using visible light Diffused Illumination (DI).

If you can minimize shadows with good ambient light sources, you can get pretty decent blobs. And the only change I had to make to the default touchlib configuration was add an invert filter right before the threshold filter.

I still have not mounted the projector, or the camera, but I will post on how well the table does when I do. And I still have not given up on multi-touch xserver so I will post more on that as well when I have more to post.

The State of X Blob Events

2009-08-19T20:28:00.000-07:00

My progress on this project isn't picking up quite as quickly as I had expected it to. At the moment I have in place most of what is needed for blob events to work, the only problem is that much of it has not been entirely reworked for all the updates made in the XI2 protocol. There are parts that are updated, but I am still working on sorting through the rest of the code left in the patch originally created by Peter Hutterer.

I assumed that this would go quickly once I got the hang of it, but as I continued on to different parts of the patch, I realized how little I actually followed. So I am not approaching this project the same way as my previous projects. I am treating it like a jigsaw puzzle and getting a piece in where ever I can, and reworking it until it is right.

I feel as if this is foul way to go about a project, but it is the only way I can think of right now. This project has left me asking so much questions, that I find myself at a point where I have become reluctant to ask them, for fear that I may just be wasting other people's time. I will, however, continue to work on this project until it is complete, but I feel as though it is time for me to rethink my approach. I made a github repository for my blob branch, it is mainly for me to back up my work, since it doesn't include the changes to inputproto, and doesn't compile, but it would also be a good place for anyone willing to throw some good advice my way to start.

This is my todo list so far:

~~Create an internal event in include/events.h [include/eventstr.h]~~
~~Use the internal event in GetBlobEvents [dix/getevents.c]~~
~~Convert from internal to XI2 event in EventToXI2 [dix/eventconvert.c]~~
Move blob stuff from slave to master devices in DeepCopyDeviceClasses
Add blob class stuff to internal DeviceChangedEvent
Move Xi/listdev.c stuff to Xi/querydev.c

Tips for Setting Up an Xorg Development Environment

2009-05-22T10:14:00.000-07:00

First you should go here. I would also recommend is who-t.blogspot.com, where you can find a neat git super module that, if you can get it working, would be the best solution. If you are still pulling your hair out, read on.

I had many frustrations getting an X development environment set up for the first time so I will try and list some tips so that you can avoid the trouble I did.

First install the following packages, I may have missed a few but you should be able to tell by errors you get along the way what packages you need.

sudo apt-get install autoconf libtool gettext xutils-dev libssl-dev

The build script at the website above is good, but when you can't get stuff working and find yourself repeatedly running the script, you want something that will let you pick up where you left off. I modified the script to possibly save you hours you can find the script at the bottom of this post.

You can use it the same way you used the other script, with one added feature. If it quits on you run:

export stage=$?

when you want to try building again from that step, run:

./build.sh build $stage

or if you have a different step that you want to go from, you can just type the step number.

Do not run the script with sudo, use su. The pkgconfig doesn't like sudo.

I am using nvidia, you will have to replace the nv driver in the script with whatever driver you have.

If you still have trouble building, look in the output to see where it is going wrong. If a package is missing install it, then try again.

The Build Script

PREFIX="/opt/gfx-test"
PKG_CONFIG_PATH=/opt/gfx-test/lib/pkgconfig

# Attempt to detect proper concurrency level
CPU_CORES=`cat /proc/cpuinfo | grep -m1 "cpu cores" | sed s/".*: "//`
CONCURRENCY_LEVEL=$(( $CPU_CORES + 1 ))

MAKE="make"

REPOS="\
git://git.freedesktop.org/git/xorg/util/macros \
git://git.freedesktop.org/git/xorg/proto/x11proto \
git://git.freedesktop.org/git/xorg/proto/damageproto \
git://git.freedesktop.org/git/xorg/proto/xextproto \
git://git.freedesktop.org/git/xorg/proto/fontsproto \
git://git.freedesktop.org/git/xorg/proto/videoproto \
git://git.freedesktop.org/git/xorg/proto/renderproto \
git://git.freedesktop.org/git/xorg/proto/inputproto \
git://git.freedesktop.org/git/xorg/proto/xf86vidmodeproto \
git://git.freedesktop.org/git/xorg/proto/xf86dgaproto \
git://git.freedesktop.org/git/xorg/proto/xf86driproto \
git://git.freedesktop.org/git/xorg/proto/xcmiscproto \
git://git.freedesktop.org/git/xorg/proto/scrnsaverproto \
git://git.freedesktop.org/git/xorg/proto/bigreqsproto \
git://git.freedesktop.org/git/xorg/proto/resourceproto \
git://git.freedesktop.org/git/xorg/proto/compositeproto \
git://git.freedesktop.org/git/xorg/proto/fixesproto \
git://git.freedesktop.org/git/xorg/proto/evieproto \
git://git.freedesktop.org/git/xorg/proto/kbproto \
git://git.freedesktop.org/git/xorg/lib/libxtrans \
git://git.freedesktop.org/git/xorg/lib/libX11 \
git://git.freedesktop.org/git/xorg/lib/libXext \
git://git.freedesktop.org/git/xorg/lib/libxkbfile \
git://git.freedesktop.org/git/xorg/lib/libfontenc \
git://git.freedesktop.org/git/xorg/lib/libXfont \
git://git.freedesktop.org/git/xorg/lib/libXfixes \
git://git.freedesktop.org/git/xorg/lib/libXdamage \
git://git.freedesktop.org/git/xorg/lib/libXv \
git://git.freedesktop.org/git/xorg/lib/libXvMC \
git://git.freedesktop.org/git/xorg/lib/libXxf86vm \
git://git.freedesktop.org/git/xorg/lib/libXinerama \
git://git.freedesktop.org/git/xorg/proto/dri2proto \
git://git.freedesktop.org/git/xorg/proto/glproto \
git://git.freedesktop.org/git/xorg/lib/libpciaccess \
git://git.freedesktop.org/git/pixman \
git://git.freedesktop.org/git/xcb/proto \
git://git.freedesktop.org/git/xcb/pthread-stubs \
git://git.freedesktop.org/git/xcb/libxcb \
git://git.freedesktop.org/git/xorg/proto/randrproto \
git://git.freedesktop.org/git/mesa/drm \
git://git.freedesktop.org/git/mesa/mesa \
git://git.freedesktop.org/git/xorg/xserver \
git://git.freedesktop.org/git/xorg/driver/xf86-input-mouse \
git://git.freedesktop.org/git/xorg/driver/xf86-input-keyboard \
git://git.freedesktop.org/git/xorg/driver/xf86-video-nv"

modules="\
fontsproto \
x11proto \
xextproto \
videoproto \
renderproto \
inputproto \
damageproto \
xf86vidmodeproto \
xf86dgaproto \
xf86driproto \
xcmiscproto \
scrnsaverproto \
bigreqsproto \
resourceproto \
compositeproto \
resourceproto \
evieproto \
kbproto \
fixesproto \
libxtrans \
proto \
pthread-stubs \
libxcb \
libX11 \
libXext \
libxkbfile \
libfontenc \
libXfont \
libXv \
libXvMC \
libXxf86vm \
libXinerama \
libXfixes \
libXdamage \
dri2proto \
glproto \
libpciaccess \
pixman \
randrproto"

init()
{
        for repo in $REPOS; do
                echo "Cloning $repo"
                git clone $repo
        done
        cd macros
        echo "Building macros"
        ./autogen.sh --prefix="$PREFIX"
        ($MAKE)
        make install
        cd ..
}

update_modules()
{
        for module in $modules; do
                echo "Updating $module"
                cd $module
                git pull
                cd ..
        done
}

build_module()
{
 cd $1
 echo ======================
 echo configuring $1
 echo ======================
 ./autogen.sh --prefix="$PREFIX"
 echo ======================
 echo building $1
 echo ======================
 if [ $? -ne 0 ]; then
  echo "Failed to configure $1."
  exit $build_stage
 fi
 ($MAKE)
 make install
 cd ..
}

build_drm()
{
        cd drm
        ./autogen.sh --prefix="$PREFIX"
        ($MAKE)
        make -C linux-core
        # assuming you're on Linux, otherwise use bsd-core
        make install
        cd ..
}

build_mesa()
{
        cd mesa
        ./autogen.sh --prefix=$PREFIX --with-driver=dri --disable-glut #--with-state-trackers="egl dri2"
        if [ $? -ne 0 ]; then
                echo "Failed to configure Mesa."
                exit $build_stage
        fi
        ($MAKE)
        make install
        mkdir -p $PREFIX/bin
        install -m755 progs/xdemos/{glxinfo,glxgears} $PREFIX/bin/
        cd ..
}

build_xserver()
{
        cd xserver
        ./autogen.sh --prefix=$PREFIX --enable-builtin-fonts --with-xkb-path=/usr/share/X11/xkb
        if [ $? -ne 0 ]; then
                echo "Failed to configure X server."
                exit $build_stage
        fi
        ($MAKE)
        make install
        chown root $PREFIX/bin/Xorg
        chmod +s $PREFIX/bin/Xorg
        cd ..
}

build_mouse()
{
        cd xf86-input-mouse
        ./autogen.sh --prefix=$PREFIX
        ($MAKE)
        make install
        cd ..
}

build_keyboard()
{
        cd xf86-input-keyboard
        ./autogen.sh --prefix=$PREFIX
        ($MAKE)
        make install
        cd ..
}

build_nvidia()
{
        cd xf86-video-nv
        ./autogen.sh --prefix=$PREFIX
        ($MAKE)
        make install
        cd ..
}

build ()
{
        export ACLOCAL="aclocal -I $PREFIX/share/aclocal"
        export PKG_CONFIG_PATH="$PREFIX/lib/pkgconfig"
 export build_stage=0
        for i in $modules; do
  if [ $build_stage -ge $1 ]; then
   build_module $i
  fi
  let "build_stage += 1"
        done
# build drm
 if [ $build_stage -ge $1 ]; then
  build_drm
 fi
 let "build_stage += 1"
#build mesa
 if [ $build_stage -ge $1 ]; then
  build_mesa
 fi
 let "build_stage += 1"
#buildxserver
 if [ $build_stage -ge $1 ]; then
  build_xserver
 fi
 let "build_stage += 1"
#mouse
 if [ $build_stage -ge $1 ]; then
  build_mouse
 fi
 let "build_stage += 1"
#keyboard
 if [ $build_stage -ge $1 ]; then
  build_keyboard
 fi
 let "build_stage += 1"
#nvidia
 if [ $build_stage -ge $1 ]; then
  build_nvidia
 fi
 let "build_stage += 1"
}

case "$1" in
        init)
                init
                ;;
        build)
                case "$2" in
                  ?*)
                    build $2
                    ;;
                  *)
                    build 0
                    ;;
  esac
                ;;
        update)
                update_modules
                ;;
        *)
                echo "Usage: $0 init | build [stage] | update"
                exit -1
esac

Running your new X

Follow the instructions here to get it running, you will probably need to link your xkeyboard-config to your current setup unless you want to build that too.

A New Summer with New Projects

2009-05-13T21:40:00.000-07:00

The focus of this summer is going to be on open source projects and CSH related projects. Now anyone who is reading this should know what open source is, but you probably don't know what I mean by a CSH project. CSH is the Computer Science House at Rochester Institute Of Technology where I am wrapping up my Freshman year. I have been living on CSH all year, and have benefited greatly from the experience.

Each year CSHers work on big projects, we have a great deal of projects that receive a good deal of work. This summer I have a few that I plan to single out. One thing I have always wanted to work on, and finally have an excuse to, is multi-touch technology. CSHers this year built a new Frustrated Total Internal Reflection (FTIR) table and has been working hard to get the hardware working as much as they can.

They are using TouchLib, or TBeta, which ever will co-operate for one demo or the next, and they are interfacing with home-brew TUIO applications that several people have been working on.

Now the part that bothers me, is that the multi-touch input completely bypasses the computers native systems, and goes directly to whatever applications are implementing the protocol. This works for demos, but it isn't a multi-touch computer, its a multi-touch demo. Multi-touch demos are all too common, but multi-touch computers are few and far between.

My first goal for this summer is to get the foundations for an open source multi-touch computer working using the groundwork already laid by Peter Hutterer with MPX, which was recently merged with the mainstream X. I have contacted Peter, and my first goal is to accomplish the task he gave me. While it is a relatively simple task, the hard part will be familiarizing myself with the X code base, and even setting up a proper building and testing environment.

My Mac Projects

2008-04-23T10:38:00.000-07:00

At this point it is looking like I will never get the chance to fix up all of my mac projects like Gwidget or Wcode. I would be happy to pass either of them on to anyone willing to pick up where I left off. Drop me an email if your interested, my only condition is that previous Wcode customers get free updates.

Delay in Wcode/Disappear/Gwidget updates and fixes

2007-11-02T17:19:00.000-07:00

It may be clear to anyone looking for a working version of Gwidget, or a more Leopard friendly version of Wcode that I haven't had a chance to update any of my software. I have been very busy lately with other things like school work. I also am currently unable to update my website at http://bryan.iindigo3d.com because of ftp problems. This doesn't mean that I am done developing my software, it just means that I am waiting until at least second semester to get my own hosting and start all my projects back up. I also have some pretty good ideas for future killer apps, so hang in there. For those of you that need support, or just have questions/suggestions about future versions of my software, feel free to email me.

Update: I no longer have a need to find hosting, because I have found all I need for free. This blogger page, combined with google pages, is now my new website.

Gwidget 1.1 Released

2007-05-06T20:37:00.000-07:00

I just posted a minor update of Gwidget, there is but one, very handy difference in this new version. The difference is that this version gives you the ability to select and copy text. There are some small changes in links on the back also but nothing that is very noticable.

More Info | Download

New Home For My Software

2007-05-05T15:09:00.000-07:00

I have finally created a new web site after the web site that widgetfactor.com, the web site for wcode, which I had been paying someone an overly large ammount to create and host, has disappeared and took the site down with him. The person I was paying's boss at Lexink took the domain for his own site without any response when I emailed him about posibly aquireing the domain from him.

After being severely ripped off like that, I have recoved with a basic web site of my own. I will begin searching for my own domain and hosting but in the mean time, it is kindly being hosted by John Wells at http://bryan.iindigo3d.com. This means the the very new very fresh integration of sparkle into Wcode will unfortuately not be able to automatically update the next version of Wcode.

Gwidget 1.0 Is HERE!

2007-04-23T17:40:00.000-07:00

I am proud to announce the immediate availability of Gwidget 1.0. It now uses Skweezer instead of Google mobile. As a result, the search results are much neater. Features such as Google Calculator, Google Dictionary, and Google Spellcheck now work flawlessly. When you click on the results now the page loading is generally much faster and adds a page loading indicator so you will know if the page is loading or Gwidget is just not working. All of the colors are the same and the news and image search options were removed in order to put more focus on the web searching. Don't take my word for it, try it yourself and see why I am so excited about it!

Download Gwidget 1.0 Now!

Please leave a comment if you have questions, suggestions, compliments, or criticism.

Gwidget+Wcode Progress

2007-04-12T17:46:00.000-07:00

Gwidget:

The other day I worked on Gwidget. I changed the method of getting pages and results from Google mobile to skweezer and the regular Google search. The search results are now much more presentable. Opening pages in Gwidget is also much faster now, and when you do open the page it is not split into sections on multiple pages like it was before so it is much more compatible with the widget. The other advantage this setup gives besides improved speed and reliability, is the ability for me to set up support for Google dictionary, calculator, and other similar search services. With that, I also removed the image and news search in favor of spending more time on the regular web search. I would consider reviving them later on if I get enough requests for it. I will be releasing it as soon as I get a chance to brush it up a bit.

Wcode:

Yesterday a friend sent me a class to add some syntax coloring. I tried it out in Wcode and I thought it was fantastic. In addition to line numbering, it colors the html tags and the html comments and only has some minor faults to overcome. I also wanted it to color quotes, javascript, and css. Coloring quotes was a nearly impossible task since a bug in the NSScanner class does not allow searching of the same character twice in a row with one scanner. I stayed up until two in the morning writing an extremely complicated work around for this bug. So now the quotes are colored and I will be working on adding and improving more syntax coloring. Once I complete my work with syntax coloring I hope to make a system to manage indenting. You can probably expect another release when that is done.

Please leave a comment if you have questions, suggestions, compliments, or criticism.

Plans for Gwidget

2006-12-18T15:11:00.000-08:00

I enjoy working on Gwidget a lot and I have tons of things I would like to add to it when I have time. I would like to change gwidget to get it's results from google.com instead of google's mobile web. This way a bunch more of google's search features will work. Another thing that would allow you to do is make all of the customizations that google allows like changing the number of results per page. The next thing I want to do is have clicked results open with skweeze.com instead of google's mobile web. This would eliminate having the displayed page on multiple pages instead of just one. After that there are a whole bunch of things I could think of doing. I got requests for country specific searches, I will look into that. I will also try and fix gwidget so it works as well in foreign languages as it does in english, but I don't know how hard that will be. Any way, I can't say if I will have time to do all this, but keep watching for updates.

Gwidget 0.5 (Now 0.5.1)

2006-12-09T17:59:00.000-08:00

Click here to download

The the most frequent request for Gwidget is for it to be resizable. Well now, after about twelve hours of non-stop working, you can finally resize Gwidget. I also added a white color scheme option because someone wanted it to look more like googles' widgets. You may also notice other small changes. Also, If you want to show your support for Gwidget you can donate however much you feel it's worth.

I have also released version 0.5.1 which is just a bug fix for a pretty big problem that occurs for people who have not used any version of Gwidget before version 0.5.

Gwidget 0.2

2006-12-03T13:01:00.000-08:00

I just released Gwidget 0.2. The major difference is that there are now four colors to pick from. Other small changes have been made that you may or may not notice. Click here to download it now.

Gwidget 0.1 Released!

2006-11-26T17:54:00.000-08:00

My first widget, Gwidget (jee' wid jet), was just released. It is unlike any of the other search widgets currently up for grabs. It searches google and displays the results right on your dashboard. Also, unless you select the option not to, it displays the website you click on right in the widget. Try it out. Leave a comment and tell me what you think about it, also tell me what you think I should add.

Click here to download it.

Wcode 2.0 Released!!!!!!!

2006-11-20T10:56:00.000-08:00

Download Wcode 2.0 Here

Wcode 2.0 version was released last night somewhere close to 2am. It is the result of hours and hours and hours of hard work. Although it is rewritten from scratch, some of the noticeable features are the new template system that allows anyone who wishes to easily create and share their own templates for Wcode. Another noticeable feature is the built in widget preview, this allows you to get your layout straight with out going back and forth to dashboard a million times. Another feature you will notice is a remade info.plist editor. This is a new full featured design that gives you every option available for creating your info.plist file. Also, when you start typing in the search field, you will notice a big difference. Instead of just searching the file you have open, it searches all of the files you have opened and the titles of all the files you have not yet opened. You will also notice the improved design and stability. In addition to that their are many things you will not notice right of the bat, but it is all new, completely remade. Do yourself a favor and download a copy, you'll love it!

Wcode 2.0 getting closer

2006-10-22T19:17:00.000-07:00

I accomplished a lot this weekend in terms of Wcode. I created the info.plist editor and it is a hundred times cooler than the last one. I also worked out a few bugs and worked on making this release perfect. Also Jeremy and I have started working on converting the templates, we have the search widget template done and the default plain template done. The rest should be done within one or two weeks. After that, all that is left to do is code the registration system in and it's done! Also, the people that created the code that is used in the rss template do not want us releasing it with our program, so it will be available for download seperately and all that you will have to do is open in, and it will be installed into wcode. But if anyone at all is interested in making a template before the release of Wcode 2.0 please contact me. Wcode is going to need good templates in order to have a fighting chance against dashcode, apple's version of my program. Alse, feel free to make comments, I will try to answer them all.

Wcode 2.0 Questions

2006-10-15T15:18:00.000-07:00

OK, a lot of you are probably have a few of the same questions about wcode 2.0. Widgets in leopard, as far as I am aware of are the same as widgets in tiger. Second, the 2.0 release will be a universal binary. The last question everyone is probably wondering is why the heck is this thing taking so long. The answer to that question is that while this version is almost complete, I have not yet created the templates. If you've read my blog you know the templates are now just files instead of code that is built into the program. So while the template system works for the default blank template, I have not had any time to port the other templates. The last thing I have not done yet that I would like to do is create an interface for the info.plist file. This is available in the current wcode but I would like to improve it.

If you are interested in making a template that you would like to have posted with the release of Wcode 2.0, email me at brysgo at gmail d0t ç0m and i will try and help you to make a template.

Accepting Google Checkout as well as paypal for wcode.

2006-10-09T13:00:00.000-07:00

Now in addition to accepting purchases via paypal I will also accept purchases with Google Checkout. Here here is the new button.

Wcode 2.0 Coming Soon

2006-05-27T09:00:00.000-07:00

I have been working very hard for the last couple of weeks to bring you Wcode 2.0. Wcode 2.0 is a complete rewrite of wcode, the design is simmilar but the code is rewriten from scratch.

Some new features:
- There is a new template system uses template files so anyone who wants can create and share their own templates.
- The preview feature now runs the widget in wcode. It is not a substitute for the build and run button but it is definetly better than previewing in Safari.
- The search bar is also improved. It searches every file you've opened and all imediate files in the widget's titles. The search doesn't make it through folders unless you have opened a file the when you search the folder that file is in will not be filtered out.
- there is also an huge increase in overall performance

I hope everone else is as excited about it as I am.

What is this blog about?

2006-05-27T08:39:00.000-07:00

I just decided I am going to use this blog. It will be about whatever I decide to post on it, mainly about my software and macintosh stuff but also other random things.