I Need To Let Go of Eclipse

Eclipse is a really powerful IDE for PHP but I need to let go this powerful tool. It was so powerful it overcome my machine. Maybe it’s misleading to tell that the real problem is that my unit is not powerful enough but yes it’s the sad truth, but in any case I will be biased of my unit.


At first installation I really felt the powerful prowess of Eclipse IDE at times there is a bit of a lag when you click an option at first. There are a lot of options to set up your environment and I thought I don’t need them as of the moment. I try to set up my snippets but it’s more of “fill-in-the-blanks” feature that you can trigger via shortcuts, I am uncomfortable of it a bit since all I need are HTML framework structure (title, body etc.) and some reusable codes that instead of copying and pasting it trigger it with a few keys.

Mainly the project is to be able to use the features of Eclipse in web development through the Project Genesis. I found it difficult to navigate and the learning curve is a steep one. So I will let go of Eclipse at the moment and will try Netbeans.


Project Genesis: Enrollment Functionality

For every School Information System, the functionality to enroll someone in the system is very very important. In fact, in the geneSIS project this is the entry point for all needed information in the system, I don’t need to add further on that. What is needed in this functionality? The information of your incoming students and of course it’s payment frequency. In developing this project a question popped up in the scenario of enrollment. What is to be considered if a person is enrolled or not? Is it just because the person sign up for the school does it mean that person is enrolled? Or if the system will be considering enrollees that were not yet paid or given any amount to be considered to be enrolled?

For me, for the system to be installed into an organization, the developer or the installer of the system needs to have a certain amount to be paid first to move forward with project. For a School Information System to be developed or to be rolled out to a school, the school should have a capability to spent an amount to a software before the organization really reap the benefits of it. Same goes to the school before rendering services to its clients, at least an amount of money should be spent just to ensure or to reserve a seat in the class. So for our geneSIS project we will have consideration to add a student to a class if there is already an amount is paid. The minimum amount should be variable depending on the discretion of the administrator.

We put checks on the student’s profile if this is already enrolled. That would mean if he already declared a payment frequency plus an amount that can be set in the admin panel. This amount would serve as a down payment for the school and a deadline when the payment should be in full before proceeding on the breakdown of the frequency. The flexibility of this payment will be still researched in the coming releases.


OOP Review: Protected and Private

You already coding something and you are start engaging with OOP or Object Oriented Programming. But have you heard of these two attributes? Maybe you are in a start up company for example, and as new advocate of programming concepts you want to be trained but yet there is none since the company is starting really fast. Due to a lot of clients there is not much of a time that you will be thought or explained what are the tech jargon or technical terms are there to learn.

Let’s go back a few years back, where in these concepts are defined during class, College. Before we head on to the definition, remember on your youth where in you are not really listening to your instructor, not because she is boring or something else, but what the hell is she/he talking about?

I was asked this day to define the two, protected attribute and private attribute. There is really a thin line between the two. The protected attribute is defined that only the current class and subclass can access the method or property. The private attribute is that only the current class can have access to the method and cannot be inherited.

I guess to be able to grasp the definition on an ideal scenario is that to have an example of those two attribute and see it in actual program. The concept is to have everything private as possible. This is to have a more security and the program is not easily overridden. Code something today and try to use those attribute so you will able to differentiate in the actual code or program the two attributes.

Here are some cool discussions of the two.



Happy Coding!