yet2.com sees a lot of market interest in encapsulation technologies.

We are having a webinar on 4 that we think are particularly interesting. This live webinar features four new technologies and an overview of the market by Dr. Eugene Buff, yet2.com’s vice president of consulting. Not just a lecture, the webinar format offers ample opportunity for electronic interaction with the principals.

REGISTER NOW
https://www2.gotomeeting.com/register/310003931

As of the writing of this blog post 84 companies have singed up to participate on Friday December 11, 11:00–12:30pm US Eastern Standard Time.

Moderator:

• Dr. Eugene Buff, yet2.com vice president, consulting

4 New Technologies:

• Microencapsulation for drug delivery, Cory Berkland, Orbis Bioscience
• Efficient membrane coating and production technology, Luc Vanmaele, AGFA
• Microencapsulated, water-dispersbile nanomaterials, Ken Yoon, Vive Nano
• Controlling free radical polymers using “Living Polymers,” Vendy Tomko, DuPont

Dr. Buff will present opening remarks and overview, followed by the four presentations in order at approximately 15-minute intervals. Each presenter will answer submitted questions at the end of his presentation.

Tugas PBO yang ke-dua ini adalah mengenai contoh dari information hiding, encapsulation dan inheritance atau pewarisan.

****

1. Superclass dan Subclass

SUPERCLASS:
class hewan {
public void methodAwal() {
system.out.println(“Action superclass: “);
system.out.println(“a. Berjalan”);
system.out.println(“b. Bernafas”);
}
public static void main(string[] args) {
hewan oks = new hewan();
oks.methodAwal();
}

}

OUTPUT:
Action superclass:
a. Berjalan
b. Bernafas

*****************************

SUBCLASS:

class hewanBersayap extends hewan {
public void methodPemanggil() {
super.methodAwal();
}
public void methodNama() {
system.out.println(“Subclass: Hewan bersayap “);
system.out.println(“a. Angsa”);
system.out.println(“b. Capung”);
}
public void methodJmlsayap() {
system.out.println(“Jumlah sayap:”);
system.out.println(“a. Satu pasang”);
system.out.println(“b. Dua pasang”);
}
public static void main(String[] args) {
hewanBersayap oks = new hewanBersayap();
oks.methodPemanggil();
oks.methodNama();
oks.methodJmlsayap();
}
}

OUTPUT:
Subclass: Hewan bersayap
a. Angsa
b. Capung
Jumlah sayap:
a. Satu pasang
b. Dua pasang

********************************

2. Information hiding dan Encapsulation

public class persegi {
private double sisi;
public persegi() {
sisi=0;
}
private double luas(double s) {
return s*s;
}
public void setSisi(double sisi) {
this.sisi=sisi;
}
public double getSisi() {
return sisi;
}
public double getLuas() {
return luas(sisi);
}
}

public class mainPersegi {
public static void main(string[] args) {
persegi pp = new persegi();
pp.setSisi (15);
system.out.println(“Sisi = “+ pp.getSisi());
system.out.println(“Luas = “+ pp.getLuas());
}
}

OUTPUT:
Sisi = 15.0
Luas = 225.0

yuniarty utami

Stopping mold, rot and odors in crawl spaces
There are only two primary ingredients needed for rot and mold to thrive: one is organic material, like the wood beneath a home, and the second is water. Replacing the wood in a house is practically impossible, so the only avenue to preventing structural damage and those musty smells is to eliminate the moisture.

Crawl Space Encapsulation Previously the tactic was to add vents to a crawl space, which were supposed to allow the moisture to dissipate. These vented crawl spaces, instead of becoming less damp, end up being more wet for several reasons. The stack effect, a house’s natural tendency to draw air in from the crawl space and lower levels upward into living spaces, means that instead of letting moist air out, a house sucks more moist air in! Another problem with venting a crawl space is that it allows all kinds of bugs and critters direct access to a home.

The biggest issue with adding vents is that it does not address the main problem – moisture from the dirt beneath a home – so venting a crawl space isn’t even addressing the actual problem.

Even if a crawl space is not flooded or visibly wet, that additional humidity can spell trouble for your home – and your health. The fungus responsible for rot and mold not only eats away at the structure of a home, but spreads by producing millions and millions of airborne spores. These spores are a prime suspect for aggravating allergies and many people don’t even know what it is that bothers them when they are at home.

Crawl Space Rot & MoldThere is a solution, however, to all of these problems. Instead of struggling against nature to remove moisture from a crawl space, The Basement Doctor and Basement Systems developed the CleanSpace Crawl Space Encapsulation System, which seals a crawl space off from that moisture coming up from the dirt and from the damp air outside.

CleanSpace Crawl Space Encapsulation System
Rather than let the moisture in and then try to get rid of it, CleanSpace isolates a home from the earth entirely so the humidity never gets in there to begin with. This strategy also stops bugs and other critters from getting into a crawl space while reducing, or sometimes even eliminating mold growth and rot.

The key to the CleanSpace system is the patented, 20-mil thick liner material. It is a tough blend of seven polyethylene and polyester cord reinforcement layers, designed specially for crawl spaces. Since the side you see after installation is bright white, it really brightens a crawl space and lets you know that it is free of mold, insects and dirt. The liner is so tough you can crawl on it and use your crawl space for storage without worry of putting holes or tears in it. And, of course, it completely stops moisture from getting in and ruining the underside of your house.

If you would like to read more about the CleanSpace Crawl Space Encapsulation System The Basement Doctor website has more information.

The Basement Doctor organization has local offices with crawl space experts in Columbus Ohio (servicing Worthington, Westerville, Reynoldsburg, Gahanna, Dublin, Powell, Pickerington, Grove City, Bexley, Grandview, Hilliard, Whitehall, New Albany, Upper Arlington, Marysville, Delaware, Marion, Delaware county, Franklin county), Cincinnati (servicing Dayton, Fairfield, Hamilton, Kettering, Lexington and Louisville Kentucky), Lima (servicing Toledo, Sidney, Defiance, Celina, Kenton, Bowling Green, Findlay, Wapakoneta, Ottawa, Bluffton, Cridersville, Maumee, Perrysburg, St Mary’s, Van Wert, Tiffin, Fremont, Norwalk, Sandu, skynorthwest Ohio and Ft Wayne, Elkart Indiana) plus Parkersburg West Virginia and Evansville Indiana!

In the software industry we tend to come across this term a number of times. It mainly deals with separating all the concerns (overlapping features) of a computer program into distinct features or behaviours.

This is mainly achieved through modularity and encapsulation. Usually in any major application we have a number of layers like the presentation, business logic, data access and the database layer. This is also an example of separation of concerns(SoC).

The most common and lucid example of separation of concerns has to be the web page. It is a combination of html(content), css(style) and javascript(behaviour). As a good practice all these 3 layers are always maintained separately (SoC) so that the content is always available(visible to the user) irrespective of failures of the presentation and the behaviour layers.

MVC also achieves something similar by separating the content from presentation and model from content.
Languages like C#, Java etc achieve this by separating concerns into objects while procedural programming languages like C etc achieve the same by separating concerns into procedures.

Có bao giờ bạn tự hỏi các chữ viết tắt, tín hiệu đèn, các cổng trên modem ADSL có ý nghĩa gì ? Bình thường có thể bạn không cần quan tâm nhưng đến khi xảy ra sự cố không truy cập được Internet thì những thông tin trên hết sức quan trọng vì có thể giúp bạn tự tìm ra nguyên nhân và cách khắc phục trước khi gọi cho nhà cung cấp dịch vụ. eBook “Cấu hình 12 loại modem ADSL thông dụng” của tác giả Napoleon_tq sưu tầm và tổng hợp từ internet sẽ giúp bạn hiểu rõ hơn về thông tin, cách cài đặt, cách truy cập vào modem để cấu hình. Mỗi modem được trình bày trong eBook đều có hình minh họa và những hướng dẫn cài đặt rất chi tiết. Hiện tại bạn có thể tìm hiểu thông tin của 12 loại modem (bao gồm username, password và điạ chỉ IP mặc định cuả modem) : Micronet, Aztech, SpeedTouch 530, Postef, Prolink, SmartLink, Billion, Zoom, Zyxel, SpeedStream, Huawei, D-Link.
Đọc tiếp… »

ကဲ ဒီေန႔ေတာ့ database အပိုင္းေလး ခဏနားျပီး C# ဘက္ကို နည္းနည္းျပန္လွည့္ေအာင္။ ကြၽန္ေတာ္တို႔ အခုေနာက္ပိုင္း programming language မွာ အသံက်ယ္က်ယ္ေလာင္ေလာင္ ျဖစ္လာတာက OOT လို႔ ေခၚတဲ႔ Object-Oriented Technique ပဲျဖစ္ပါတယ္။ OO မွာ ဘာေတြပါလဲ…

အေမြဆက္ခံျခင္းလို႔ ေခၚတဲ႔ inheritance၊

အသြင္ေျပာင္းျခင္းလို႔ေျပာလို႔ရတဲ႔ Polymorphism၊

Data hiding လို႔ေခၚတဲ႔ member data ေတြကို သို၀ွက္သိမ္းဆည္းထားျခင္း၊

Encapsulation သိမ္းဆည္းထားတဲ႔ member data ေတြကို တဆင့္ခံျဖင့္ သံုးခြင့္ေပးျခင္း၊

စသည္ျဖင့္ေပါ႔ဗ်ာ.. အဲ့ဒါေတြ ပါပါတယ္။

Inheritance အေမြဆက္ခံျခင္းဆိုတာဘာလဲ???

ဒီလိုေလးေတြးၾကည့္ရေအာင္ဗ်ာ အခုကြၽန္ေတာ္တို႔ မိဘေတြပိုင္ဆိုင္တဲ႔ ပိုင္ဆိုင္မႈေတြဟာ ကြၽန္ေတာ္တို႔ရဲ႕ ပိုင္ဆိုင္မႈေတြပါပဲ။ ဒီလိုပါပဲ ကြၽန္ေတာ္တို႔ရဲ႕ ပိုင္ဆိုင္မႈေတြကိုလည္း ကြၽန္ေတာ္တို႔ရဲ႕ မ်ိဳးဆက္သစ္ေတြက ပိုင္ဆိုင္ၾကဦးမွပါ။ ဒီသေဘာတရားေလးကို ယူျပီး OOမွာ inheritance ဆိုတာေပၚေပါက္လာတာပါ။ class တစ္ခုရဲ႕ ပိုင္ဆိုင္မႈ property ေတြဟာ အဲ့ဒီ class ရဲ႕ child ေတြကလည္း ပိုင္ဆိုင္နိုင္ပါတယ္။ ဒီလို ပိုင္ဆိုင္နိုင္ျခင္းအားျဖင့္ ကြၽန္ေတာ္တို႔က class ေတြအားလံုး အတြက္ တူညီတဲ႔ property ေတြကို အၾကိမ္ၾကိမ္ေၾကျငာေပးေနစရာ မလိုေတာ့ပါဘူး။ ဥပမာဗ်ာ ကြၽန္ေတာ္က လူတစ္ေယာက္ကို ကိုယ္စားျပဳမယ့္ class တစ္ခုေဆာက္မယ္ဆိုရင္ အဲ့ဒီ class ထဲမွာ ဘယ္လို member ေတြပါမလဲ စဥ္းစားၾကည့္၊ နံမည္ပါမယ္၊ အသက္ပါမယ္၊ ေနရပ္လိပ္စာပါမယ္ဗ်ာ၊ စသည္ျဖင့္ေပါ့။

class People
{
    string Name;
    int Age;
    string Address;
}

ကဲ…အခု ေနာက္တစ္ခါ ကြၽန္ေတာ္က ေက်ာင္းသားတစ္ေယာက္ကို ကိုယ္စားျပဳမယ့္ class တစ္ခုထပ္ေဆာက္ဖို႔ လိုလာျပီဆိုရင္ေရာ ဘယ္လို member ေတြပါမလဲ၊ ေက်ာင္းသားမွာလည္း နံမယ္ပါမယ္၊ အသက္ပါမယ္၊ လိပ္စာပါမွာပါပဲ၊ ေက်ာင္းသားမွာ ပိုပါလာတာက roll နံပါတ္ပါမယ္၊ class ပါပါမယ္။

class Student
{
    string Name;
    int Age;
    string Address;
    int Roll;
    int Class;
}

ဟုတ္ျပီ ဒီလိုအေျခအေနမ်ိဳးမွာ နံမည္တို႔ အသက္တို႔ကို ထပ္ျပီး မေၾကျငာခ်င္ဘူးဆိုရင္ ကြၽန္ေတာ္တို႔ Student class ကို People class ရဲ႕ child အျဖစ္ ေၾကျငာလို႔ ရပါတယ္။ ဒီလိုမ်ိဳးပါ…

class Student : People
{
    int Roll;
    int Class;
}

ဒါကို inheritance လုပ္တယ္လို႔ ေခၚပါတယ္။ inheritance လုပ္လုိက္ျခင္းအားျဖင့္ People class ထဲက member data ကို Student class ထဲမွာ ျပန္ျပီ ေၾကျငာေပးေနစရာ မလုိေတာ့ပါဘူး။ ဒါေပမယ့္ ဒီေနရာမွာ အေရးၾကီးတဲ႔ အခ်က္တစ္ခ်က္ကို သိထားဖို႔ လိုပါေသးတယ္။ ဒီလိုဗ်ာ ကြၽန္ေတာ္တို႔ မိဘရဲ႕ ပိုင္ဆိုင္မႈအားလံုး ကြၽန္ေတာ္တို႔ရမလား၊ မရပါဘူး သူတို႔ ကိုယ္ပိုင္အတြက္ သိမ္းထားတာေတြလည္း ရွိနိုင္ပါတယ္။ C# language မွာလဲ အဲ့ဒီလိုမ်ိဳး ခြဲျခားဖို႔အတြက္ ကြၽန္ေတာ္တို႔ Access Modifier ဆိုတာကို သိဖို႔လိုအပ္လာပါတယ္။ C# language မွာ access modifier ၅ မ်ိဳးရွိပါတယ္။ အဲ့ဒါေတြ ကေတာ့

-       public                            ( အမ်ားသံုး )

-       protected                       ( မိမိႏွင့္child ေတြသံုး )

-       private                          ( မိမိကိုယ္တိုင္သံုး )

-       internal                         ( library တူအတြင္းသံုး )

-       protected internal           ( child ျဖစ္လွ်င္၄င္း၊ library တူလွ်င္၄င္း သံုး )

စသည္တို႔ ျဖစ္ပါတယ္။ အေပၚက example People class ေလးမွာ ကြၽန္ေတာ္တို႔ access modifier မထည့္ေပးလိုက္ပါဘူး။ ဒါဆိုရင္ default အေနနဲ႔ private ပါ။ ဒါေၾကာင့္ People class ထဲက member data သံုးခုက people class အတြင္းမွာပဲ သံုးခြင့္ရွိပါတယ္။ Student မွာ သံုးလို႔ မရပါဘူး။ အခုကြၽန္ေတာ္တို႔က Student class ထဲကေနပါ သံုးခြင့္ရခ်င္တာျဖစ္လို႔ protected member အျဖစ္ေၾကျငာေပးရမွာပါ။

class People
{
    protected string Name;
    protected int Age;
    protected string Address;
}

Polymorphism အသြင္ေျပာင္းျခင္းဆိုတာကေရာ???

ကြၽန္ေတာ္တို႔ ရပ္ကြက္ေတြမွာ လုပ္ေလ့ရွိတယ္ဗ်ာ တခါတေလ ရပ္ကြက္ရံုး ကေနျပီးေတာ့ တစ္အိမ္ကို လူတစ္ေယာက္ႏႈန္း အစည္းအေ၀းတက္ရမယ္တို႔ ဘာတို႔ ၾကံဳဖူးမွာေပါ့။ ဟုတ္ကဲ႔ ရပ္ကြက္ရံုးက ေခၚတာက လူတစ္ေယာက္လို႔ ေခၚတာပါ တနည္းအားျဖင့္ people class ကို ေခၚတာပါ။ အဲ့ဒါကို အိမ္မွာ ရွိေနတဲ႔ ေက်ာင္းသားတစ္ေယာက္က သြားတက္လို႔ မရဘူးလား၊ ရပါတယ္။ Teacher တစ္ေယာက္သြားတက္မယ္ဆိုလို႔လဲ ရပါတယ္။ Teacher ကလည္း people တစ္ေယာက္ပဲ ျဖစ္လို႔ပါ။ ဒါေပမယ့္ Student ပဲ သြားသည္ျဖစ္ေစ၊ Teacher ပဲသြားသည္ျဖစ္ေစ၊ ဒါမွမဟုတ္ People ကိုယ္တိုင္ပဲ သြားသည္ျဖစ္ေစ၊ အားလံုးကို People လို႔ပဲ ျမင္ပါတယ္။ အားလံုး အခြင့္အေရးတန္းတူပါပဲ။ Student မို႔ အခြင့္အေရးပိုရမလား မရပါဘူး။ အိုေက အဲ့ဒီလိုမ်ိဳး People ကိုေခၚတာကို Stuent သြားလိုက္တာကို အသြင္ေျပာင္းလဲျခင္း ( polymorphism ) လို႔ ေခၚပါတယ္။

static void Main()
{
    People p;
    p = new Student();
}

Polymorphism မွာ သတိထားရမည့္ အခ်က္ကေတာ့ child ကို parent အသြင္ေျပာင္းနိုင္ေပမယ့္ parent ကိုေတာ့ child အျဖစ္ေျပာင္းလို႔ မရပါဘူး။ ဆိုလိုတာကေတာ ေက်ာင္းသားအားလံုး စာေမးပြဲလာေျဖပါဆိုျပီး ေခၚတာကို အိမ္မွာ ရွိတဲ႔ လူၾကီးေတြသြားေျဖလို႔ ရမလား မရပါဘူး၊ ဒီသေဘာပါ။ Student ကိုေတာင္းရင္ေတာ့ People ေပးလို႔ မရပါဘူး၊ Student ပဲ ေပးမွ ရမွာပါ။

Data Hiding

Data hiding ဆိုတာကေတာ့ ကြၽန္ေတာ္တို႔ အိမ္မွာ မိသားစုပိုင္ဆိုင္မႈေတြကို တျခားလူေတြသိေအာင္ ထုတ္ေၾကျငာေလ့ရွိလား? မရွိပါဘူး တိတ္တိတ္ေလးပဲ သိမ္းထားေလ့ရွိပါတယ္။ ဒီသေဘာပါပဲ class ေတြထဲမွာရွိတဲ႔ member data ေတြကိုလည္း အျပင္ကေန ေခၚလို႔မရေအာင္ private လုပ္ထားျခင္းကို data hiding လို႔ ေခၚပါတယ္။ ဥပမာဗ်ာ အခု student class ထဲမွာ roll နဲ႔ class ပါတယ္မလား၊ အဲ့ဒီ member data ေတြကို အျပင္ကေန ေခၚသံုးလို႔ မရပါဘူ။ ဘာလို႔လဲဆိုေတာ့ private member data ေတြ ျဖစ္လို႔ပါ။ ဒီလုိမ်ိဳး class member data ေတြကို private အျဖစ္ပဲ ေၾကျငာတာကို Data Hiding လို႔ေခၚပါတယ္။

Encapsulation

Encapsulation ဆိုတာကေတာ့ ကြၽန္ေတာ္တို႔ hide လုပ္ထားတဲ႔ data ထဲက လိုအပ္တဲ႔ dataေတြကို function ေတြကေနေသာ္လည္းေကာင္း၊ property ေတြကေနတဆင့္ေသာ္လည္းေကာင္း၊ အသံုးျပဳနိုင္ဖို႔အတြက္ စီမံေပးျခင္းပဲ ျဖစ္ပါတယ္။ ကြၽန္ေတာ္တို႔ C# မွာေတာ့ member data ေတြကို ကိုယ္စားျပဳဖို႔အတြက္ property ေတြကိုသံုးေလ့ရွိပါတယ္။ ဒီလိုမ်ိဳးပါ..

class Student : People
{
    	int Roll;
    	int Class;
	public int RollNo
	{
		get
		{
			return Roll;
		}
		set
		{
			Roll = value;
		}
	}
	public int ClassID
	{
		get
		{
			return Class;
		}
		set
		{
			Class = value;
		}
	}
}

Hello there!

Just to let you know about one of Tufcoat’s latest projects.
Tufcoat shrink-to-fit scaffolding covers are being used to protect the Holburne Museum of Art in Bath during its refurbishment and extension. The building work should be going on for another two years and will restore the building to its former glory.

If you have a project needing encapsulation, please give us a call on 01752 227 333 and we’ll find a solution for you.

www.scaffoldwrap.com

Today was my first good day of being lived by Fernando.  I’m not sure what it is.  The company?  The light at the end of the tunnel?  Or the inevitable resignation to the week which comes, each week, by Monday?  Anyway, friends, it was good.  Or good enough.

I woke up early, as usual, but had to 1. stay in bed until 10:40 (up late with Jess [P] I didn’t make it to bed until 2:40 last night).  I find when I’m confined to bed until a particular hour, I experience a much greater sense of impotence than I did when “paralysed” & confined to a wheelchair, as in Week 6.  I tossed & turned, & read some of the Nicholson Baker book I picked up recently.

Then arose.  Did some light housework while Jess was in the shower & then made some tea for her (hot 2. water for me) & chatted before she left for lunch.

Jess, artfully backlit.

As she prepared to leave, I 3. prepared my breakfast of oatmeal.  By now you know the drill.  I 4. added some blueberries as it was cooking & then 5. sweetened the whole mess with honey.  Said my goodbyes to Jess & got on the phone with a future participant (not to give too much away, but it involves a vineyard!).

Meanwhile, Bella finished my mostly uneaten oatmeal.

Mairzy doats & dozy doats

Then I waited… & waited… & waited for Braden to arrive so we could 6. watch La jetée/Sans soleil.

Just as I gave up & started the movie(s) he arrived.  We had a grand old time with the films.

They seemed a little dull at first & throughout. I eventually liked the first one very much.  The second one made me awfully sleepy, & there was a particularly horrible moment in which I had to watch a dying giraffe with spurts of blood coming out of the gunshot wounds on either side of its neck.  That woke me up a little.

By the time the second film ended (& it seemed interminably long) I realized that the movie was not boring, exactly.  Rather, it so closely approximated a dream state that it was impossible not to feel very sleepy as it was going on.  I can’t say I exactly enjoyed watching it, but after it was over I felt I was in a heightened state of consciousness.  I’ve never seen a film quite like it before.  Nor a film quite like the other one (composed almost entirely of still snapshots & a voiceover).  Each worked within an entirely unfamiliar genre & I was certainly improved by watching them.  It’s hard to explain, though I’m sure I could do it if I wasn’t so tired right now.  If you’re curious, I recommend that you watch them for yourselves.

Bella & Braden fell into deep post-Sans soleil slumber.

I 7. Read the booklet that came with the DVD.  I liked it much better than the other one.  There was a short interview with Chris Marker (the director) & I appreciated his refreshing snarkiness.

Woke up Braden, & began my long 8. walk to the 7-11.  Then we sat in a park, where I was to 9. Write whatever came to mind. Prompted by Sans soleil, I decided to write a list of the first 10 things I saw which “quickened the heart.” I would have liked to take corresponding photographs, as it seemed only right, but I’d left my phone at home, sadly.  Here’s the list.

1. glint of bearded man’s septum piercing
2. pigeon coasting on an updraft
3. brown water moving over green tile inset in stone moat of fountain
4. tree with a knot in it, small manageable size
5. congregation of pigeons bathing on ledge of fountain
6. skull patch on arm of sweatshirt belonging to 1. as he leaves park
7. my shoelaces are still too long (I always appreciate this extravagance on part of designer)
8. shadows of pigeons on blue, sky-colored wall
9. long ears of Wiemaraner disappearing behind wall of red flowers, smoke coming out of owner’s nostrils
10. airplane noise? passing train? buses.  like movement of wind over mouth of cave/breath over neck of a bottle

So there, I’ve 10. posted what I wrote.

Then I went home, where I prepared my 11. no-carb lunch.  It’s an exciting new take on cucumber sandwiches.  I cut open a cucumber & scraped the seeds out, then put a can of tuna in the middle.  With some seasoning & mayonnaise for good measure, of course.

Curiouser. & curiouser.

I ate this bizarre concoction.  I 12. took my time, enjoyed it.

Then, after some more Nicholson Baker, I read a random page from 13. Luis Cernuda’s Written in Water. The poem was “Time.”  The final paragraph of the poem reads:

There, in the absolute silence of summer, underscored by the murmuring water, my eyes open to the clear half-darkness that heightens the mysterious life of things, I saw how time can hold still, suspended in air, like the cloud that conceals a god, pure and weightless, never passing.

Quite appropriate.  It encapsulated the strange sensory experience I’d been having since the movies ended very nicely. Right down to the murmuring water.

I went about my chores.

Then I finished my (somewhat pornographic) Nicholson Baker book on the couch.  As soon as I was done, I had a call from TD.  He was outside!  He’d finally arrived!  I took out the garbage & then joyfully went to greet him.

After I got dressed in normal clothing, we went for a 14. walk.  Where did we walk?  To 15. dinner.  It was delicious, if carb-less.  He consumed the entire contents of the breadbasket.  Good.  It was otherwise too tempting to me.  We got some oysters & he had some chowder & I had some steamed clams.  I would’ve taken a picture but I’d forgotten my phone again.

Upon returning home, TD took the dog for her nightly constitutional & I sat down to 16. write for an hour.  Here you see the result of that writing.

Tomorrow we have a very busy day.  Not only do I have to accomplish all of my directives for Day 7, I also have to run some errands, rent a car, & ferry over to Galiano Island, where a family friend has graciously agreed to lend me a house for the first few days of Week 8.  Quite excited.  Next week we will witness a new strain of vicarious living, perhaps more true to the intentions of the project.  It’s being choreographed by a certifiable stranger (only the second true stranger we’ve seen).

All I have left to do is 17. abstain from use of electronic devices in the hour before bed & 18. go to bed at 2:20am.  I’m at this point so well-versed in Week 7 that I have the whole schedule down by memory.  Staying up late will be hard to do– I have almost three empty hours looming before me, along with a house guest who will certainly be asleep well before 2:20am.

I suppose I will occupy myself by responding to comments, handing out a gold star, & maybe picking up another book to read before turning in.

Oh, the fun of it.

For the first time this year Tufcoat are exhibiting at the Interbuild show, 18 – 21 October 2009.

This is the trade show for the Construction industry and we’ll be there to showcase Scaffwrap, the construction grade flame retardant heat shrinkable cladding.
You’ll find us in Hall 5, stand C31 at the NEC in Birmingham.

We have tickets for you to come and visit us, so feel free to give us a shout on 01752 227 333 or send us a line info at tufcoat dot co dot uk.

As part of a £4million programme to revitalise Tower Bridge, 1,500 tonnes of expendable abrasive is being used to blast Tower Bridge back to its metal framework  before 22,000 litres of paint is used to restore the traditional blue and white colour which dates back to 1894. Tufcoat Scaffwrap has been chosen to encapsulate this internationally recognised landmarks to catch old paintwork as it falls, protecting Thames river life.

Scaffwrap is a durable cladding which is heat shrunk to create a continuously bonded skin over the roof and sides of scaffold structures without the holes or gaps typical of traditional cladding systems such as ‘Monarflex’ and ‘CI sheets’. Scaffwrap is recommended for projects where high level of environmental containment or weather protection is required.

By creating a ‘drum tight’ and tear resistant covering, Scaffwrap is able to stand up to the most severe weather conditions, eliminating the problem of detached sheets and emergency repairs. Should it be necessary to gain access through the plastic shrink wrap scaffold sheeting, i.e. for craneage, Scaffwrap can be cut open and re-sealed to maintain 100% containment.

Tufcoat supply Scaffwrap and training direct to the construction industry. Alternatively, installation services may be provided by approved installers. Tufcoat are an ISO9001 accredited company and NASC members. Training courses are approved by the CITB.

For further details see www.scaffoldwrap.com.

Java reflection is a very powerful framework.

Sometimes its power seems outside the usual Java methodology.

For example, I needed to manually change a private variable in one of the classes I was testing.

Java reflection has an API that allows this. Of course, the API does not know if one is in a test or production source code. It works anywhere!

Below is an example of three classes.

• IntWrapper is the class under question.
• IntWrapperTest is the JUnit class
• RegularMainClass is a class with a main method, almost a copy of IntWrapperTest.

It is worth noting that the testers and the testee are in separate packages. So one can change the private variable or call a private method of any class in any package!

package com.otherexample;

public class IntWrapper {

	private int i;

	public IntWrapper(int i) {
		this.i = i;
	}

	private void incrementI() {
		i++;
	}

	public int getI() {
		return i;
	}

}

package com.example;

import java.lang.reflect.Field;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;

import org.junit.Test;

import com.otherexample.IntWrapper;

import static org.junit.Assert.*;

public class IntWrapperTest {

	@Test
	public void testPrivateMembers() {
		try {
			IntWrapper iw = new IntWrapper( 15 );
			assertEquals(15, iw.getI() );
			Field f = iw.getClass().getDeclaredField("i");

			f.setAccessible(true);
			f.setInt(iw, 18);
			assertEquals(18, iw.getI() );

			Method m = iw.getClass().getDeclaredMethod("incrementI");
			m.setAccessible(true);
			m.invoke(iw);
			assertEquals(19, iw.getI() );
		} catch (SecurityException e) {
			e.printStackTrace();
		} catch (NoSuchFieldException e) {
			e.printStackTrace();
		} catch (IllegalArgumentException e) {
			e.printStackTrace();
		} catch (IllegalAccessException e) {
			e.printStackTrace();
		} catch (NoSuchMethodException e) {
			e.printStackTrace();
		} catch (InvocationTargetException e) {
			e.printStackTrace();
		}
	}

}

package com.example;

import java.lang.reflect.Field;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;

import com.otherexample.IntWrapper;

public class RegularMainClass {

	public static void main(String[] args) {
		try {
			IntWrapper iw = new IntWrapper( 15 );
			if( 15 != iw.getI() ) System.err.println("Assertion failed");
			else System.out.println("all is well 1");
			Field f = iw.getClass().getDeclaredField("i");

			f.setAccessible(true);
			f.setInt(iw, 18);
			if( 18 != iw.getI() ) System.err.println("Assertion failed");
			else System.out.println("all is well 2");

			Method m = iw.getClass().getDeclaredMethod("incrementI");
			m.setAccessible(true);
			m.invoke(iw);
			if( 19 != iw.getI() ) System.err.println("Assertion failed");
			else System.out.println("all is well 3");

		} catch (SecurityException e) {
			e.printStackTrace();
		} catch (NoSuchFieldException e) {
			e.printStackTrace();
		} catch (IllegalArgumentException e) {
			e.printStackTrace();
		} catch (IllegalAccessException e) {
			e.printStackTrace();
		} catch (NoSuchMethodException e) {
			e.printStackTrace();
		} catch (InvocationTargetException e) {
			e.printStackTrace();
		}
	}

}

Probiotic dietary supplements need to contain LIVE microorganisms to be able to deliver the presently expected benefits which include not only the ability to improve the patient’s intestinal microbial balance which can inhibit harmful bacterial growth, and stop toxin producing bacteria, but also the potential abilities to prevent pathogen caused diarrhea, atopic diseases, and to stop chronic intestinal inflammatory diseases.  Micrencapsulation within a nonanimal derived shell offers a means to ensure that the bifidobacteria or lactic acid bacteria remain active and alive during the necessary shelf life and delivery of a normal consumer product.  Micrencapsulation needs to be completed with minimal heat history and low stress as far as sheer.  This is possible with vibrational dripping technologies which allow seamless microcapsules to be formed holding the necessary amounts of live bacteria, yeasts and bacilli for effectiveness.  The microencapsulate shell can also be made to provide the correct release profile so that the live microorganisms reach their intended destination in our bodies to be beneficial.

This is my first post. This article won’t be the definitive guide of Object oriented Programming System an entire book could easily be devoted to that. Instead, think of this as a good place to start. Good for those how had already know about OOPS. If you get sometime wrong / new please comment me.

Basics of Object Oriented Programming System

What is Opps?
Oops is a problem solving technique.

What is Class?
Class is a description of an Object.

What is an Object?
An Object is an entity that has attribute, behavior and identity of a class.

What is the relation between Class and Object?
Class is the defection, while Object is an instance of the Class created.

What is Encapsulation?
Encapsulation is the localization or hiding of information and processes within an object. Because objects encapsulate both data and processes, the user of an object can view the object as a black box that provides services. Instance variables and methods can be added, deleted, or changed, but as long as the services provided by the object remain the same, code that uses the object can continue to use it without being rewritten.

public class TestMain
{
    private string _Name = string.Empty;

    public string Name
    {
        get
        {
            return _Name;
        }
        set
        {
            _Name = value;
        }
    }
}

Like the above way we can protect the private data from the outside world. In the above example we can’t access the private data Name from an object instance. We manipulate the data only using the property.

What is Polymorphism?
Through inheritance, a class can be used as more than one type; it can be used as its own type, any base types, or any interface type if it implements interfaces. This is called polymorphism. In C#, every type is polymorphic. Types can be used as their own type or as an object instance, because any type automatically treats Object as a base type.

public class BaseClass

{

    public virtual void DoWork() { }

    public virtual int WorkProperty

    {

        get { return 0; }

    }

}

public class DerivedClass : BaseClass

{

    public override void DoWork() { }

    public override int WorkProperty

    {

        get { return 0; }

    }

}

DerivedClass B = new DerivedClass();

B.DoWork();  // Calls the new method.

BaseClass A = (BaseClass)B;

A.DoWork();  // Also calls the new method.

What is Access Modifiers?
Access modifiers are keywords used to specify the declared accessibility of a member or a type. They are …….

1. Public
2. Private
3. Protected
4. Internal
5. Protected Internal.

Public: All members have access in the classes.
Private: Only members of class have access.
Protected: All members in current class and in derived class can access the variables.
Internal: Only members in current project have access to the element.
Protected Internal: All members of the current project and all members in derived class can access the variables.

What is Properties?
Properties are members that provide a flexible mechanism to read, write, or compute the values of private fields.

Public Int32 ID
    {
        get { return _ID;  }
        set { _ID = value; }
    }

Read Only Property

Public Int32 ID
    {
        get { return _ID;  }
    }
Write Only Property

Public Int32 ID
    {
        set { _ID = value; }
    }

What is Implementation Inheritance?
When a class is derived from another class such that it inherits all the members of the base type it is Implementation Inheritance.

What is Interface Inheritance?
When a type (class or a structure) inherits only the signatures of the functions from another type it is Interface Inheritance.

What is Abstract class?
Abstract classes are classes that contain one or more abstract methods. An abstract method is a method that is declared, but doesn’t contain implementation. Abstract classes can’t be instantiated, and require subclasses to provide implementations for the abstract methods. This class must be inherited. This class is mostly used as a base class.

Abstract Class

public abstract class TestAbstract
{
    public abstract int AddNumber(int One, int two);

    public virtual int AddTwoNumber(int One, int two)
    {
        int Result = One + two;
        return Result;
    }
}

Child Class

public class TestMain:TestAbstract
{
    public override int AddNumber(int One, int two)
    {
        int Result = One + two;
        return Result;
    }

    public override int AddTwoNumber(int One, int two)
    {
        int Result = One +two;
        return Result;
    }

}

What is Virtual function?
A virtual function is a function whose behavior can be overridden within an inheriting class by a function with the same signature. A base class must provide the virtual modifier for any virtual method, and derived classes must provide the override modifier for any override method inherited from a base class.
Virtual methods allow subclasses to provide their own implementation of that method using the override keyword.

What is Abstract  function?
Abstract functions in a class contain no method body, and are implicitly virtual function. Abstract function-modifier exists only to provide a uniform syntactical style.

Neither abstract nor virtual can be declared private, since it would defeat the purpose, and subclasses must override them using the same method signature. If a class has any abstract methods, then it must tag itself as abstract, and no instances of it can be created.

What is Interface?
An interface is a reference type containing only abstract members. These can be events, indexers, methods or properties, but only the member declarations. A class implementing an interface must provide the implementation of the interface members. An interface cannot contain constants, constructors, data fields, destructors, static members or other interfaces. Interface member declarations are implicitly public.

Interface
public interface TestInterface
{
    Int32 ID
    {
        get;
        set;
    }

    String Name
    {
        get;
        set;
    }

    string Address
    {
        get;
        set;
    }

    bool Add();

    bool Update();

    bool Delete();
}

Class
public class Employee : TestInterface
{
    public int ID
    {
        get
        {
            //Implement………
        }
        set
        {
            //Implement………
        }
    }

    public string Name
    {
        get
        {
            //Implement………
        }
        set
        {
            //Implement………
        }
    }

    public string Address
    {
        get
        {
            //Implement………
        }
        set
        {
            //Implement………
        }
    }

    public bool Add()
    {
        //Implement………
    }

    public bool Update()
    {
        //Implement………
    }

    public bool Delete()
    {
        //Implement………
    }
}

When a class or structure is said to inherit an interface, it means that the class or structure provides an implementation for all of the members defined by the interface. The interface itself provides no functionality that a class or structure can inherit in the way that base class functionality can be inherited. However, if a base class implements an interface, the derived class inherits that implementation. A class or structure can inherit more than one interface. When a class or structure inherits an interface, it inherits only the method names and signatures, because the interface itself contains no implementations.

Interface versus Abstract Class.
 
An Interface cannot implement methods.
An abstract class can implement methods.
An Interface can only inherit from another Interface.
An abstract class can inherit from a class and one or more interfaces.
An Interface cannot contain fields.
An abstract class can contain fields.
An Interface can contain property definitions.
An abstract class can implement a property.
An Interface cannot contain constructors or destructors.
An abstract class can contain constructors or destructors.
An Interface can be inherited from by structures.
An abstract class cannot be inherited from by structures.
An Interface can support multiple inheritances.
An abstract class cannot support multiple inheritances.

What is Sealed Class?
A sealed class cannot be used as a base class. For this reason, it cannot also be an abstract class. Sealed classes prevent derivation.

What is Sealed Methods?
A class member, method, field, property, or event, on a derived class that is overriding a virtual member of the base class can declare that member as sealed. This negates the virtual aspect of the member for any further derived class. This is accomplished by putting the sealed keyword before the override keyword in the class member declaration.

public sealed override int AddTwoNumber(int One, int two)
    {
        int Result = One +two;
        return Result;
    }

What is Function Overloading?
Function overloading is the practice of declaring the same function with different signatures. The same function name will be used with different number of parameters and parameters of different type. But overloading of functions with different return types is not allowed.

public Int32 AddTwoNumber(Int16 One, Int16 Two)

public Int32 AddTwoNumber(Int32 One, Int32 Two)

What is function overriding?
If a base class is declared as virtual and derived class is declared as virtual. This redefinition of virtual in derived class is known as Function overriding. Both functions have same parameters.

public virtual int AddNumber(int One, int two)

public override int AddNumber(int One, int two)

What is Class Constructor?
A constructor is a special function which can be included in a class. It is unusual as a function because it is never specifically called, the same way that other functions are. A constructor function is called automatically when the class variable is declared. It is used to set up the class variable with sensible values in the member variables. There is more then one Constructor in a class within a class with different parameters.

public Class ABC
{
public ABC()
{
//Implement………

}
public ABC(string xyz)
{
                        //Implement………
}
}

What is Class Destructor?
Destructor is a special function that is called whenever a class variable is destroyed. A destructor is declared as having the same name as the function, except that the name is preceded by the ~ symbol before it. Apart from that symbol, the declaration of a destructor would be indistinguishable from a constructor. There is always one destructor in a class.

public Class ABC
{
public ABC()
{
//Implement………

}
public ~ABC()
{
                        //Implement………
}
}

What is Delegate?
A delegate is a function pointer. A delegate allows encapsulating a reference to a method inside a delegate object. The delegate object can then be passed to code which can call the referenced method, without having to know at compile time which method will be invoked. Delegates are multicasting which means that they can point to more than one function at a time.

What is Event?
An event is a mechanism via which a class can notify its clients when something happens. For example when you click a button, a button-click-event notification is sent to the hosting the button. Events are declared using delegates.

What is Generic Class?
Generic classes encapsulate operations that are not specific to a particular data type. The most common use for generic classes is with collections like linked lists, hash tables, stacks, queues, trees, and so on. Operations such as adding and removing items from the collection are performed in basically the same way regardless of the type of data being stored.

• All properties must be declared and be preceded by one of the visibility keywords: public, protected, or private. (As with every rule, there is one exception when the visibility keyword is optional.)
• Using a visibility keyword is optional when defining a method, but is recommended. If no keyword is used, the method is automatically treated as public.
• “Method” is simply OOP (Object-Oriented Programming) terminology for a function inside a class. Use the function keyword when defining a method.
• Use the new keyword to create an instance of a class (an object).
• The $this variable inside a class refers to the current object.
• Use the -> operator to access an object’s methods or properties (there is no space between – & >).
• When accessing a property with the -> operator, omit the $ sign.
• Attempting to access a protected or private property or method from an external script triggers a fatal error.
• Use getter and setter methods to access protected and private properties and methods from an external script.

Source: “PHP Object-Oriented Solutions” by David Powers. A definite reference material to keep side by side with your famous “Gang of Four” book (What? You don’t own it?)

There’s only one thing that bothers me a bit. It says PHP triggers a fatal error when trying to access any private or protected properties from an external script. Does only trying to access them from an external script trigger error? Isn’t it that anything outside the class (in the same script) trying to access protected or private property triggers a fatal error?

Encapsulation is often needed to protect the activity of a compound whether it is for a pharmaceutical that needs to be delivered to the lower gut without being destroyed or it is an additive for a detergent which has to be protected from the detergent until it is in the washing machine.  Many problems are solved each year by encapsulation, but visual appeal is also an advantage of this problem solving approach.  Those same solid spheres or liquid filled spherical capsules add consumer appeal to body washes, toothpastes, and shampoos while they deliver product performance improvements.  There are nearly as many different shell materials which are used to make encapsulates as there are active compounds needing to be encapsulated, and often the best one is found only through working with companies who have successes in multiple industries.  What works in industrial chemicals may have applicability to pharmaceuticals;  what has been found effective for pharmaceuticals may be just the right solution for agricultural chemicals.  It is a fascinating area in which to work because it is effective  for so many applications.

Have you ever found the need to hide data inside a namespace in C++.

That isn’t possible since scope attributes are not valid inside namespaces.

Here is an example of how this should have been done in my opinion:
namespace foo
{
private:
int baz;
public:
class bar;
}

This of course provides an error since such thing doesn’t exist in C++.

There are many ways to solve this problem.

1) Using the class keyword instead of the namespace keyword:
class foo
{
private:
int baz;
public:
class bar;
}

While it works it is unclear that class foo is actually a namespace.

Also a class can’t be declared on multiple files so it doesn’t really solve our problem.

Using an unnamed namespace is better in this case.

2) Creating a private namespace:
namespace foo
{
namespace PrivateData
{
int baz;
}
class bar;
}

While this is clearer it still provides access to the private namespace. The boost library uses this approach. They call their private namesapces details

3) There is a third way. One can use a static class where all of the fields are protected and inherit that class.



namespace foo
{
class PrivateData
{
public:
PrivateData &operator=() = delete;
PrivateData() = delete;
protected:
static int baz;
};
class foo : public PrivateData
{
public:
foo(int value)
{
baz += value * 5 + 2;
}
};
int PrivateData::baz = 0;
}



This is a bit clearer and it also hides the data inside a class. Any class that doesn’t inherit from PrivateData won’t have access to the private data of the namespace. Logically no one outside of the class will inherit from it. This is possible but the trick is that it creates external coupling. Inheritence is the thightest coupling possible after freindship. This is costly.
Inside the namespace we create internal coupling but internal coupling is no coupling at all since we already know the namespace. External coupling creates depeandecies.
But this code seems to me too verbose and redundant.
I don’t really think that I’d use this method.

I’d like to hear more suggestions

I’m one of those programmers who HATES it when he sees things like:

public class Grunt
{
  private int m_hp ;

  public int HP
  {
    get
    {
      return m_hp ;
    }
    set
    {
      m_hp = value ;
    }
  }
}

Encapsulation or no encapsulation, this just SEEMS dumb.

Sometimes you’ll see this written as:

public class Grunt
{
  private int m_hp ;

  public int HP
  {
    get { return m_hp ; }
    set { m_hp = value ; }
  }
}

Which further proves my point: You can compress code like that when its not meant to be looked at.

The point is, THERE IS NO POINT in having pass-thru getters/setters like this.

In languages other than C#, you’ll see people using functions of course instead of C# properties.

class Grunt
{
private:
  int m_hp ;

public:
  void ChangeHp( int toVal )
  {
    m_hp = toVal ;
  }

  int Hp()
  {
    return m_hp ;
  }
} ;

VERSUS:

class Grunt
{
public:
  int hp ;
} ;

Isn’t there a very slight performance hit for writing code that always uses methods? Yes. ++points for public members.

HOWEVER. Recently I have thought of ONE major benefit to this “methods only/no public members” style that I never really credited to the style before.

Readability.

Think of client code using the Grunt class:

Grunt g ;

if( g.Hp() > 10 )
{
  g.ChangeHp( 12 ) ;
}

VERSUS:

Grunt g ;

if( g.hp > 10 )
{
  g.hp = 12 ;
}

What reads better? g.ChangeHp( 12 ) or g.hp = 12?

Really, g.hp = 12 ; LOOKS more cryptic because even though you know what its doing if you think about it for a fraction of a second, (changing hp to 12), for the method way g.ChangeHp(12) you CANNOT READ IT without knowing exactly what it does like, even faster than the one with the =.

SO. Maybe all private members and all accessor methods aren’t such a bad idea after all.

Most of people consider encapsulation feature of object oriented programming as data hiding. But Encapsulation stands for few more features. Suppose we have a Vehicle registration software. Which has following properties,

• Vehicle has a engine/chesis number
• Vehicle may have door
• Vehicle have wheels
• Vehicle can be different type: Bus, Car, Bike

Suppose we have a Abstract Vehicle

Class public abstract class Vahicle {
public abstract String getChesisNumber();
public int getNumberOfDoor() {}
public abstract int getNumberOfWheel();
}

Now Bus, Car, Bike extend Vehicle

public abstract class Bus extends Vehicle {
public int getNumberOfDoor() {}
}public abstract class Car extends Vehicle
{
public int getNumberOfDoor() {
return 4;
}
public abstract class Bike extends Vehicle { }

Now a Car can be a Private car or Taxi so

public PrivateCar extends Car {
public String getChesisNumber() {
return "CN354656565";
}
public int getNumberOfWheel(){
return 4;
}
}


Suppose we have a special type of Air Conditioned Taxi named ClassicTaxi

public ClassicTaxi {
public String getEngineNumber(){
return "CN35465655498";
}
public int getTotalNumberOfWheel(){
return 4;
}
}

Only the Taxi know about this

public Taxi extends Car {
private ClassicTaxi ct;
public String getChesisNumber(){
return ct.getEngineNumber();
}
public int getNumberOfWheel(){
return ct.getTotalNumberOfWheel();
}

Now you can notice the different levels of Encapsulation in this example.

1. Encapsulation of Data: Bus, Bike and PrivateCar and Taxi are encapsulation from everything
2. Encapsulation of Type: Client of Vehicle do not know about Bus, Car and Bike
3. Encapsulation of Method: getNumberOfDoor() of Bus and Car are hidden from all
4. Encapsulation of Object: Only Taxi is aware abot Classic Taxi

So as we can see. Its not only bounded to the hiding data but also hiding type, method as well as object too. There is land mark theory described in the book of Gang of Four(GOF) “Consider what should be variable in your design. This approach is the opposite of focusing on the causes of redesign. Instead of considering what might force a change to a design, consider what you want to be able to change without redesign. The focus here is on encapsulating the concept that varies, a theme of many design patterns.”(Ref 1) The Book of Shalloway define this simply as “Find what varies and encapsulate it.” (Ref 2).

References:

1. Design Pattern: Elements of Reusable Object-Oriented Software
2. Design Pattern Explained: A new perspective on Object Oriented Design

By: Md. Shahjalal

The development of a controlled release product to fulfill your
specific requirements should always be done with the consideration
that the formulation development efforts must be scalable.  Scalability must
consider not only whether it is possible but also whether it is
economical.  Formulation development carried out with the above
ultimate requirements will have a much greater likelihood of  producing a successful product.  For microsphere or micrencapsulate formulations, vibrational laminar flow drip forming is one example of a straight forward scalable technology working from grams to thousands of litres per hour and has been employed in pharmaceutical, nutraceutical, cosmetic, consumer care, catalyst, PV, agricultural, and other industries such as the food and ceramic and gas and oil drilling for sustained release.  It is not the only method to form controlled release spheres.  For very high active loading levels, the process of low pressure extrusion followed by spheronization has lead to very successful formulations and products.  These are each very empirical technologies where theoretical sophistication as well as hands on experience will all contribute positively to your new controlled release product development and production.