Do TP take more quiries??

[Xarcell]

Object Oriented programming does nothing but strain the server and and causes bloated software. It's only good to use with multiple developers on a single project.

Who wants all that extra overhead?

[JPDeni]

I still don't understand how it doesn't use any queries. It doesn't use or access any database tables at all?

[feline]

This you have to explain..are you using OOP just to able to locate functions by line number in the PortaMX source code..?

Do you want a serious discussion about the advantages and disadvantages of OOP and the different result between OO programming and procedural programming? Ok, then start a call.
But do not pretend that we use code from TinyPortal. The thought is just ridiculous ...

Fel

[feline]

Object Oriented programming does nothing but strain the server and and causes bloated software. It's only good to use with multiple developers on a single project.

You know the difference between OO Programming and procedural programming?
You know what's is a class, constructor, inheritance, method overload and much more?
If not, then go to Wikipedia and read a little bit ...

Feline

[Swampy]

No quiries allowed!  Only straight thinkers please! We all ready got our fair share of warped minds, including mine! 

[Xarcell]

Object Oriented programming does nothing but strain the server and and causes bloated software. It's only good to use with multiple developers on a single project.

You know the difference between OO Programming and procedural programming?
You know what's is a class, constructor, inheritance, method overload and much more?
If not, then go to Wikipedia and read a little bit ...

Feline

I did genius...

I've already studies on a bit and had a look at your code awhile back. I'm not saying you used lines of code from TP. I'm saying you "borrowed" or downright stole several concepts from TP.

It really pisses me off hearing you talk about it over at SMF saying it was all your concept. Yes, you programmed your software yourself, but your engine design was based on TP. I remember your early stages of software when you did have lines of TP code in there. But then you switched to OOP programming, which is good, at least there is some variety our there for members.

I'm not bashing PortaMx, it's good software. I just get upset hearing you mislead people into thinking it's so much better than everything else out there just because it's written in OOP. Especially when you say it doesn't even use any queries.

Anyway, ...

But back to OOP... Anyone here can use GOOGLE to do a search on "pros & cons of OOP programming". They don't need to take my word on it, and they don't have to take your word on it. They can see for themselves, but don't come here and mislead our members.

Personally, I don't see OOP programming being all that beneficial at all when used with SMF, just because of the way SMF was designed. It's unnecessary. Now if SMF was designed on OOP programming, then you could see PortaMx being very beneficial. Although since SMF is not, I don't see the added benefit as you brag that it does. I see bloated software that doesn't really offer alot of features considering how much code is there. Again, anyone can crack open PortaMx and take a look for themselves, as I have.

I'm not going to go into a debate with you on this. I'm just letting members know that they can do a search on OOP Pros & Cons and read some unbiased material.

Members here can also do some research or ask other developers. Any software that uses a Database has to have queries. Period. I do agree with the fact that PortaMx uses less queries than TP because some of it's material get's cached. However, as already mentioned, Bloc will address that (better) in Beta 6. Comparing the 2 portal softwares now, you can imagine how much better TP will be by Beta 6. I don't want to mention the wonderful ideas he has up his sleeve for this here, as I would rather point it out at a later time how you "borrowed" concepts again after PortaMx gets mysteriously updated after TP Beta 6 release.

What I'm saying that when that time comes, I'll wager those concepts used in Beta 6 will most likely pop-up in PortaMx, and other portals as well. As it usually does. Dream Portal is the only other portal that has come up with original ideas, so I respect them for it, and even support them. I'm all for competitiveness, because then everyone wins. I don't respect people who mislead SMF user's who don't know any better.

Your welcome to browse our boards and interact with our members. But don't troll here, it's not nice.

I leave it in the hands of our members to research further, and come to there own conclusion. I'll be helping Bloc bounce ideas around so that we can offer a great product to our members. I will not reply to this topic again. Good day to you.

[Swampy]

I am no programmer but I have been around since dos 2.2 and being totally fair about this, how would it be the least bit possible to build a portal for smf without appearing to have copied concepts from other portals.

It is like saying build a browser but have no concepts from firefox or explorer.  I somehow think that would be impossible.

Just my two cents worth.

:angel:

[bloc]

This you have to explain..are you using OOP just to able to locate functions by line number in the PortaMX source code..?

Do you want a serious discussion about the advantages and disadvantages of OOP and the different result between OO programming and procedural programming? Ok, then start a call.
But do not pretend that we use code from TinyPortal. The thought is just ridiculous ...

Fel

Hm. I am not sure its language barrier or if you are just out to pick a fight..but nevertheless: based on what you said I understood it as you meant lines could be found by numbers (..) ...but I now see you prob. meant one could find code from TP in PortaMX..or rather it CANNOT be found. Anyway, thats unnecessary to point out, its quite obvious that they are very different.

But back to the original statement: that PortaMX have fewer queries and would put less strain on the server, thats of course true...but the reason for it isn't HOW you programmed the caching routines - but the caching in itself. TP hasn't any kind of caching right now, but it doesn't have to be programmed using OOP.  It would seem you meant it was.

[feline]

But back to the original statement: that PortaMX have fewer queries and would put less strain on the server, thats of course true...but the reason for it isn't HOW you programmed the caching routines - but the caching in itself. TP hasn't any kind of caching right now, but it doesn't have to be programmed using OOP.  It would seem you meant it was.

The caching itself and OOP have no common point. We use us own caching routines .. they are fast and optimized for our portal. But the cache trigger(new post, read post etc.) are handled in the block constructor ..

Fel