- Hiding certain fields in an idea.
- Hovering over a minimized list field will show a small sub-menu that allows them to either expand the list within the idea or show the linked ideas to the side with lines connecting them. Maybe rather than a typical menu, the choices would be visual. In other words, to the side would be a faint image of lines branching out to squares and below it would be a faint image of a list of idea names. They need only hover over one and click.
- Operations on multiple ideas at once. For example, if the user selects a group of "scene" ideas, then he can have them all show the "character" ideas linked to them.
- Automated arranging. Somehow, I'd like to allow the user to make the layout of the drawing board automated. In other words, when the user expands a list of ideas next to a parent idea, rather than just placing them on top of other ideas, arrange them in a visually pleasing way...somehow. I'll have to research that. The biggest difficulty would be dealing with all the "link" lines running around. Maybe I'd have them go "around" other ideas rather than keep them as straight lines. We'll see.
- Masks. A user can create a "mask" which is a preset view for an idea type. In the mask, the user will set how the idea will be displayed on the drawing board. For example, he/she can choose which fields will be displayed, which ones are read-only, etc. The user can set certain drawing boards to only show certain ideas with their masks or the user can open individual ideas with certain masks.
Monday, July 14, 2014
User Interface
Friday, July 4, 2014
Inheritance
Lately, I've been implementing all the database interaction. Using a database is really an ideal way for Idea to work. However, there are a few things that databases don't necessarily do well that are important to Idea. The most prominent is inheritance, which I talked about in my last post.
Inheritance is an important concept in object-oriented programming, but it's non-existent in relational databases. Therefore, I had to come up with a way to imitate it in a database. I can tell you, it wasn't easy.
Sometimes things just click and I gain momentum, and I never seem to hit any ruts. Well, I was that way in my first few iterations of Idea, but I'm not that way now. It's mostly because my current version requires alot of work on the foundation before I can ever even test the thing. So far, I've had to hold everything in my head, and I'm doing something that hasn't really been done before, so I don't really have any precedents. The best way to do things isn't very obvious.
Before, I just jury-rigged everything, but now I'm focused on quality and performance. This time, it's not just a fun experiment. This time, I really want to take it somewhere.
Thus, I was determined to find the best way to implement inheritance. I'll be honest, the first way I thought up seemed really nice at first, but then I realized that it opened a huge can of worms when changing existing idea types' settings. Then I came up with my current method, which at times seems a little tedious, but it utilizes the nifty perks of relational databases better, which actually make things sooo much easier in the end. For example, if you were to change an existing idea type's inherited type, the old way would have been ridiculously hard and impractical. The new way, while still difficult, makes it infinitely easier.
I'm actually a bit proud of my inheritance code. However, it's probably riddled with bugs. I haven't tested anything yet. I'm excited to get to that point. However, I know I'll spend a couple days just ironing out bugs. But that's fine with me.
Thanks for reading!
clevceo
Saturday, June 28, 2014
Idea
You are the master of the idea types. Until you're more comfortable, you can stick to prefab types. However, when you're ready, you can edit the prefabs or create your own idea types, allowing you to use Idea for just about anything.
Tuesday, June 24, 2014
SQLite
I'm working on the foundation of the software at the moment. I have a decent idea how I want it to work, and it's coming along nicely. I've got the database pretty much designed, and now I'm implementing it. The problem is that SQLite's version of SQL leaves out some handy features. For example, you can't drop or modify columns once they're in place. Instead, the way to do that is to copy the data into a temporary table, drop the table, recreate it with the changes, and copy the data back in. It sounds like it would make more sense to just create one new table, copy the data over, drop the original and rename the new one, but that would actually mess things up. In other words, it's a bit inconvenient. However, I'm going to make it work, and I'm excited.
SQLite is the absolute perfect solution to the issues I had with Idea's design. It's no longer impractical and really hard to manage. I could go on and on why this solves all of my life's problems, but I won't. Just know that this makes my life soooooo much easier. Basically, once I have this part developed (which will be soon), then I can start experimenting and having fun.
Anyway, gotta go. I hope to keep this updated as I continue to build it. Thanks for reading!
clevceo
Wednesday, July 10, 2013
Maybe in the Future
However, the problem is that I only know database software built to run hundreds of queries at the same time on a server. I definitely don't need that, and I'm not sure what the solution is, but I'll find it.
I guess what I really wanted to say is that debt collection software is great and all, but I would love to finish Idea one day. I really like the concept and I'd love to use it myself, to be honest, but I'd really need to flesh it out more before it would be useful to anyone.
Hopefully I'm able to pick this back up in the next couple years.
clevceo
Tuesday, March 12, 2013
Backburner
Thursday, October 18, 2012
Idea Is Officially Back
Around this time, a friend of mine mentioned this event at the end of the semester where students can present a project of their own creation to a panel of judges who will give feedback and compare it to the other projects in a contest. The winner gets some award and it goes in his/her resume. This got me thinking. This could be my chance to restart Idea.
If you look at the beginning of this blog, you will see that Idea has been floating in the back of my mind for a long time. It was my first real project, and it went through a number of iterations before I set it on the back-burner to make way for Sever. Sever, I thought, was a simpler, more practical project for my limited skill set and resources. Little did I know, even Sever would grow too big for me.
I have come to realize that in order to finish anything without a full team of programmers working full-time, my projects will have to be limited to proofs of concept. With that in mind, Idea becomes much more doable. I no longer have to worry about the best way to store and update mass amounts of data. I can instead keep it simple, though inefficient, so that I can focus on the project as a whole. Besides, no one is going to be using this version seriously. The chances that it will ever need to accommodate large amounts of data are small. That can come later.
As with every new iteration, I have made significant changes. If you've read my last post, you'll know that I was unsure about how to link ideas. This time around, the answer just came to me almost as if I had always known it. It made so much sense that I assumed it wasn't anything new. I had already begun coding it when I stopped and realized that I had just completely changed the way things worked and had utterly solved one of my biggest dilemmas without blinking an eye. It was exciting.
I switch to part-time in five days. The switch is solely for the sake of Idea, so I am committed to it. I am excited and intend to work hard on it daily.
clevceo