Catch the Phillies Phever World Series 2008 Unique Collectibles and T's

Archive for the 'programming' Category

EnvisionBasic Programming

Friday, June 6th, 2008

Writing in Envision Basic and UniBasic code to use DataTel’s Computer-Aided Software Engineering (CASE) Tool, the Envision Tool Kit to create programs and write subroutines for DataTel solutions …

Envision provides a code generator that you can use to generate dynamic user-end processes… The Envision Tool Kit fits between the process stacks of the database management and the application software.

  • The screen of the View Batch Process Status (VBS)
  • View Single Batch Job Step (VBSD) displays error msgs.
  • Re-Run a Procedure (UTRR)
  • Application Definition (APD) use this screen to create new applications

 

 

 

 

Casino Programming

Monday, June 2nd, 2008

Mike Cassell
Jeff Burbank
Ross Harris
Larry Volk
Rex Parlson
Max Rubin

java return method

Wednesday, May 21st, 2008
return statement has purpose to exit from the current method and jump back to the statement within the calling method that follows the original method call 2001-10-19 11:37:49.0

Python for News Aggregation

Tuesday, May 20th, 2008

http://www.djangoproject.com

DRY principle

Tuesday, May 20th, 2008

I aspire to automate as much as possible adhering to the DRY principle

compareTo

Thursday, May 15th, 2008

One should always compare strings for equality using the compareTo method and not the double equals, “==” operator. The latter, as indicated earlier, compares only the object references that will be different when comparing two identical but independent strings.

MVC

Wednesday, April 30th, 2008

The MVC architecture has its roots in Smalltalk, where it was originally applied to map the traditional input, processing, and output tasks to the graphical user interaction model. However, it is straightforward to map these concepts into the domain of multi-tier enterprise applications.

  • Model - The model represents enterprise data and the business rules that govern access to and updates of this data. Often the model serves as a software approximation to a real-world process, so simple real-world modeling techniques apply when defining the model.the bottomline here is this is a blueprint of your data
  • View -The view renders the contents of a model. It accesses enterprise data through the model and specifies how that data should be presented. It is the view’s responsibility to maintain consistency in its presentation when the model changes. This can be achieved by using a push model, where the view registers itself with the model for change notifications, or a pull model, where the view is responsible for calling the model when it needs to retrieve the most current data.but how / when can a view be considered a Template ?
  • Controller - The controller translates interactions with the view into actions to be performed by the model. In a stand-alone GUI client, user interactions could be button clicks or menu selections, whereas in a Web application, they appear as GET and POST HTTP requests. The actions performed by the model include activating business processes or changing the state of the model. Based on the user interactions and the outcome of the model actions, the controller responds by selecting an appropriate view.

Web-based clients such as browsers. JavaServer PagesTM (JSPTM) pages to render the view, Servlet as the controller, and Enterprise JavaBeansTM (EJBTM) components as the model.

Some innovators recently have also begun to say MTV for Model -Template-View in advanced alternative perspectives…

Capitolization Catch

Wednesday, April 30th, 2008

There’s a very simple trick you can learn :-

  • all methods and member variables in the Java API begin with lowercase letters
  • all methods and member variables use capitalization where a new word begins e.g - getDoubleValue() this is pascal/cammel case notation.

pascal/cammel case notation is also the coding standard for MSDN and is coding convention for .NET as seen in

* http://msdn2.microsoft.com/en-us/library/ms229043.aspx
* http://msdn2.microsoft.com/en-us/library/ms229045.aspx

Using OO style names, i’d prefer it Java style:

http://java.sun.com/docs/codeconv/h…tions.doc8.html

If you use this pattern for all of your member variables and classes, and then make a conscious effort to get it right, you can gradually reduce the number of mistakes you’ll make. It may take a while, but it can save some serious head scratching in the future.

when considering hungarian, vs. cammel notation its prefix vs postfix
when you see a long list postfix wins when I read it out…

I strongly recommend the following for Java:

Class names should always begin with an upper case character and be followed by mixed lower and upper case when using a multiple-word identifier such as LandBasedVehicle.

Field and method names should always begin with a lower case character and be followed by mixed lower and upper case when using a multiple-word identifier such as myLandBasedVehicle.

A command should be named as a verb or verb phrase. Examples include push, fireRocket, performComputation.

Using a verb phrase places the emphasis on the action to be performed.

A query should be named as a noun or noun phrase. Examples include top, speed, rocketWeight. If a query returns a boolean value, a phrase starting with ‘’is” might be considered. Examples include isEmpty, isFull, and isCorrect.

COMING SOON!!!!

Friday, April 18th, 2008

Keep an eye out for my 2 new websites, They are both currently under construction.

But I wanted ALL OF YOU to know…..

I am sparking the beginning of an entrepreneurial adventure in the world of Beauty!!

At www.beatifulskinrapporto.com I will be featuring Products for sale from Jordan Essentials, Seriesse, S-Force Anti-Aging & Wellness and MUCH MORE!!!

Then my open forum Beauty Blog will be held at www.skin-care-secrets.info come on in and SHARE YOUR SECRET with me……

} The Mrs {

PostgreSQL vs MySQL

Monday, April 14th, 2008

Ask yourself why you are paying so much in licensing costs and annual maintenance when you could use PostgreSQL.

  1. it’s free
  2. you get community support
  3. upgrades are free as well

In terms of standard SQL support, PostgreSQL is very good indeed. If a feature is in the SQL92 standard, you can be pretty sure that PostgreSQL is going to support it correctly.

I advise developers to stay away from extensions to the SQL standard in any case.

The ability to write functions and stored procedures is somewhat limited in PostgreSQL.

The advantages of PostgreSQL are cost and the ability to look at the source code to understand what’s going on. Very few developers will ever make changes to the source or, even better, submit fixes. I do believe the ability to examine the code in order to understand why something doesn’t behave as you expect is a great benefit.

In my opinion, PostgreSQL is enterprise ready. For many uses, PostgreSQL is just as suitable as Microsoft SQL Server or Oracle, but with a big cost advantage. The features that you need 95% of the time are there and work as expected. The underlying engine is very stable and copes well with a good range of data volumes. It also runs on your choice of hardware and operating system, not just whatever some big vendor might insist you buy to run your database .

Of course, it’s not the solution to all database needs, any more than any other vendor’s product would be. For a large, multi-terabyte data warehouse you still need a specialized database product with some advanced features, specifically for handling those kinds of data volumes.

It’s difficult to see why you would use MySQL and PostgreSQL side-by-side. MySQL has historically traded some functionality for performance. For most purposes, you don’t need to make that trade, and PostgreSQL performance is more than adequate.

http://www.postgresql.org/

install

Refactoring code

Friday, April 11th, 2008

Code evolves as technology and market demands evolve. Over time, existing code may need to be changed to allow more room to grow, to improve performance, to accommodate changing needs, or simply to clean up the code base. Refactoring is the term used to describe the process of redesigning existing code without changing its behavior from the user’s point of view.

Refactoring may be small or extensive, but even small changes can introduce bugs Refactoring must be done correctly and completely to be effective. One change can have permutations throughout the entire codebase. Refactoring handles the entire set of permutations responsibly and durably, with safe operation, so that no behavior is changed beyond improvements in performance or maintainability.

JBuilder provides many types of refactorings. Refactorings are available from the Refactor menu, editor context menu, the structure pane context menu, and a UML diagram context menu. (UML is a feature of JBuilder Enterprise.)

Jbuilder

Thursday, April 10th, 2008

Heres a good ebook reference on JBuilder A Developer’s Guide

or try this JBuilder 2005 resource